Android :: SmsManager Causes Com.android.phone Force Closes Randomly?
Nov 15, 2010
I am using SmsManager to send text messages from my application. The code snippet is smsManager.sendTextMessage(number, null, content, null, null);
For messages with less than 160 characters. And for multipart messages I use,
code:..........
These statements cause The process com.android.phone has stopped unexpectedly please try again in a random fashion. I don't understand what's going on.
This is the stack trace I got:
code:................
View 1 Replies
Sep 11, 2010
Anyone noticed their phone randomly force closing? Mine just started and I've had it for about 6 weeks. I will say that my daughter and I both have DX's. Her brand new, out of the box DX forced closed within an hour of starting it up. It had done it a few times, when we swapped batteries. Now, mine (with her battery) just forced closed (mine hadn't done it previously).
View 3 Replies
View Related
Jan 2, 2010
Idk what could be causing it, I removed taskiller & any newer apps from the past few days I've added but is this something I should call tech support about ?
View 6 Replies
View Related
Sep 4, 2013
I'm having a weird issue where after I successfully rooted my Samsung Galaxy S3 (following a guide from androidcentral) every time my phone encounters an application force close, the phone will freeze up and eventually restart. Before rooting my phone, whenever an application would force close all I would get was a notification telling me <application name> had closed unexpectedly, as it should in Android. Now I'm not seeing that, phone just goes to black and then restarts. This wouldn't be a huge deal, but since I'm using it as a development platform, having your phone restart every time your application crashes takes a lot of time.
What's really weird is that Logcat will continue to scroll (in Eclipse) even after the phone is frozen to input (so its not a system wide lock up).
View 3 Replies
View Related
Aug 9, 2010
I have a Driod Ally that is less than 2 months old.
This is the problem I am experiencing: Whenever I open an email from my second account, the Corporate Email account, the email I'm reading won't stay open. Sometimes the email closes immediately, sometimes it closes after a minute, but it always closes. I don't have time to read it, let alone reply to it. Also, if I'm in the inbox, it will close and goes back to the Home screen. All of this happens randomly.
My Gmail account has no problem staying open. In fact, none of my other apps share this problem, it only happens to my corporate email account which happens to be the most important aspect of the phone.
I tried nuking the account and re-establishing it- to no avail.
View 2 Replies
View Related
Nov 23, 2010
My mother is having this random problem where her web browser closes, sends her back to the Google search page. It seems to only happen when she has some tabs open. Note that it does not force close it just crashes. She is very disappointed and would like to know the solution. My evo sometimes send me to the home screen but does not close.
View 1 Replies
View Related
Oct 30, 2010
I have a rooted Fascinate. After a second re-root my SF has been very buggy. My first root was successful. I messed something up trying to install voodoo and had to flash back to stock. Now, after a second buggy root I am faced with many freezes and FC's. (primarily in com.android.settings, but will float to various apps). Battery pulls don't seem to help. After a certain amount of using my phone, hopping WiFi, maps, email, just normal use, something will need to FC.
Within the next few days I plan on un-lagfixing my phone & un-rooting it. Ultimately I'd like to take it back stock and not root. This leads to my question: what is the best way to flash stock. I don't want anything left. I can tell there was something left from my first root because ads still do not show up. I had an ad block program installed on my first root.
View 2 Replies
View Related
Nov 9, 2010
Everytime i reboot my phone, I get bunch of problems with my phone. when I try to open the phone dialer I get a force close on com.google.process.acore. Sometimes it completely prevents me from using the phone.
Then on occasion the phone freaks out and shuts the screen off, but leaves the navigation lights on the bottom of the phone. At that point the phone is completely unusable for about 1-2minutes. Sometimes when it comes back on, it starts rerunning the media scanner.
View 7 Replies
View Related
Feb 23, 2010
My phone is moving extra slow, Handcent is giving me a lot of force closes, or not opening at all. I can't delete messages...can't download out the market, it will say starting download but will never actually start...I want to throw it against the wall
View 17 Replies
View Related
Oct 8, 2009
I'm getting reports from users about force closes in my app after the donut OTA. One of them was kind enough to send me a logcat which included these two gems (right after he installed it from market):
10-02 15:56:35.708 D/PackageManager(71): New package installed in / data/app/com.billnapier.android.livebookmarks.apk 10-02 15:56:35.708 W/PackageManager( 71): Unknown permission com.android.browser.permission.READ_HISTORY_BOOKMARKS in package com.billnapier.android.livebookmarks 10-02 15:56:35.708 W/PackageManager( 71): Unknown permission android.permission.READ_HISTORY_BOOKMARKS in package com.billnapier.android.livebookmarks
The second one makes sense, since that name has gone away. But I can't figure out why the first one would show up, since that permission should exist on the phone. anybody got any clues? I can't reproduce this on my phone, so it's kinda hard to debug.
View 2 Replies
View Related
Nov 24, 2009
Some of my users are reporting force closes. Does anyone have some ideas about how to track these issues down when I can't reproduce them in the Emulator or on my Hero? This is my app btw if anyone wants to logcat it for me:
http://aliceonandroid.wordpress.com/
View 5 Replies
View Related
Jul 5, 2010
I used Handcent for a while and I really liked it, however you can't send MMS using it for whatever reason which is a big deal breaker for me.I uninstalled it and went back to the original messaging application, but now it just closes randomly.Like I'll open it and it will close instantly. Then I open it again and it works fine.Other times it will open fine, but then I'll try to open up an conversation and it closes automatically, then when I open it again everything works fine.It is very annoying. It just closes out to the home screen. I've deleted all my existing messages and I've tried resetting my phone, nothing seems to help.
View 2 Replies
View Related
Sep 12, 2010
I am new to android development and I have made this using help from a website. The XML files dont have any errors,Here is my Main java code: package com.CFConverter;
import android.app.Activity; import android.app.AlertDialog; import android.content.DialogInterface; import android.os.Bundle; import android.os.Message; import android.view.View; import android.view.View.OnClickListener; import android.widget.EditText; import android.widget.RadioButton; import android.widget.Toast;
public class CFConverter extends Activity {
/** Called when the activity is first created. */ private EditText text;
@Override public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
text = (EditText) findViewById(R.id.EditText01);
} //This Handler is called when we click the button01.
public void myClickHandler(View view) //passing the current view {
if(view.getId()== R.id.Button01) {
RadioButton celsiusButton = (RadioButton)findViewById(R.id.RadioButton01);
RadioButton farhrenheitButton = (RadioButton)findViewById(R.id.RadioButton02);
if(text.getText().length()==0) { Toast.makeText(this, "Please Enter a Valid Number", Toast.LENGTH_LONG);
return; } float inputValue = Float.parseFloat(text.getText().toString());
if(celsiusButton.isChecked()) { text.setText(String.valueOf(convertCToF(inputValue)));
// calling function to convert } else {
text.setText(String.valueOf(convertFToC(inputValue)));
} return; } } private float convertCToF(float fahrenheit) {
return ((fahrenheit - 32) * 5 / 9);
} private float convertFToC(float celsius) {
return ((celsius * 9) / 5) + 32;
} }
View 3 Replies
View Related
Sep 11, 2009
We have had a couple users on the myTouch phone have issues in our application. It apparently is force closing on them. I am not sure of why it is, and the 1.6 SDK is not out yet. Has 1.6 been released into the wild? If so, do you know where I can download the image for my G1 dev phone to test w/?
View 7 Replies
View Related
Jan 20, 2010
I have the Motorola droid. I can see my inbox but when I try and open an email the app force closes. Anyone else had this problem?
View 1 Replies
View Related
Aug 1, 2010
I have a Service with a MediaPlayer which streams audio from the Internet but when I press the Home button and it goes back to the home screen it Force Closes. It's strange though because it works perfectly in the emulator and sometimes it doesn't Force Close on my phone (G1), when I've just turned it on.
This is my code:
CODE:............
Log:
CODE:....................
View 1 Replies
View Related
Jul 5, 2010
Would anyone have an idea as to why an app would work on almost every phone that has 2.1 but not the Desire?
One of my apps uses voice input and the Desire is the only phone that force closes when the voice prompt comes up.
The worst part is that I don't know how to test this, I don't have one or know anyone who does.
I finally found out that HTC disabled voice in the Desire and you have to do a work around to install it.
So if you are relying on voice input make sure you use the code in the google example to catch the error:
CODE:......................
View 1 Replies
View Related
Sep 13, 2010
I'm attempting Google University Android lab1 you are asked to change a TextView's text content according to the value passed via the Intent from another activity.
I tried out the rest of my code but...why does my app force close when I add the "tv.settext(...) line"?
CODE:...................
View 1 Replies
View Related
Nov 4, 2010
My app works when GPS is disabled, but FC's when starting while GPS is enabled. On a cold start it offers the option to turn on the GPS. After doing that, pressing the back arrow button it returns to the app activity (although the GPS icon is not visible in the status bar, on a side note, how do I get it to display here?).
I exit the application by pressing the back button or using the menu option whilst GPS is still on.
Now, when I try to start the app, it FC's. The blinking GPS icon appears behind the FC message and disappears when I acknowledge the FC.
Here is the code:
CODE:........
And this is the logcat from eclipse:
CODE:........................
View 1 Replies
View Related
Oct 15, 2009
I spent a month stocking my SugarSync folder full of files and entertainment for my big vacation. On day one of my trip the Donut 1.6 update came through and now SugarSync force closes constantly, haven't been able to use it since. I've been emailing the developers and they refuse to see a connection (despite several comments in the Market of other users blaming 1.6). Is there a chance it isn't 1.6 and how can I fix this? I've uninstalled and reinstalled several times with no improvement. It was an awesome app when it worked, I'll be damn sorry to have to delete it.
View 4 Replies
View Related
Jun 15, 2010
I'm having an issue linking my wife to her Facebook profile in the contact "people." When she calls her number comes up. After I hang up, I try to "connect with person already in contacts" and it forces "People" to close. I tried to add her manually and it deleted it before my very eyes while I was within "people." I did it using the Google phonebook and not the phone's. Is there any issue with this, and what's the difference between the Google and Phone options (benefits, etc... ?).
View 3 Replies
View Related
May 6, 2010
Essentially my problem is this, I open my Activity. It binds to a local service that "appears" to be connected. I get a force close when I press the back button:
"IllegalArgumentException: Service not registered" when unbind is called in my onPause method...
public void onPause() { super.onPause(); if (isFinishing()) {
if (mConnection != null){ Log.i(TAG,"onPause, mConnection" + mConnection.toString());
mDbS.unbindService(mConnection); }else { Log.i(TAG,"mConnection is null");
} The service is bound in onCreate // bind to our sdCard database using our Service Connection
mServiceIntent = new Intent(this,DatabaseService.class);
if(bindService(mServiceIntent, mConnection, Context.BIND_AUTO_CREATE)){
Log.e(TAG, "service bound"); }else{ Log.e(TAG, "service not bound");
} bindService is returning true.
My Service connection is as follows. onServiceConnected is called and goes to completion. onService Disconnected is never called (presumably because my service is in same process)
private ServiceConnection mConnection = new ServiceConnection() {
public final String TAG = "LoadView.ServiceConnection"; //$NON- NLS-1$
public void onServiceConnected(ComponentName className, IBinder service) {
mDbS = ((LocalBinder<DatabaseService>) service).getService(); .....
stuff not relevant.... Log.i(TAG, "finished onServiceConnected");
//$NON-NLS-1$ } public void onServiceDisconnected(ComponentName className) {
Log.e(TAG, "onServiceDisconnectedCalled"); //$NON-NLS-1$ } };
The only thing I do a little different is that I don't use an inner class in my service for the Binder object - I use a separate class. This is mostly because I have several databases and wanted code I could reuse and set up simply rather than worry about all the ins and outs and memory leak issues.
import android.os.Binder; import android.util.Log;
public class LocalBinder<S> extends Binder { private String TAG = "LocalBinder";
private S mService; @SuppressWarnings("unused") private LocalBinder() {
} public LocalBinder(S service){ mService = service;
} public S getService() { return mService;
} public void finalize(){ mService = null;
try { //TODO reinstate this after Issue 8046 is resolved
//super.finalize(); } catch (Throwable e) { Log.e(TAG,"Unable to finalize Binder");
} } }
View 2 Replies
View Related
Mar 31, 2009
This morning, we updated our app on AM; this was our first update since release of Android 1.1.
In testing, on the emulator and with the signed .apk installed on our handsets, everything appeared to be working fine; however, we uploaded to AM, selected the new CopyProtection option, and published. Wertago disappeared for about 30 minutes, and as soon as it reappeared, we downloaded, installed, and started. Immediately upon starting, we got a force close and were never able to get the app started at all.
We've seen some discussions about similar app behavior experienced by other developers, and there was mention of likely bugs in AM or in the Copy Protection scheme. Has this been confirmed by Google, is there any communication from them about a coming fix, or anything like that?
Here's a little detail about what we gather from the logcat output. Our app appears to fail upon attempting to open/create the database; the relevant line is:
tmpDatabase = instance.openOrCreateDatabase(SEARCH_DATABASE_NAME, Context.MODE_PRIVATE, null);
which throws the sqlite3_open_v2 error.
View 2 Replies
View Related
Sep 29, 2010
I've narrowed down the problem to WebView; my application force closes every time. If I take out the WebView and put in a color change button or something, the case switching works and the application loads. I'm fairly new to the plaform, but I'm (mostly) copying directly from examples here for WebViews.
CODE:........
main.xml
CODE:............
AndroidManifest.xml
CODE:.................
View 1 Replies
View Related
Mar 12, 2009
I've been using Snap Photo since early on, and it was cool. Then I bought Pro. I went through several updates and checked out all the features. I have to say, this application is getting worse with time! Here are all my complaints. All of these problems happen intermittently. I can never seem to reproduce the problems at will, but they've all occurred multiple times.
1. Saves corrupted pictures. This is the worst! You take a pic, it looks good on the screen. You have auto-save turned on, so it just starts saving it, and shows the spinner. Later you go look for your photo in the Pictures app and there it is with a broken-looking, gray icon instead of a thumbnail. And now it's too late to try again. This is a complete deal breaker for me. If you can't trust the app to save a photo 100% of the time then it's useless!
2. Takes a LOT longer to save a photo to the SD card than the regular photo app. I mean after the picture it taken, and the still image is on your screen, and it's showing the spinner icon as it saves. You have to wait at least 5 seconds for it to finish saving the pic. The regular app does it in two. It's probably using its own shoddy code to compress the JPEG file. Hence why you can change the quality, and why it screws up sometimes and saves a corrupted pic.
3. The app stops listening to any input at all. Several times I would be waiting for the perfect time to take a pic and would click the button nothing. Click it again Nothing! Click the on-screen button. Nothing! Press the back button to leave the app and go use the regular one. Won't even quit! I had to use the Home button and leave it running. This is almost as bad as #1.
4. The horizon line feature is a joke. I don't know why you'd want it, but that's beside the point. I would hold my phone on a level surface, like my coffee table, press the calibrate button, and the line would still be cocked at an angle by a few pixels!
5. Force closes occasionally for unknown reasons. Try to take a pic crash. Change some settings crash. Useless. It would crash at some point 1 out of 20 uses. Unacceptable.
Good thing it only cost me $1. But it's actually cost me more than that in lost photos and much frustration.
View 4 Replies
View Related
Dec 25, 2009
ProgressDialog during location tasks either won't show or force closes - I have tried everything!
I now have it in a Handler with a full 1 second delay (one method another post suggested) but it doesn't show. I simply am stuck. Threads are usually force closing when I use those methods.
View 6 Replies
View Related
Jul 9, 2010
i created a custom layout where i have a couple of LinearLayout in a ScrollView. Problem is when i set my SetContentView to my custom Layout (when the application starts), the emulator gives an error and force closes! i don't know why. i have tried with another custom layout or set it to main and it seems to work fine.
View 1 Replies
View Related
Oct 1, 2009
Almost all our users complain that after upgrading to the newest version of our "Camera Pro" app, either the app crashes or the icon is not showing up anymore in the home screen. The problem seems to be gone after deinstalling and reinstalling the app. How can it be possible that the icon is gone? This is the first version we used zipalign on, can this have something to do with it?
View 10 Replies
View Related
Jul 26, 2010
I am trying to write the system setting using:
Settings.System.putInt(getApplicationContext().getContentResolver(), Settings.System.WIFI_SLEEP_POLICY, Settings.System.WIFI_SLEEP_POLICY_NEVER_WHILE_PLUGGED);
But it force closes my application. Any Idea? My has user following permissions:
<uses-permission android:name="android.permission.WRITE_SETTING"/>
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/
View 3 Replies
View Related
Nov 19, 2010
I'm trying to bring up the standard window for Bluetooth Settings (with Device name, Discoverability etc). However, general approach with startActivity(intent) ends with NullPointerException pointing to BluetoothSettings.java onCreate:135. Checking with the Android code, I've found that at line 135 they get some extras from the intent. So I prepare the same extras (names I've found in android core BluetoothDevicePicker interface) and issue it -- the same effect with NullPointerException. Might be the wrongs names of the extras I prepare? So is there a way I can see those extras (with names especially) from the intent the system itself submits when I open Bluetooth Settings manually acting like a user. Code...
View 1 Replies
View Related
