Re: [android-developers] Re: log disappears
tanx for command line tip ;) 2011/9/8 Indicator Veritatis mej1...@yahoo.com: A common reason for its disappearance is that Eclipse somehow lost track of which device it is supposed to be connected to. Clock on the little 'Device' icon in the DDMS perspective to make it come back. But this irritating disappearing trick, and a few other inconveniences, is why for serious debugging, I do not rely on the DDMS perspective: I open a terminal window (yes, I run Eclipse under Linux) and use a command line such as adb logcat or even adb logcat tee | logcatout.txt to keep a copy for handy searching later. Sometimes even this fails, but then stopping and restarting adb almost always fixes it. On Sep 8, 12:08 pm, Rafael Maas rafaelm...@gmail.com wrote: same thing happens here :( 2011/9/8 bob b...@coolgroups.com: Anyone know why sometimes the log disappears in the Eclipse log window? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: log disappears
A common reason for its disappearance is that Eclipse somehow lost track of which device it is supposed to be connected to. Clock on the little 'Device' icon in the DDMS perspective to make it come back. But this irritating disappearing trick, and a few other inconveniences, is why for serious debugging, I do not rely on the DDMS perspective: I open a terminal window (yes, I run Eclipse under Linux) and use a command line such as adb logcat or even adb logcat tee | logcatout.txt to keep a copy for handy searching later. Sometimes even this fails, but then stopping and restarting adb almost always fixes it. On Sep 8, 12:08 pm, Rafael Maas rafaelm...@gmail.com wrote: same thing happens here :( 2011/9/8 bob b...@coolgroups.com: Anyone know why sometimes the log disappears in the Eclipse log window? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log file on device
okay. so.. -d mean we dump everything in one shot to log.txt? thank's for the really helpful info! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Log file on device
On Tue, Jun 28, 2011 at 6:04 PM, EdwardComb dzn.aie...@gmail.com wrote: okay. so.. -d mean we dump everything in one shot to log.txt? Yes. You can filter the output by specifying additional options to adb if you don't need everything. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log of my application
http://developer.android.com/guide/developing/tools/adb.html James -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Log of my application
Thanks 2011/6/8 James Ots james...@gmail.com http://developer.android.com/guide/developing/tools/adb.html James -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: LOg in form
Possibly in Your checklogininfo function if (password-set email-
set) should have the logical and not
On Jun 3, 10:11 am, Knutsford Software i...@knutsford-
software.co.uk wrote:
I am doing my first login form
public class login extends Activity {
/** Called when the activity is first created. */
private EditText Email;
private EditText Password;
private Button btnLogin;
private Button btnCancel;
private TextView lblResult;
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
ImageView image = (ImageView) findViewById(R.id.logo);
Email = (EditText)findViewById(R.id.email);
Password = (EditText)findViewById(R.id.password);
btnLogin = (Button)findViewById(R.id.login_button);
btnCancel = (Button)findViewById(R.id.cancel_button);
lblResult = (TextView)findViewById(R.id.result);
if (checkLoginInfo()) {
String url = http://www.blablabla/index.php;;
Intent i = new Intent(Intent.ACTION_VIEW);
i.setData(Uri.parse(url));
startActivity(i);
}
btnLogin.setOnClickListener(new OnClickListener() {
public void onClick(View v) {
String email = Email.getText().toString();
String password = Password.getText().toString();
final SharedPreferences mPreferences;
mPreferences = getSharedPreferences(CurrentUser, MODE_PRIVATE);
if(email.equals(guest) password.equals(guest)){
SharedPreferences.Editor editor=mPreferences.edit();
editor.putString(Email, email);
editor.putString(PassWord, password);
editor.commit();
String url = http://www.blablabla/index.php;;
Intent i = new Intent(Intent.ACTION_VIEW);
i.setData(Uri.parse(url));
startActivity(i);
}
else {
SharedPreferences.Editor editor=mPreferences.edit();
editor.remove(Email);
editor.remove(PassWord);
editor.commit();
lblResult.setText(Login failed. Email address and/or password
doesn't exist.);
}}
});
btnCancel.setOnClickListener(new OnClickListener() {
public void onClick(View v) {
// Close the application
finish();
}});
}
private boolean checkLoginInfo() {
final SharedPreferences mPreferences;
mPreferences = getSharedPreferences(CurrentUser, MODE_PRIVATE);
boolean email_set = mPreferences.contains(Email);
boolean password_set = mPreferences.contains(PassWord);
if ( email_set password_set ) {
return true;
}
else {
return false;
}
}
}
When I click on the cancel button checkLoginInfo() returns true when you
next try the app which is correct. If however I log into the url then close
the browser then try the app again then I end up with the login form filled
in with the login details instead of going to the url. What have I missed out
please?
Thanks
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log every action/event to an external file
Hi there, Thank you for the feedback. I actually thought there was something to automatically log this information, I read some project (Microlog for Android) but I must have misunderstood. So basically what you're saying is that I'll have to log every piece of code that I actually want to a internal file and like this have posterior access to the information and I'll also be able to just log the valuable information that I need instead of everything that device might do, right? I'll dig on this, thank you very much for your time. P On Mar 12, 7:43 pm, TreKing treking...@gmail.com wrote: On Sat, Mar 12, 2011 at 11:52 AM, Pedro Teixeira pedroteixeir...@gmail.comwrote: I'd like to store events like pressing buttons but also store the location and orientation of the device while using my application as well as the time between this actions. Stuff like this you'd have to have your own code to read the device settings. If you're hoping for some automatic way to log all this information, I doubt you're going to find it. Is there any good approach for this? Was I clear or can I try and explain in another way? You are free to create and write to files on your own app's space (or even the SD card) for logging purposes. I have a log class that not only writes to the LogCat in debug mode but generates an internal log that I can send in bug reports if and when the app crashes on user devices. It has been *far* more useful than the generic stack traces in the developer console in resolving issues that crop up in the wild. You just have to be careful about logging only what's actually useful and keeping the log file size to something reasonable for a mobile device. --- -- TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log every action/event to an external file
There are examples for custom exception handlers that make the stack trace nicer to read and allow to save the result to SD card. Users can then decide if they want to help you and send you these files. Market has the option to show the raw stack traces but I found these insufficient for troubleshooting. On Mar 13, 7:28 am, Pedro Teixeira pedroteixeir...@gmail.com wrote: Hi there, Thank you for the feedback. I actually thought there was something to automatically log this information, I read some project (Microlog for Android) but I must have misunderstood. So basically what you're saying is that I'll have to log every piece of code that I actually want to a internal file and like this have posterior access to the information and I'll also be able to just log the valuable information that I need instead of everything that device might do, right? I'll dig on this, thank you very much for your time. P On Mar 12, 7:43 pm, TreKing treking...@gmail.com wrote: On Sat, Mar 12, 2011 at 11:52 AM, Pedro Teixeira pedroteixeir...@gmail.comwrote: I'd like to store events like pressing buttons but also store the location and orientation of the device while using my application as well as the time between this actions. Stuff like this you'd have to have your own code to read the device settings. If you're hoping for some automatic way to log all this information, I doubt you're going to find it. Is there any good approach for this? Was I clear or can I try and explain in another way? You are free to create and write to files on your own app's space (or even the SD card) for logging purposes. I have a log class that not only writes to the LogCat in debug mode but generates an internal log that I can send in bug reports if and when the app crashes on user devices. It has been *far* more useful than the generic stack traces in the developer console in resolving issues that crop up in the wild. You just have to be careful about logging only what's actually useful and keeping the log file size to something reasonable for a mobile device. --- -- TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log every action/event to an external file
This is a thesis project so I'm actually conducting the user testing on a singular device that I will have access to the information I need. That's a thing to consider then. Thanks for the feedback On Mar 13, 12:23 pm, lbendlin l...@bendlin.us wrote: There are examples for custom exception handlers that make the stack trace nicer to read and allow to save the result to SD card. Users can then decide if they want to help you and send you these files. Market has the option to show the raw stack traces but I found these insufficient for troubleshooting. On Mar 13, 7:28 am, Pedro Teixeira pedroteixeir...@gmail.com wrote: Hi there, Thank you for the feedback. I actually thought there was something to automatically log this information, I read some project (Microlog for Android) but I must have misunderstood. So basically what you're saying is that I'll have to log every piece of code that I actually want to a internal file and like this have posterior access to the information and I'll also be able to just log the valuable information that I need instead of everything that device might do, right? I'll dig on this, thank you very much for your time. P On Mar 12, 7:43 pm, TreKing treking...@gmail.com wrote: On Sat, Mar 12, 2011 at 11:52 AM, Pedro Teixeira pedroteixeir...@gmail.comwrote: I'd like to store events like pressing buttons but also store the location and orientation of the device while using my application as well as the time between this actions. Stuff like this you'd have to have your own code to read the device settings. If you're hoping for some automatic way to log all this information, I doubt you're going to find it. Is there any good approach for this? Was I clear or can I try and explain in another way? You are free to create and write to files on your own app's space (or even the SD card) for logging purposes. I have a log class that not only writes to the LogCat in debug mode but generates an internal log that I can send in bug reports if and when the app crashes on user devices. It has been *far* more useful than the generic stack traces in the developer console in resolving issues that crop up in the wild. You just have to be careful about logging only what's actually useful and keeping the log file size to something reasonable for a mobile device. --- -- TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log every action/event to an external file
I found a really helpufll class that helps me easilly to Log into a a .log file on the SDCARD and all I have to do is to call it whenever I need it during my application. You can actually almost creat a script of the user action. Thank you very much for your input that helped me finding this. P On Mar 13, 12:43 pm, Pedro Teixeira pedroteixeir...@gmail.com wrote: This is a thesis project so I'm actually conducting the user testing on a singular device that I will have access to the information I need. That's a thing to consider then. Thanks for the feedback On Mar 13, 12:23 pm, lbendlin l...@bendlin.us wrote: There are examples for custom exception handlers that make the stack trace nicer to read and allow to save the result to SD card. Users can then decide if they want to help you and send you these files. Market has the option to show the raw stack traces but I found these insufficient for troubleshooting. On Mar 13, 7:28 am, Pedro Teixeira pedroteixeir...@gmail.com wrote: Hi there, Thank you for the feedback. I actually thought there was something to automatically log this information, I read some project (Microlog for Android) but I must have misunderstood. So basically what you're saying is that I'll have to log every piece of code that I actually want to a internal file and like this have posterior access to the information and I'll also be able to just log the valuable information that I need instead of everything that device might do, right? I'll dig on this, thank you very much for your time. P On Mar 12, 7:43 pm, TreKing treking...@gmail.com wrote: On Sat, Mar 12, 2011 at 11:52 AM, Pedro Teixeira pedroteixeir...@gmail.comwrote: I'd like to store events like pressing buttons but also store the location and orientation of the device while using my application as well as the time between this actions. Stuff like this you'd have to have your own code to read the device settings. If you're hoping for some automatic way to log all this information, I doubt you're going to find it. Is there any good approach for this? Was I clear or can I try and explain in another way? You are free to create and write to files on your own app's space (or even the SD card) for logging purposes. I have a log class that not only writes to the LogCat in debug mode but generates an internal log that I can send in bug reports if and when the app crashes on user devices. It has been *far* more useful than the generic stack traces in the developer console in resolving issues that crop up in the wild. You just have to be careful about logging only what's actually useful and keeping the log file size to something reasonable for a mobile device. --- -- TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Log every action/event to an external file
On Sun, Mar 13, 2011 at 9:42 AM, Pedro Teixeira pedroteixeir...@gmail.comwrote: I found a really helpufll class that helps me easilly to Log into a a .log file on the SDCARD and all I have to do is to call it whenever I need it during my application. Er ... what did you find and where did you find it ? :-) - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log every action/event to an external file
I was thinking about that whole process some more, and in order to make it easier for users I thought I could immediately bring up the email chooser when the crash report is ready. But it looks like startActivity(Intent.createChooser(intent, Send crash report via:)); is not possible from within UncaughtExceptionHandler. Is there a way around that? Lutz On Mar 13, 1:48 pm, TreKing treking...@gmail.com wrote: On Sun, Mar 13, 2011 at 9:42 AM, Pedro Teixeira pedroteixeir...@gmail.comwrote: I found a really helpufll class that helps me easilly to Log into a a .log file on the SDCARD and all I have to do is to call it whenever I need it during my application. Er ... what did you find and where did you find it ? :-) - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Log every action/event to an external file
On Sun, Mar 13, 2011 at 9:28 PM, lbendlin l...@bendlin.us wrote: I was thinking about that whole process some more, and in order to make it easier for users I thought I could immediately bring up the email chooser when the crash report is ready. But it looks like startActivity(Intent.createChooser(intent, Send crash report via:)); is not possible from within UncaughtExceptionHandler. Is there a way around that? In the uncaught exception handler you can set a SharedPreference flag and check on main activity start. If it's set, the app crashed and you can do your thing. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log
Here are the logs, # reboot reboot C:\android-sdk-windows\toolsadb devices List of devices attached HT058HL00699device C:\android-sdk-windows\toolsadb shell # su su # mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system # cat /proc/mounts cat /proc/mounts rootfs / rootfs ro 0 0 tmpfs /dev tmpfs rw,mode=755 0 0 devpts /dev/pts devpts rw,mode=600 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0 none /dev/cpuctl cgroup rw,cpu 0 0 /dev/block/mtdblock4 /system yaffs2 rw 0 0 /dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0 /dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0 tmpfs /app-cache tmpfs rw,size=8192k 0 0 /dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gi 1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1 hortname=mixed,utf8,errors=remount-ro 0 0 # cd /sdcard/ cd /sdcard/ # ls -l ls -l d---rwxr-x system sdcard_rw 2010-04-09 15:38 HTC Sync d---rwxr-x system sdcard_rw 2010-04-09 15:39 Music d---rwxr-x system sdcard_rw 2010-04-09 15:39 Sample Photo d---rwxr-x system sdcard_rw 1980-01-06 00:00 LOST.DIR d---rwxr-x system sdcard_rw 2010-05-20 11:04 rssreader d---rwxr-x system sdcard_rw 2010-11-14 16:45 albumthumbs d---rwxr-x system sdcard_rw 2010-05-20 11:19 rosie_scroll d---rwxr-x system sdcard_rw 2010-06-12 14:16 tmp d---rwxr-x system sdcard_rw 2010-05-20 12:48 Android d---rwxr-x system sdcard_rw 2010-11-16 12:19 DCIM d---rwxr-x system sdcard_rw 2010-09-12 15:04 download d---rwxr-x system sdcard_rw 2010-05-20 17:45 media d---rwxr-x system sdcard_rw 2010-05-20 22:10 Downloads rwxr-x system sdcard_rw55715 2010-11-17 16:06 cacerts.bks d---rwxr-x system sdcard_rw 2010-05-23 00:38 agilefusion d---rwxr-x system sdcard_rw 2010-05-23 11:15 Qik d---rwxr-x system sdcard_rw 2010-05-25 08:46 thumbs rwxr-x system sdcard_rw55715 2010-11-15 18:39 new-cacerts.bks rwxr-x system sdcard_rw 535540 2010-11-17 15:21 busybox # # ls -l ls -l d---rwxr-x system sdcard_rw 2010-04-09 15:38 HTC Sync d---rwxr-x system sdcard_rw 2010-04-09 15:39 Music d---rwxr-x system sdcard_rw 2010-04-09 15:39 Sample Photo d---rwxr-x system sdcard_rw 1980-01-06 00:00 LOST.DIR d---rwxr-x system sdcard_rw 2010-05-20 11:04 rssreader d---rwxr-x system sdcard_rw 2010-11-14 16:45 albumthumbs d---rwxr-x system sdcard_rw 2010-05-20 11:19 rosie_scroll d---rwxr-x system sdcard_rw 2010-06-12 14:16 tmp d---rwxr-x system sdcard_rw 2010-05-20 12:48 Android d---rwxr-x system sdcard_rw 2010-11-16 12:19 DCIM d---rwxr-x system sdcard_rw 2010-09-12 15:04 download d---rwxr-x system sdcard_rw 2010-05-20 17:45 media d---rwxr-x system sdcard_rw 2010-05-20 22:10 Downloads rwxr-x system sdcard_rw0 2010-11-17 16:26 cacerts.bks d---rwxr-x system sdcard_rw 2010-05-23 00:38 agilefusion d---rwxr-x system sdcard_rw 2010-05-23 11:15 Qik d---rwxr-x system sdcard_rw 2010-05-25 08:46 thumbs rwxr-x system sdcard_rw55715 2010-11-15 18:39 new-cacerts.bks rwxr-x system sdcard_rw 535540 2010-11-17 15:21 busybox # dd if=/sdcard/new-cacerts.bks of=./cacerts.bks dd if=/sdcard/new-cacerts.bks of=./cacerts.bks 108+1 records in 108+1 records out 55715 bytes transferred in 0.018 secs (3095277 bytes/sec) # cd /system/etc/security cd /system/etc/security # ls -l ls -l -rw-r--r-- root root 1107 2010-04-28 19:10 otacerts.zip -rw-r--r-- root root55715 2010-04-28 08:54 cacerts.bks # df df /dev: 201900K total, 0K used, 201900K available (block size 4096) /sqlite_stmt_journals: 4096K total, 4K used, 4092K available (block size 4096) /system: 358400K total, 217796K used, 140604K available (block size 4096) /data: 437888K total, 85680K used, 352208K available (block size 4096) /cache: 163840K total, 1416K used, 162424K available (block size 4096) /app-cache: 8192K total, 1092K used, 7100K available (block size 4096) /sdcard: 7753728K total, 132032K used, 7621696K available (block size 32768) # dd if=/sdcard/new-cacerts.bks of=./cacerts.bks dd if=/sdcard/new-cacerts.bks of=./cacerts.bks ./cacerts.bks: write error: No space left on device 42+0 records in 41+0 records out 20992 bytes transferred in 0.384 secs (54666 bytes/sec) On Wed, Nov 17, 2010 at 4:50 PM, chetan achar chetan...@gmail.com wrote: Hi all, *In android,* **if i remove file from file system, he wont allow to write if i change in sdcard it allows when i do df he says size is available and once i do dd it goes for a toss see the logs How is it possible to change the file pulled ane write into it and push it
[android-developers] Re: Log
# ls -l ls -l -rw-r--r-- root root 1107 2010-04-28 19:10 otacerts.zip -rw-r--r-- root root55715 2010-04-28 08:54 cacerts.bks # dd if=./cacerts.bks of=./cacerts.bks dd if=./cacerts.bks of=./cacerts.bks 0+0 records in 0+0 records out 0 bytes transferred in 0.001 secs (0 bytes/sec) # ls -l ls -l -rw-r--r-- root root 1107 2010-04-28 19:10 otacerts.zip -rw-r--r-- root root0 2010-11-17 16:54 cacerts.bks On Wed, Nov 17, 2010 at 4:52 PM, chetan achar chetan...@gmail.com wrote: Here are the logs, # reboot reboot C:\android-sdk-windows\toolsadb devices List of devices attached HT058HL00699device C:\android-sdk-windows\toolsadb shell # su su # mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system # cat /proc/mounts cat /proc/mounts rootfs / rootfs ro 0 0 tmpfs /dev tmpfs rw,mode=755 0 0 devpts /dev/pts devpts rw,mode=600 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0 none /dev/cpuctl cgroup rw,cpu 0 0 /dev/block/mtdblock4 /system yaffs2 rw 0 0 /dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0 /dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0 tmpfs /app-cache tmpfs rw,size=8192k 0 0 /dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gi 1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1 hortname=mixed,utf8,errors=remount-ro 0 0 # cd /sdcard/ cd /sdcard/ # ls -l ls -l d---rwxr-x system sdcard_rw 2010-04-09 15:38 HTC Sync d---rwxr-x system sdcard_rw 2010-04-09 15:39 Music d---rwxr-x system sdcard_rw 2010-04-09 15:39 Sample Photo d---rwxr-x system sdcard_rw 1980-01-06 00:00 LOST.DIR d---rwxr-x system sdcard_rw 2010-05-20 11:04 rssreader d---rwxr-x system sdcard_rw 2010-11-14 16:45 albumthumbs d---rwxr-x system sdcard_rw 2010-05-20 11:19 rosie_scroll d---rwxr-x system sdcard_rw 2010-06-12 14:16 tmp d---rwxr-x system sdcard_rw 2010-05-20 12:48 Android d---rwxr-x system sdcard_rw 2010-11-16 12:19 DCIM d---rwxr-x system sdcard_rw 2010-09-12 15:04 download d---rwxr-x system sdcard_rw 2010-05-20 17:45 media d---rwxr-x system sdcard_rw 2010-05-20 22:10 Downloads rwxr-x system sdcard_rw55715 2010-11-17 16:06 cacerts.bks d---rwxr-x system sdcard_rw 2010-05-23 00:38 agilefusion d---rwxr-x system sdcard_rw 2010-05-23 11:15 Qik d---rwxr-x system sdcard_rw 2010-05-25 08:46 thumbs rwxr-x system sdcard_rw55715 2010-11-15 18:39 new-cacerts.bks rwxr-x system sdcard_rw 535540 2010-11-17 15:21 busybox # # ls -l ls -l d---rwxr-x system sdcard_rw 2010-04-09 15:38 HTC Sync d---rwxr-x system sdcard_rw 2010-04-09 15:39 Music d---rwxr-x system sdcard_rw 2010-04-09 15:39 Sample Photo d---rwxr-x system sdcard_rw 1980-01-06 00:00 LOST.DIR d---rwxr-x system sdcard_rw 2010-05-20 11:04 rssreader d---rwxr-x system sdcard_rw 2010-11-14 16:45 albumthumbs d---rwxr-x system sdcard_rw 2010-05-20 11:19 rosie_scroll d---rwxr-x system sdcard_rw 2010-06-12 14:16 tmp d---rwxr-x system sdcard_rw 2010-05-20 12:48 Android d---rwxr-x system sdcard_rw 2010-11-16 12:19 DCIM d---rwxr-x system sdcard_rw 2010-09-12 15:04 download d---rwxr-x system sdcard_rw 2010-05-20 17:45 media d---rwxr-x system sdcard_rw 2010-05-20 22:10 Downloads rwxr-x system sdcard_rw0 2010-11-17 16:26 cacerts.bks d---rwxr-x system sdcard_rw 2010-05-23 00:38 agilefusion d---rwxr-x system sdcard_rw 2010-05-23 11:15 Qik d---rwxr-x system sdcard_rw 2010-05-25 08:46 thumbs rwxr-x system sdcard_rw55715 2010-11-15 18:39 new-cacerts.bks rwxr-x system sdcard_rw 535540 2010-11-17 15:21 busybox # dd if=/sdcard/new-cacerts.bks of=./cacerts.bks dd if=/sdcard/new-cacerts.bks of=./cacerts.bks 108+1 records in 108+1 records out 55715 bytes transferred in 0.018 secs (3095277 bytes/sec) # cd /system/etc/security cd /system/etc/security # ls -l ls -l -rw-r--r-- root root 1107 2010-04-28 19:10 otacerts.zip -rw-r--r-- root root55715 2010-04-28 08:54 cacerts.bks # df df /dev: 201900K total, 0K used, 201900K available (block size 4096) /sqlite_stmt_journals: 4096K total, 4K used, 4092K available (block size 4096) /system: 358400K total, 217796K used, 140604K available (block size 4096) /data: 437888K total, 85680K used, 352208K available (block size 4096) /cache: 163840K total, 1416K used, 162424K available (block size 4096) /app-cache: 8192K total, 1092K used, 7100K available (block size 4096) /sdcard: 7753728K total, 132032K used, 7621696K available
[android-developers] Re: Log messages no longer appear in LogCat
When you have multiple devices/emulators connected its sometimes important to go the DDMS perspective and select the relevant device in the left (Devices) pane. Whenever I see none of them selected then I don't get any logcat messages and the FileExplorer does not reflect the actual filesystem. On Nov 20, 3:59 pm, mh haye...@gmail.com wrote: No I did not get an answer but I found a solution that works here. Disconnect the device before running the emulator. The messages appear in LogCat as expected even if I the device is then reconnected. Debugging on the device seems to disable further logging of Logx until the device is again disconnected. On Nov 15, 11:11 pm, android beginner mirra07aurobin...@gmail.com wrote: s i experience the same.did u get any answer -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log messages no longer appear in LogCat
Westmeadboy, That was it. Thanks On Nov 20, 1:03 am, westmeadboy westmead...@yahoo.co.uk wrote: When you have multiple devices/emulators connected its sometimes important to go the DDMS perspective and select the relevant device in the left (Devices) pane. Whenever I see none of them selected then I don't get any logcat messages and the FileExplorer does not reflect the actual filesystem. On Nov 20, 3:59 pm, mh haye...@gmail.com wrote: No I did not get an answer but I found a solution that works here. Disconnect the device before running the emulator. The messages appear in LogCat as expected even if I the device is then reconnected. Debugging on the device seems to disable further logging of Logx until the device is again disconnected. On Nov 15, 11:11 pm, android beginner mirra07aurobin...@gmail.com wrote: s i experience the same.did u get any answer -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log messages no longer appear in LogCat
No I did not get an answer but I found a solution that works here. Disconnect the device before running the emulator. The messages appear in LogCat as expected even if I the device is then reconnected. Debugging on the device seems to disable further logging of Logx until the device is again disconnected. On Nov 15, 11:11 pm, android beginner mirra07aurobin...@gmail.com wrote: s i experience the same.did u get any answer -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Log in to google account without browser?
On Sep 3, 8:23 am, Per Sandström pg.sandst...@gmail.com wrote: Hi, Im currently trying to combine android and google apps engine for a real neat application, not unlikehttp://3banana.com/. However I want to enable the user to login to his google account without opening the browser. I have made some attempts to just simulate the http-posts done, but to no avail. Are there any nice way of doing this google account login in android code? For example, to make my own loginscreen, and then send user/pass to the google apps server and get an aknowledgement if the login information was correct. Take a look at http://code.google.com/apis/accounts/ Neil --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: log info, pls help
Thanks a lot. Both of you. On Aug 5, 10:19 am, Yusuf T. Mobile yusuf.s...@t-mobile.com wrote: You can build the SDK (with make sdk) and then run the emulator (with emulator) and look at thelog(with adb logcat). Yusuf Saib Android ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 9:56 pm, yosemite gaoqing2...@gmail.com wrote: thanks. Could you please give me some instructions about how to do that in the emulaor? On Aug 4, 4:44 pm, Roman roman.baumgaert...@t-mobile.com wrote: Before flashing your phone, did you try to run the emulator with your new system.img? -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 11:16 am, yosemite gaoqing2...@gmail.com wrote: Hi, I made some changes to the Android source code and rebuilt a system.img file. After that, I use fastboot flash system system.img to flash my Android Developer phone. However, there is a crash during the loading process. Is there any way I can read thelogfor this kind of crash? Thanks a lot. -M --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: log info, pls help
When you build the whole platform you can find all new created platfrom imsages and binaries in out/host/darwin-x86/. In the bin folder you also find the emulator. When you do changes on framework code or dalvik a new system.img should be created. The emulator has this new system image included. You can put some debug prints to your framework code changes to make sure that you can check whether you run in your code. With using mmm you can speed up your build. For example mmm frameworks/base/services snod would compile only services. Also here a new emulator image will be created (verify the compile date of the emulator to make sure that you will have a new compiled version). In general before you do any critical changes on your system.img you can check it first with the emulator. Of course there might be changes related to HW interfaces which you cannot verify with the emulator. Hope, this helps! -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 9:56 pm, yosemite gaoqing2...@gmail.com wrote: thanks. Could you please give me some instructions about how to do that in the emulaor? On Aug 4, 4:44 pm, Roman roman.baumgaert...@t-mobile.com wrote: Before flashing your phone, did you try to run the emulator with your new system.img? -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 11:16 am, yosemite gaoqing2...@gmail.com wrote: Hi, I made some changes to the Android source code and rebuilt a system.img file. After that, I use fastboot flash system system.img to flash my Android Developer phone. However, there is a crash during the loading process. Is there any way I can read the log for this kind of crash? Thanks a lot. -M --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: log info, pls help
You can build the SDK (with make sdk) and then run the emulator (with emulator) and look at the log (with adb logcat). Yusuf Saib Android ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 9:56 pm, yosemite gaoqing2...@gmail.com wrote: thanks. Could you please give me some instructions about how to do that in the emulaor? On Aug 4, 4:44 pm, Roman roman.baumgaert...@t-mobile.com wrote: Before flashing your phone, did you try to run the emulator with your new system.img? -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 11:16 am, yosemite gaoqing2...@gmail.com wrote: Hi, I made some changes to the Android source code and rebuilt a system.img file. After that, I use fastboot flash system system.img to flash my Android Developer phone. However, there is a crash during the loading process. Is there any way I can read the log for this kind of crash? Thanks a lot. -M --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: log info, pls help
Before flashing your phone, did you try to run the emulator with your new system.img? -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 11:16 am, yosemite gaoqing2...@gmail.com wrote: Hi, I made some changes to the Android source code and rebuilt a system.img file. After that, I use fastboot flash system system.img to flash my Android Developer phone. However, there is a crash during the loading process. Is there any way I can read the log for this kind of crash? Thanks a lot. -M --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: log info, pls help
thanks. Could you please give me some instructions about how to do that in the emulaor? On Aug 4, 4:44 pm, Roman roman.baumgaert...@t-mobile.com wrote: Before flashing your phone, did you try to run the emulator with your new system.img? -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Aug 4, 11:16 am, yosemite gaoqing2...@gmail.com wrote: Hi, I made some changes to the Android source code and rebuilt a system.img file. After that, I use fastboot flash system system.img to flash my Android Developer phone. However, there is a crash during the loading process. Is there any way I can read the log for this kind of crash? Thanks a lot. -M --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Log with Production App
I know its not the same, but is this a more recommended approach than to wrap each log with a call to Log.isLoggable()? I know this would not have the benefits (like app size) you mentioned, but, since I've had problems with the isLoggable() method anyway, it seems like a simple and effective approach to go with. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Log with Production App
Please do remove them. They make your app larger, slower to run (can be SIGNIFICANTLY slower because of the work Java ends up doing building strings), and... for people working on the platform having an app spewing logs is super annoying, since it buries any -interesting- messages that other parts of the system print. Actually if I see an app I have installed spewing logs, I will often uninstall it because it is so annoying and greatly reduces the amount of information available in the log if I need to track down something going wrong with my device. Fyi, it is very easy to conditionally compile them -- just define a static final boolean DOLOG = false value, and check that before each log. The Java compiler will strip all of that code out when the constant is false. On Mon, Jul 27, 2009 at 9:01 PM, Maps.Huge.Info (Maps API Guru) cor...@gmail.com wrote: I've been working on an app for a couple of months, it's loaded with log statements (android.util.Log) now and they are very useful. Question: Is it better to remove log statements before deploying to the market or can they be left in? Are there good reasons to remove them regardless? Thanks in advance. -John Coryat -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Log with Production App
Dianne, Thanks, that's exactly the kind of answer I was looking for, -John Coryat On Jul 27, 11:12 pm, Dianne Hackborn hack...@android.com wrote: Please do remove them. They make your app larger, slower to run (can be SIGNIFICANTLY slower because of the work Java ends up doing building strings), and... for people working on the platform having an app spewing logs is super annoying, since it buries any -interesting- messages that other parts of the system print. Actually if I see an app I have installed spewing logs, I will often uninstall it because it is so annoying and greatly reduces the amount of information available in the log if I need to track down something going wrong with my device. Fyi, it is very easy to conditionally compile them -- just define a static final boolean DOLOG = false value, and check that before each log. The Java compiler will strip all of that code out when the constant is false. On Mon, Jul 27, 2009 at 9:01 PM, Maps.Huge.Info (Maps API Guru) cor...@gmail.com wrote: I've been working on an app for a couple of months, it's loaded with log statements (android.util.Log) now and they are very useful. Question: Is it better to remove log statements before deploying to the market or can they be left in? Are there good reasons to remove them regardless? Thanks in advance. -John Coryat -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Log in to an application?
Question: how should I implement this? 1. Are there e.g. onStartup() and onShutdown() per-application events, or similar, that I can hook into, to serve up a login dialog and set the login state in Preferences? If not, then how should I implement login? So, your first problem is conceptual. The idea of an application isn't as well defined in Android as a desktop OS (deliberately). For instance, it's pretty clear what happens when the user presses the icon on the launcher or home screen - you display the login screen. What if the user receives a call whilst using your app, and it switches to the background? Does the user have to log in again when returning? No, that makes no sense. What if they press home and do something else for, say, 20 minutes - log in again then? Probably not. Could you describe why you want this in a bit more detail? Phones are already protected by key locks, I don't see why you need a separate login system for your app? 2. Assuming that I save the login state and the user's password (hashed with a salt) in Preferences, how secure will that be? That's impossible to answer because you did not describe what the login is protecting. Saving a hashed password with a salt isn't really secure because somebody can just decompile the apk to find out what the salt is then brute force the result *if* the phone is rooted. If it is not rooted they'd have to do that first. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Log in to an application?
Hi Mike, Thanks for the advice... here are my answers. 1. Are there e.g. onStartup() and onShutdown() per-application events, or similar, that I can hook into, to serve up a login dialog and set the login state in Preferences? If not, then how should I implement login? So, your first problem is conceptual. The idea of an application isn't as well defined in Android as a desktop OS (deliberately). For instance, it's pretty clear what happens when the user presses the icon on the launcher or home screen - you display the login screen. What if the user receives a call whilst using your app, and it switches to the background? Does the user have to log in again when returning? No, that makes no sense. What if they press home and do something else for, say, 20 minutes - log in again then? Probably not. Ideally I'd like to give people the choice of (a) mild security - log in only when they first start the app, or (b) strong security - log in every time they switch away from it, for whatever reason. At a minimum I'd like to offer (a) mild security - log in every time the app is launched if it's not already running in the background. If there's no onStartup/onShutdown event, then I guess I can't store a boolean value for logged_in in the Preferences, since it'll persist. I could pass it in a Bundle back and forth between activities, which would die with the app. But how secure would that be? Could someone pass a Bundle to the activity automatically? Could you describe why you want this in a bit more detail? Phones are already protected by key locks, I don't see why you need a separate login system for your app? Ah, it's because I've already released an app on the market and the #1 feature request from users is for a password. I know, I find it surprising too! I guess it must be either people who don't use a keylock most of the time, or who share a phone occasionally, or who are paranoid about other people reading their private stuff (it's a notebook app). 2. Assuming that I save the login state and the user's password (hashed with a salt) in Preferences, how secure will that be? That's impossible to answer because you did not describe what the login is protecting. Saving a hashed password with a salt isn't really secure because somebody can just decompile the apk to find out what the salt is then brute force the result *if* the phone is rooted. If it is not rooted they'd have to do that first. Thanks. Um, sorry for the naive question, how hard is it to root a phone? I just want to know what to say to users. Saying your private details are secure from other normal users, but probably not if a determined hacker with root access steals your phone would be fine. cheers Anna --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
