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 ?
View 2 Replies
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 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 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.
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 View RelatedI 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 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.
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.
I'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.
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 RelatedI posted a question yesterday about determining when an app is being finalized vs destroyed for screen orientation change. Thanks to the answers I received I was able to resolve my problem with the screen orientation change. However, I am still running into a roadblock.
This app I am working on logs into a website with an HttpClient. As long as the app remains in memory the HttpClient will retain the cookies from logging in. However, once it is killed, it would need to log in again.
My question: How can I determine when the app is being killed from memory so I can set a boolean to false telling the app it has been removed from memory so the next time it starts it will read this and determine is must log in again? Or is it possible to serialize an HttpClient and put that in the savedInstanceState bundle? May extract the cookies from the client and put those in the savedInstanceState bundle? Is there something I'm completely missing here maybe?
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 am relatively new to the Android world and am having some difficultly understanding how the whole screen orientation cycle works. I understand that when the orientation changes from portrait to landscape or vice versa the activity is destroyed and then re-created. Thus all the code in the onCreate function will run again. So here's my situation: I have an app that I am working on where it logs into a website, retrieves data, and displays it to the user. While this is all done in background threads, the code that starts these threads is in the onCreate function. Now, the problem lies in that whenever the user changes the screen orientation, the app will log in, retrieve the data, and display it to the user again. What I would like to do is set a boolean that tells the app if it is logged in or not so it knows whether or not it must log in when the onCreate function is called. So long as the app is in memory the HttpClient will exist and contain the cookies from logging the user in but when the app is killed by the system those will go away. So I would assume that I need to do something like setting the logged in boolean to false when the app is killed but since onDestroy is called when the screen is rotated how is this possible? I also looked into the finalize function and isFinishing() but those seem to not be working.
Shorter version: How can I distinguish between when an app is being killed from memory from when an activity is being rotated and different code for each event?
Is 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 created a sql lite database with the following columns:
static final String dbName="demoDB";
static final String tableName="Employees";
static final String colID="EmployeeID";
public void onCreate(SQLiteDatabase db) {
// TODO Auto-generated method stub
db.execSQL("CREATE TABLE "+tableName+" ("+colID+" INTEGER PRIMARY KEY AUTOINCREMENT, "+
colName+" TEXT, "+colAge+" Integer);");
I want to select all the records in the database like this and display them in a gridview:SQLiteDatabase db=this.getWritableDatabase();Cursor cur= db.rawQuery("Select "+colName+", "+colAge+" from "+tableName, new String [] {});String [] from=new String []{DatabaseHelper.colName,DatabaseHelper.colAge};
int [] to=new int [] {R.id.colName,R.id.colAge};
SimpleCursorAdapter sca=new SimpleCursorAdapter(this,R.layout.gridrow,c,from,to);
GridView grid=(GridView)findViewById(R.id.grid);
grid.setAdapter(sca);but i receive the following exception:java.lang.IllegalArgumentException: column '_id' does not exist.the db table does not have a column with name '_id'so what is wrong with this code
Im looking for a wake-up app that speaks messages, preferably notes or arrangments from google calendar. It should say something like "good morning <name> You have an appointment eight o'clock in the lab according to google calendar".
View 1 Replies View RelatedI need to cause the display to light up programmatically. Is there an established way of doing this?
View 4 Replies View RelatedI have a requirement to wake up my application upon receiving a particular formatted SMS or App directed notification from server.My application is in dead state. Whenever the device receives a event may be a SMS in a particular format OR some notification(eg app directed notification from server), android OS will start my application.Its possible in Windows Mobile and BREW.Please let me know if its possible in Android and how.
View 11 Replies View RelatedI would like to know the way to know when the user are using his phone.There is intent Boot_completed, but it's just at beginning. I have to know when user take it's phone, press a key to use it.Any idea?
View 2 Replies View RelatedI have an application with notification. I want my notification can wake the device up when it goes off but the device is asleep. Could anybody tell me how to do by some code?
View 4 Replies View RelatedI need to use a wakelock to hold the screen active while its required. I was recommended to use a service which I have been trying but on the onDestroy I am getting "wl cannot be resolved".
Code below:
CODE:...............
Looking for a great app that will allow me to selectively turn off anything that would beep or ring during the night but perserve at least two things:
1. Phone - in case the family has an emergency.
2. Alarm - so I do not lose my job.
Facebook, tweets, reminders, etc. need to be turned off.
Often my mobile network is turned off and I just use a Wi-Fi hotspot.
If the phone is not plugged in, the Wi-Fi connection will go to sleep after some length of inactivity.
I could be wrong, but a call to ConnectivityManager.getActiveNetworkInfo().isConnected() does not wake the connection.
So, what is the best way to wake the connection?
In general, I'm looking to write an isConnected() method which will return true/false, optionally blocking returning until a wakeable internet connection is awoken.
I am using the factory Alarm Clock on my Inc. It works okay but if my phone is off, the alarm will not wake up the phone and sound alarm or at least the alarm going off would work for me.
On my BB Curve even if the phone was off the alarm would go off at the set time and the phone would turn on. Kinda nice, only downfall is only had 1 alarm where as Inc has a few.
With the marginal battery life on this thing I sometimes turn it off to charge when going to sleep at nite and do a few bumps in the morning. Problem is the alarm doesnt go off if the phone is off.
IF the factory phone alarm does not do this does anyone know of one that does? Perhaps in Market?