We have a very simple ViewFlipper widget in a layout. The following trace back happens when it crashes. This does not trace back into our application code at all.
There is a similar bug logged for 2.1 http://code.google.com/p/android/issues/detail?id=6191
We are running on 2.2 and getting this error.
Is this fixed or is it necessary to create a workaround subclass?
CODE:....................
View 6 Replies
I am using viewflipper for fling gesture recognition everything works fine for 2.0 and prior but in 2.2 and 2.1 it throws exception as "java.lang.IllegalArgumentException: Receiver not registered: android.widget.ViewFlipper" below is full debug trace.
CODE:.....................
There is issue on Google related to this bug 6191.
And the solutions mentioned in there seems to work only if your are creating ViewFlipper through code but in my case i am using ViewFlipper in XML which is my layout file and so i cant use the solution mentioned for extending the ViewFlipper i tried using delay nothing seems to work.
Below is my layout code.
CODE:...............................
I have a ViewFlipper in my app.
When my app is running and the phone goes to sleep it works fine.
When I wake the phone up and my app then tries to display again, I get the following error.
I can't figure this out.
CODE:......................
I need to check if my registered receiver is still registered if not how do i check it any methods?
View 2 Replies View RelatedI'm using more than 1 instance of MapActivity in an application that look different from each other. I'm running into an issue sometimes when leaving a MapActivity doesn't unregister it's BroadcastReceiver and going Back to resume the MapActivity page it tries to re-register the receiver again, thus receiving an Exception that Receiver already registered.
Anyone know of a way to tell if a Broadcastreceiver is registered and is listening?
I have been able to register and unregister a broadcast receiver from the java code and know that a broadcast receiver is unregistered (even if it is not done explicitly) on its own as the process that registered it is killed. Now I have a broadcast receiver which has been registered through manifest file and not through the java code, and need to unregister the broadcast receiver from the java code. Since this, i think would need a reference to System context that instantiates the broadcast receiver.
View 4 Replies View Relatedtrying to create a broadcast receiver which responds to system events and change system settings. I don't need any interaction from the user so I don't need an activity and have been trying to do everything through the manifest file. I've put a log event into my onReceive method but it never logs anything so I'm presuming my method is never called. I've tried this with both the 1.5 and 1.6 SDKs. I was hoping somebody could have a look at my code please and let me know if there are any problems.
View 2 Replies View Relatedam developing an app that needs to track incoming calls. I have set up a phonelistener which is launched form a service like so
TelephonyManager tm = (TelephonyManager)getSystemService (TELEPHONY_SERVICE); tm.listen(mPhoneListener, PhoneStateListener.LISTEN_NONE);
This seems to work for a while but then fails to fire after - say an hour. I have tried relaunching the listening in a timertask every 60 seconds but this does not seem to work. Is there a way of keeping a listener alive for a long period of time. I can only assume the system is garbage collecting it.
A service is setup by an activity with startService(service_intent). This service is meant to run 24 hours a day. After some amount of time, 5 or 6 hours sometimes but its not predictable, the service is killed.In the database log, the destroyed message does not show up and the notification #1 is not cancelled. Android makes no attempt to restart the service. The database log will show the startup of the replacement service if I trigger it by visiting the activity. What can I do to keep this service running or at least get it restarted by android automatically?
View 6 Replies View RelatedI have a snippet of code that I'm calling from a service:
CODE:........
What I would like is a way to check and make sure that the registerReceiver isnt already listening before it calls it again. Is this possible?
For example if my snippet of code is in a method, and I call the method 10 times, right now the onReceive method appears to run 10 times.
I have a ViewFlipper with two ImageView widgets. I have set the in and out animation as android.R.anim.slide_in_left and android.R.anim.slide_out_right
Now when the two ImageViews have two different drawables, then the animation is sleek and smooth. But when I set the both the ImageViews to the same Drawable, the screen flickers. Why is this happening and how do I prevent it?
I have a program that monitors incoming SMS's, and I want it to monitor them full-time, so I registerReceiver with a Broadcast receiver that I've created. The problem is, if I want to unregister that receiver, I can't unless I know the original Broadcast Receiver class I registered. This is not a problem if I set it to stop when the program stops, but I want the receiver to keep running, only stopping when the user specifies. EDIT: Or is there a way of "Storing" the Broadcast Receiver class that I've created, such that when onDestroy is called it can be saved and when create is called again it can be pulled out.Is there any way of doing this?
View 1 Replies View RelatedIs there a way to check before sending a broadcast (from a remote service) whether there are registered broadcast listeners? What I'd like to do is to send broadcasts only if there are registered listeners, otherwise make a toast. Does it make any sense?
View 3 Replies View RelatedI am implementing Localytics.com useage statistics in my Android app.
I am still just testing.
I note that just starting my app and then immediately exiting will register two sessions (as they are called by Localytics) in the live statistics.
I have followed the guidelines in Android Integration.
My app consists of a main Class of the TabActivity type. This TabActivity holds two tabs in which I display two other activities.
Like this:
CODE:..............
I instantiate the Localytics object in all three Activities like this:
CODE:............
So, the above code lines are repeated in each of the three Activities. In the TabHost Activity (only in this Activity) I then follow the instantiation with a this.localyticsSession.upload();
And then (only in the TabHost Activity) I have these to finish things off:
CODE:.......
How to make my code generate just one session per app-launch?
I see that multiple broadcasts (ACTION_TIME_TICK, for example) cannot be registered in the manifest, the must be explicitly registered via Context.registerReceiver(). I am having trouble with the ACTION_USER_PRESENT broadcast intent. Specifically, I test on the emulator and my application keeps force closing with the error:
CODE:...................
This is caused by
CODE:.......................
My manifest is fairly simple:
CODE:........
I am essentially attempting to create a Receiver that is awakened as soon as possible after my application is installed. The first time it is awakened, it registers a few listeners, and then it unregisters itself so it is never called again. (I really wish there was an intent fired immediately after your app had been installed, to allow a small bit of setup.
I'm trying to register the phone as a HID device through bluetooth. So far I did the following - Created a BluetoothServerSocket with bluetoothAdapter.listenUsingRfcommWithServiceRecord("Any name", "00001124-0000-1000-8000-00805f9b34fb"). The UUID is the standard one for HID devices. - Paired the phone with a Windows PC - The phone is recognized as "Bluetooth HID device, but I get the error "Device driver software was not successfully installed"
Does anyone know what steps can be taken next to make it work? I think I should register a SDP service record, but I'm not sure if Android Bluetooth API has support for this.
Camera application process dies and restarts again when device is Locked/End Call Key is clicked. Steps to reproduce: 1) Launch Camera application. 2) Click on End Call key(it acts as lock screen when there is no active call) or wait till device is locked. 3) Camera application is paused and surfaceDestroyed callback is not being called. 4) Camera process has died and restarted again. I would like to know why Camera process has died after onPause is being called and restarted again when device is put to Lock state. For all key events like BackKey,HomeKey and Accept Key it is working fine.
View 4 Replies View RelatedI am using "ViewFlipper" for my application. This ViewFlipper includes 5 layouts. I am trying make it that can be changed from current layout to any layout. In other words, it can be changed Layout#1 -> Layout#5 or Layout#4 -> Layout#1 ..etc. How to make it? I used showNext() and showPrevious(). It is not better idea for my case. Can I use ViewSwither instead of this case?
View 1 Replies View RelatedI am trying to create a widget which functions in a similar manner to the new Marketplace widget.The Marketplace widget fades between different views (each view being a sample Marketplace app with a TextView and an ImageView describing the Marketplace app).I would like to mimic this fading between different views behavior. Unfortunately, as is clearly stated in So, how can we mimic this fading behavior?
View 12 Replies View RelatedI am using gesture detector to catch "flings" and using a view flipper to change the screen when this happens. Some of my child views contain list views. The the gesture detector wont recognize a swipe if you swipe on the list view. But it will recognize it if it is onTop of TextView's or ImageView's. Is there a way to implement it so that it will recognize the swipes even if they are on top of another view that has a ClickListener?
View 3 Replies View RelatedI am developing a Music Player and I have a view flipper to control all the artist view, album view, so on and so forth. What I am doing now is that I have list view in each view of the view flipper. However, I do not want to put all my codes inside one activity but rather, to have different activities for each view. Is that possible to implement?
View 1 Replies View RelatedI am trying to use a ViewFlipper and make it act like the home screen(The layout will move with your finger). Check out this for an example. I want to do this with a ViewFlipper that only contains two children so the opposite view should be shown on either side of the current view depending on which way the user moves their finger. This code works but only for 1 direction at a time. This is in onTouchEvent.
CODE:............................
Which ever of the bottom two lines I put last that direction will work correctly but the other will not.
Here is how I set the leftView and rightView:
CODE:............................
Is it going to be possible to set it up so that the same view is shown on both sides of the current view?
I have a ViewFlipper defined that contains 3 views...
CODE:.........
I also have a custom View defined within my Activity...
CODE:........
Some how, I need these linked together so that the 'third_view' defined in the XML layout file needs to be a CompassView, or have a CompassView added to it.
What I can do is drop the 'third_view' from the layout and then add in the CompassView manually..
CODE:........
But then I lose the ability to define other view controls within the layout file.
Can I add CompassView to 'third_view' declaratively?
I need to include multiple images in my Android app. It's like an image viewer/slideshow. Currently I switch between pictures from /drawable-mdpi dir simply with ImageView and adapter, using gestures to left/right. Works but nothing impresive :/
Basically I could use something like Android (2.1) gallery with some image show animation.
1st question: what's the best way to include many (50-100) fullscreen images in App?
2nd: is it possible to use ViewFlipper animations directly to images? or do i have to somehow populate Views?
I need to take the Bitmap of all the Views in ViewFlipper. But it gives me the Bitmap of only the current content on the screen. Is there any way of getting Bitmap of all the Views in the ViewFlipper.
Or is there any other way around to get the Bitmap of all the Views. I have four views and need to load them at the same time and get their Bitmap so that I can resize it and later display with Gallery.
I hope to get a quick response this time around.
I would like to switch to certain views in a ViewFlipper. Currently, I have 6 children inside the ViewFlipper. And I am having some buttons for navigation. It is very much similar to "News and weather" application.
View 1 Replies View RelatedI have a ViewFlipper that contains Layouts.
Is there a way I can hook up a Class to manage each layout seperately?
Kind of like setContentView(R.layout.main); but I'm not sure how to reference the 3 different layouts in code...
Currently my application is configured to always receive the CONNECTIVITY_CHANGED action to force an update if the previous update failed because there was no connectivity. What I don't like about this is that the broadcast receiver gets to be called too many times although it is not needed. I was thinking to register my broadcast receiver only if an update failed using the Context.registerReceiver(BroadcastReceiver receiver, IntentFilter filter) method. But I'm not so sure if this is a good idea. I'm concerned that if my application is evicted from memory the broadcast receiver will be unregistered or lost and my application will not be notified about the future CONNECTIVITY_CHANGED actions. The update is done in a short lived service. So if the update fails, the service will register the broadcast receiver just before it ends its execution time. Can somebody explain what happens to my broadcast receiver after the application is evicted from memory?
View 4 Replies View RelatedI would like to check which receivers are there for a specific Intent yet queryBroadcastReceivers() ignores receivers that were registered in code using registerReceiver() call. It returns only receivers declared in the AndroidManifest.xml file. Is this behavior by design ? Any other way I can get information on *all* receivers capable of handling an Intent even if they where registered in code ?
Had this happened last night for the first time, last time i looked at the phone it was at 66% battery, an hour or so later it was completely dead and would not charge, not even the indicator light came on. Pulled the battery, nothing, switched chargers and still nothing.
Put a call into HTC and we pulled the battery again as well as did the power and low volume toggle reset and it turned on finally, showing the orange light. Did a soft reset again after that to make sure, everything is fine again, but very very strange.
HTC said they've had some of these issues pop up recently for no apparent reason. The problem would have been if the phone didn't come back at all ...