Is waiting for the application to change the content ???

Many methods online, but I have tried many without success, is still stuck in this "is waiting for the application to change the content does not respond.

See:
iOS: Troubleshooting applications purchased from the App Store
Contact the developer/go to their support site
Restore from backup. See:
iOS: How to back up
Restore to factory settings/new iPod

Similar Messages

  • Thanks for the reply to my question regarding sound in iMovie and sending me the online links.  however the online links are impossible to play as they upload too slowly with the result that the playing keeps stopping waiting for the content to catch up

    Thanks for your reply to my question regarding sound in iMovie.  However I cannot follow the links you sent as they upload too slowly and therefore the instructional movie keeps stopping waiting for the content toload.  Surely theremust be a solution for this??
    Thanks in advance
    lolly

    Please continue posting in your original thread.
    With the amount of traffic on these forums it is impossible to chase around finding this.

  • Itune display "is waiting for the application to change the content"

    I don't now why my itune display "is waiting for the application to change the content"??

    See:
    iOS: Troubleshooting applications purchased from the App Store
    Contact the developer/go to their support site
    Restore from backup. See:
    iOS: How to back up
    Restore to factory settings/new iPod

  • Application waits for the thread to finish

    Hi all,
    I have a class let say test that extends Thread.
    In my application i say:
    test Xtest = new test();
    Xtest.start();
    System.out.println("Thread finished");
    I need my application to wait for the thread to finish for it to continue, i.e. in my example print "Thread finished" .
    Can someone help me.
    Thanks in advance for your help.
    Best regards,
    Saadi MONLA

    This should work:
    test Xtest = new test();
    Xtest.start();
    Xtest.join();
    System.out.println("Thread finished");

  • IPhone sync stuck at Step 5 of 5 waiting for the changes to be applied

    iPhone sync stuck at Step 5 of 5 waiting for the changes to be applied

    For me it was stuck. So with the iphone/pad etc plugged in I was having the failings at the last step.
    I got it to work by unticking "Sync this ****** over wifi" and onnly ticking"manually manage music and videos"
    Maybe it gets confussed and I thought I was managing it anyway.
    Anyway - that worked for me, literally did the ticks. Off it goes, now adding 1500+ tunes

  • I have an ipad 4 running ios 7 but i noticed ios 7 on my ipad seems laggy. I already did a factory reset but it seems doesn't change a bit. Are there any solution for this or I need to wait for the next ios 7 update?

    Am I the only one who facing this problem or there someone else. I did a factory reset yesterday but it still laggy. Do I need to wait for the next ios 7 update or what?

    Hi Amish,
    I should have mentioned that I have signed out of the iCloud Control Panel several times and no syncing occurs.
    Thanks for your response anyway. I appreciate your feedback.

  • Should You Buy An iPhone Now, Or Wait For The Next One?

    Great article by HuffPost Tech.
    The most common thing I get asked whenever I tell anyone I'm a tech writer is some version of the question: "Should I get a new iPhone now, or should I wait until the next one comes out?" It is as though my business card should read not "Technology Writer," and instead "iPhone Psychic"
    Not that I am not happy to prognosticate! And in that spirit, here's a look at the questions on everyone's mind: Should I buy an iPhone now? And if not now, when?
    First, let me say that I am fascinated by the peculiar kind of panic that I encounter in people I meet who are deciding on a purchase date for their next Apple phone. I call it the iSenberg Uncertainty Principle: Potential iPhone buyers exist in a constant state of anxiety, perpetually worrying that purchasing an iPhone on any given day will mean that they will miss out on the inevitably cooler version with the mind-blowing new features soon down the road. The Cupertino Sword of Damocles constantly dangles over their heads, threatening to pierce them with unhipness and iShame.
    Here is one solid piece of advice I can offer to help you avoid the Sword: Do not buy any new iPhone until September. Apple has an annual media conference each September, and every blog with the word 'Mac' in the title is reporting that Steve Jobs is going to do his black turtleneck thing and introduce some kind of new iPhone there. The September Media conference is generally used to present the new iPods, but as All Things Digital reports, Apple plans to "commandeer" the conference for its official iPhone announcement.
    Apple is long overdue to release its new iPhone anyway, if history is any indication. Look at this handy little timeline:
    June 2007: original iPhone released
    June 2008: iPhone 3G released
    June 2009: iPhone 3Gs released
    June 2010: iPhone 4 released
    June 2011: Nothing!
    In other words, the 5th generation iPhone is already a month late, so it makes sense that the rumors are swirling. Apple's tardiness can be explained by the fact they've actually already released two iPhones in 2011 -- the Verizon iPhone in February and the unlocked iPhone 4 in June. Their schedule is all screwy, like a traveler trying to get over jet lag. But all signs point to them getting right with a September Apple iPhone release.
    So what jaw-dropping new feature will this iPhone boast? We're hearing that the "iPhone 4S," as it is rumored to be called, won't be the dramatic re-imagining that many of us have come to expect with each new iPhone release. Tech blogThis Is My Next thinks that it will be thinner and lighter, and that it will run on a new chip; the New York Times thinks that it will be the same dimensions as the iPhone 4 but that it will be cheaper. Bloomberg agrees with This Is My Next on the chip and adds that the rear-facing camera will upgrade to 8 megapixels from 5 megapixels.
    Now, even if you're just a normal, non-geek iPhone user, who doesn't care if the rear-facing camera doubles its megapixel count, or if Apple has changed the manufacturer of its data processors, or whatever, you still need to at least wait for the alleged iPhone announcement, and here's why: if history is any indicator, the introduction of a newer iPhone model is accompanied by a drop in price of older iPhone models. When the iPhone 3GS was announced, the price of the iPhone 3G dropped by $100; when the iPhone 4 was announced, the price of an iPhone 3GS also dropped by $100. Even if you know that you're not going to drop $400 on whatever iPhone Apple begins peddling in September, there is no sense in paying more money for an iPhone 4 or 3Gs now when the base price of both seem like locks to drop in two months.
    But before we start fantasizing, how can we be so certain that Jobs is even going to announce an iPhone in September if Apple hasn't so much as indicated such a thing? How do we know that all of these rumors weren't just started by lonely nerds like me and my co-workers emailing each other from our mother's basements, inciting iPhone rumors all on our own?
    Well, first of all, I don't live with my mother; and second of all, the new iPhone rumors have sprung forth from two reliable sources held in high journalistic regard.
    The first is esteemed, award-winning tech journalist John Paczkowski of All Things Digital, who blazed iPhone prognostication trails by predicting back in April that an updated iPhone 4 would be unveiled at the September Apple music Conference and has steadfastly maintained the claim is true through June and into July. In fact, he confirmed as recently as July 5 that a shiny new iPhone looked to be in the early stages of supply chain production, and that people close to the company still believe that the new iPhone would be ready for the Jobs treatment in September.
    So there is Reliable Source One.
    Reliable Source Number Two is the Wall Street Journal, not exactly a one-laptop operation. The paper gives "the end of September" as a target launch date, which squares up with both Paczkowski's prediction of a September announcement and release. This doesn't even mention This Is My Next's separate prediction of a September release, nor 9to5Mac reporting that there are going to be two new iPhones in September, one low-end and high-end. But now we're falling down the rabbit hole and into the basement again, so let's focus:
    There is likely to be a new iPhone in September. It will likely affect the price of all the other iPhones. The iPhones available now -- the iPhone 4 and the iPhone 3Gs -- will probably be cheaper in two months. Unless you drop your current iPhone in a pool, a bathtub or a volcano, do not buy an iPhone until Steve Jobs opens his beautiful brilliant mouth at the Apple conference in early September. When the post-turtleneckian dust settles, we'll have a clearer picture of whether or not this rumored new iPhone is worth the money. And then we can talk about--well, whether or not you should buy an iPhone now, or wait until the next one comes out.
    http://www.huffingtonpost.com/2011/07/12/iphone-release-5-september_n_896345.html

    Apple has two prototypes out testing now.  One is a thinner totally redesigned case.  The problem with it is that Foxconn can't seem to build it.  Hence the delay.  The other prototype uses the existing case, but with updated (read dual core) internals.  If they can get production up by September the first phone will be released and will be the iPhone 5.  If they cannot, then the second prototype will be released as the iPhone 4GS.  

  • Please wait for the group policy client - shutting down issues

    Hi
    I have issues with shutting down machines. When machine is connected to company's LAN everything works fine. However, if machine is connected to VPN - Juniper NC - 1 hour or more it always hangs when it is shutting down. When I shut down the machine
    (verbose mode on), first stage is:
    Please wait for the system Event Notification service. 
    This ends exactly
    after 3 minutes. Next stage:
    Please wait for the group policy client windows 7
    ...is never timed out (even after few hours). Machine never shuts down.
    In Application logs there are always these 4 events when machine is unsuccessfully shutting down:
    6005: The winlogon notification subscriber <Sens> is taking long time to handle the notification event (Logoff).
    4627: The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978650-5B9F-11D1-8DD2-00AA004ABD5E} for publisher  and subscriber .  The subscriber failed to respond within 180 seconds.
    The display name of the subscription is "ISensLogon2". The HRESULT was 80010002.
    6006: The winlogon notification subscriber <Sens> took 180 second(s) to handle the notification event (Logoff).
    6005: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (Logoff).
    Sens is timed out after 3 minutes while there is no 6006 event for GPClient and machine is stuck there for ages (Please wait for the group policy client
    stage). I noticed in System logs that machine always hangs if there is this error
    5783: The session setup to the Windows NT or Windows 2000 Domain Controller \\server for the domain X is not responsive.  The current RPC call from Netlogon on \\machine to \\server has been cancelled.
    I made a group policy log and below you can see part of GPSVC log when machine is unsuccessfully shutting down:
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe58
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls
    GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
    GPSVC(438.1a04) 21:31:24:327 Waiting for user group policy thread to terminate.
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xe10
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Canceling pending calls
    GPSVC(218.c88) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525
    GPSVC(2d4.1cfc) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x71a
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Cancelled pending calls
    GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xdcc
    GPSVC(218.1054) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0x20cc
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(2d4.9c8) 21:31:24:327 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::UnregisterNotification: Entering with event 0xd90
    GPSVC(218.1054) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(2d4.1cfc) 21:31:24:327 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(2d4.1cfc) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
    GPSVC(218.d48) 21:31:24:342 Client_CompleteNotificationCall: failed with 0x525
    GPSVC(218.d48) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
    GPSVC(218.1c04) 21:31:24:327 Client_CompleteNotificationCall: failed with 0x525
    GPSVC(218.1c04) 21:31:24:342 CGPNotify::OnNotificationTriggered: Completenotification failed with 1317
    GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
    GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x2100
    GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
    GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Entering with event 0x1264
    GPSVC(218.1054) 21:31:24:342 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(218.1054) 21:31:24:342 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0
    I tried with signing out from VPN before shutting down machine, I even switched off WiFi but machine still hung. If i tried to get GP results before shutting down machine it takes ages and it is stuck in "Getting the user name" stage.
    Gpupdate /force never updates policy (It stops at Updating Policy...). I tired with installing different hotfixes which did not resolve the issue. I never have any
    issues with logging in, no GP scripts are applied when user is logging off or on, no roaming profiles. The only issue is when machine needs to be shut down.
    I excluded 1 machine from GP and left it on VPN for a few hours, several times. It always shuts down successfully. I applied GP back one by one and the one which is presumably causing an issue is Avecto which adds admin rights when VPN application
    starts (event 100):
    Process started with admin rights added to token.
     Command Line: "C:\Users\User\AppData\Roaming\Juniper Networks\Setup Client\JuniperSetupClient.exe"
     Process Id: 5540
     Parent Process Id: 2252
     Policy: EA-PrivilegeGuardSettings.UK Policy
     Application Group: EA-PrivilegeGuardSettings.Applications Granted Admin Rights
     Reason: <None>
     File Name: c:\users\User\appdata\roaming\juniper networks\setup client\junipersetupclient.exe
     Hash: 27D8463A913A802E555AEEF45717B122249AA993
     Certificate: Juniper Networks, Inc.
     Description: Juniper Setup Client
     Application Type: exe
     Product Name: Juniper Setup Client
     Product Code: <None>
     Upgrade Code: <None>
     Product Version: 8.0.6.48695
    I guess there is a DNS issues when machine is on VPN which leads that GP cannot be applied / updated. Not sure if or why Avecto would have an impact on this. When machine is trying to shut down it still somehow thinks it is connected to DC. What
    I also noticed are several explorer crashes while machine is on VPN.
    Does anyone have same issues? All machines are Dell with Juniper NC (VPN).
    Thanks,

    Hi,
    According to event log, Winlogon process takes a long time to handle logoff event. That's to say winlogon process is waiting for response to logoff.  
    According to your description after, this problem is most probably caused by Avecto. You can try to disable or uninstall it temporarily for test.
    To make further troubleshoot with this problem, you can try to use WPT (Windows Performance Tool) to make troubleshoot.
    http://blogs.technet.com/b/askpfeplat/archive/2013/03/22/troubleshooting-windows-performance-issues-using-the-windows-performance-recorder.aspx
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Windows 7 very slow logon, Waiting for the User Profile Service, winlogon event 6006

    Hello,
    Every so often one of our Windows 7 clients which is not normally having any delay at logon will take a very long time to login. This may be 10 or 20 minutes or up to an hour in some cases.
    Typically the event log will contain entries like
    The winlogon notification subscriber <Profiles> took 572 second(s) to handle the notification event (Logon).
    There is no further information available from Event Log Online Help, nor any additional detail as to why the logon event was so slow. During the delay the user will just see "Waiting for the User Profile Service" on their screen.
    We first started seeing this problem with Windows Vista and if anything the situation has not improved since then. It has never happened with any of our Windows XP users.
    We are currently planning a migration of computers to Windows 7 but stuff like this which has not been resolved in Windows over a 2 year period will stall that migration. The least improvement is to increase the event notification to give a lot more
    information on why the user profile processing has stalled.

    Hi,
    When did the issue begin to occur? Did it occur after installing certain application or applying certain policy?
    To troubleshoot the issue, please perform the following step.
    1. Restart the machine in Safe Mode with Networking to check whether the system can login quicker.
    2. Type “gpedit.msc” in Search box and press Enter. Navigate to the following location:
    Computer Configuration->Administrative Templates->System->Logon
    Please double click “Always wait for the network at computer startup and logon” policy and disable it.
    3. Perform a
    Clean Boot to check the result.
    Thanks,
    Novak

  • I WANT TO BUY A MAC BOOK PRO. MUST I WAIT FOR THE ONE WITH RETINA DISPLAY. WILL THE FACT THAT THERE IS NO CD ROAM BE A PROBLEM. CAN YOU USE A EXSTERNAL CD ROAM ON A MAC?

    I WANT TO BUY A MAC BOOK PRO. MUST I WAIT FOR THE ONE WITH RETINA DISPLAY. WILL THE FACT THAT THERE IS NO CD ROAM BE A PROBLEM? CAN YOU USE AN EXSTERNAL CD ROAM WITH A MAC?

    Apple will gladly sell you a color coordinated and texture matching external SuperDrive to go with your Retina'ized MBP for about $80 bucks.
    Note that those models are completely sealed with no serviceable or upgradeable parts inside. So if you decide to bite the bullet, be sure to customize its guts to your heart's content from the get-go as no further change will be possible. This means CPU speed, amount of RAM and size of the solid state drive. Other external options, like the Superdrive, can be added later.

  • Disk Utility "waiting for the drive"

    I'll be calling Applecare on this, but would like to know if anyone else has experienced this problem:
    I have a 2 month old MBP with the following model Super Drive:
    HL-DT-ST DVDRW GSA-S10N (according to System Profiler, it can write to all formats including -R, +R, DL). From another thread, I assume this is an LG?
    I decided to test the drive - made a short 40 second movie and created a disk image. Upon opening Disk Utility and inserting a DVD (Verbatim +R), I got the following: "waiting for the drive" for 5 minutes. Ejected the disk and tried again - same result.
    On the third try, it actually recognized the DVD, but only gave me the option to burn at 4x or 8x. I usually burn at the slowest speed available (2x), so I cancelled, ejected the disk and tried again. Fourth and fifth tries: no action, just "waiting for the drive".
    I then tried to use Toast with the Super Drive; before inserting the disk, I set Toast to burn at 2x, but once I inserted the disk, Toast recognized it, but changed the available burn options to 4x or 8x.
    Next I connected my external burner and got the options to burn at 2.4x, 4x, or 8x both in Disk Utility and Toast.
    I then used the same disk on my iMac; tried both the Super Drive and my external burner (using both Disk Utility and Toast with both) and got the following burn options:
    iMac Super Drive/Disk Utility: 2.4x, 4x, 8x
    iMac/external burner/Toast: 2x, 4x, 6x, 8x
    There seem to be a couple of issues:
    The "waiting for the drive" problem (what could possibly cause this?)
    The "non-availability" of a slow burn speed of the Super Drive
    And a third problem: this DVD drive is the slowest I've ever experienced; it took 50 seconds for the icon to appear on the desktop after inserting the DVD vs. 7 seconds on the iMac (this is the DVD I burned using Toast/exterbal burner,testing it on a TV and the iMac). It played fine on all three.
    Has anyone encountered a similar "waiting for the drive" issue and/or the fact that this drive takes a very long time to recognize/read a DVD?
    Appreciate any input!

    I spoke with a product specialist at Apple and it was agreed that we'd wait to see if the problem persisted; at that time, we'd talk about getting the drive replaced.

  • [Solved] systemd does not wait for the unit to finish

    My problem is described in the title. I have made a test by enabling the following unit:
    [Unit]
    Description=/etc/rc.local Compatibility
    [Service]
    Type=forking
    ExecStart=/bin/sleep 1000
    TimeoutSec=0
    RemainAfterExit=yes
    After=network.target
    [Install]
    WantedBy=multi-user.target
    The unit is well started (a process sleep 1000 exists). But with a type=forking, systemd is supposed to hang in this case. Instead, the graphical.target is launched, systemctl list-units mention it as dead, but the display manager is started before the sleep 1000 completes. Ho can I force systemd to wait?
    Last edited by olive (2015-03-16 16:49:34)

    olive, now you're making even less sense. I didn't say the sleep example was stupid and I didn't question your reasons for doing/wanting this.
    I suggested you add "Before=display-manager.service" and you respond "I added Before=graphical.target and it didn't change anything."
    I also tried to explain why systemd has no reason to delay the display-manager.service. You could have asked for further clarification, as berbae has now done. Let's try a longer explanation.
    Service startup
    Services can be started in different ways, as configured with Type=. This determines when a service is considered "started" (or when the service's start-up is considered finished). When a service reaches this state (some time after being started), units that are supposed to start After= this service will be started (and no sooner).
    With simple systemd has no further information about the start-up process. It launches whatever you specify in ExecStart and this is the main process that continues to run till the service stops. systemd assumes this type of service is started immediately. All the other types have some way for the process to indicate to systemd (either directly or indirectly) when it has finished starting.
    Actually oneshot is also a bit special and that is where RemainAfterExit comes in. For oneshot, systemd waits for the process to exit before it starts any follow-up units (and with multiple ExecStarts I assume it waits for all of them). So that automatically leads to the scheme in berbae's last post. However, with RemainAfterExit, the unit remains active even though the process has exited, so this makes it look more like "normal" service with
    begin of unit/startup ---- end of startup ------ end of unit
    This is the relevant behavior for this thread. First sleep starts, then after 1000 seconds, start-up finishes and follow-up units will be started. Then either the unit dies, or (with RemainAfterExit) it stays "active".
    The man page describes how "end of startup" is determined for each Type.
    Targets
    Targets are meant to group units together, to provide synchronization points (and replace runlevels). When you start a target, all its units will be started (in parallel if possible). The man page says:
    Unless DefaultDependencies= is set to false, target units will
           implicitly complement all configured dependencies of type Wants=,
           Requires=, RequiresOverridable= with dependencies of type After= if the
           units in question also have DefaultDependencies=true.
    This means that (by default) when a target is requested, all it units are started first. Only after all units have finished starting, the target itself will be started (and since the target doesn't do anything by itself, this startup is basically instantaneous). Without this dependency, the order between the target and its units is unspecified, so in theory the target could finish starting immediately while its units are still being started.
    Back to olive
    graphical.target has these DefaultDependencies, so it is not started until all its units (like display-manager.service) and other After= dependencies (like multi-user.target) have finished starting. Your sleep service has to be started before multi-user.target starts (again due to default target dependencies). So first display-manager and the sleep service are started and after 1000 seconds, the sleep service finishes starting and then (assuming all other dependencies were quicker) multi-user.target is started and graphical.target as well (assuming display-manager didn't need 1000 seconds).
    If you want display-manager.service after the sleep service, add a Before/After line to specify that (this was your original goal and my suggestion).
    olive wrote wrote:However, units that are parts of the graphical target are still launched before the graphical target become active. I am still unable to completely delay the starts of the graphical target before a specific unit completes.
    It should be clear now how this works. "units that are part of the graphical target" can only mean "units that are wanted/required by the graphical target" but that is basically all the units that are started when you boot your system, because multi-user.target is a part of graphical.target. And your sleep service is a part of multi-user.target, so in fact you're saying you want to delay starting the sleep service until the sleep service completes
    What you probably intended was to delay all units that are a part of graphical.target but not of multi-user.target until after the sleep service. I can't think of an easy (or even good) way to do this and this post is already too long, so I'll table that for now.

  • Is there a way to passcode lock my iPhone without waiting for the preset idle time?

    Is there a way to passcode lock my iPhone without waiting for the preset time?
    My iPhone is set up to require a passcode after 15 minutes of idle time. Normally, this setting works best for me. However, there are times when I would like to lock it immediately, without waiting for the 15 minutes of idle time to pass. Is there a way to do that easily, without changing my settings? I know that I can click the power button to immediately kill the screen, but that just defaults to "slide to open" with no passcode required.
    Just to clarify, the idea is to leave my 15 minute setting, since this is the way I like it 98% if the time. I'm just wondering if, let's say I am resting my phone down while a curious person is around, I can quickly pass code lock it, much like I could just click the power button to put it to sleep.

    Unfortunately, my phone doesn't ask for the passcode when I do this (just slide-to-open). I've searched settings, but I don't see any way to set it up to require the passcode after the screen is locked with the power button.
    Do you remember how you set your iPhone up to achieve this?

  • E61 sync problem: 'Waiting for the mobile phone to...

    Setup: Nokia E61 Windows XP Pro w/Service Pack 2 PC Suite 6.80.53.3 Nokia supplied cable.
    The body of this has been essentially copied from two other people who've had the same problem. One's problem spontaneously disappeared while the other's was solved by removing the phone's battery for a minute. My problem was not solved by that and I throw it to the group for its collective wisdom.
    I have successfully synchronised my Outlook Contacts & Calendar for over a week. Now I can't. On selecting Synchronise Now in the Nokia PC Sync dialog, the blue & green bubbles continue to rotate and the message 'Connecting to E61'continues to flash for some 5 mins. The message then changes to 'Waiting for the mobile phone to send data'. This continues for approx. 3 mins, where upon synchronisation stops and the message Synchronisation Completed appears. However, 0 entries have been updated, despite several updates to contacts. Previously, having pressed the Synchronise Now button, synchronisation would take typically less than a minute and all updates would be transferred OK. I have tried everything I can think of. Included, completely de-pairing the phone from the PC, uninstalling PC Suite, installing again from scratch and re-establishing the connection. The other functions in PC Suite seem to be fine. For example, I can use the file manager to see what's on my phone. At the bottom of the PC Suite page it says that my phone is connected via USB. At the task bar at the bottom of the Windows screen it also shows everything OK. The icon there says"Nokia PC Suite Nokia E61 conected via USB". It's only when I press the synchronize button on PC Suite that the next screen pops up and says that it's trying to connect. Any suggestions to this vexing problem?

    try recreating the sync settings from PC Sync, select settings - create bew settings - and run through the wizard. then sync

  • I ordered a battery for my laptop because it said to replace battery soon.  How long can I let the new battery sit around as I wait for the old one to run out of more charge?

    I ordered a battery for my laptop because it said to replace battery soon.  How long can I let the new battery sit around as I wait for the old one to run out of more charge?  Will the new one become less effective if it sits around too long?

    How much capacity is remaining on your current battery?
    Check your power status
    From the  menu: Hold OPTION and click System Information... èHardware è Power
    Copy and Paste in your reply.
    The new battery will become less effective if you store it in a hot or humid environment. It should be stored at room temperature (22 C).
    Long term storage (6 months):
    Apple recommends that you store the battery with a 50% charge. If you store a battery when it’s fully discharged, it could fall into a deep discharge state, which renders it incapable of holding any charge. Conversely, if you store it fully charged for an extended period of time, the battery may experience some loss of battery capacity, meaning it will have a shorter life.
    http://www.apple.com/batteries/

Maybe you are looking for