timeToCurrentFormat bug?

The problem:

While creating a script in After Effects CS3, I noticed that there are some cases where the function overall timeToCurrentFormat returns the same value for seconds different values. It makes sense, of course, for seconds values that differ only slightly to return the value even if the difference in seconds values is not greater than the length of a frame in a few seconds. However, the time values that I used in the first parameter of the timeToCurrentFormat function found by getting the value of time of brand with a layer via the object model of AE.

There were some seemingly arbitrary cases where, even if the values of time of two markers were extracted markers that have a frame part, the same value was returned by the function timeToCurrentFormat for each of the markers. What is more confused, even if the time for the start of the project is set to 0, the function timeToCurrentFormat returns different values when the isDuration parameter is set to true.

The test:

To test this odd behavior, I set up a test by finding the length of a frame (1 divided by the frameRate of the composition: 1 / 29.9700012207031 = 0.03336669867431) and using a loop to go through 30 seconds value of executives to find the corresponding frame the value returned by the timeToCurrentFormat function. I quickly realized that this test would be unreliable since the rate of 29.97 uses a framework of drop. So, I instead used the loop to create markers on a layer for each image for 30 seconds, looping through all the layer markers, obtained their time value and used in the timeToCurrentFormat function. Below a link to a spreadsheet that I created that represents the values of time (in seconds) is from markers that 30 seconds were spaced 1 frame out (901 markers in all). I've also linked to the After Effects CS3 file I was working with that.

The data link can be found here:
http://spreadsheets0.Google.com/CCC?key=tqjM5RB38-fMluBGnsU2cbw & hl = #gid = 1

A link to the AE file to use when you run the test yourself with the code below:

http://aenhancers.com/download/file.php?id=165

The results:

First of all, here is my current work environment:

After effects Version: After Effects CS3 8.0.2.2.7 dva: 2.0.0.127845
OS: Mac OSX 10.5.08
QT: 7.6.6

Here are a series of descriptions for each of the header lines in the data help you to decipher and understand what is happening:

  • Key ID: -this column contains the index of the current marker whose time value is referenced.
  • Creation time of marker : - This column contains the value of seconds having served to create the current marker on the layer of 'Test '. It is provided to demonstrate that the time listed under "Marker Time Value" is not calculated based on the time value used to create marker.
  • Time marker value: -this column contains the value for seconds that is returned by the method keyTime (keyIndex) of the property of "Marker" of the layer of 'Test '. As noted above, this value does not seem to be calculated based on the value of time that the marker was created with.
  • timeToCurrentFormat W / True: -this column contains the frame number returned by the timeToCurrentFormat function when it is isDuration parameter is set to true.
  • Matches previously calculated Frame: -this column contains a ' * ' if value "timeToCurrentFormat W / True" marker current corresponds to the same value in the previous iteration of the loop. These fields have been highlighted in red in the data.
  • default timeToCurrentFormat: -this column contains the frame number returned by the timeToCurrentFormat function when it comes isDuration parameter is not defined (which then by default, false).
  • Matches previously calculated Frame: -this column contains a ' * ' if value "default timeToCurrentFormat" marker current corresponds to the same value in the previous iteration of the loop. These fields have been highlighted in red in the data.
  • currentFormatToTime W / True: -this column contains the value returned by the currentFormatToTime function when it is isDuration parameter is set to true. The value of the image that is used in the first parameter of the function is taken from the value "timeToCurrentFormat W / True" of the current iteration.
  • Initial value of seconds matches: -it is used to determine if the time value ("marker Time Value") that is sent through the function timeToCurrentFormat (with isDuration set to true) is reproduced correctly when the value returned by the function timeToCurrentFormat is executed through the function currentFormatToTime (with isDuration set to true).
  • default currentFormatToTime: -this column contains the value returned by the currentFormatToTime function when the parameter is not defined (default is false). The value of the image that is used in the first parameter of the function is taken from 'timeToCurrentFormat' default value of the current iteration.
  • Matches Initial Seconds value: -it is used to determine if the time value ("marker Time Value") that is sent through the function timeToCurrentFormat (with isDuration undefined) is reproduced correctly when the value returned by the function timeToCurrentFormat is executed through the function currentFormatToTime (with isDuration undefined).

From the data, I have come to believe the calculations within the timeToCurrentFormat function are not accurate. Even if I tried to exclude any error on my part, using only the values returned by the properties and methods of the AE object model, it is quite possible that I made a mistake somewhere along the line; where the reason why I want to share my discoveries and allow everyone to comment. At the end of the day, I need the timeToCurrentFormat function works correctly in order to finish the script I'm working on. Therefore, if you notice any errors in my code, don't be shy, I'm not offended.

Scripts:

The script that I used to create markers on the layer of 'Test'

{
//Before running this script, create a composition and then add
//a null layer named "Test"
var comp = app.project.activeItem,
   info = "",
   layer = comp.layer("Test"),
   frameRate = comp.frameRate,
   i;
   
   for (i = 0; i <= comp.duration; i += (1/frameRate))
   {
      layer.property("Marker").setValueAtTime(i, new MarkerValue(i));
   }
}

The script used to create the data (copy and paste the results into a spreadsheet):

{
   //Using the composition and "Test" layer created by the previous script
   var comp = app.project.activeItem,
      info = "",
      layer = comp.layer("Test"),
      markerRef, markerTime, markerFrame,
      maxSeconds = 30,
      frameRate = comp.frameRate,
      numKeys,
      i,
      timeToCurrentFormatTrue,
      timeToCurrentFormatDefault,
      currentFormatToTimeTrue,
      currentFormatToTimeDefault,
      keyId,
      keyTime,
      prevTimeToCurrentFormatTrue = null,
      prevTimeToCurrentFormatDefault = null,
      usersTimecodeType;
   
   //Get the user's timecode display type so we can change it back when
   //we're done.
   usersTimecodeType = app.project.timecodeDisplayType;   
   
   //Set the current timecode display type to frames
   app.project.timecodeDisplayType = TimecodeDisplayType.FRAMES;
   
   alertInfo = function (m)
    {
      myWindow = new Window("dialog",
         "Info",
         undefined,
         {resizeable: false}
      );

      myWindow.grp = myWindow.add(
      "group { orientation: 'column', margins:0," +
      "alignment: ['fill','fill'], size: [350, 450]," +
      "msg: EditText {properties: {multiline:true}," +
         "alignment: ['fill', 'fill']," +
         "size: [350,430]}," +
         "b: Button {text: 'Ok'}" +
      "}");

      myWindow.grp.b.onClick = function () {
         myWindow.close();
      };

      myWindow.center();
      myWindow.grp.msg.text = m;
      myWindow.show();
    };   
   
   
   info += "Composition Name:\t" + comp.name + "\n" +
      "Layer Name:\t" + layer.name + "\n\n" +
      "Frame Rate:\t" + frameRate + "\n" +
      "Frame Length (s):\t" + (1/frameRate) + "\n\N" +
      
      //Header Rows
      "Key ID\t" +
      "Marker Creation Time\t" +
      "Marker Time Value\t" +
      "timeToCurrentFormat W/ True\t" +
      "Matches Previously Calculated Frame\t" +
      "timeToCurrentFormat Default\t" +
      "Matches Previously Calculated Frame\t" +
      "currentFormatToTime W/ True\t" +
      "Matches Initial Seconds Value\t" +
      "currentFormatToTime Default\t" +
      "Matches Initial Seconds Value\n";

   numKeys = layer.property("Marker").numKeys;
   
   for (i = 1; i < numKeys; i += 1)
   {
      //Set values      
      keyId = i;
      keyCreationTime = layer.property("Marker").keyValue(i).comment;
      keyTime = layer.property("Marker").keyTime(i);
      timeToCurrentFormatTrue = timeToCurrentFormat(keyTime, frameRate, true);      
      timeToCurrentFormatDefault = timeToCurrentFormat(keyTime, frameRate);
      currentFormatToTimeTrue = currentFormatToTime(timeToCurrentFormatTrue, frameRate, true);
      currentFormatToTimeDefault = currentFormatToTime(timeToCurrentFormatDefault, frameRate);

      //Output row
      info += keyId + "\t" +
         keyCreationTime + "\t" +
         keyTime + "\t" +
         timeToCurrentFormatTrue + "\t";
      if (timeToCurrentFormatTrue === prevTimeToCurrentFormatTrue) {
         info += "*\t";
      } else {
         info += " \t";
      }

      info += timeToCurrentFormatDefault  + "\t";
      
      if (timeToCurrentFormatDefault === prevTimeToCurrentFormatDefault) {
         info += "*\t";
      } else {
         info += " \t";
      }

      info += currentFormatToTimeTrue + "\t";
      
      if (currentFormatToTimeTrue === keyTime) {
         info += "*\t";
      } else {
         info += " \t";
      }
         
      info += currentFormatToTimeDefault + "\t";
      
      if (currentFormatToTimeDefault === keyTime) {
         info += "*\n";
      } else {
         info += "\n";
      }
         
      prevTimeToCurrentFormatTrue = timeToCurrentFormatTrue;
      prevTimeToCurrentFormatDefault = timeToCurrentFormatDefault;
   }
   alertInfo(info);
   
   //Reset the timecode display type to the user's preference   
   app.project.timecodeDisplayType = usersTimecodeType;
}

Any help would be greatly appreciated! Thanks in advance.

I'm glad it's working for you now. So what happens is that when you do the math of 1/frameRate in JavaScript, you have finite resolution number IEEE floating point. As you can see, this isn't 0.03336670333667... Repeat forever, which is the mathematically correct value of 29.97. Then AE that converts a fractional value, which ideally would be 1000/2997 (or a multiple of it), but it cannot be - we drop exactly on the bases, because of things like temporal keyframes. You have no control over the question of whether if it has rounded upwards or downwards, unfortunately. Then when you retrieve this time of return, it is converted to once more to comma floating and then converted back to a fixed fraction when you pass it to timeToCurrentFrame. So basically you just don't have the control you need over the rounded. The only way I think we could do this more reliable work would expose our rational fraction time directly to the JavaScript, but I think it would be generally a fairly high load on the film script author. (I can feel the eyes of most people, and more of you, me and a handful of geeks hardcore glazing above long ago).

So I think that we have developed with you to workaround is the best thing for now - you don't need to add 1/1000 everywhere, just at the moment you create new keys that deeply concerns you line up exactly on a framework. For normal use, when you are not trying to recover by a time of the entire image, you would not need to bother this is why I believe that no one has reported this problem so far (it has probably been there for AE 5.0 in Y2K).

Tags: After Effects

Similar Questions

  • strangeness rounded when time-remapping is 512 seconds?

    OK, this one is total of disconcerting.

    I have a script to configure comps with a stack of layers where each layer is actually a stop on images from the video, each layer has activated the time remapping and then I put the value at time 0 for each layer (and then delete the key of the second). I have been using this technique one way or another for years without any problem. Then today, I noticed some glitchy from a certain point results. I assumed it was a matter of 24 / 25 fps but not, it seems to be a rounding problem when the defined time-remapping is greater than 512 dry.

    so my troubleshooting code looks like this (the timeOffset value is 0.04 or 1 frame at 25 fps)

    alert("tmap about to set as " +  (i*timeOffset))
tMap.setValueAtTime(0,(i*timeOffset);
alert("tmap value that was actually set" + tMap.valueAtTime(0,true))

    then, when trying to put the first alert returns with 512.04 as expected but the second alert is back with 512.039978027344 always 512.04 time.

    obviously done Ae internal to come round returns with an entire image number (as shown in the user interface), but here's the weird part, this internal rounding seems to work very well all the way to the point of 512 dry but starts then will knock out, almost as if he went from round() to floor()

    i.e.

    If I put the 484.04 I actually get get 484.039978027344 that I rang the Bell to show the 00:08:04:01 structure, which is what I want

    But if I put 512.04 I get 512.039978027344 Ae rounds down to show the frame 00:08:32:00 instead of 00:08:32:01, not what I want.

    very frustrating.

    It is certainly a bug right?

    .. /JL

    The floating point precision of ExtendScript is based on the old ECMA 3 Javascript since 1997. A lot has changed/been fixed in nineteen years. There was a few posts related to the disorder of precision.

    Problem of precision CompItem.displayStartTime

    Problem of duration and composition accuracy

    What is the problem with the term?

    timeToCurrentFormat bug?

  • Problem of precision CompItem.displayStartTime

    I have a model of 24 frames per second, and I'm putting the displayStartTime to match the time code of the sequence inside.  I have précomposé the film and consulted the displayStartTime of the precomp, which is 69085.2916666667 (1658047 images @ 24 fps).  When I apply this value to the property displayStartTime of the main computer, the result of the operation is 69085.2916666667.  However, when I then check the value of displayStartTime to the main computer, I get 69085.2890625 instead.  It is originally a discrepancy of 1 image.

    What makes possible a scenario in which you create a model of a piece of images of a model using precompose or dragging the comp on the 'new model' button, select the model, and then run the following statement:

    app.project.selection[0].displayStartTime = app.project.selection[0].displayStartTime

    and the value of the pass of displayStartTime.

    Any thoughts on how to deal with this?

    This has been a recurring problem to treat unfortunately. Is there a solution posted here by Paul...

    bug in comp.displayStartTime

    and he mentions another thread that was on the same subject here...

    timeToCurrentFormat bug?

  • macOS bug Sierra - Possible? (Terminal)

    I use the Terminal Df-h command to find the percentage of used space on the hard drive of my Mac, and I've noticed that since the upgrade to Mac OS Sierra; It came out that I used 0% (which may not be true); I was wondering could this be a bug and this is the case with anyone else?

    In fact, it is show you used 6% of disk space. 0 percent at the end relates the number of inodes that are used (data structures that manage the different metadata). Because you have so few files you are not yet using 1% of inodes, so he says always 0% are used.

    So, no, no bug

  • Calendar Apple App Bug frozen works only with iOS 10 update grrr

    Since I updated to iOS 10 (more more later than 10.2, etc.), everything was not too bad except THE APPLE CALENDAR app, its deiving me crazy when I click on the app it's like it freezes and past shift x 50 mode still something to do with the calendar app will cause either a frozen or a black screen or white and then crashed ack to main menu. Sometimes it will allow me to create but will be trolling with typing and finally crashed or not even save it... Please HELP I am sure what else to do, I tried to download google calendar and which seemed to have something of bug he loves too then something happens. And I tried to delete it and download it again, / force delivery, nothing has changed

    Hi there calsparks!

    Thank you for bringing your question on the calendar of freezing and trolling since the update to iOS 10 on your iPhone for Apple Support communities.  I rely on the calendar to keep my life organized, so I'm happy to help you resolve this issue today.

    Looks like you did a few good troubleshooting by force to leave the app, force to restart the iPhone and deleting and reinstalling the application calendar.  At this stage my next recommendation would be to backup your iPhone, then erase and restore your iPhone as a new device, then test calendar to see if it behaves correctly, and then restore your backup.

    The backup of your iPhone, iPad and iPod touch

    Use iTunes on your Mac or PC to restore your iPhone, iPad or iPod to factory settings

    Restore your iPhone, iPad or iPod touch from a backup

    Have a great day!

  • iPhone restore backup encryption bug in iTunes

    First the details of my system:

    El Capitan 10.11.6

    iPhone iOS 6 10.0.2

    iTunes 12.5.1.21

    Steps to reproduce:

    1 backup the by using the encrypted password (current running iOS 10) iPhone

    2. once the backup is complete change password encrypted from A to B

    3. restore the iPhone using the backup.

    The backup cannot be restored with A password or password B.

    I think that most people would say I forgot the password B. You would be a mistake. Password B was stored in my keychain and it wouldn't work. To check that I had the correct password, I downloaded a password free utility cracking. For some reason, these utilities are available for Windows only. I used the utility of tenorshare. Since I was sure I knew the password, I used boxes of prefix and suffix of the utility to verify that the password is correct. The utility shows you only the first 2 characters of your password once he finds her. Since I am sure that I knew the password, I put the first 7 characters of the password in the prefix box password and he assumes that the last of them (which I knew that). Then I put the first 6 characters of the password in the prefix area of password and the last character in the zone suffix and guess the second to the last character (which I knew that too). In both cases, he finds the password, which confirmed that all my characters were correct, but iTunes would not accept. At this point, I was convinced this is an Apple bug, so I googled some more and found this blog https://deciphertools.com/blog/ios-10-backup-password-incorrect/ which confirms:

    "If you recently changed your password backup in iTunes, and iTunes is now reports that 'the password was incorrect' when you try to restore this backup, then we may be able to help."

    There is a small problem affecting backups iOS 10 - sometimes changing password causes backup the password being rejected (both new and old passwords) when you try to use the backup that you did. »

    I was able to solve my problem of password associated with the procedure.

    My backup was too important to wait for a solution possible iTunes. Apple should recognize this problem and have a fix as soon as POSSIBLE.

  • IOS 10 keyboard bug

    There is a bug at the moment where the software keyboard when my iPad Pro running the latest iOS (from today 06/10/16) displayed in the bad sense.  It happens as follows:

    I'm holding the iPad in Vertical Mode (Home button down) and I'm on the home page of apps.

    I pull down from the center of the screen to access frequently used applications.

    As soon as these applications appear that the software keyboard appears also, but in fashion landscape on the left side of the screen. It crashes me out to make a choice of app and I have to tilt the iPad to type the first letters of a couple of my app type laterally in the wrong way.

    Expected behavior: in a vertical position the keyboard should be popping up by underneath the screen, applications frequently used at the top of the screen and there is no occlusion.

    If someone has corrected it somewhere, I'm all ears, but I expect that what needs to be fixed with some magical-spackle code.

    Thank you all!

    Hello. You have restarted your iPad since the last update? Here's how

    1. Press and hold the sleep/wake button until the Red slider appears.
    2. Drag the slider to turn off your device completely off.
    3. Once the device turns off, press and hold the sleep/wake button again until you see the Apple logo.

    What you describe works normally for me on iPad Air with iOS 10.0.2, so it looks just a curiosity for you. By the way, is your Pro model 9.7 to 12.9 inches?

  • Bug in iOS Schedule 10: jumps to two months

    Presently I found what seems to be a bug in iOS 10 calendar: sometimes, when choosing a certain day in the month view + list of activities below, the real selected jumps from day to another month, which is currently not displayed on the screen. Then the red circle suddenly disappeared from the current month and jump out of view to a different month (usually 1 month in the future).

    Anyone else having this problem? I use iCloud for calendar synchronization.

    I did not have this experience so far.  This - try restarting your iPhone, iPad or iPod touch - Apple Support

  • Numbers 4.0 - Bug with default date when entering the time alone?

    I've just updated to 4.0 numbers after upgrade to Mac OS Sierra and met with what seems to be a bug.

    Previously when I enter a time in the format hh: mm in a cell that has the format of Date and time, it would create the date date of the day, because none has been provided explicitly. It is the behavior expected according to this support article:

    If you do not enter a date and a time, Numbers adds a default value for you. For example, if you type '13:15 ', Numbers adds today's date by default.

    What happens now in numbers 4.0 for me when I get home just a moment, is that it gives me 01/01/2016 as the date, which is a huge pain, because I rely on the fact that the date is (or should be) today's date by default when you enter data in my spreadsheet and right now that means I have to manually change each date by hand to be released today.

    All confirm that this behavior occurs in numbers 4.0 (Build 3507)?

    Thank you

    Michael

    Here is what I get here after typing 13:15 in numbers 4.0 under Sierra:

    I left the Format of data in automatic mode, but get the same result when the format Date and time.

    It might have something to do with your region settings in system preferences (I'm using the default values for the United States).

    Have you tried numbers, reboot and try in a document of closing costs?

    SG

  • activation iPad 9.3.5 blocking bug

    Sorry if this thread in the wrong section, I can't find the section support or tag you,

    Ive updated my ipad 9.3.5 once ive power used for one day in empty battery.

    then it restarts and now im on this activation of the lock screen but my apple ID does not.

    screenshots:

    1. no language > This means I already configure it.

    2 NOTE: after 9.3.5 strings I could change the apple for a * s, even managed to download apps on it, then ipad ID drain its battery and restarted, it went to the lock of activation screen and does not my i.d.

    Ive tried to log a * s , but does not, so I thought he came back to the previous owners i.d.

    I heard that there is a bug like that when it updated to 9.x or older.

    a * 6 is my aunt apple id and the previous owner, we have already made contact with apple on the recovery of this apple ID (case ID: *), and we managed to get password reset e-mail. but still do not accept.

    I hope someone can help me with this, waiting for response from the apple support.

    < personal information under the direction of the host >

    MARK AS RESOLVED.

    another successful apple ID to unlocked it.

  • What restoration brings back old bags in the device? I was always told that icloud restoration brings all the bugs back, yet care apple lately told me than vice versa. I'm lost in a cleaner for restoration of backup: icloud or itune?

    What restoration brings back old bags in the device? I was always told that icloud restoration brings all the bugs back, yet care apple lately told me than vice versa. I'm lost in a cleaner for restoration of backup: icloud or itune?

    I've never heard a backup report bugs, however if you are interested in, you can always restore the device as good as new.

  • iMessage/Facetime activation on iOS 10 bug

    Hello

    The bug appeared after the first intentional reboot after iOS 10 updated, my iPhone 5 has been disconnected for a few hours. When it started I started to receive petitions of iM/FT on reboot or a random time after even if iM/FT completely!

    I did not move my SIM card. If I refuse to activate iM I can't see my phone number in the Contacts section.

    The same bug persists on the iPhone of my 5s wife while his phone has never been disconnected except 10.0.2 update.

    Hi Valsh,

    Here is how to fix iMessage / FaceTime activation do not question.

    Before you begin, you'll need sort these things:

    • Make sure that in the phone application, you got your registered number. On top of "Contacts", you should see your registered number (My Number :). If not, you will need to go to settings → → my phone number and enter your number.
    • Make sure that the Date and time (in general) are correct. Set to "Set automatically" to ensure that the time zone is correct and the iPhone is at the right time.
    • Also make sure you have a working network. Problems of Wi - fi can cause iMessage activation problems therefore have active cell.
      For some users, the message for activation goes out as an international SMS. Make sure that your carrier allows these and you have a sufficient amount to send them.


    1. contact your operator

    First of all, make sure that your carrier supports iMessage or not. Contact the support team of carrier and check any condition limiting on your iMessage, blocks or text filters.

    2. airplane mode

    As strange as it sounds, maybe you should try this method if nothing else works. We found the airplane mode activation mode in one of the discussions. It sounds simple, and if it is correct, it would be nice, right?

    Here's how it works:

    Step #1. Get off at scroll → settings touch Messages and turn offiMessage (also turn off FaceTime)

    Step #2. Turn on airplane mode. WiFi will be disabled automatically.

    Step #3: Turn ON Wifi.

    Step #4. Return to Messages and ignition iMessage.

    Step #5. You will be prompted for your Apple ID if you have not yet added it. (otherwise, you get no notification)

    Step #6. Now, go back to the settings and disable airplane mode.

    Step #7. For the most part, you will see a notification that says "your carrier may charge for SMS" - press OK

    Step #8. If this is not the case, go to Messages, disable iMessage and then turn on again.

    Step #9. In a few moments, iMessage should be enabled.

    Step #10. You will see a greyed number and e-mail ID. A little later, the number should be checked, and that's all.


    3 Apple ID disconnect, connect

    Sometimes, you just need to logout of your identifier Apple and then sign in again.

    Step #1. Under Settings → Message, scroll up to where it says 'Send and receive'and tap on it.

    Step #2. Type on the Apple ID, then tap Sign Out.

    Step #3. Now turn off iMessage.

    Step #4. Wait for a while (toggle Wifi) and then turn on the iMessage.

    Step #5. Enter the details of your Apple ID now and try to reactivate iMessage

    4. set or restore

    If things do not work, you must first reset the settings of your location, then the iPhone. Reset is just a force so restart your data stays secure. After the reset, you will just connect with your Apple and implementing iMessage like new.

    If this fails, you may need to restore the iPhone as new or from a backup.

    Hope this helps,

    See you soon.

  • The closed display mode is no longer works after update of the Sierra on my MBPro. Known bug?

    I use a vertical dock for awhile, so my MBPro retina works in closed with external display, KB and mouse display mode.

    But since I installed the update of the Sierra, the external display not Mac OS desktop.

    It only works when I open the built-in screen...

    The bug is known? Or y at - it a setting to adjust on the Sierra?

    Thank you in advance

    Hi darklemon,

    I understand that, since the update to Mac OS Sierra, you've been unable to use your MacBook Pro in closed view. I know it's important to use your computer in a way that suits you, then I'm happy to help you.

    Let's start by resetting your memory NVRAM and SMC which can often help with system display and related issues:

    How to reset the NVRAM on your Mac - Apple Support
    Reset the management system (SCM) controller on your Mac - Apple Support

    Once you have done this, follow the steps here to set up the closed display mode:

    Use your Mac laptop to view closed with an external display - Apple Support

    Thank you for using communities Support from Apple. See you soon!

  • major bug in iOS 10.0.2.

    I just updated my iPhone with iOS 10.0.2 + 6 last night.

    Problem 1:

    Since keep freeze then my texts.  In the middle of sending a new or reply to a text, keyboard hangs just straight up.  The screen freezes and I have to press the home button to get out of the text. Once I'm back in, my only half typed original text is no longer there and I start over again.  Then it crashes again.

    This happens about 80% of the time!  Very frustrating!

    Problem 2:

    Since my recent update, when I go to a form of browser and the beginning of filling in the details, the browser/keyboard crashes.

    The screen freezes and I have to press the home button to get out of the text. Once I'm back in, my only half typed original text is no longer there and I start over again.  Then it crashes again.

    This happens about 90% of the time!  Very frustrating!

    Problem 3:

    Since my recent update, when I go to one of my applications that have a form to fill in content or answer a question (i.e. Maven), the application block to halfway through typing me

    I just press the home button to exit the text. Once I'm back in, my only half typed original text is no longer there and I start over again.  Then it crashes again.

    This happens about 100% of the time!  Very frustrating!

    These are not bugs in 10.0.2. They are questions that are specific to your device.

    Solve problems.

    Reset.

    Reset all settings

    Restore iOS and your backup.

    Restore iOS and configured as a new device.

    Sides are one of those who will fix it. If this is not the case, make an appointment at the genius bar.

  • When do we get a fix for the bug to peripheral mode Bluetooth iOS 10?

    There are many articles on the web report a bug in the iOS 10 Bluetooth peripheral mode implementation, in particular in articles related to locks Kwikset Kevo.  This correction in iOS 10.0.2?  If no, what is the timeline / release targeted for a fix version?

    You do not discuss Apple here. This is a user to user support forum. If you want to report a problem to Apple, and then use the comments here, http://www.apple.com/feedbacklink. As much as if/when Apple would only know and you have to watch for announcements. Here nobody.

Maybe you are looking for