My app requires alerts at certain events, which are very likely to happen while the screen is off. It captures those event perfectly, however, I'm struggling to hide the T-Mobile screen lock after I've acquired wake lock from the PowerManager. I've tried broadcasting Intent.ACTION_CLOSE_SYSTEM_DIALOGS, however, that seems not to work.
View 2 Replies
just wondering if there is an app that makes a sound when ive done my patteren correct and unlocks my phone? some people usually have their phone say something like "Droid" just wondering if theres an app for that, thanks for reading
View 3 Replies View RelatedWhen I use wake lock to screen at the specific time on the device as follows code. But every time I release this wake lock, the screen will force to close. I think it must to release the wake lock, or screen will always on. It's wasting power. Does anyone knows how to release the screen wake lock and don't need to close the screen?
View 2 Replies View RelatedNeed some help with phone locking behavior, good peoples. here's what i'd like to end up with:
1. always wake based on volume OR power button
2. when on phone - no locking at all, (additionally wake based on orientation like is done currently)
3. some sort of "lock phone" widget on home screen for manual lock
4. auto-lock timer set to say...5 minutes (longer than sleep timer)
5. sleep/screen-off timer set to 30 seconds
6. disable the slide lock (sense UI?) and only use the pattern lock. why do i have to power button wake, slide unlock, then pattern unlock my phone after it goes to sleep after 30 seconds, it's ridiculous! i want to pick it up press a volume key and put my pattern in - after 5 minutes. before 5 minutes i want to just pick it up and wake it unless it was manually locked.
I'll root it if that's what it takes. this is pissing me off daily.
My wife's Eris will frequently not allow her to open the lock page. It's like the screen becomes totally unresponsive. There is no lock-out pattern stored, it's all stock. If someone calls we can use the hard answer button but can't answer a call on the touch screen from the lock screen. The only way to fix it is to pull the battery and restart it. But this seems to be temporary since the problem comes back every few days, but not all the time. The "experts" at verizon told her just to keep pulling the battery every time this happens.
My question to you all is....WTF?
Is there another way to open the lock screen? Like with the trackball or something?
1) I can press a button to 'wake' up the phone to the lock screen, but I may have to press a button 2 or 3 times to wake the phone up. it seems like it's not waking up correctly and on the first button press.
2) Twitter and other notifications 'sometimes' dont happen until I unlock the screen...this COULD be coincidence, but I thought I would throw it out for people.
3) I didnt get a voicemail given on Friday until today, which appeared as a result of me switching off my phone and switching it back on. has anyone else heard of this???
4) I cant figure out a way to stop apps from starting on bootup, such as peep? I use twidroid, so dont need two apps running of the same ilk?? Any help here?
Thanks in advance guys.
Closest thing I can find is Popup Notifier, but not only does it wake up the device, it leaves a ton of popups when unlocked. I would rather have popups on the lock screen.
View 2 Replies View RelatedAny other way than going to recovery and wiping data/factory reset in order to unlock the cell becausei have much important data in my phone in internal sd.
View 1 Replies View RelatedIs there anyway that you can get the screen to "wake" from just touching one of the softkeys and then enter the screen unlock pattern, rather than having to use the dedicated lock button on the side?
It's pretty annoying, especially if the phone is lying on the table and u just wanna look at the screen you cant just mash one of the softkeys.
I'm developing an app in which i need the TCP connection to stay alive. I've implemented a kind of ping/pong system to do this. It works perfectly when the screen is on, but when it goes of the phone stops responding to the pings after a while. I've created a Wi-Fi wake lock but i'm still experiencing still the same problem. Code...
View 1 Replies View RelatedI have a question about alarms used with services with regards to wake locks. The documentation explains the behavior using BroadcastReceivers, a wakelock is held during onReceive(), but doesn't describe the behavior for alarms starting services with the RTC_WAKEUP flag. What is the behavior in this case?
I have an app implementing this, an alarm is created with the RTC_WAKEUP flag that starts a service. The service onCreate() then starts a thread to do some network activity. It seems to work just fine but I just want to make sure that I don't need to explicity hold a wakelock myself.
I'm acquiring a wake lock and apparently, it gets garbage collected in my app at some point with the following error;
code:...........
What is the recommended approach to overwrite the finalize to force releasing the lock or -better- force the GC not to release the lock ?
I have a service which holds on to a wakelock and the code is similar to this,
public class WakeLockService extends Service {
PowerManager.WakeLock wl;
@Override
public IBinder onBind(Intent arg0) {
// TODO Auto-generated method stub return null;
} public void onCreate() {
PowerManager pm = (PowerManager) getSystemService (Context.POWER_SERVICE);
wl = pm.newWakeLock (PowerManager.PARTIAL_WAKE_LOCK, "My Tag");
wl.acquire();
} public void onDestroy() {
wl.release();
}
For past two days, my phone has been restarting randomly. Today it was worse, it kept restarting until I uninstalled the app. I tried to search about this behaviour online and found that too many wakelocks may coz the phone to restart. Can there be any other reason? Is the above code right? Should make wl as a final variable? Does the service call onDestroy method when phone shuts down? I am using a broadcastreceiver to start my service at boot up as well.
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 problem. I am trying to make a broadcast receiver acquire a wake lock so my alarm will wake the phone from sleep mode.
In the broadcast receiver below, the program crashes with "source not found" on line "sCpuWakeLock.acquire(); when the class "AlarmAlertWakeLock" is called by AlarmReceiver.
Any idea what's going on? Is there a better way to do what I'm trying to do?
In one file:
CODE:..............
In a separate file:
CODE:......................
Since 1.5 I've been having partial wake problems. My eris normally will last a few hours in airplane mode or with just wifi on before the battery drops one or two percent. Sometimes, it will drop like 5 percent in an hour with low battery usage occuring, for example, when airplane mode is on. I check spare parts under partial wake usage, and it is usually very high, sometimes 100% after hours. I have to reboot my phone to fix these problems.
View 2 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.
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.
After noticing my battery was draining quickly, and then after reading this thread, I installed Android System Info to see what was draining my battery so fast. I notice that whenever I would turn on WiFi, the phone will never go to sleep , regardless of what I set the WiFi sleep policy to. After turning off WiFi, the battery still drains heavily.
The WiFi will shut off after 15mins (if you set it to "When screen turns off" or "never when plugged in"). However it seems to keep the CPU on causing it to drain down the battery.
It would seem that whenever WiFi is enabled, the Android system process creates a partial wakelock that does not go away even if you turn off WiFi. The only way to resolve this is by powering off or rebooting the phone.
You can verify this in Android System Info by going into Battery-History-Other Usage-Partial Wake usage to see how much time the "Android System" process holding a partial wake.
I even did a factory reset on the device; and it is still happening so it doesn't appear to be any app that caused the issue. As I said, it works fine as long as I don't enable WiFi.
I already know of two users having this issue, but I'm wondering if folks having battery problems are going through this as well. Is anyone else having similar issues after using WiFi? I'm hoping someone will be able to identify what exactly is putting the wakelock on and we'll be able to find a fix for it. Other than not using WiFi at all or rebooting the phone after using Wifi.
Any Android Agenda Widget users here? Downloaded the newest update today (there were a few updates in succession, I think) and it's causing my Droid X to not sleep and it's showing up as Partial Wake Lock the entire time my phone is on. I emailed the developer, but if others are seeing this, please do so as well. It's probably killing many batteries right now.
View 2 Replies View RelatedI am trying to implement a wake lock for an application.
PowerManager pm = (PowerManager) getSystemService(Context.POWER_SERVICE);
PowerManager.WakeLock wl = pm.newWakeLock(PowerManager.FULL_WAKE_LOCK, "My Tag");
It seems to force close when defining the PowerManager shown in the code above. Whats going wrong?
I need to cause the display to light up programmatically. Is there an established way of doing this?
View 4 Replies View RelatedIs there a program like sms popup that wakes up the screen to alert you to an email?
View 1 Replies View RelatedI have an android application that I want to always be running in landscape mode.
I have the following code implemented to keep the app in landscape mode all the time:
inside my activity in the Application Manifest
android:screenOrientation="landscape"
This seems to launch and keep the application in landscape view for the whole duration of the application. Perfect!
However, if I have the app running on my HTC Aria (Android 2.1) and the phone locks, if I unlock the phone, I see the application for probably half a second and it's in portrait orientation and then quickly switches back to landscape mode. It is quite frustrating because all of my views are jumbled around and it looks unprofessional as you can imagine. This happens in both the emulator and on my real phone.
Does anyone know how to stop the application from temporarily rotating when the phone is unlocked?
I have tried overriding onConfigurationChanged() but with no success.
I have also tried putting setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE); into the onResume() but the app still shows as the incorrect orientation for a split second when the phone is unlocked.
I have a specific problem that has persisted through multiple android devices, through all ROMs and builds. Currently I am on a Verizon galaxy nexus with cyanogen 10.1 (background in case it's more relevant than I believe).
When a timer or alarm goes off on my device, or when I receive a call or text, my screen wakes automatically. I think this may be considered a "feature" in android. However, since my phone is nearly always in my pocket, it means that the screen turns on and often receives enough of a false signal in my pocket to disable an alarm or decline/accept a call. It is very inconvenient and would be alleviated if I could specify that I want my device to turn on the screen ONLY when I press the power button.
I know that others have the same problem from searches on xda and elsewhere, but I don't see solutions (except what looks like a registry hack on some specific devices)
How to get a cover to stop screen interactions while in my pocket, nor do I want to hear about a more elaborate lock screen to keep said interactions from interfering with alarms/calls. The problem is simply that the screen comes on at all with seemingly no way to change the behavior.
Is it me or you fellow incredible owners as well? And also notice when im about to send a text sometime it highlight the send button even tho I didn't press it. Hope they fix this issue soon its kind of annoying.
View 4 Replies View RelatedWhen I receive a call the screen quickly goes blank. What is the best way to keep the screen on and active? This is a problem when your listening to an answer machine asking you to push a certain number to get so-n-so.
View 3 Replies View RelatedWhen the phone is sleep why can't u change the volume without unlocking the screen u know there should be a way to adjust the volume while the phone is locked.
View 2 Replies View RelatedAfter upgraded to 2.0.1, the screen unlock always give me phone vibration. Does anyone know how to disable the energy-spending vibration from Setting? I could disable the 4 soft buttons vibration but I don't know how to disable this.As I remember, there is no such vibration in version 2.0.
View 7 Replies View RelatedSeems like all of a sudden my Moment never sleeps. I can press the red end call button to put it to sleep, but when I turn it back on after a few minutes or even an hour or so later, when I check spare parts it says under battery history 100% running. The screen is not on and shows a small % and since this started the battery life has gotten horrible again. The only thing I see that is running when I look at partial partial wake usage is android system and it is showing the full bar in blue. Does anyone have any idea what can be causing this problem. When I had advanced task manager installed it showed many things running in the background like music, system update, messages ect ect ect and these programs were never opened by me. I thought maybe this was the program that was running all the time because after I uninstalled it the phone started sleeping. But now it is back to staying awake 100% of the time. Any help would be appriciated.
View 4 Replies View Related