Kenster999

About

Username
Kenster999
Joined
Visits
13
Last Active
Roles
member
Points
27
Badges
0
Posts
24
  • AppleInsider readers are split on the iPhone X notch, but most support Apple's decision to...

    I haven't read all 53 comments yet, so excuse me if someone else has already posted this. The thought occurs to me: what does the removal of the home button actually accomplish? There are various drawbacks (loss of Touch ID, familiarity, etc), but people assume that the extra screen space is a gain. But, is it? 🤔 It looks like the extra bottom portion of the screen is now mostly reserved for the thumb that you use to slide up your app. And now all of those pixels in the new bottom section have to be powered 100% of the time that the screen is on. Hmm...
    macplusplus
  • How to secure AirDrop on your iPhone to prevent unwanted photos on the subway

    This should be called "AirBombing" 😁
    razorpit
  • Video: Stop force closing all apps on your iPhone, it's a waste of time

    I agree with some prior comments, what is said in this video is untrue. Many apps run background processes which are killed off if you manually remove them from the active list (although some like Facebook run no matter what you).
    Can you please provide some examples of background processes that apps run?  Audio can be one, but that one's pretty obvious.  What other processes are my apps running in the background and how long do those processes run?  Thanks!
    Sure thing! An app is allowed to run in the background (for non-trivial amounts of time) for the following types of tasks:

    1. Audio, AirPlay, and Picture-in-Picture
    2. Location updates (eg, mapping) but only if it asks for location updates "always" instead of "when in use". (By the way, "always" actually means when the app has been launched and is still running in the background; if you force-close the app, then it no longer gets location updates. I think they should reword "always" to mean "if in foreground or background" and reword "when in use" to mean "only when in the foreground".)
    3. Voice over IP
    4. Newsstand downloads
    5. External accessory communication
    6. Uses Bluetooth LE accessories
    7. Acts as a Bluetooth LE accessory
    8. Background fetch (the app will be "woken up" every now and then so it can download any info it needs from the Internet)
    9. Remote notifications (a remote / "push" notification can be sent that will let the app run for a short time in the background)

    Note that these aren't simply loopholes; the apps have to actually use that feature. For example, if an app provides voice over IP, it can run in the background when handling a call. But when the call ends, the app goes to sleep again. (It gets woken up by iOS when a new call comes in.)

    In addition, all apps run for a very short time (up to ~10 seconds) when they are put into the background, so that they can save their state / data. If they need extra time (eg, to finish a large download), they can request a little more time; in iOS 10 this tends to be around 179 seconds in my testing. But they have to actually do something during that time, and can't simply go into a loop requesting another 179 seconds.

    Beyond that, answers #25 (by Xmcgraw) and #31 (by Randominternetperson) have a good overview of memory management.

    To flesh out a related topic: when you put an app into the background, it has a short time (~10 seconds) to save its "state." As stated in answer #25, when you bring it back into the foreground, it will restore its state, so it looks to you like it is still running, even though it may have been completely removed from memory if iOS needed to do so. (But you have no way of knowing if this happened, and you really don't care.) A caveat is that if you manually force-close an app, then the last saved state information is deleted, so the next time you launch the app it will launch from a "clean" state. This may be useful sometimes if the app has subtle bugs in its state saving / restoration code.
    nhughesjony0pscooter63dysamoriaspheric
  • Watch: iOS 11 adds Live Photos editing tools, new effects and more

    Minor usability tip: when I see a title like "Watch: iOS 11 adds Live Photos editing tools, new effects and more" for posts like this, it makes me think the post is about watchOS. Maybe use a post title like: "Video: iOS 11 adds Live Photos editing tools, new effects and more" ?
    seanismorriscornchipbeowulfschmidtMetriacanthosaurussmaffei
  • Apple's iOS 10 now on 3 out of 4 compatible devices

    I know this is going to be an unpopular comment, but I regret installing iOS 10 on my iPhone 6. I've been an extremely satisfied iPhone user since 2008, to the point where friends sometimes tease me about it, but for the first time in almost 9 years I now have to be very careful to not kill the battery before the end of the day. Until iOS 10, I typically ended the day above 80%, so the change is pretty drastic, and sometimes the phone just dies with no warning. I was recently on my way to a party far from home in the early evening, and I pulled out my phone to check the address and it died before I could pull up the details, so I had to wander around and hope I recognized the building from memories of a previous party in the same place a few years ago. I really hope they do something to solve this problem in an update soon.
    Apple has admitted a problem with "a small number" of iPhone 6s phones, but I have had the exact same problem on my iPhone 6 as you're describing (as have many other people, from what I've seen).

    For example, one day I was getting "normal" usage out of my battery. Suddenly it dropped down to about 30%. I called an Uber. Within a minute or two the battery level dropped from 30% down to 2%. It then stayed at 2% for about 15 minutes while I drove home. As soon as I got home I plugged it in to charge, and the level *immediately* jumped from 2% to 27%. In short, I've seen lots of weirdness with battery levels, including a few times when the phone died on me unexpectedly.

    My iPhone 6 never had any sort of battery problem until I put iOS 10 on it. It seems to me that they've screwed up something in their battery-monitoring logic.
    GeorgeBMac