I need to load a .so library in my Service onCreate method, but the process just down after System.load. On the other hand, the same code can work in Activity. Are there some differences between activity and service in the way of load .so file.
My code class AisoundService extends Service
CODE:......................
View 3 Replies
At a certain point in my program, when I'm completely done with my service, my activity executes unbindService() and stopService() -- yet the process persists. I can tell that it persists because I run "ps" in "adb -e shell":
CODE:.............
"adb logcat", I can show you the sequence of events:
ACTIVITY: context.unbindService(serviceConnection);
SERVICE: onUnbind();
ACTIVITY: stopService(serviceIntent); & returns true!
SERVICE: onDestroy();
First, my activity calls unbindService(serviceConnection). According to the documentation, unbindService() will "Disconnect from an application service. You will no longer receive calls as the service is restarted, and the service is now allowed to stop at any time." So that is fine, and it is happening.
Appropriately, we see the onUnbind() call happen on the service side. According to the documentation, onUnbind() is called when "all clients have disconnected from a particular interface published by the service." So this confirms the correct service connection is being passed, and that the service is responding accordingly.
Next, my activity calls stopService(serviceIntent), and returns true. According to the documentation, stopService() does the following: "If there is a service matching the given Intent that is already running, then it is stopped and true is returned; else false is returned." Again, this is happening and returning true.
In response, the service's onDestroy() method is called. According to the documentation, onDestroy() is "Called by the system to notify a Service that it is no longer used and is being removed. The service should clean up any resources it holds (threads, registered receivers, etc) at this point. Upon return, there will be no more calls in to this Service object and it is effectively dead."
At this point I expect the process to disappear from the process table. Yet it remains indefinitely. But why?
Also, the process is so persistent that I can bind to it again, and I see that it is the same exact process responding because the PID (process ID) is the same!
If an application begins a Service via bindService or startService, will this Service object ever run from a process different from that of the application? I ask because many Android example projects begin a service and communicate to them using IPC which seems wholly unnecessary considering that, according to the Android Service documentation, "... services, like other application objects, run in the main thread of their hosting process." IPC, AIDL, and the IBinder interface only seem useful if connecting to a Service started by an application other than your own. Is this a correct or fair understanding?
View 1 Replies View RelatedI have two services, both of them lies in separate apk, which run in same process. The two service share same jar file by <uses-library> method. The jar file implement a class, say "test", is a singleton. But I found that two instance of test is created under this case, could anybody give me some tips? I want to ensure it's singleton. Code...
View 8 Replies View RelatedI intended to show a dialog in a service process, then I tried to use the AlertDialog but got the below error message: WindowManager$BadTokenException: Unable to add window -- token null is not for an application The reason seems to be that the dialog is not used in a application context (activity should be fine?) Was there any way that can solve this problem?
View 2 Replies View RelatedDoes anyone know how to, or if it's even possible to check the (foreground process/top of the activity stack) from a service?
View 20 Replies View RelatedI'm designing an android app which will need to do the following steps:
1. User pushes a button or otherwise indicates to "sync data".
2. Sync process will use rest web services to move data to and from the server.
3. The data will be stored locally in a sqlite database.
4. The sync process should provide status updates/messages to the UI
5. The user should not be allowed to wander off to other parts of the application and do more work during the sync process.
The first time the sync process runs, it may take 10-20 minutes. After the initial sync, less data will be transferred and stored and I expect the process to take 1-2 minutes or less. I've been doing a lot of reading about android's AsychTask and various examples of using a Service. But I don't fully understand the design considerations and trade-offs of choosing one design over the other. I currently have my demo project stubbed out using an AsychTask. After watching (most of) Developing Android REST client applications:
http://code.google.com/events/io/2010/sessions/developing-RESTful-and...
I'm left confused the design patterns described here feel overly complex, perhaps because I just "don't get it" yet.
I am attempting to signal my widget such that it receives my new Intent from my service
The code I am using to send from the service is as follows:
CODE:...........................
I have a Service/AlarmManager set to go off ever hour; as seen at: http://github.com/commonsguy/cw-advandroid/tree/master/SystemServices...
The Alarm triggers a Socket connection to communicate with a Web Server. I'm logging the interaction to a file so I can see it later. When I leave the phone on my desk for a day, it seems that more often than not I get a "Network unreachable" error when trying to do any networking.
I believe it is related to how deeply the phone goes into sleep. Is there a special kind of lock I have to hold, or some command required to prep the wireless radio so that it can be ready to access the Internet?
I'm having an issue with inter-process communication with a Service and Notifications
The structure of my application is as follow: - ListActivity (TunnelDroid), once the user presses a listitem it will start a Service. The ListActivity is binded to the service for intra-process communication
- Service (TunnelManagerService): running in the background. This service will add a (permanent) Notification in the statusbar. Using a Handler I sometimes need to communicate with the ListActivity (to show GUI Dialogs)
- Notification: Once this notification is clicked it should open the ListActivity.
To add the action when the user touches the notification I use the following code: notificationIntent.setClassName("net.sourceforge.tunneldroid","net.sourceforge.tunneldroid.TunnelDroid"); Then I use the intent to create the notification.
Unfortunately a new Intent is opened. When I press the back button the original ListActivity is shown. So I have two instances of my same class/list.
How could I make sure the original ListActivity is opened when the user touches the Notification?
It's OK for me if the original ListActivity was previously destroyed, but I cannot have two instances. The problem is that the Handler in the Service has a reference to the ListActivity (PARENT_ACTIVITY), so if another instance is created I have invalid references. I could overwrite the PARENT_ACTIVITY, but then when the user presses the back button I have an instance with no correct link to my Service resulting in a crash/nullpointer.
The complete source can be found here: http://tunneldroid.svn.sourceforge.net/viewvc/tunneldroid/tunneldroid. Attached you can find a drawing of (most of the) inter-process communication. Could someone point me in the right direction?
I'm working on establishing a two-way communication between an Activity and a Service which runs in a different process.
Querying the process from the Activity is no big deal. But I want the process to notify the Activity on events. The idea behind it is this: the service runs independently from the actual app. It queries a webserver periodically. If a new task is found on the webserver the process should notify the activity.
I found this thread over at AndDev.org but it doesn't seem to work for me. I've been messing around with BroadcastReceiver. I've implemented an interface which should notify the Activity but the problem is that the listener is always null since the Broadcast from the process is done via Intent, hence the class that extends BroadcastReceiver will be newly instantiated.
How can I establish a 2-way communication? This has to be possible.
I needed to call a remote service. The service basically fetches data from the network. I am bind the connection once,and then I unbind the connection when the user is no more in that page. Everything works fine.Except that when I call the sa,e remote method for 17th time,it just does not call the service at all.It neither throws the DeadObjecti Exception. I have run out of ideas.Is there anything that I may be missing.
View 7 Replies View RelatedWe have several Android apps and found that the process of uploading apps for each release via Android Developers website slow and ineffective. We like to automate the process. To be more clear, we have automation for compiling and building the apps, it's a matter of uploading them to Android Market and fill in the app details for publishing. This is where we are left with manual publishing.
I am interested to learn how people automate the processing?
Does Google have a web service of some sort for publishing Android App on Android Market?
The app widget documentation indicates that the "widget provider"being a receiver of a broadcast service may not exist (the process) beyond the completion of the call.If I want to maintain state between two broadcast events, such as say widgetProvider.onUpdate(), can I start a local service and leave it hanging there until my widgets are disabled? If I didn't explicitly stop that service will it be loaded again and resumed when the device wakes up.
View 4 Replies View RelatedWhen you do a Thread.currentThread().getId(), is the resulting thread id scoped per process or scoped to the current Activity/Service?
View 1 Replies View RelatedWhat is weird to me is that on the closeup line graph the second half plummets much faster than the first half. But at the same time, the second half doesn't nearly have as many wakelocks (as indicated by the "Awake" bar being basically completely empty during that time.
What the mobile network colours represent but I never had this problem previously with it on all the time so this shouldn't be an issue. GPS is always on. Again, this was never an issue until supposedly now so this also shouldn't be an issue.
Now, the four big drainers are Cell Standby, Android System, Google Services, and Android OS. Cell Standby I know is due to a missplaced decimal point in the framework, so I know that's just false battery recording. Android System I don't have a clue what the problem is, I read somewhere it might have to deal with wakelocks. But it won't tell me what process exactly is causing battery drain. Google Services are well, google services. I don't know what are classified as google services exactly (like this was never a problem before..), and finally Android OS. Again, the battery statistics thing isn't nearly specific enough.
I am trying to reduce the battery consumption on my Note. I have several apps which use the GPS but the gpsd process is being called quite a lot, even when I am not using any GPS app.
Simple question - now that I have established which service is being called (using better battery stats) is there a way to determine which app(s) are using it? GT-N7000
I'm getting beat down with GTALK_ASYNC_CONN wakelocks while on my work's AP.... the specific WL is :gtalk_async_conn com.google.android.gsf.gtalkservice.androidendpoint.... something everyone has been complaining about recently, and I never saw it until recently (now that I got up to 4.1.2 a short time ago.
Is there a way to determine exactly who is generating that WL? It's not related to GTALK, as the WL name incorrectly leads us to believe, but it must be google, and I only see it fire when the Wi-Fi is connected and in use. It's non-existent when I'm on Mobile. It comes and goes, sometimes chugging wake time like its cheap beer, othertimes it's dormant, and I haven't been able to figure out who is using it based on the context of when it occurs.
There HAS to be a log or something somewhere that says process X is responsible.
Whenever the memory needs to be reclaimed, the process is being killed by Activity Manager Service in killPidsForProcess. I have a back button in my activity window on right corner of the title bar.
I want to kill the activity completely on clicking the close button. Can I reuse the same function and will it have any major effect? Please help me out in this.
Sometimes the DDMS in the Eclipse not listing the process.
To do the debug in this condition,
1) Is their any way force the DDMS to list the process?
2) Any command to attach the process from the command line?
So, I decided to give Tridents ROM a try about 10-minutes ago.
I used ROM Manager, backed-up my old ROM, then downloaded Velocity 0.2.
Now, my phone will do nothing, it turns on and shows the red Droid eye, then when it's time to go to the home screen I get pop-up after pop-up saying that "The process com.android.phone has stopped unexpectedly. Please try again."
I have no way of getting on my phone at all, what can I do?
I Just installed a new theme (Live Wire) for my Lithium Mod Rom. Don't know if there is a connection, but when I need to update an app, I get the message something like "process android media process stopped unexpectedly" and it will not allow the update. Everything else works well. I have turned it off for awhile, and have done a battery pull.
View 1 Replies View RelatedEvery 5 minutes this error pops up "Sorry! the process android.process.acore has stopped unexpectdly. please try again." It doesnt actually close anything. It pops up even when im not in an app. So it's more annoying than anything.
View 3 Replies View RelatedI'm using Xperia x10 mini. Whenever I try to add a contact to my phonebook, before clicking save this message appears: "The process android.process.acore has stopped unepectedly. Please try again." And I have no other choice but to click "force close"... Another thing is, even though my contacts' names appears in the messages in my inbox, when I click on the phonebook icon, the phonebook is empty...
View 4 Replies View RelatedAre the processes in android asynchronous? If they are asynchronous then how can we conclude when the activity or process is finished or completed its execution.
View 2 Replies View RelatedSo since I got the phone on Thursday, at random, I'll get these popup crash messages, that say "The process com.google.process.gapps has stopped unexpectedly" it has a "Force Close" button, which doesn't seem to change anything other than to acknowlege the message.It will happen at random, sometimes while I'm on the home screen, or sending a text message, but more recently, as I was trying to manage & link contacts. When I searched for this message it seemed to be related to people using Gmail, but I always get this message when I'm doing other things and not even touching my Gmail account.
View 1 Replies View RelatedI bought a new phone, but I can not run it.
I get the following information: "Sorry! The process com.google.process.gaps has stopped unexpectedly. Please try again".
I've searched around the forums (here and SDX forums) and although it seems the few people that had this issue were able to solve it, my case seems a bit different.
It's different because of the people I've read solving the issue, it was a problem with something they changed / removed with gmail / gmail storage or talk / talk storage. And when they cleared the cache or re-installed the problem went away. Also, it seemed that the same people had a problem with downloading from the market...
Neither of the above apply to me, but yet I'm still getting this FC error all the time!
I was helping a friend with their CL14 Moment out of the box...and went from stock 1.5 CL14 to 2.1 DD03 w/Joey recovery to EclairDD10 and v5 root. I then did the streaming media fix, and then the private app (build.prop) fix (all previously done with my phone no problems). I did all of these update right in a row, and after my last re-boot the FC error (process com.google.process.gapps has stoped unexpectedly) started showing up and won't go away.
The only .apk / odex files I removed were the preloaded Sprint apps
Does anybody have any other ideas on how I can get this FC error to stop? I've tried clearing the cache / data for all the mail / talk apps, rebooted, cleared dalvik cache...
Keep getting this message "The process com.google.process.gapps has stooped working unexpectedly. Any thoughts on what this is and how to resolve?
View 3 Replies View RelatedIs there a way to craft a daemon process as to make it "unlistable" to a process viewer?
OR
is there a way to dynamically change a process name?
I'd like to design a security application without having to modify the firmware, if possible (yes I know about "security through obscurity"...).