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
Google+ 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 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 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 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:..................
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'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 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() ?
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 RelatedI have been noticing that the Calendar is always at the top of the partial wake usage when I check it in spare parts. As of right now my phone has been unplugged for 3 hours and the calendar has held a 30 minute partial wake lock. The second on the list is the Android system which has only held a 4 minute partial wake lock. Is this normal for the calendar to hold a partial wake lock like this? I heard about the Flickr bug but I do not sync my account with Flickr and never have. I'm not even syncing my calendar with Google currently.
View 5 Replies View RelatedMy mail cal and contacts sync via my Google account.One of my Google calendars On phone only partially sync. I go to the cal on internet to verify the missing events. From inside the cal app and phone settings I run the refresh.Am I forgetting something in the phone settings?
View 7 Replies View RelatedI'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've got a desire and handcent has been pretty good to me so far. the latest update has things a bit more stable (or so it seems at least) when sending group texts, however,i woke up to find my phone had 3 new text messages..but the phone battery went down from 100% to 83%! i know it's shocking but i got up at 2pm haha today and i got the texts at intervals of 8am and 11am. anyways i'm pretty sure it wasn't any other app as i usually lose about 8-13% at most. i checked the *#*#4636#*#* and in 'partial wake up' battery usage, it said handcent had been on for 4 hours! i know the phone can still be awake even if the screen is off but my settings have always been to not turn on screen when receiving a new message. i'm guessing this problem is because of the message popup staying active? i'll see how this fairs when i wake up tomo morning and if i get any texts..
View 7 Replies View RelatedI remember hearing that charging slightly, but not letting it charge all the way is dangerous to the battery. It this true, or is can I let my battery charge a little and then unplug it without any problems?
View 12 Replies View RelatedWhen I go to the default contacts from the home screen I can see all of my contacts, including a lot of duplicate entries where one person will have 2 contact cards, 1 with a plain phone number, and 1 with their number labeled "mobile" (... through research found that the plain-numbered versions are probably simcard saved contacts, which can only contain 1 number per contact)all the apps that use the contacts (ie. hancent) refuse to recognize contacts saved in the sim format, so when i get a text from these people it just comes up with their number.All my contacts look fine in Gmail on the web and I even did a "merge contacts" command on duplicates to try and solve the issue. Looks fine on the web but my phone still has all these dupes, any ideas?
View 5 Replies View RelatedPartial multitasking and folders. Wow, so ground breaking.
View 49 Replies View RelatedI remember seeing somewhere that one of JB's new features is the ability to only download the parts of an app that changed for an update instead of downloading the entire app again to save data. I'm on a Bionic with the 232 ICS leak and just watched a 45 MB app update download only 13 MB and then successfully complete the update and run. Is this a feature of ICS now too?
View 3 Replies View RelatedI'm getting wake times near 100% with this ROM and I don't have the first clue why. I wiped and installed properly, and I have autokill set to optimal. Not runinng setCPU or anything, and I've never had this problem before so I don't think its an app.
If anyone could help, I would REALLY appreciate it. I tried dc2.05, but now I have the no audio issue on phone calls from this ROM, so I had to switch back for the fix -.- Really frustrated and really need a working ROM + phone =
AlwaysFlash seems to be the problem, uninstalled and wake time seems to be staying low under all circumstances.
The accelerometer turns off when the screen is off. I'm guessing this is a bug but I haven't seen it logged. Am I missing something?
Perhaps the power management features need some improvement - the ability to specify what components are needed during a partial_wake_lock so that power can be conserved as efficiently as possible.
BTW, there is a bug logged noting that onSensorChanged() continues to be called for the orientation sensor (during sleep) but the values are not being updated.
I have a vanilla Hero. Since I bought it (around 2 months ago), the awake time has NEVER been under 100%. I installed the Modaco 2.9 ROM yesterday (which I highly recommend; my Hero is now much faster) and it's STILL 100%.
Spare parts tell me that the culprit appears to be 'Android system'.
I'd like to reduce my wake time if it's at all possible.
I'm aware of the messaging app/dialer issue; that's not what this is, since I'm using CHOMP sms and it's still an issue.
So this is Ground Shattering news for anyone having sleep issues. If your Hero is reporting 100% awake status, you'll need to find out what the culprit is. Until today I had only known to remove and install apps one by one. A developer just brought my attention to the app Spare Parts. Download Spare Parts from market, open it,>Battery History>drop down menu default is CPU Usage, select and change to partial wake Usage. This will show which apps are keeping phone from sleeping.
View 8 Replies View Related