My iphone got slow on keyboard after upgrade...  Any hints ?  Tia .

Hi team
my iphone got slow on keyboard after upgrade...  Any hints ?  Tia .

No, I have not done a restore with no backup but I'll try (when my job will let me some time to spend for myself).
Contacts, music, calendars etc. work fine (I don't have pictures on my iPhone) but everything "feels" slow and intermittent.
I'll let you know about the complete initialization.
cheers
rob

Similar Messages

  • My iPhone 4S no longer syncs after upgrading from 10.5.8 to Snow Leopard 10.6.3

    y iPhone 4S no longer syncs after upgrading from 10.5.8 to Snow Leopard 10.6.3 - any solutions out there?

    Thanks - got stuck with the upgrade to 10.6.8, but Apple Support was able to navigate me through that, the date settings caused a problem here.

  • My iPhone 4 can not reboot after upgrading to iOS 6; keeps trying and cannot shut off either.

    My iPhone 4 can not reboot after upgrading to iOS 6; keeps trying and cannot shut off either.

    I FINALLY got it to work on BOTH iPhone 4 and iPpad 3.  Here is what I had to do:
    Had to DELETE all e-mail accounts including icloud.
    Did a hard reset (hold down button on top right corner and round button on bottom center)
    Then once it came back on, the iPhone had ALL of the accounts still on it and it was receivng e-mail.
    The iPad receive e-mail until I did the steps above 5 times.  Plus, I had to add back all of the e-mail accounts vs. on the iPhone 4 they were there when my phone came on.
    Now I am receiving e-mail on both devices normally.
    No clue why this happened, but Apple needs to find a fix ASAP.

  • Slow down Database after upgrading to 10.2.0.5

    Hi
    I am having performance problems after upgrading to 10.2.0.5
    At the beginning I thought the problem was sga too smalle ( ini: 598M , now 1408M ) but even after recreating the database with the new value the problem remains.
    I am sending reports so that someone could give me an idea.
    Thanks in advance!
    DETAILED ADDM REPORT FOR TASK 'TASK_240' WITH ID 240
    Analysis Period: 22-JUN-2011 from 08:34:06 to 16:00:13
    Database ID/Instance: 2462860799/1
    Database/Instance Names: DXT/DXT
    Host Name: thoracle
    Database Version: 10.2.0.5.0
    Snapshot Range: from 71 to 78
    Database Time: 6726 seconds
    Average Database Load: .3 active sessions
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    FINDING 1: 38% impact (2540 seconds)
    SQL statements consuming significant database time were found.
    RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
    ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
    possible performance improvements.
    RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
    PLAN_HASH 2734400036
    select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
    :"SYS_B_01" from sys.all_objects a where a.object_type IN
    (:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
    like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
    like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
    c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
    sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
    and c.table_name = a.object_name and a.object_type IN
    (:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
    like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
    like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
    CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
    min(b.position), max(b.overload) from sys.all_arguments b where
    b.package_name IS NOT NULL and b.owner
    like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
    like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
    CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
    distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
    b.object_name), min(b.position), max(b.overload) from
    sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
    and c.table_name = b.package_name and b.package_name IS NOT NULL and
    c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
    like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
    CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
    distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
    from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
    and c.table_owner=b.package_name and c.table_name=b.object_name and
    c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
    like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
    RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
    times and had an average elapsed time of 0.036 seconds.
    RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
    "Concurrency" accounted for 7% of the database time spent in
    processing the SQL statement with SQL_ID "30rku9qg2y30j".
    RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
    ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
    "7yv1ba0c8y86t".
    RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
    PLAN_HASH 2684283631
    Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
    From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
    WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
    (WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
    And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
    ((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
    Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
    Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
    RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
    times and had an average elapsed time of 32 seconds.
    RECOMMENDATION 3: SQL Tuning, 14% benefit (926 seconds)
    ACTION: Use bigger fetch arrays while fetching results from the SELECT
    statement with SQL_ID "7yv1ba0c8y86t".
    RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
    PLAN_HASH 2684283631
    Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
    From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
    WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
    (WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
    And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
    ((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
    Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
    Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
    FINDING 2: 37% impact (2508 seconds)
    Time spent on the CPU by the instance was responsible for a substantial part
    of database time.
    RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
    ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
    possible performance improvements.
    RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
    PLAN_HASH 2734400036
    select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
    :"SYS_B_01" from sys.all_objects a where a.object_type IN
    (:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
    like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
    like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
    c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
    sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
    and c.table_name = a.object_name and a.object_type IN
    (:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
    like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
    like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
    CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
    min(b.position), max(b.overload) from sys.all_arguments b where
    b.package_name IS NOT NULL and b.owner
    like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
    like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
    CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
    distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
    b.object_name), min(b.position), max(b.overload) from
    sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
    and c.table_name = b.package_name and b.package_name IS NOT NULL and
    c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
    like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
    CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
    distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
    from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
    and c.table_owner=b.package_name and c.table_name=b.object_name and
    c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
    like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
    RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
    times and had an average elapsed time of 0.036 seconds.
    RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
    "Concurrency" accounted for 7% of the database time spent in
    processing the SQL statement with SQL_ID "30rku9qg2y30j".
    RATIONALE: Average CPU used per execution was 0.036 seconds.
    RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
    ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
    "7yv1ba0c8y86t".
    RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
    PLAN_HASH 2684283631
    Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
    From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
    WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
    (WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
    And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
    ((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
    Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
    Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
    RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
    times and had an average elapsed time of 32 seconds.
    RATIONALE: Average CPU used per execution was 32 seconds.
    RECOMMENDATION 3: SQL Tuning, 5.8% benefit (390 seconds)
    ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
    "cbtd2nt52qn1c".
    RELEVANT OBJECT: SQL statement with SQL_ID cbtd2nt52qn1c and
    PLAN_HASH 2897530229
    Select DAE_.ROWID, DAE_.*, HAE_.*
    From THPR.GACCENTRYD DAE_, THPR.GACCENTRY HAE_ Where ((HAE_.TYP_0(+)
    = DAE_.TYP_0) AND (HAE_.NUM_0(+) = DAE_.NUM_0))
    And HAE_.CPY_0 = :1 And HAE_.ACCDAT_0 >= :2 And HAE_.ACCDAT_0 <= :3
    And DAE_.ACC_0 = :4 And HAE_.FCY_0 >= :5 And HAE_.FCY_0 <= :6
    Order by DAE_.BPR_0,DAE_.CUR_0,DAE_.ACC_0
    RATIONALE: SQL statement with SQL_ID "cbtd2nt52qn1c" was executed 12980
    times and had an average elapsed time of 0.03 seconds.
    RATIONALE: Average CPU used per execution was 0.029 seconds.
    RECOMMENDATION 4: SQL Tuning, 2.1% benefit (138 seconds)
    ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
    "33t7fszkr29gy".
    RELEVANT OBJECT: SQL statement with SQL_ID 33t7fszkr29gy and
    PLAN_HASH 2684283631
    Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
    From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
    WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
    (WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
    And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
    Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
    (((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7)))
    Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
    Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
    RATIONALE: SQL statement with SQL_ID "33t7fszkr29gy" was executed 1
    times and had an average elapsed time of 136 seconds.
    RATIONALE: Average CPU used per execution was 138 seconds.
    FINDING 3: 15% impact (1008 seconds)
    SQL statements with the same text were not shared because of cursor
    environment mismatch. This resulted in additional hard parses which were
    consuming significant database time.
    RECOMMENDATION 1: Application Analysis, 15% benefit (1008 seconds)
    ACTION: Look for top reason for cursor environment mismatch in
    V$SQL_SHARED_CURSOR.
    ADDITIONAL INFORMATION:
    Common causes of environment mismatch are session NLS settings, SQL
    trace settings and optimizer parameters.
    SYMPTOMS THAT LED TO THE FINDING:
    SYMPTOM: Hard parsing of SQL statements was consuming significant
    database time. (20% impact [1336 seconds])
    SYMPTOM: Contention for latches related to the shared pool was
    consuming significant database time. (2% impact [135
    seconds])
    INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
    database time.
    SYMPTOM: Wait class "Concurrency" was consuming significant
    database time. (2.3% impact [154 seconds])
    FINDING 4: 8.5% impact (570 seconds)
    Wait class "User I/O" was consuming significant database time.
    NO RECOMMENDATIONS AVAILABLE
    ADDITIONAL INFORMATION:
    Waits for I/O to temporary tablespaces were not consuming significant
    database time.
    The throughput of the I/O subsystem was not significantly lower than
    expected.
    FINDING 5: 5.3% impact (355 seconds)
    The SGA was inadequately sized, causing additional I/O or hard parses.
    RECOMMENDATION 1: DB Configuration, 3.2% benefit (215 seconds)
    ACTION: Increase the size of the SGA by setting the parameter
    "sga_target" to 1740 M.
    ADDITIONAL INFORMATION:
    The value of parameter "sga_target" was "1392 M" during the analysis
    period.
    SYMPTOMS THAT LED TO THE FINDING:
    SYMPTOM: Hard parsing of SQL statements was consuming significant
    database time. (20% impact [1336 seconds])
    SYMPTOM: Contention for latches related to the shared pool was
    consuming significant database time. (2% impact [135
    seconds])
    INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
    database time.
    SYMPTOM: Wait class "Concurrency" was consuming significant
    database time. (2.3% impact [154 seconds])
    SYMPTOM: Wait class "User I/O" was consuming significant database time.
    (8.5% impact [570 seconds])
    INFO: Waits for I/O to temporary tablespaces were not consuming
    significant database time.
    The throughput of the I/O subsystem was not significantly lower
    than expected.
    FINDING 6: 4.2% impact (281 seconds)
    Cursors were getting invalidated due to DDL operations. This resulted in
    additional hard parses which were consuming significant database time.
    RECOMMENDATION 1: Application Analysis, 4.2% benefit (281 seconds)
    ACTION: Investigate appropriateness of DDL operations.
    SYMPTOMS THAT LED TO THE FINDING:
    SYMPTOM: Hard parsing of SQL statements was consuming significant
    database time. (20% impact [1336 seconds])
    SYMPTOM: Contention for latches related to the shared pool was
    consuming significant database time. (2% impact [135
    seconds])
    INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
    database time.
    SYMPTOM: Wait class "Concurrency" was consuming significant
    database time. (2.3% impact [154 seconds])
    FINDING 7: 4% impact (266 seconds)
    Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
    were consuming significant database time.
    RECOMMENDATION 1: Host Configuration, 4% benefit (266 seconds)
    ACTION: Investigate the possibility of improving the performance of I/O
    to the online redo log files.
    RATIONALE: The average size of writes to the online redo log files was
    26 K and the average time per write was 2 milliseconds.
    SYMPTOMS THAT LED TO THE FINDING:
    SYMPTOM: Wait class "Commit" was consuming significant database time.
    (4% impact [266 seconds])
    FINDING 8: 2.9% impact (192 seconds)
    Soft parsing of SQL statements was consuming significant database time.
    RECOMMENDATION 1: Application Analysis, 2.9% benefit (192 seconds)
    ACTION: Investigate application logic to keep open the frequently used
    cursors. Note that cursors are closed by both cursor close calls and
    session disconnects.
    RECOMMENDATION 2: DB Configuration, 2.9% benefit (192 seconds)
    ACTION: Consider increasing the maximum number of open cursors a session
    can have by increasing the value of parameter "open_cursors".
    ACTION: Consider increasing the session cursor cache size by increasing
    the value of parameter "session_cached_cursors".
    RATIONALE: The value of parameter "open_cursors" was "800" during the
    analysis period.
    RATIONALE: The value of parameter "session_cached_cursors" was "20"
    during the analysis period.
    SYMPTOMS THAT LED TO THE FINDING:
    SYMPTOM: Contention for latches related to the shared pool was consuming
    significant database time. (2% impact [135 seconds])
    INFO: Waits for "cursor: pin S wait on X" amounted to 1% of database
    time.
    SYMPTOM: Wait class "Concurrency" was consuming significant database
    time. (2.3% impact [154 seconds])
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ADDITIONAL INFORMATION
    Wait class "Application" was not consuming significant database time.
    Wait class "Configuration" was not consuming significant database time.
    Wait class "Network" was not consuming significant database time.
    Session connect and disconnect calls were not consuming significant database
    time.
    The database's maintenance windows were active during 100% of the analysis
    period.
    The analysis of I/O performance is based on the default assumption that the
    average read time for one database block is 10000 micro-seconds.
    An explanation of the terminology used in this report is available when you
    run the report with the 'ALL' level of detail.

    user12023161 wrote:
    I have upgraded 10.2.0.3.0 to 10.2.0.5.0 and facing same issue. The database is slow in general after upgrade compared to 10.2.0.3.0.Try setting OPTIMIZER_FEATURE_ENABLE parameter to 10.2.0.3.
    Refer following link:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams142.htm

  • Exchange SBS2003: Email that is deleted in Outlook 2010 is not deleted on iPhone 4, or marked read after upgrading to 6.0.1.  Win 7 64bit.  2 Other users in our office with iPhone 4 and iPhone 4s aren't having this issue.  They didn't upgrade to 6.0.1.

    Exchange SBS2003: Email that is deleted in Outlook 2010 is not deleted on iPhone 4, or marked read after upgrading to 6.0.1.  Win 7 64bit.  2 other users in our office with iPhone 4 and iPhone 4s aren't having this issue.  They didn't upgrade to 6.0.1 though.  Mail that is deleted or read on the iPhone 4 is deleted or marked read in Outlook 2010.  So it's a one-way problem.

    Exchange SBS2003: Email that is deleted in Outlook 2010 is not deleted on iPhone 4, or marked read after upgrading to 6.0.1.  Win 7 64bit.  2 other users in our office with iPhone 4 and iPhone 4s aren't having this issue.  They didn't upgrade to 6.0.1 though.  Mail that is deleted or read on the iPhone 4 is deleted or marked read in Outlook 2010.  So it's a one-way problem.

  • IPhone 4, 16 GB. After upgrading to iOS 7, despite having 10 GB free, the phone says No storage available. Tried a soft reset, tried restore as well. Still not working. iCloud is switched off.

    My wife has an iPhone 4, 16 GB. After upgrading to iOS 7, despite having 10 GB free, the phone says No storage available. Tried a soft reset, tried restore as well. Still not working. iCloud is switched off.
    Please help.. This has become a pain.. and of course theres no way to go back to iOS 6.

    Make sure you have the Latest Version of iTunes (v11.1.5) Installed on your computer
    iTunes free download from www.itunes.com/download
    Then... Restore as New (not backup) and Re-Sync your Content.
    Restoring  >  http://support.apple.com/kb/HT1414
    SYNCING with iTunes >  http://support.apple.com/kb/HT1386

  • SAP B1 APPLICATION IS RUNNING SLOW IN SERVER AFTER UPGRADE

    Hi,
    The sap application is running slow in server after upgrading it from 9.0 to 9.1 it's taking 5-10 secs to open a document after clicking it and its taking more time in client system.
    what are the steps to be taken so that the application will run without any delay.
    Regards,
    Karthik B

    hi please check bellow thread ,it may help you
    Client Machines Logon to SAP Server is Very Slow
    update the status
    regards
    AKR

  • W/i 5 weeks my iphone broke 2x...after upgrading to ios7

    w/i 5 weeks my iphone broke 2x...after upgrading to ios7

    I went to Settings > iCloud > Documents and Data, then turned off  documents and data, and now it is back to normal.  Apparently you cannot take advantage of both on the iphone 4 and 4s.

  • Hi, my iphone could not be activated after upgrade it from IOS4 to IOS6, it shows that is due to activation server is unavailable and no sim card in the iphone. Anyone can help me please?

    Hi, my iphone could not be activated after upgrade it from IOS4 to IOS6, it shows that is due to activation server is unavailable and no sim card in the iphone. Anyone can help me please?

    It is 99% hacked/jailbroken iPhone to use a different carrier than intended. You have to put the sim from the original carrier or ask them to unlock the iPhone. We as well as Apple cannot help you with this.

  • My iPhone 4 turns off (crashes) after accesing any apps, It work fine when plugged to charger. I tried all troubleshooting steps suggested by Apple but it doesn't work. What could be the problem and what are the solutions?

    My iPhone 4 turns off (crashes) after accesing any apps, It work fine when plugged to charger (power supply). I tried all troubleshooting steps suggested by Apple but it doesn't work. I backed up my phone. I restored it several times. Even I re-installed iphone software. Also I restored it as a new iphone but doesn't work. What could be the problem and what are the availble solutions?

    We can't know if there's a "fixture" because we can't examine your phone.  But Apple can.  Make a Genius Bar appointment and get your phone evaluated.

  • Iphone 3gs problem with network after upgrading to 5.1.1

    Hi...
    I have Iphone 3gs and requested official unlock from my provider. They said they did it and all I have to do is connect it with iTunes.
    I had ios 3.x and upgraded to 5.1.1 through iTunes.
    But now after upgrade, my phone is not unlocked and niether works with original card.
    3G network is one second ok, after one second drops to 1 line, and after that I got No network.
    I managed to make call, but that call only last for 1 second.

    I wouldn't assume that.  Don't know anyone who changed carriers without canceling the original.  The intermittent connections he describes are typical of SIM card issues.
    The point is that your statement that "updating is not enough" is incorrect.  When he "updated" to iOS 5, a full restore was already done. If there were errors during that process, restoring again might help, but its not necessary to restore.

  • IPhone Home Button not working after upgrade to ios 5.1.1

    Hey everyone,
    I'm pretty sure this is a software failure due to the symtoms the iPhone is showing;
    0 - the home button does not work at all when the phone is turned on and running ios 5.1.1, well it used to work okay when i had ios 5.0.1, I upgraded to 5.1.0 and started working randomly, upgraded to 5.1.1 to see if it was fixed with no luck at all.
    1 - When locked the screen does sometime light up, like when you press the home button and don't slide the unlock button. but it does not exit apps anytime, I mean it doesn't act like it's pressing the home button randomly but only when the phone is locked.
    2- The button does work perfectly when iOS is not running: I can get in and get out of recovery and dfu mode at will, that wouldn't be possible if the button were broke.
    3- what else? Oh yea, not really a symtom: Tried the 'home button calibration' several times.
    4 - It's not filthy, since I really cleaned it thoroughly with a powerful tiny nozed air blower I got and gave a rubbing alcohol treatment too.
    5 - when I shut the phone down it instantly turns back on, I can interrupt the turning on for turning the phone into dfu mode (i'm sure It's in DFU mode because the tinyumbrella log monitor tells me)
    I'm now using the 'soft' home button that goes in the accesibility options, but hey, I didn't pay a ton of money for a phone that the same Apple is gonna break down.
    It's out of warranty and I don't have apple stores where I live.
    I'd downgrade to 5.0.1 in a snap if I could but I'm not into jailbreaking, so the shsh blob thingie is not a possibility.
    Any apple dev around that can give me a workaround?
    thanks a lot in advance
    Added more info ~ 

    I had the same problem with Home button not responding after upgrading from iOS 5.1 to iOS 5.1.1 on an iPhone4.   I solved it but not sure exactly what fixed it.   Here is what I did.
    1.  Took it local Apple store Genius appointment.   They used a special tool and took some lint out of the connector opening.   The Home button started working.   They said even though the phone was out of warranty, I could buy a new replacement one without a contract for $150. 
    2.   The Home button stopped working when I got home.   I got some compressed air in a can and blew the air through the connector to try and clean out more dust.   I now keep the phone with the connector opening facing down in my pocket.   I also struck the phone downward on my hand or other soft surface to force as much dust out as possible.
    3.  The Home button still was intermittent.  I then tried to do a hard reset by holding the power on key and the Home button simultaneously for about 10 seconds.  This doesn't work if the Home button doesn't respond.
    4.  I connected the iphone to Itunes via the USB to sync the phone.  While connected, I did a Hard Reset by Holding the Power button and Home button simultaneously.  I noticed the Home button responded better when connected to ITUNES via the USB.
    5.  I did a backup of the iphone4 by highlighting the iphone 4 while connected to ITunes and right mouse click and selecting BACKUP.    I was prepared to reset my phone4 in iTUNES and restore it from the backup.
    The phone worked consistently before I had to do this.
    6.  As a last resort which I didn't need to do, I was going to copy all my settings for the iphone by selecting the phone in iTUNES and looking at all the sync settings.   I would then have restored the iphone to original factory settings and then sync the phone using the copied settings.  This would have made sure that the backup didn't include the bug.
    Fortunately, I didn't have to do step 5 and 6.   Things started working after Step 4.  So I don't really know if it was the iOS 5.1.1 upgrade or pure coincidence that the Home button stopped working immediately after the upgrade.

  • IPhone 4S wont sync music after upgrading to iOS 7 on windows 7

    After upgrading to iOS 7 on my iPhone 4S, I lost all my music.
    When I try and sync (USB) with iTunes 11.1 (on Windows 7)
    it hangs at the last step "waiting for changes to be applied" (step 5 of 5)
    i am looking for weeks for a solution to this problem and i saw meny pepole suffer from it
    but still i cannot find a way to fix it
    help me please

    You got it downloaded and I assume you mean it is installed as well.  It was buggy for me.
    I had to close and restarted iTunes before I could use it properly.
    Then, I had to unplug and replug in my phone before it recognises it.
    Just had to try everything.  As final choice, update over the air.  I try to avoid it as it tends to have more problems than a tethered update.

  • IPod in iPhone 3Gmusic doesn't work after upgrade to iOS4

    My iPhone is very unstable after upgrade to iOS4 and one major failure is that iPod music doesn't work properly, some song (recently purchased from iTunes) cannot be played even if it is in the list. There are a lot of new space in memory after upgrade, seems songs are removed or compressed in some stupid way.
    Spotify is also working like **** after upgrade to iOS4. Also big problems with the phone being slow and hanging in many different kind of modes.
    From being a real iPhone fan, I am very disappointed. Maybe Apple think they are immortal now and think they can release any kind of crap and still keep their customers...

    Try resetting the App Store and Clearing Cookies.
    Reset       Learned from Old Toad
    App Store support. There is troubleshooting and a contact link.
    Support
    Time Machine
    Inherit a Backup
    Inherit a Backup (2)

  • Iphone 5 slow wi-fi after update to ios8

    My iPhone 5 has a slow wi-fi speed or not working at all after upgrading to ios8. My other apple devices including a iPhone 4s works normal. Also the pc from which i am typing now has no problem with the wi-fi. I try-ed to reset to network settings but still the same. When i try to run an internet test with the "speet test" app, it says Latency Test Failed...
    Anybody in the same pain as me?
    Thanks!

    Actually, is not working... I don`t now why it worked for a few seconds after I did the channel change, and then it suddenly stop...

Maybe you are looking for