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
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;
} }
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:.................
Regardless of the launcher when I try to add a widget and the list is about to show up I get a force close from the Settings app. Im assuming that the Widgets list is part of the settings app but I don't know what I can do to fix it. I've tried:
1 - Using Clockwork to fix permissions.
So I rooted my inc using unrevoked 3 beta. I had upgraded to 2.2 using the leaked update.zip. I installed cyanogenmod, didn't like it, and did a nandroid backup restore to get back to sense. I then installed hydra kernel 1.15. I went back to the stock kernel thinking that that might be it, but to no avail. Now, after turning my phone on, the following screen pops up 5 or 6 times:
I'd be willing to totally wipe my phone and start new. (I can reinstall apps with titanium after I reroot).
I am trying to display the image on the ImageView object. But the setImageResource fails to display the image. Here is my XML file looks like:
<?xml version=*"1.0"* encoding=*"utf-8"*?>
<LinearLayout xmlns:android=*"http://schemas.android.com/apk/res/android" *
android:orientation=*"vertical" *
android:layout_width=*"fill_parent" *
android:layout_height=*"fill_parent"*>
<FrameLayout
android:orientation=*"vertical" *
android:layout_width=*"fill_parent" *
android:layout_height=*"fill_parent" *
android:layout_weight=*"1"*>
<ImageView
id=*"@+id/batteryLevelview"*
android:layout_width=*"wrap_content"*
android:layout_height=*"wrap_content"*
android:layout_gravity=*"center"*/>
</FrameLayout>
</LinearLayout>
Here is my code:
@Override
*public* *void* onCreate(Bundle savedInstanceState) {
*super*.onCreate(savedInstanceState);
setContentView(R.layout.*main*);
ImageView batteryLevelImage = (ImageView) findViewById(R.id.* batteryLevelview*);
batteryLevelImage.setImageResource(R.drawable.*notconnected*);
}
Since few days ago, com.htc.bgp has been force closing on my HTC Hero. I have tried pretty much any remedy I have found on the internet, but it still bugs. Here's a list:
-Hard reset
-Deleting caches from ALL of the apps
-Deleting the HTC Sense app on Facebook.com (with hard reset)
-Turning off Facebook sync (this DID work, but losing functionality that worked just a few days ago kind of sucks).
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.
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/
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 RelatedI 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:....................
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:......................
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:...................
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:........................
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 RelatedI'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 RelatedEssentially 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");
} } }
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.
I have a replacement incredible, but over the last week I'm getting more and more force closes than I did with the first one.
View 3 Replies View RelatedI'm working on this new app, and it's force closing before it even opens, why it's force closing? (I've tried this app on my samsung transform and my motorola xoom yesterday, both worked, and them i added the image button inplace of the regular button, and now it won't work. here are my files;
Main.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:orientation="horizontal" >
<EditText
android:id="@+id/editText1"
[code]...
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.
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.
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 RelatedAlmost 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 RelatedI just got my Legend today. Had many problems getting it to work on Tmobile US. Finally got it working, but now I can not personalize it. Everytime I go to Menu-Settings-Personalize- either Scenes, Home wallpaper or Lock screen Wallpaper I get a Force Close. My Sotware information is:
Firmware version
2.1
Baseband version
47.23.35.03U_7.05.35.03
Kernel version
2.6.29-00980ffd
Build number
1.11.997.0 CL128574
Software number
Unknown
Browser version
Webkt 3.1
I've had this phone for about a month now. No problems whatsoever, until the other day. My phone was turned off. Then, it "magically" turn on ans started ringing. I turned my phone back off for a while. Later, I turned it back on and the second the home screen pops up, like 10 force close screens pop up. I can't text, internet, nothing. No settings either. I click the phone tab at the bottom and another force screen pops up, same as everything else. It also shows I have no signal at all, when normally I have almost full bars. A few days prior to this, my phone would phase in and out of service for no reason.
View 7 Replies View RelatedI figured I might try starting something up for those who are having problems with Launcher Pro. It's a great home replacement and has far better functionality than Sense does IMO. The only issue is that it seems like some people are getting a lot of FC's.
I had a good week long run without any FC's, and then after an upgrade it seems like they're back.
If anyone has found any malicious widgets or apps that don't play nicely with LP, can you please post them up here?
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"/
Anyone noticing a ridiculous amount of force closes on LP+ while running CM6? I originally was on the newest "stable" build, go ta lot of FCs, so updated to the 9/25, still getting the FC's. Then went back to the stable one, updated LP in the market, and still getting the FC's.
View 6 Replies View RelatedA couple days ago I flashed the 2.1 icon pack, used MetaMorph to apply a theme and ended up getting force closures. I did a wipe and restored my last nandroid -- no luck. Then I restored with the RUU and put Fresh 1.1 on my phone. I want to switch to MoDaCo 2.2 but when I do I'm getting those force closes again.
View 1 Replies View Related