[android-developers] Re: Is it possible, that Android kills a service inside an app?
It depends on the Service which you have. Service in android is of two types: Bound Service and Unbounded Service. Binded Service is what is bound to the activity and it lives as long as activity is running. But unbound service is like a *Separate Process. The Service can still be killed by Android.*To avoid this in the onDestroy() method just call the BroadcastReceiver which launches the service. On Tuesday, November 25, 2014 4:38:18 PM UTC+5:30, Oleksii Bieliaiev wrote: Hey guys, let's imagine we have an app with a service and an activity inside. Both components live in a same process, our service is started (in terms of Android) and a user does some interaction with an activity. Eventually our app goes to background. My question is, whether is it possible, under certain conditions (low memory, timeout, etc), that Android kills our started service separately, without killing entire process? Thank you, Alex -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-developers] Is it possible, that Android kills a service inside an app?
Hi, thank you for your answer, I really appreciate that :) However, my question appeared right after I've read the article you mentioned. It doesn't state, that Android can kill a SERVICE, even if its host PROCESS has background priority. It states, that Android kills entire PROCESS, based on its priority. From my point of view, under memory pressure you have to act quickly. How much memory is it possible to free in case you stop a SERVICE? Nobody knows. In theory you can calculate retained size of an object, but in this case you have to rely on GC. When garbage collection will happen? Again, depends on GC. On the other hand, OS knows each process memory footprint. OS has their priorities. OS has enough information to act quickly and be effective under memory pressure. I can be wrong, but for me it doesn't make sense to kill a SERVICE without killing entire PROCESS. Yes, user can do this manually, but it doesn't mean Android does that. Again, I can be wrong. But I really need some proofs :) Thank you, Alex On Friday, December 5, 2014 4:12:21 AM UTC+1, TreKing wrote: On Tue, Nov 25, 2014 at 5:08 AM, Oleksii Bieliaiev abel.th...@gmail.com javascript: wrote: My question is, whether is it possible, under certain conditions (low memory, timeout, etc), that Android kills our started service separately, without killing entire process? Yes, it's possible. If the process does not have a foreground UI element (an Activity the user is using or an ongoing notification created with startForeground) the Service is considered to be background and more susceptible to being killed. See: http://developer.android.com/guide/topics/processes/process-lifecycle.html - 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-developers] Is it possible, that Android kills a service inside an app?
Sorry, but I'm asking about OS behavior, not about my possibilities. Thank you, Alex On Friday, December 5, 2014 4:23:14 AM UTC+1, SIVAKUMAR.J wrote: Yes you can call stop service method On 25 Nov 2014 16:38, Oleksii Bieliaiev abel.th...@gmail.com javascript: wrote: Hey guys, let's imagine we have an app with a service and an activity inside. Both components live in a same process, our service is started (in terms of Android) and a user does some interaction with an activity. Eventually our app goes to background. My question is, whether is it possible, under certain conditions (low memory, timeout, etc), that Android kills our started service separately, without killing entire process? Thank you, Alex -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@googlegroups.com javascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-developers] Re: Is it possible, that Android kills a service inside an app?
It depends on the Service which you have. Service in android is of two types: I'm asking specifically about Started service http://developer.android.com/reference/android/content/Context.html#startService(android.content.Intent) *The Service can still be killed by Android.* Any proofs? Thank you, Alex On Friday, December 5, 2014 12:32:33 PM UTC+1, Ashik Vetrivelu wrote: It depends on the Service which you have. Service in android is of two types: Bound Service and Unbounded Service. Binded Service is what is bound to the activity and it lives as long as activity is running. But unbound service is like a *Separate Process. The Service can still be killed by Android.*To avoid this in the onDestroy() method just call the BroadcastReceiver which launches the service. On Tuesday, November 25, 2014 4:38:18 PM UTC+5:30, Oleksii Bieliaiev wrote: Hey guys, let's imagine we have an app with a service and an activity inside. Both components live in a same process, our service is started (in terms of Android) and a user does some interaction with an activity. Eventually our app goes to background. My question is, whether is it possible, under certain conditions (low memory, timeout, etc), that Android kills our started service separately, without killing entire process? Thank you, Alex -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-developers] Re: Is it possible, that Android kills a service inside an app?
What? Whether a Service runs in a separate process or not DOES NOT depend on whether you bind to it and/or start it using startService. That is only controlled by the process attribute, see http://developer.android.com/guide/topics/manifest/service-element.html#proc. On Friday, December 5, 2014 12:32:33 PM UTC+1, Ashik Vetrivelu wrote: It depends on the Service which you have. Service in android is of two types: Bound Service and Unbounded Service. Binded Service is what is bound to the activity and it lives as long as activity is running. But unbound service is like a *Separate Process. The Service can still be killed by Android.*To avoid this in the onDestroy() method just call the BroadcastReceiver which launches the service. On Tuesday, November 25, 2014 4:38:18 PM UTC+5:30, Oleksii Bieliaiev wrote: Hey guys, let's imagine we have an app with a service and an activity inside. Both components live in a same process, our service is started (in terms of Android) and a user does some interaction with an activity. Eventually our app goes to background. My question is, whether is it possible, under certain conditions (low memory, timeout, etc), that Android kills our started service separately, without killing entire process? Thank you, Alex -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-developers] How do I get logcat working on my LG G Tab 7.0?
One thing I usually do when I'm preparing a device to work with adb for debugging is to switch it to appear on the USB bus as a Camera, instead of a Media device. I do this with my Nexus 5 and Nexus 7 devices (which are running my AOSP builds with root access). This often solves the device not found problem. I am guessing that the Camera mode supplies the two-way host-client communication protocol that adb needs, while the Media mode operates in a Master-Slave paradigm, meant only for transferring files. Another of my solutions is to make sure the device is being registered within the OS as the right type of device. For Windows I use USBDeview, and on Linux I use lsusb. (There is a Mac version of lsusb here: https://github.com/jlhonora/lsusb .) These tools will show the presence of the device on the USB bus, and the Vendor and Product ID numbers for it. Those numbers determine the identity of the device within the operating system, which leads to the choice of which device driver is used to communicate with it. If the device is in Media mode, then the OS will probably connect it to the Media device driver. When the device is in Camera mode, a different driver is selected. The goal is to get the OS to identify the device in such a way as to get the right driver attached to it. Then it will appear where adb can see it, and adb devices will list it. Setting up Linux to use udev to recognize an Android debug device and assign the right permissions and driver to it is covered here: http://source.android.com/source/initializing.html#setting-up-a-mac-os-x-build-environment . There is a page of udev configuration in the Linux section (above where that Mac OSX link points you). The device identifiers in that list are what I'm talking about. They configure udev to detect and properly represent the device within the system so adb can see it. Windows uses the same Vendor/Product ID system as udev. Each device driver install package has a .inf file that specifies which devices the device driver is meant to work with. Not having a device driver with the Vendor/Product ID of a device being plugged into USB causes Windows to display the Search the Internet or select a device driver package dialog. Getting Android device drivers working on Windows is not easy, but I find that USBDeview helps a lot, since it displays the Vendor/Product IDs, and you can easily determine if a particular driver is going to respond to those IDs. NOTE:Switching the device from Media to Camera mode with cause it to display a different Vendor/Product ID within the USB system. (This also happens when rebooting to Recovery or Bootloader.) BTW, I wouldn't blame Google for the adb problems. They wrote what they could, and it now has to run in a chaotic third party OS environment. USB needs to be configured on the host OS, which is not under Google's control. Also, Vendors often like to turn off adb access like some Internet sites like to turn off ping responses. They think it helps, but it gets in the way of development. For example, I have yet to find a way to logcat my Kindle Fire. It seems that Amazon doesn't want me to do that. If I wanted to develop for the Kindle, I'd approach Amazon with a willingness to sign an NDA, and become a member of their development community (if there is one). Otherwise, I'm locked out, and I would probably use some other device to do development. Device manufacturers are not obligated to support development. This sentiment is best expressed in Google's explanation of why they use the Apache Source License for the AOSP project: http://source.android.com/source/licenses.html#why-apache-software-license On Thursday, December 4, 2014 11:15:43 PM UTC-6, Spooky wrote: On Thu, Dec 04, 2014 at 10:44:46PM -0600, TreKing wrote: On Thu, Dec 4, 2014 at 9:23 PM, Jim Graham spook...@gmail.com javascript: wrote: You did not clarify, so, to be sure, you followed the directions on that page, right? Well, given that this post just now showed up here, no, I didn't even know about that. But...it worked! At least, for showing Developer Options. Now for the next question: what option(s) do I need to select in Developer Options to enable logcat on 4.2+ (on my devices) WITHOUT root? Ok, we're on the way to overriding Google's infinte stupidity ... maybe this will actually work right (like it used to) after all. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) | spook...@gmail.com javascript: | BOFH Excuse for the day: Running Mac OS X Lion | ICBM / Hurricane: | Paradigm shift without 30.44406N 86.59909W| a clutch. -- 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
Re: [android-developers] How do I get logcat working on my LG G Tab 7.0?
On Fri, Dec 05, 2014 at 08:12:33AM -0800, andrew_esh wrote: One thing I usually do when I'm preparing a device to work with adb for debugging is to switch it to appear on the USB bus as a Camera, instead of a Media device. I do this with my Nexus 5 and Nexus 7 devices Actually, while I haven't had time to mess with this again since last night, I'm 99% certain that the reason the tablet wasn't connecting via USB is the fact that the USB debugging, located in the formerly hidden Developer Options (thanks again, TreKing, for the help with that), was off. After I get some more work done on my port of my desktop brewers beer formula calculator (GTbrew2 --- GTbrew2/Android)---trying to get the big database working today, and hopefully move foreward from there, I'll be trying to get adb working across TCP/IP (I saw the options to connect via TCP/IP in the adb options, but so far, no luck getting it to actually connect from my Mac to the adb server I think I started on my tablet). Then I could use my Mac to directly receive logcat data (I also found out how to filter the results, so it would actually end up being an improvement...if I can just get past that very short USB cable...with the Android-side connector being about 1/2 the size of normal). BTW, I wouldn't blame Google for the adb problems. They wrote what they could, and it now has to run in a chaotic third party OS environment. I blame google for what google did: deliberately make developers jump through hoops to debug apps we're developing by breaking what was working fine before. This morning, I started seeing indications that not only is logcat screwed up now, it may actually be deprecated. If that's the case, there's a new method that should be an improvement, if they'll just let us know what it is.. I'm not holding my breath, though. This sentiment is best expressed in Google's explanation of why they use the Apache Source License for the AOSP project: http://source.android.com/source/licenses.html#why-apache-software-license Wait, isn't the Apache Source License one of the most open ones? Maybe I've missed something...who knows. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) | AN EXCERCISE is a situation in which you stop what spooky1...@gmail.com | you're doing in order to simulate doing what you Running Mac OS X Lion | were doing so you can show someone else that you ICBM / Hurricane: | can simulate what you were doing as well as you 30.44406N 86.59909W| were doing it before you were interrupted. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-developers] Database access error causes force close
I'm trying to use an SQLite table with Android (and for almost the first
time, period, but I familiarized myself with it using SQLite3 /
tclsh8.4), and I've run into a bit of a problem where I can't seem to
spot the error.
Here is the code where it's failing and force closing:
--- CUT HERE ---
// global - before start of DataBaseHelper class:
private static final String TABLE_GRAINBRANDS = grainbrands;
// much later in DataBaseHelper
ListString grainBrandsList = new ArrayListString();
String selectQuery = SELECT * FROM + TABLE_GRAINBRANDS;
String brand;
SQLiteDatabase db = this.getWritableDatabase();
Cursor c = db.rawQuery(selectQuery, null); // This is the line (75)
// that logcat says causes the force close
--- CUT HERE ---
Surrounding logcat code:
--- CUT HERE ---
I/ActivityManager(15152): Start proc com.jdgapps.andgtbrew2 for activity
com.jdgapps.andgtbrew2/.AndGTbrew2: pid=28296 uid=10327
gids={1015, 1028}
I/ActivityManager(15152): Displayed com.jdgapps.andgtbrew2/.AndGTbrew2: +3s183ms
E/AndroidRuntime(28296):
at
com.jdgapps.andgtbrew2.DataBaseHelper.getGrainBrands(DataBaseHelper.java:175)
E/AndroidRuntime(28296): at
com.jdgapps.andgtbrew2.AndGTbrew2$1.onClick(AndGTbrew2.java:92)
W/ActivityManager(15152): Force finishing activity
com.jdgapps.andgtbrew2/.AndGTbrew2
W/ActivityManager(15152): Activity pause timeout for
ActivityRecord{4280e468 com.jdgapps.andgtbrew2/.AndGTbrew2}
I/ActivityManager(15152): Process com.jdgapps.andgtbrew2 (pid 28296) has died.
--- CUT HERE ---
Unfortunately, this error message doesn't tell me much, and while looking
between tutorials and my code here, I can't see what's wrong with it.
I tried to check in /data/data/com.jdgapps.andgtbrew2/ to see if gtbrew2.db
was there, but /data was empty, so I gather it's hidden. Good security,
normally, but a PITA right now.
Logcat does not show any of the errors that would be generated if the
dabase copy (from assets to the above) failed, so it should be there.
Does anyone see anything that I might have missed?
Thanks,
--jim
--
THE SCORE: ME: 2 CANCER: 0
73 DE N5IAL (/4) |
spooky1...@gmail.com | TeX actually recognizes several kinds of
Running Mac OS X Lion | infinity, some of which are ``more infinite''
ICBM / Hurricane: | than others.
30.44406N 86. 59909W | --Donald Knuth in {The TeXbook}
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[android-developers] Re: Interfacing an android device (host mode) directly with a microcontroller via usb
The simplest way to do that is to use a USB-to-serial converter and program your Android app to talk to the converter module using the USB SPP protocol. Then your micro controller program is simply talking over its UART. If you want to stay with USB all the way, then you will have to use a micro with a USB interface and implement the SPP protocol on that micro. This is not easy. USB is not a generic communication protocol like serial async. The Android system needs to have a driver to the specific USB protocol you want to use. Besides SPP, you could use the HID protocol and make your micro controller emulate a keyboard. Then your application would have to be structured so as to use a keyboard interface, which is quite restrictive on your application. Overall, I would say the converter module is the easiest approach. Robert Scott Hopkins, MN -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-developers] Re: Database access error causes force close (Update)
On Fri, Dec 05, 2014 at 02:59:20PM -0600, Jim Graham wrote: I'm trying to use an SQLite table with Android (and for almost the first time, period, but I familiarized myself with it using SQLite3 / tclsh8.4), and I've run into a bit of a problem where I can't seem to spot the error. Update: There may be a problem with the initial copying of the database. The copy in assets (according to ls -l is 150528, but long size = new File(db.getPath()).length(); reports a size of 12288. Does Android silently do compression of the database? Or was it only partially copied, thus likely explaining the error? Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4)MiSTie #49997 Running Mac OS X Lion spooky1...@gmail.com ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye! -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-developers] Database access error causes force close
You could try putting a try/catch block around the offending statement to
catch a generic exception, maybe finding out exactly what exception pops up
might give you a clue?
On Dec 5, 2014 4:00 PM, Jim Graham spooky1...@gmail.com wrote:
I'm trying to use an SQLite table with Android (and for almost the first
time, period, but I familiarized myself with it using SQLite3 /
tclsh8.4), and I've run into a bit of a problem where I can't seem to
spot the error.
Here is the code where it's failing and force closing:
--- CUT HERE ---
// global - before start of DataBaseHelper class:
private static final String TABLE_GRAINBRANDS = grainbrands;
// much later in DataBaseHelper
ListString grainBrandsList = new ArrayListString();
String selectQuery = SELECT * FROM + TABLE_GRAINBRANDS;
String brand;
SQLiteDatabase db = this.getWritableDatabase();
Cursor c = db.rawQuery(selectQuery, null); // This is the line (75)
// that logcat says causes the force close
--- CUT HERE ---
Surrounding logcat code:
--- CUT HERE ---
I/ActivityManager(15152): Start proc com.jdgapps.andgtbrew2 for activity
com.jdgapps.andgtbrew2/.AndGTbrew2: pid=28296 uid=10327
gids={1015, 1028}
I/ActivityManager(15152): Displayed com.jdgapps.andgtbrew2/.AndGTbrew2:
+3s183ms
E/AndroidRuntime(28296):
at
com.jdgapps.andgtbrew2.DataBaseHelper.getGrainBrands(DataBaseHelper.java:175)
E/AndroidRuntime(28296): at
com.jdgapps.andgtbrew2.AndGTbrew2$1.onClick(AndGTbrew2.java:92)
W/ActivityManager(15152): Force finishing activity
com.jdgapps.andgtbrew2/.AndGTbrew2
W/ActivityManager(15152): Activity pause timeout for
ActivityRecord{4280e468 com.jdgapps.andgtbrew2/.AndGTbrew2}
I/ActivityManager(15152): Process com.jdgapps.andgtbrew2 (pid 28296) has
died.
--- CUT HERE ---
Unfortunately, this error message doesn't tell me much, and while looking
between tutorials and my code here, I can't see what's wrong with it.
I tried to check in /data/data/com.jdgapps.andgtbrew2/ to see if gtbrew2.db
was there, but /data was empty, so I gather it's hidden. Good security,
normally, but a PITA right now.
Logcat does not show any of the errors that would be generated if the
dabase copy (from assets to the above) failed, so it should be there.
Does anyone see anything that I might have missed?
Thanks,
--jim
--
THE SCORE: ME: 2 CANCER: 0
73 DE N5IAL (/4) |
spooky1...@gmail.com | TeX actually recognizes several kinds of
Running Mac OS X Lion | infinity, some of which are ``more infinite''
ICBM / Hurricane: | than others.
30.44406N 86. 59909W | --Donald Knuth in {The TeXbook}
--
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 unsubscribe from this group and stop receiving emails from it, send an
email to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [android-developers] Database access error causes force close
On Fri, Dec 05, 2014 at 10:27:56PM -0500, Steve Gabrilowitz wrote: You could try putting a try/catch block around the offending statement to catch a generic exception, maybe finding out exactly what exception pops up might give you a clue? I tried that. The catch statement, which should have logged the error, became the new source of the force close. And logcat did not give ANY additional data. :-( I also tried deleting the database and re-creating it. It STILL shows up as much smaller than the copy in assets, but I'm still assuming Android quietly does some kind of compression on it. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4)MiSTie #49997 Running Mac OS X Lion spooky1...@gmail.com ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye! -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-developers] Database access error causes force close
Put a breakpoint in the catch clause and when it gets there examine the exception - that's how I recently figured out a similiarly puzzling force close. On Dec 5, 2014 10:36 PM, Jim Graham spooky1...@gmail.com wrote: On Fri, Dec 05, 2014 at 10:27:56PM -0500, Steve Gabrilowitz wrote: You could try putting a try/catch block around the offending statement to catch a generic exception, maybe finding out exactly what exception pops up might give you a clue? I tried that. The catch statement, which should have logged the error, became the new source of the force close. And logcat did not give ANY additional data. :-( I also tried deleting the database and re-creating it. It STILL shows up as much smaller than the copy in assets, but I'm still assuming Android quietly does some kind of compression on it. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4)MiSTie #49997 Running Mac OS X Lion spooky1...@gmail.com ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye! -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-developers] Database access error causes force close
On Fri, Dec 05, 2014 at 10:40:01PM -0500, Steve Gabrilowitz wrote: Put a breakpoint in the catch clause and when it gets there examine the exception - that's how I recently figured out a similiarly puzzling force close. Honestly, I don't even know how to do that. I've never run into a situation like this, where logcat says, something happened...and it was here. I've always gotten more useful information either from it, or Eclipse warnings. The most frustrating thing about this stuff is that I'm trying to (hopefully) use this app to make enough money to pay for advertising so the games I'm working on (using AndEngine) will have a chance of making money to either directly make me enough money to get out from under Social (IN)Security Disability, which was forced on me by cancer #1, or to make money to add to my investing, which ultimately the same goal. The ironic part is, I can't afford to pay for advertising for the app I hope to make money to pay for advertising so my games can have a chance So when you combine that with this kind of stuff, where I'm completely at a loss, it makes for a really bad week. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4)MiSTie #49997 Running Mac OS X Lion spooky1...@gmail.com ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye! -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
