I tried to use VBO on 1.6 Android SDK and get a crash whenever I try to give the VBO id free using glDeleteBuffers. The issue has already been filed here: http://code.google.com/p/android/issues/detail?id=4273
Is there any way of giving a VBO id free, then? Otherwise I'm afraid that I can't use VBO because I might run out of graphics memory/buffer IDs.
View 3 Replies
Has anybody else here had any problems with the dialer app locking up when placing or trying to pick up calls? I returned my phone after the 5th time it happened. Just curious if anybody else has had this problem, as I want to wait until this is fixed before getting another G1.
View 4 Replies View RelatedI have an app that is not in the market place (signed with a debug certificate), but would like to get crash log data, whenever my application crashes. Where can I find a log of why my app crashed?
View 3 Replies View RelatedI am experiencing a crash in my app when I quit (via the back button) out of my Activity. So far as I can tell this is happening in the Android codebase and not mine, but I'm not completely convinced of that.
AndroidRuntime E Uncaught handler: thread main exiting due to uncaught exception
AndroidRuntime E java.lang.RuntimeException: Unable to stop activity {MyApp/MyApp.MainActivity}: java.lang.NullPointerException
AndroidRuntime E at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3097)
AndroidRuntime E at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3159)
AndroidRuntime E at android.app.ActivityThread.access$2400(ActivityThread.java:112)
AndroidRuntime E at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1724)
AndroidRuntime E at android.os.Handler.dispatchMessage(Handler.java:99)
AndroidRuntime E at android.os.Looper.loop(Looper.java:123)
AndroidRuntime E at android.app.ActivityThread.main(ActivityThread.java:3948)
AndroidRuntime E at java.lang.reflect.Method.invokeNative(Native Method)
AndroidRuntime E at java.lang.reflect.Method.invoke(Method.java:521)
AndroidRuntime E at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)
AndroidRuntime E at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
AndroidRuntime E at dalvik.system.NativeStart.main(Native Method)
AndroidRuntime E Caused by: java.lang.NullPointerException
AndroidRuntime E at android.app.Activity.performStop(Activity.java:3575)
AndroidRuntime E at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3092)
AndroidRuntime E ... 11 more
My app is running into the following crash and I'm having a hard time diagnosing it. We have multiple background threads (including a couple pthreads started via JNI that are making calls back up to Java occasionally), but none of them are reporting errors . Any suggestions on how to go about isolating this? There are no symbols in libdvm, so I've been unable to figure out where the stack trace points. This has happened 3 times so far, with the same stack trace each time.
CODE:..................
Android VM crash in a Samsung Galaxy running a code good working with emulator. My code call facebook rest service to get my friends info. But when I get server response VM crash...........
View 5 Replies View RelatedI got a crash with the following stack trace:
CODE:.................
Line 130 in my code is: ...........
What's wrong and what checks can I perform on gesture before sending it to recognize to avoid this crash?
If I physically slide out the keyboard on my Moto Droid A855, it crashes my test app with the stack trace pasted below. I don't understand why? Also, if I start my app with the keyboard out, my app crashes immediately on startup. The app consists of an activity, which contains a viewflipper as the main view layout. The viewflipper contains two linearlayouts..
View 2 Replies View RelatedI got a strange message from a user: he is talking about my application: " >I have been using v.7 on my new Samsung Hero device. >When I updated to v.8 I get a force close every time I try and start it up. It is using 1.5 kernal. I have had to go back to v.7 in order to use this >product which by far is the best one out there.
View 5 Replies View RelatedI built an app to show a ListView with different layout of each row within it. I extend BaseAdapter to construct my own adapter class and override its getView() method. In getView() method, I use
view = mInflater.inflate(mResource, parent, false); to obtain which layout xml file that be needed to generate different layout for each row.
After coding and running, the problem occurs. While I'm scrolling the list, this app crashes and pop-up an warning dialog that says "The application has stopped expectedly. Please try again."
If I use the same layout xml file to enable each row has the same layout, everything is all right. Does somebody has any ideas about that?
I haven't manage all errors on my application anymore. So I would like to know if it is possible to Kill the entire app when it crashes? (when the message "app MyApp crash, force close" appear, I would like the application to be killed when user clicks on "force close")
View 1 Replies View RelatedI have id "@+id/call" in single_item.xml when i use findVewById it (the layout setcontextview(R.layout.main)) .the app crash .how to fix the error
View 2 Replies View RelatedI am busy writing an app and I have noticed that it sometimes crashes, and when it does and I get back to my computer then I only have the stack trace.
Is there a way for me to take a memory dump of the app at crash time?
I want to the procedure to simulate the modem crash in android mobiles
View 3 Replies View RelatedI'm trying to display a map using that rotates according to the phone's orientation. I have rewrite a part of the google sample to use a SensorEventListner instead of a SensorListener.
My Problem is when I try to use the findViewByID() method to display the map my application crashes on start. If I use MapView(Context, String) to create my view it works fine. Did I miss something to use main.xml layout file ? What's wrong with this ?
Here is my code :.......................
I'm trying to create a form like dialog to accept a few EditText and a spinner. Somehow I can display the spinner but then I start implementing the array and setOnItemSelectedListener it crash. Did I do anything wrong?
LayoutInflater inflater = (LayoutInflater) getSystemService(Context.LAYOUT_INFLATER_SERVICE);
final View layout = inflater.inflate(R.layout.generate_pwd, (ViewGroup) findViewById(R.id.generate_pwd));
final AlertDialog.Builder builder = new AlertDialog.Builder(this);
Spinner spin=(Spinner)findViewById(R.id.spinner);
spin.setOnItemSelectedListener(this);
ArrayAdapter<String> pwdTypeArray = new ArrayAdapter<String>(this, android.R.layout.simple_spinner_item, R.array.password_type);
pwdTypeArray.setDropDownViewResource(android.R.layout.simple_spinner_dropdown_item);
spin.setAdapter(pwdTypeArray); builder.setView(layout);
// Now configure the AlertDialog builder.setTitle(R.string.generate_pwd_title);
Activity SplashScreen is the launching activity for my app. It sends a request to my server and gets back a user data it then uses to populate a user object which is a static object. Once it has that it calls the MyMapView activity and finishes itself. A force close occurs when I hit the home button and then open up enough other apps so that Android kills MyMapView to get more resources. Now when I open my app again it tries to start MyMapView and bypasses SplashScreen. There is no user object so I get null pointer exceptions. I have tried to Override the onSaveInstanceState and OnRestoreInstanceState but it seems that those are not available when Android kills the activity. I also tried android:finishOnTaskLaunch with the SplashScreen (maybe this should be put on MyMapView but the article I read said different) and that seems to have no effect. What I would like is for the activity to not restart after Android has killed it. What can I do about this?
View 5 Replies View RelatedLooking at the search results on the internet and on this group,I find several mentions of the problem. Eclipse crashes while opening layout in the editor.
View 2 Replies View RelatedI have been trying to set a new xml layout, when a particular item on this list is clicked.
Am I missing something, because the emulator crashes when clicked?! setContentViewById(R.id.newxml file)
public class intentProject extends ListActivity
{
ListView list;
ArrayAdapter<String> aa;
List<String> data = new ArrayList<String>();
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);........................
I have an app that uses quite a few graphics in it. When I open and close my app repeatedly on my emulator (1.5 - 2.2) it runs fine and by checking the heap I can see everything is being cleaned and gc'd properly. However, when I run my app on an HTC Aria phone (2.1) the app crashes every time I try to re-open it. When I look at the heap I can see that objects are NOT being cleaned up like they are in the emulator. Does anyone know why this behavior could be happening? I did try it on another HTC Aria (a friends) and it crashed the same way as on my phone so I think it's not just isolated to my particular phone. Any thoughts or ideas would be really appreciated on why things are cleaning up properly on the emulator, but not on my phone. One thing to note, is that I DID have it working and gc'ing fine on my phone a few days ago and I didn't change much and now it's not working on my phone so it's a bit of a mystery to me.
View 1 Replies View RelatedIs there any differences between M100S and M110S? My app uses camera component. codes are as follows. So I wonder if app is crashed because of the difference between the devices or my codes are wrong.Code...
View 1 Replies View RelatedI am having difficulties with the lifecycle of the opengl context. While rendering my scene and the user hits the back button, home button or another application opens in front of my application, my app is still running in the background.
So when my application comes to the foreground later on (user relaunches it or the app that was opened on top of it finishes), my application crashes and leaves me nothing but a GL stack trace which i can't properly decipher.
For rendering i use the GLSurfaceView and therefore delegate the onPause and onResume. The crash happens on the first call to glDrawElements(..).
I have tried to reload my resource (geometry/textures etc.) on onSurfaceChanged but with or without reloading... The problem persists.
This behavior can be observed on all AVD versions of the emulator as well as on the G1.
Here is the gl stacktrace i get.
CODE:.............
Does someone know how to simulate service crash in emulator ?
View 2 Replies View RelatedI have made a program that reads in a txt file of the users choice from the sd-card into and edittext window. I am reading in the file using a strings and a vector. This seems to work fine on most phones except on moto droid and g1.
View 2 Replies View RelatedI'm playing around with android, and I'm creating a simple twitter app to test what I've learned so far. But I've run into a problem that I don't understand. I created a thread to fetch the tweets, no problems there, but then added a ProgressDialog to show when that thread was running. Doing so caused a very unusual behavior. If the user rotates from Vertical orientation, to horizontal orientation, program behaves as expected, no problems, but if he then rotates back, the program crashes saying a window leaked.
The problem only happens on a horizontal to vertical layout switch. I know of the issues of if you try to rotate while the dialog box is running, but I've made sure that the dialog box has finished running and dismissed before rotating and it will still crash. Heres my code:
package com.onesmartpuppy.puppytweet;
import java.util.ArrayList;
import com.github.droidfu.widgets.WebImageView;
import winterwell.jtwitter.Twitter;
import winterwell.jtwitter.Twitter.Status;
import android.app.ListActivity;
import android.app.ProgressDialog;
import android.content.Context;...............
I m developing an app.in which service start at boot time. but after some time it goes crash and also it is installing a new apk.. i m not understanding what is the problem..becoz there are so many problems in this Plz take a look at it and help me..
I/DEBUG ( 30): debugged: Jun 30 2010 13:59:20
D/qemud ( 37): entering main loop
I/Netd ( 29): Netd 1.0 starting
I/Vold ( 28): Vold 2.1 (the revenge) firing up
D/Vold ( 28): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
W/Vold ( 28): No UMS switch available
D/qemud ( 37): fdhandler_accept_event: accepting on fd 10
D/qemud ( 37): created client 0xe078 listening on fd 8
D/qemud ( 37): client_fd_receive: attempting registration for service 'boot-properties'
D/qemud ( 37): client_fd_receive: -> received channel id 1
Code...
My game is crashing on the HTC Hero and I have managed to get a user to send me their log. I don't see a Java stack trace at all. It looks like it's crashing in the OpenGL driver. I was wondering how I could go about trying to determine the problem. I was thinking of adding that acra project that sends crash reports to a server but I am thinking it will just send the same that is in this log. I have error checking everywhere so I am really at a lose where to go from here. I even went out and bought a HTC Hero but Canada only has 1.5 for the OS. Code...
View 10 Replies View RelatedI am very new to Android Development. I am trying a sample application and it is generating a button dynamically using Java and it is working fine.
This works fine in my emulator. However when i try do with an XML based layout, my app crashes in the emulator.
Main.XML contents
<?xml version="1.0" encoding="utf-8"?>
<Button xmlns:android="com.testing"
android:id="@+id/button"
android:text=""
android:layout_width="fill_parent"
android:layout_height="fill_parent" />
Code:
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
btn=(Button)findViewById(R.id.button);
btn.setOnClickListener(this);
updateTime();}
Does anyone know why this simple application is crashing because of the XML layout?
Been slowly building my app and now JUnit is crashing regularly with logcat as below.
There are no other real hints. No relevant code as this can happen at multiple points of the code. There are no other errors or exceptions thrown. As far as I can tell there is plenty of memory left and my app does not appear to have any leaks I can find during a run outside of JUnit.
CODE:.....................
I wrote a test case with ActivityUnitTestCase which was working fine.
Now I added a dimensions file (dimens.xml) and using the values with a style.xml.
Here some parts from the dimens.xml:
CODE:..............
The style.xml is in the android manifest.
On the G1 and the emulator the code works fine. In the test case I'm getting a crash.
CODE:...........
From the call stack I can see that this line causes the crash:
CODE:..........................