I am trying to use a service to control a wakelock so I can permanently leave the screen on when my application is running. I create the wakelock and activate it in onCreate() and release it in onDestroy() however I get the error "wl cannot be resolved".
Can someone explain how I can get over this? Code below:
CODE:..................
View 2 Replies
I have a service that acts a download manager, downloading files in the background. I have aquired a partial wake lock while the downloads are going. When the downloads finish, I manually release the wakelock. Because I am paranoid, I acquired the wakelock also with a timeout. The problem I am seeing is that if I have already manually released my wakelock, when the timeout period expires an error is presented to the user (and adb logcat shows an under-locked wakelock exception).
Is there any way to use a timeout (as backup wakelock release in case the app force closes for some reason) without getting this error?
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.
I have a problem with acquiring a WakeLock. It seems not to work. I am trying to acquire a FULL_WAKE_LOCK but neither the display gets enabled nor is my app able to perform tasks.
I am using the following permission: android.permission.WAKE_LOCK
My acquire code looks like this:
CODE:...........
What am i doing wrong?
Added another flag ACQUIRE_CAUSES_WAKEUP ... but no changes in behavior
All i am trying to do is, to play music and to wake my device up upon a certain event. The music is working perfectrly but the device stays black.
The new IntentService in Android 1.5 looks excellent for handling AlarmManager-initiated broadcasts for scheduled WAKEUP work...except I can't see that it uses a WakeLock anywhere, either in itself or Looper/MessageQueue.
Does this implicitly hold a WakeLock that I'm not seeing? Or would I need to create a WakingIntentService that has an active WakeLock so long as there are messages in the queue?
My WakeLock isn't keeping my device awake.
In OnCreate() I've got:
CODE:...............
Then:
CODE:........
The screen turns off before the timer finishes, how can I make the screen stay visible?
mWakeLock is a field previously declared like so: private PowerManager.WakeLock mWakeLock;
My device uses Android 1.6. I would really appreciate any help to resolve this.
I'm just wondering if I do this correctly; I'm programming a notification app which can display a notification when the phone is sleeping
Disable keyguard lock. Aquire a wake lock. show notification. Set alarm for timeout and reenabling keyguard and release wakelock is the user dont touches the screen. 4.1 User touches the screen, and I disable the timer. Do nothing more. Done and done 4.2 User dont touch the screen, so reenable keyguard and release wakelock. Phone sleeps again
Basically I'm wondering about point 4.1 the most. cancel the pendingintent for the alarm, and do nothing more? or should the keyguard and wakelock that are set be dealt with in some way?
I have a signal that puts my app to sleep for a given number of minutes (using AlarmManager) and then wakes it back up.Everything is working except the screen doesn't ever come on.I then release the wakelock when I'm sure that my app is up and running and connected again. However, the screen never comes on! The app only actually comes back to life when I hit the power button to wake up the screen manually.I'm developing on an HTC Hero.
View 1 Replies View RelatedI have a terrible bug in my widget. The widget is waken up using an AlarmManager (the update interval is chosen by users, ranging from 30 mins to 2 hours) to grab some data from the Internet and display it on the widget. I do not hold a wakelock since if the phone sleeps, just let it sleeps. There's no way to update the information since nobody will see it. If I put the phone in the basement (has no wi-fi or cell signal) for about an hour. the phone will definitely not update anything. However, when I get it back from the basement, the cell network could never be recovered again no matter how long I have waited (it just get an X on the cell signal icon on the notification bar) that I must restart the phone. May I know if a partial wake lock must be held on checking network availability?
Find the code skeleton as below:
CODE:.................
I have a service which, when started, does some stuff (like downloading files) typically taking about 2-3 minutes.
If I start this service and then immediately use the power button to switch off the screen, then I would expect the phone, at some point, to fall asleep. But it never seems to fall asleep while the service is still doing its stuff. At least, not on my Nexus One.
I'm not using a wake lock (though I do use WindowManager.LayoutParams.FLAG_KEEP_SCREEN_ON in the activity that monitors the service progress).
So is it true that I don't need to use a wake lock?
I have the following code in Oncreate of my activity:
CODE:.......................
I have a service that needs to write some data to the internal storage using RandomAccessFile. Do I need to use a WakeLock to make sure the data won't get corrupted if the service process gets killed?
View 14 Replies View RelatedI'm trying to implement a times WakeLock in my Application, so this is not a Service.
I want the wakelock to simply prevent screen dimming for 3 min. Looking through the docs, this seems simple enough, but I seem to randomly encounter a Under-Locked exception that I cannot pinpoint.
Here is my WakeLock-related code:
in onCreate: PowerManager pm = (PowerManager) getSystemService(Context.POWER_SERVICE); mWakeLock = pm.newWakeLock(PowerManager.SCREEN_BRIGHT_WAKE_LOCK, TAG); // Adjust time to include user's setting int timeout = WAKELOCK_TIME - Settings.System.getInt(getContentResolver(), SCREEN_OFF_TIMEOUT, 0); if (timeout > 0) {mWakeLock.acquire(timeout);} ...
in onDestroy: if (mWakeLock != null && mWakeLock.isHeld() == true) { try { As you can see, I wrap the release and try to only execute it when necessary as a clean up only. I'm assuming that since I'm aquiring with a timeout, the PowerManager will handle the release in most cases when the timeout expires.
I don't have a copy of the logcat at the moment, but what seems to happen is I get the Under-Locked exception randomly, and at random times (it's not always when WAKELOCK_TIME elapses). The strange thing is that the exception does not point to my code - all the entries point to "internal" Android code.
It's hard to find examples of other people using aquire with timeouts. Any ideas what I could be doing wrong here?
I have a timer that schedule a task to run every 5 minutes. This task send a request to a server, so I need to be sure that CPU is on so that wifi or 3g can be used.
So the first thing I do in my run() method is :
CODE:.........
And the last thing I do in the run() is : wl.release() ;
I would like not to release here to be sure my service will run in the next 5 minutes :
The question is : if the device is already in a sleep state, can I wake up it with my wl.acquire() ?
Is it possible for a program to effectively and efficiently use partial wakelock without burning through a lot of battery? Tango, for example? I'm trying to decide if the partial wakelock usage is worth the video call ability.
View 1 Replies View RelatedI'm developing an sms receiver, and i have included a KeyguardManager and a PowerManager to be able to disable the keyguard and turn on the screen if user would like to. This works great, but only once.
When a message is received, the keyguard gets unlocked and the screen is turned on, and it gives out a sound and vibration. But if i don't read the message right away, but let the device power off by screen time out, and i then receive another message while the last one is not read, the device does not turn the screen on again, and it does not give out a sound or vibration, until i turn on the screen manually, then the sound and vibration comes.
If i close all received messages, then my app is able to disable the keyguard and turn on the screen and give out a sound and vibration when a new message is received.Here is my code that is run when the keyguard should be unlocked and the screen should be turned on.
Code:
private void disableKeyGuard()
{
KeyguardManager km = (KeyguardManager)getSystemService(KEYGUARD_SERVICE);
kl = km.newKeyguardLock("SMSHandler");[code].....
I have a N7 2013 on stock KRT16S, and my biggest wake lock is AudioMix.
I'm rooted, using Greenify, and I even have Google Search uninstalled. I am not using GEL. People suggested turning touch sounds off, and I tried that too, but it didn't work.
what is this AudioMix wakelock? Is this like Audio_Out2 on the Nexus 4? Keyboard sounds or any sounds = wakelock? I also find it odd that considering I use my phone on vibrate 98% of the time, that the on my Nexus 4 and older phones, the speaker turns on when I press any button my phone. I thought system sounds wouldn't turn on? Quite interesting. Even in silent mode, the speaker turns on. I know this because my Nexus 4 speaker used to crack everytime it would turn on. To me that's an unnecessary wakelock that should ONLY happen if you're not in silent or vibrate."
I want to generate a wakelock when my screen goes off and then release that wakelock 20 minutes later. I can't find an app that will do this for me. Is it possible with Tasker and if so, how??
View 2 Replies View RelatedGoogle+ is killing my battery with this partial wakelock. Short of freezing it with Titanium (which does solve the problem for me), how to prevent this from running? It literally runs as long as my phone is on, and is just draining my battery.
On HTC Sensation, S-Off, rooted, using stock ROM (4.0.3)
I'm using Wakelock in my application to prevent the phone from sleeping when the app is visible. The problem comes when there is an orientation change and the system destroys and re-creates the app in landscape mode. If the wakelock timer has expired in the background the system takes the release of wakelock as an opportunity to switch off the screen.
Edit: I should mention that I am setting Wakelock onResume, and releasing onPause - as I understand it, it's necessary to release then to prevent the app from leaking the wakelock. I need wakelock to continue through the orientation change. Below I've outlined a solution to this. Is this the preferred way to handle it, and are there any alternatives?
Create a service which holds wakelock (rather than the activity) and when the activity unbinds the service starts a countdown timer (for say 10 seconds) in which it will release wakelock when the timer expires if the activity does not rebind. If it was a simple orientation change the activity will rebind within that 10 seconds and so maintain wakelock, if it doesn't, wakelock will be released.
I have a service running in the background.I have a background thread that gets a reference to the service from the application's main activity. But when the background thread calls a method in the service to display a toast, I get the "Looper not initialized exception".Why,if I have a valid, bound reference to a Service, does this still happen?
View 4 Replies View RelatedI am getting following message when i try to launch service.Also is there any specific path on file system where we need to place the .apk file which contains my serivce component only.
View 2 Replies View RelatedI am trying to run the sample soft keyboard included in the SDK. I am using the debugger, and the literature says that to use a breakpoint while debugging a SERVICE, I need to include:
android.os.Debug.waitForDebugger();
So here is the portion of the code I modified:
CODE:...........
I have put a couple of breakpoints, at the statements indicated by the comments.
This is what happens: the debugger first stops at the breakpoint1, for a few seconds. But then the service restarts. For the life of me I can't figure out what makes the service to restart.
My service works exactly the way i want as long as i use start and stop and communicate using intents. However my activity needs to change the state of my service as well as retrieving state information.So i thought it would be nice to broadcast some kind of state_changed event from my service and use a binder interface to pull information from the service or change the services state based on user input.This works fine too. The only problem is that my service gets killed when i unbind it just as the documentation says.Is there any way to keep the service alive but still get an interface to control it directly. My activity offers the user a way to stop the service and the service kills itself anyway after it's work is done but i don't want the service to stop every time the activity is destroyed.
View 3 Replies View RelatedI'm confused about whether I need to run my service in a separate process. What are the advantages / disadvantages of each?For reference I'm trying to create an App that uses a service to play [streaming] audio in the background. So which one is better for my use case?
View 1 Replies View Relatedwhat I'm trying to do here is implement something like a peer-to-peer client. Being that, it will start a client thread and a server thread.I know Services themselves run in the main GUI thread, so I'll have to start a couple of independent threads (or Asynctasks?) for each server and client. The only thing I'm not so sure about is if I'll better have 1 Service starting 2 threads, or maybe 2 services, each one of them starting their own thread.
View 2 Replies View RelatedI got an problem on getting the TelephonyManager in my personal service. The code as below: public class MyService extends Service {@Override public IBinder onBind(Intent intent) { return mBinder;}
View 4 Replies View Relatedi have an app that binds to a local service.I want to add a desktop widget that binds to the same service. does my service have to be a remote service or can it still be local?if it can still be local, how can I get at the local binder?
View 2 Replies View RelatedPlease show me how to bind to a Service from another Service on Android.
If you have an image to show how to do.
I am developing an Android app which needs to poll a specific webpage in time intervals. I've got it to the point where it does indeed poll the page on a specific interval, and that interval is specified in a SharedPreference which can be changed by the user in the settings page of the app. But complications arise when network connectivity is flaky.For example, how do I ensure that the Service "wakes up" the network adapter and gives it ample time to connect before polling the page, in the case that the phone was sleeping to save power? This polling action can happen as little as once every 24 hours, so I don't want to miss one action just because the network was out (but turned on a few seconds, minutes, or even hours later).
Or there are times when the web service doesn't respond, or DNS doesn't respond, or what have you, and for any reason it doesn't get a response even though the phone is technically connected. What sort of rule do I put in place to make this retry later, so that I'm not retrying repeatedly when the user specifically turned off their internet but I'm retrying soon enough that if it was just a hiccup, the data can be received soon after the first try?Are there any examples for this type of situation? What is the logic to best handle this?