Android :: GPS Application Gets Killed On Screen Timeout
Apr 9, 2009
I can see on OMAP zoom2 platform, the moment screen timeout happens my application is getting terminated. I have a Google map based LBS application which is running on Zoom. I have implemented the interfaces given in gps.h to libhardware_legacy/gps.cpp .
GPS application talks to android framework and Framework talks to libhardware to get the GPS info. Now I can see that the moment screen timeout happens and the display goes off, my application killed. Actually from the framework the stop interface (hgps_stop() ) gets called on screen timeout.
I am wondring why this is happening, as I am not sending any stop request form my GPS application to the libhardware.
Is it something related to Android power manager, that android Power manager does not know about my application is running?
View 2 Replies
Jun 13, 2009
I have an Android (1.5) application which needs to be constantly running when a button is pressed. So, when a button is pressed I would like the phone to remain on and not want the screen or CPU to time-out.
When another button is pressed I would like the phone to be back to normal and time-out as per user settings.
View 1 Replies
View Related
May 4, 2010
is there a way to set screen timeouts to specific apps? For instance, when running navigation, can the screen time out be set to never timeout just for that app? I only want the screen to stay lite for certain apps.
View 10 Replies
View Related
Dec 8, 2009
I created application with name Test, and has a class that extends broadcastreceiver that listen for PACKAGE_RESTARTED. I use Advanced Task Killer, and killed the Test application. But when I kill another application, for example gmail, the Test's broadcastreceiver got the intent (I logged it). Does it means that broadcastreceiver will never died?
View 4 Replies
View Related
Sep 10, 2010
I have an application with many forms implemented as separate activities. The form variables are dynamically built based on a database, and there are a ton of variables in the C++ side of the application (accessed via JNI). I don't see how saving out all of this data to persistent storage each time the onPause() or the onSaveInstanceState() of one of these many activities goes into the background is a smart use of processor time. And I don't see how even if I save the local variables for each activity during that time I'd be able to restore a single activity within the context of all the others.
I have set up a service that auto saves the files when I detect that the app has gone into the background. (I set a time stamp when onPause() is called in any activity and then clear the time stamp when onResume() is called on any other activity. If the time elapsed is more than a few seconds, I know I'm not the top activity any longer and the service saves the files).
What I'd like to do is continue on as normal unless the OS kills one of my activities. Since we don't always get notified of this, I thought it would be nice if there were a way to tell the OS that I'd rather you kill the whole app than just one activity.
View 1 Replies
View Related
Jul 29, 2010
On Froyo, we found that some new "Task Manager" apps are now using the ActivityManager.killBackgroundProcesses() to kill apps. When this happens, Intent.ACTION_PACKAGE_RESTARTED is no longer fired. How can I find out that my application has been killed? I tried to start a service, and I do see this message printed in logcat:
W/ActivityManager( 2426): Scheduling restart of crashed service com.example.android.apis/.app.RemoteService in 20000ms
However, the service is never restarted as advertised, if the app is killed using the killBackgroundProcesses API. (If I go into adb shell and kill the service process, the service will indeed be restarted ...) This looks like a bug anyway, because the notification created by the app is no longer removed like in eclair (the StatusBarService, and a bunch of other system services, depend on the Intent.ACTION_PACKAGE_RESTARTED broadcast).
View 14 Replies
View Related
Apr 9, 2009
After long running the Media|Player (audio mode) the app I'm developing often crashes w/ the following error: > Process android.process.media (pid 14795) has died. > Killing <my app> because provider com.android.providers.media.MediaProvider is in dying process android.process.media
View 3 Replies
View Related
Mar 25, 2010
Currently my application is configured to always receive the CONNECTIVITY_CHANGED action to force an update if the previous update failed because there was no connectivity. What I don't like about this is that the broadcast receiver gets to be called too many times although it is not needed. I was thinking to register my broadcast receiver only if an update failed using the Context.registerReceiver(BroadcastReceiver receiver, IntentFilter filter) method. But I'm not so sure if this is a good idea. I'm concerned that if my application is evicted from memory the broadcast receiver will be unregistered or lost and my application will not be notified about the future CONNECTIVITY_CHANGED actions. The update is done in a short lived service. So if the update fails, the service will register the broadcast receiver just before it ends its execution time. Can somebody explain what happens to my broadcast receiver after the application is evicted from memory?
View 4 Replies
View Related
May 15, 2010
I have two BroadcastReceiver registered. When the app is closed they both fire at the appropriate times and do the appropriate things. If the app is closed then killed (say with an AppKiller), the receivers never receive their broadcasts, and nothing happens. Presumably the same thing happens if the parent app is killed due to low memory, so how do I ensure those broadcasts are fired/received. The API states that even if the app is killed it should fire, does anyone else have experience with this situation? If it helps my manifest is:
<!-- receivers for AlarmManager -->
<receiver android:exported="true" android:label="Shift roster updating calendar."
android:name="com.skooter.shiftroster.backend.service.UpdateCalendar" >
</receiver> <receiver android:exported="true" android:label="Shift roster checking alarm."
android:name="com.skooter.shiftroster.backend.service.SetWakeup" >
</receiver>
and nothing esoteric is going on in the AlarmManager/BroadcastReceivers
View 1 Replies
View Related
Mar 17, 2009
I have created a multithreaded application but it still hangs if the server is unavailable.causes some delay and I believe this is the cause for hanging. But if the TCPClientService Service is executing in its own thread I don't know why this affects the timeout of the main activity.I would be very thankful if anyone could show how to prevent the application from hanging when the server is unavailable.
View 1 Replies
View Related
Sep 18, 2010
I have the screen timeout set to 1 min which works fine until I use the phone. When using the phone the screen times out (and locks) in about 5 seconds. This is a real pain when using voicemail etc and you need to interact with the keypad.
View 2 Replies
View Related
Jan 26, 2010
I posted this in the Support and Troubleshooting forum but didn't get any replies, so I thought I'd post it in the main forum.Hopefully some of you guys/gals/aliens (illegal or not, I don't mind) can help me out with this one.
View 5 Replies
View Related
Dec 13, 2009
I was messaging around today and found where to shut of the screen while charging, but I wanted to turn it back on and can't find where it is? Also before the update I could have sworn there was an option on the screen timeout to set it to never. Now I don't have that option.
View 2 Replies
View Related
Sep 13, 2010
I have one application in android when I run that application it shows that exception
09-13 16:38:25.049: WARN/dalvikvm(269): VFY: arbitrarily rejecting large method (regs=132 count=21332)
09-13 16:38:25.049: WARN/dalvikvm(269): VFY: rejected Lcom/ExtraCharge/Calc;.onClick (Landroid/view/View;)V
09-13 16:38:25.059: WARN/dalvikvm(269): Verifier rejected class Lcom/ExtraCharge/Calc;
09-13 16:38:25.059: WARN/dalvikvm(269): Class init failed in newInstance call (Lcom/ExtraCharge/Calc;)
09-13 16:38:34.883: WARN/ActivityManager(64): Launch timeout has expired, giving up wake lock!
09-13 16:38:34.999: WARN/ActivityManager(64): Activity idle timeout for HistoryRecord{43f8da58 com.ExtraCharge/.Calc}
View 1 Replies
View Related
Dec 30, 2009
I saw a while ago on here an App to toggle screen timeout but whilst screen was on it would dim if not using which I like the idea of. I cannot remember what it was called can anybody help? At the moment I am using 'Toggle Screen Timout' which is great but does not dim.
View 2 Replies
View Related
Aug 21, 2010
I would like to keep the screen timeout set to the default 30 seconds to save battery while the phone is not charging. However, I'd like to increase that to at least several minutes while the phone is charging. I don't want the screen to be always on it just doesn't seem like the best thing for the life of the phone. Could be wrong, it just feels that way.Is there any setting or app that would allow this?
View 1 Replies
View Related
Oct 21, 2010
I was using Google Navigation this morning to direct me to somewhere and the screen kept timing out and locking. This was happening every 10 minutes or so.
Surley this is not meant to happen on a NAVIGATION application where you would expect the screen to stay active all the time! how can i prevent this from happening?
View 2 Replies
View Related
Nov 16, 2010
Is there a way to disable the screensaver while my app is running?
the dimming of the screen is what i mean.
View 2 Replies
View Related
Feb 22, 2010
I have a Nexus One and while using Google Listen to listen to podcasts my screen lock will go into effect. Unfortunately, when this happens, the podcast audio pauses. I can set the screen timeout to a maximum of 30 minutes but some of the podcasts are longer than that.
Is there anyway to have Listen suspend the screen timeout while it is running?
View 1 Replies
View Related
Oct 18, 2010
I will try to be as brief as possible... I have published a very simple android application it's name is "Vib-e-rator PRO". It's purpose is obvious, it can be used as a masssage vibrator or as an erotic stimulator...
My Problem is don't have an Android Phone to test my app in real time.
I have been recieving mixed comments from people. A few users say its working fine. But majority of them complained that the Phone would n quit vibrating even after the closing application.
Later i speculated that when ever the user switched off the vibrator and quit the app it would work as expected. If any user (most of em) directly closed the application ( either through the close option provided in the app itself or by pressing the END button in the phone ) without switching off the vibrator then it would not stop vibrating.
So i added myvib.Cancel() (myvib is the context for Phone Vibrator) in the exit block the close option provided in my app. For the other scenario, when it is closed by pressing the END button in phone, i have no idea how to solve it... So friends please advice me what is necessary to do... The comments i have been receiving from many users of my app is really embarassing....
View 3 Replies
View Related
Nov 3, 2010
So i was busy installing apps and moving them around my screen when i accidentally hit the auto-brightness toggle on one of my newly installed widgets, i went to hit it a few more times to restore my previous brightness, but my screen totally turned off. The phone is still on, if someone calls me i can hear the ring tone perfectly.
I've done some Googl'ing looking for answers but i havn't found anything useful, I have already ordered a replacement fascinate under warranty, but it would be nice to find a solution to save myself 20 bucks on a zagg invisi shield..are there any know solutions or ways to factory reset without using the screen?
The Samsung logo and Galaxy S boot-up are visible, but when it normally shows the unlock screen its completely black
View 7 Replies
View Related
Oct 31, 2010
I've implemented a Service in my android app that starts a timer (using the standard java.util.Timer and java.util.TimerTask mechanism) to do some processing in the background on a pre-defined interval.
CODE:...
The service is started / stopped by my application like this.
CODE:..........................
As long as the phone is active (no screen-timeout occured), the service is running fine, and the Timer is performing its job at the defined interval. Even when I quit the application (using the back button), the timer remains active.
However, as soon as the phone goes into timeout, the timer task is no longer running stable. If I leave the phone in timeout for several hours (at night), I would see that on random occasions (sometimes a several hours interval) the timer kicked in.
Also, when the phone is activated again, all timer runs that have been queued are suddenly executed in one shot before resuming back to the normal interval.
What would be the right way of implementing a timer that continues to run properly, even after the phone has gone into timeout. Should I resort to using the PowerManager and WAKE_LOCKS (as described here http://code.google.com/android/reference/android/os/PowerManager.html), or is there another mechanism ?
View 1 Replies
View Related
Jun 4, 2010
Tried a search, couldn't find anything.Can we turn it off? I checked the phone settings but couldn't find anything.
View 1 Replies
View Related
Apr 30, 2010
I finally had a chance to try the Google Maps turn by turn navigation, and i love it, but i got one problem.
To save on battery, i keep my phone display timeout to 2 minutes. The problem im running into is when the screen times out, it kills the navi and i gotta restart it....very annoying and sucks if a turn is coming up
Does anyone know a way to keep the screen from timing out while either plugged in, or in the Maps app?
View 5 Replies
View Related
Oct 3, 2010
I have had my Wildfire for a few months and am very happy.
Have an issue, my screen does not timeout. I have checked the setting under Screen timeout and is set for 15 seconds but still does not timeout!
Are ther any applications which stop this function working?
View 5 Replies
View Related
Aug 2, 2010
Updated to stock 2.2 using the OTA update just now. Everything seems OK, with one exception - the screen timeout no longer works. Doesn't matter what I set it to, the screen just doesn't turn off.
I do have KeepScreen installed, so I shut off its service just in case it was interfering with something somehow. It makes no difference - the screen just doesn't time out.
View 1 Replies
View Related
Aug 19, 2010
I've always had my screen timeout set at 30 seconds and I haven't installed any app recently that I would think messes with this setting, but twice now in the last two days my screen timeout has gone to "never."
View 3 Replies
View Related
Sep 21, 2010
I did a search but found no solutions to my problem. My screen timeout changes on its own. I usually set it for 30 seconds or 1 minute. Occasionally I notice about 2-3 times a week that the screen never shuts off and when I check my settings it is set at never. Any idea why its doing this?
View 2 Replies
View Related
Sep 23, 2010
My upgrade to 2.2 went very smooth. I do not have many of the issues people are talking about. I have one minor issue. I have my screen timeout set to 1 minute. About 3 to 4 times a day the setting changes all by itself to 15 seconds. Has anyone else had this problem? Or any suggestions on how to keep it set at one minute?
View 3 Replies
View Related
Aug 16, 2010
On my desire the screen does not timeout. I have set it to 15 seconds but the screen always stays on.
View 4 Replies
View Related
