AT&T, Alcatel-Lucent release joint statement regarding slow iPhone 4 upload speeds

Posted by:
Date: Wednesday, July 7th, 2010, 10:48
Category: iPhone, News

Following up on the recent frenzy of news since iPhone 4 users began reporting crippled upload speeds on AT&T’s 3G network at the start of the holiday weekend, AT&T and component supplied Alcatel-Lucent jointly identified a software defect that’s apparently triggered under certain conditions.

Per MacRumors, the following joint statement has been released:

“AT&T and Alcatel-Lucent jointly identified a software defect – triggered under certain conditions – that impacted uplink performance for Laptop Connect and smartphone customers using 3G HSUPA-capable wireless devices in markets with Alcatel-Lucent equipment. This impacts less than two percent of our wireless customer base. While Alcatel-Lucent develops the appropriate software fix, we are providing normal 3G uplink speeds and consistent performance for affected customers with HSUPA-capable devices.”

There is no word on a timeframe for deployment of the software fix for Alcatel-Lucent’s equipment.

AT&T upload speed limits may be bug, not intentional data throttling

Posted by:
Date: Wednesday, July 7th, 2010, 04:44
Category: iPhone, News, Software

Following up on yesterday’s story in which some iPhone 4 users are experiencing slow upload speeds on AT&T’s network, the incident may be a genuine bug and not intentional data capping.

Per AppleInsider, users across the U.S. have reported upload speeds of around 100Kbps, well below the capabilities of the HSPA-capable iPhone 4. The issue has affected users in a number of major metropolitan areas across the country, including New York and Los Angeles.

While some speculated the problems were a result of bandwidth throttling by AT&T, that is not said to be the case. Instead, sources close to the story have stated that the issues are a result of an unintentional software glitch related to High-Speed Uplink Packet Access in some sections of the country. When working properly, HSUPA can allow uplink speeds of 5.76Mbit/s.

It is believed that a fix for the issue is forthcoming, though AT&T did not provide a comment on the matter as of Tuesday evening.

Apple cites iPhone 4 reception problems as software bug, promises fix within a few weeks

Posted by:
Date: Friday, July 2nd, 2010, 04:30
Category: iPhone, News

First, as you may have noticed, there are issues with the iPhone 4′s reception. Still, Apple says this might not be what you think according to a recent press release from the company:

“Upon investigation, we were stunned to find that the formula we use to calculate how many bars of signal strength to display is totally wrong. Our formula, in many instances, mistakenly displays 2 more bars than it should for a given signal strength. For example, we sometimes display 4 bars when we should be displaying as few as 2 bars. Users observing a drop of several bars when they grip their iPhone in a certain way are most likely in an area with very weak signal strength, but they don’t know it because we are erroneously displaying 4 or 5 bars. Their big drop in bars is because their high bars were never real in the first place.

To fix this, we are adopting AT&T’s recently recommended formula for calculating how many bars to display for a given signal strength. The real signal strength remains the same, but the iPhone’s bars will report it far more accurately, providing users a much better indication of the reception they will get in a given area. We are also making bars 1, 2 and 3 a bit taller so they will be easier to see.

We will issue a free software update within a few weeks that incorporates the corrected formula. Since this mistake has been present since the original iPhone, this software update will also be available for the iPhone 3GS and iPhone 3G.

The full press release can be found here and it seems a bit strange that Apple is once again blaming the formula.

Still, this is what it is and stay tuned for the software fix as well as additional details as they become available.

Apple releases mobile configuration profile update for iOS 4 Exchange ActiveSync bug

Posted by:
Date: Thursday, July 1st, 2010, 03:10
Category: iPhone, News, Software

Apple has issued a configuration profile that addresses an issue in iOS 4 that may cause sync problems with Microsoft Exchange or Google Mail and Calendar.

Per AppleInsider, the company notes that “immediately after updating to iOS 4, some users may notice that Exchange ActiveSync Mail, Contacts, or Calendars do not sync, or sync very slowly. In addition, some Exchange Server administrators may notice their servers running slowly.”

The issue, according to a report by the site , is that iOS 4 sets a low 30 second default timeout for server requests that can overwhelm the server.

Apple has published a mobile configuration update file that administrators can distribute to iPhones and iPod touch users running iOS 4. The configuration update can also be downloaded directly to the device from Mobile Safari, using a link Apple provides.

Once installed and the device is restarted, the configuration update sets the timeout to 240 seconds, a change that has proven to fix sync issues for most users.

If you’ve seen this issue on your end, please let us know.

Carbon Copy Cloner updated to 3.3.3

Posted by:
Date: Wednesday, June 30th, 2010, 04:51
Category: News, Software

carbon.jpg

Late Tuesday, Carbon Copy Cloner, the shareware favorite for drive cloning operations by Mike Bombich, reached version 3.3.3. The new version, a 3.7 megabyte download, adds the following changes:

- Fixed a “divide by zero” error that would cause backup tasks involving very few files to fail at the end.

- Fixed a bug that would cause CCC and the scheduled task helper application to crash when certain filesystems were mounted.

- CCC now enables ownership on the target volume regardless of the ownership setting on the source volume. Previously, clones made of Macs in Target Disk Mode would have incorrect ownership information on system files if the target volume did not have ownership enabled.

- Fixed an issue in which a scheduled task would fail to run properly if the user logged out and then logged back in.

- Fixed an issue in which a scheduled task would log many errors if the user logged out while the scheduled task was in the middle of a backup.

- Fixed an issue in which CCC would not run a “Backup everything” scheduled task that used the “Delete items from the target that do not exist on the source” option.

- Fixed an issue in which a scheduled task that was configured to back up to a disk image would not run if it was set to run “When the target volume is reconnected”. These tasks now run properly when the underlying volume is reconnected to your Macintosh, whether it is a local volume or a mounted sharepoint.

- Fixed an issue in which CCC would report minor errors if a directory disappeared from the source volume in the middle of a backup task.

- Fixed an issue in which preferences from a very old version of CCC would cause errors while trying to select a source volume.

- Fixed a memory leak related to files with Access Control Entries.

- CCC no longer creates the target folder on a remote Macintosh. This enforces the behavior of aborting the backup task if the backup volume is not available, or is not mounted at the expected mountpoint on the remote Macintosh.

- The CCC.log file is now properly created when CCC is run under a non-admin user account.
Minor interface enhancements, specifically around the presentation and content of the “bootability” checks.

- Minor bug fixes around the creation of encrypted disk images.

- If you checked the box to display the scheduled task “task finished” panel only when errors occur, this panel will no longer re-present itself after the scheduled task is reloaded on startup. The setting will only be reset when changes are made to the scheduled task’s configuration in the Scheduled Tasks window.

- CCC now saves only modified scheduled tasks when clicking the Save button in the Scheduled Tasks window.

- Updated the list of items that CCC automatically ignores from a backup set. See the documentation for complete details about this list.

- Fixed an issue in which Intel systems would be permitted to run portions of CCC using Rosetta, leading to reduced performance and potentially crashing behavior.

Carbon Copy Cloner 3.3.3 retails for a US$10 shareware registration fee. The application requires Mac OS X 10.4 or later to run.

iPhone 4 “Death Grip” analyzed, iOS 4.0.1 update expected this week to resolve issue

Posted by:
Date: Monday, June 28th, 2010, 04:36
Category: iPhone, News

Following reports of reception issues observed by new iPhone 4 owners (tagged the “Death Grip” across the Internet), additional insight reveals that this may actually be a software issue that could be cleared up in the near future.

In terms of identifying the problem, clear observations of mobile signal strength and how they are affected by the placement of users’ hands are difficult to perform in part because there are multiple factors involved in receiving a mobile radio link, including outside interference and the conductivity or mass of different people’s hands.

Additionally, cellphones in general (and in particular the iPhone) have always only presented a very rough approximation of signal strength in the signal bar display, averaged over time. It appears that iOS 4, more so than previous iPhone software, presents a less accurate signal meter, showing less signal at times than an iPhone 3GS while still being able to achieve the same or better call quality.

Per AppleInsider, this has led some to jump to the conclusion that the reception problems noted by some iPhone 4 users are the sign of a hardware design flaw related to its stainless steel band antenna design. Apple’s chief executive Steve Jobs stoked a whiplash of blogger frenzy when he reportedly responded that users “were holding it the wrong way,” blocking the signal with their hands.

A variety of people have demonstrated identical problems with other phones, from the Android based Nexus One to the iPhone 3GS. However, the fact that problems observed in the iPhone 3GS are much more pronounced when the device is upgraded to iOS 4 indicate that there is also a software issue involved in the matter. iPhone 4 users can’t downgrade to earlier versions of the core software, making it impossible to compare its relative performance.

According to the article, several messages have arrived from Apple’s tech support forums confirmed that a iOS 4.0.1 software fix addressing the issue would ship early next week (as early as Monday).

The fix is expected to address a issue in iOS 4 related to radio frequency calibration of the baseband. Readers who saw the original forum discussions say that the issue is believed to occur when switching frequencies; because the lag is allegedly not calibrated correctly, it results in the device reporting “no service” rather than switching to the frequency with the best signal to noise ratio.

iOS 4 introduced some enhancements to how the baseband selects which frequencies to use, so it makes sense that the error may have crept into those changes. Additionally, this explains why iOS 4 has also caused similar problems for iPhone 3GS users.

The core software problem is likely augmented by hand placement, as Jobs noted in pointing out that holding the new phone (or any mobile device) in such a way that attenuates the signal should simply be avoided.

If you’ve seen the “Death Grip” issue on your end or have anything to add, let us know.

Google Chrome 5.0.375.86 released

Posted by:
Date: Thursday, June 24th, 2010, 03:33
Category: News, Software

google-chrome-logo

Google Chrome, Google’s new web browser, just reached version 5.0.375.86 for the Mac. The new version, an 25.4 megabyte download, offers the following the following changes:

- Medium XSS via application/json response (regression). Credit to Ben Davis for original discovery and Emanuele Gentili for regression discovery.

- Medium Memory error in video handling. Credit to Mark Dowd under contract to Google Chrome Security Team.

- High Subresource displayed in omnibox loading. Credit to Michal Zalewski of Google Security Team.

- High Memory error in video handling. Credit to Google Chrome Security Team (Cris Neckar).

- High Stale pointer in x509-user-cert response. Credit to Rodrigo Marcos of SECFORCE.

Google Chrome requires Mac OS X 10.5 or later and an Intel-based Mac to install and run.

If you’ve played with it and have an opinion, let us know what you think in the comments.

Mozilla releases Firefox 3.6.4 update

Posted by:
Date: Wednesday, June 23rd, 2010, 03:52
Category: News, Software

elfirefox

Late last week, Mozilla.org released version 3.6.4 of its Firefox web browser. The new version, an 18.6 megabyte download, sports the following major changes:

- Version 3.6.4 makes four critical security fixes. Unlike the Windows version, it does not introduce the Out-of-Process Plug-in sandboxing feature. That is expected for Mac users in Firefox 4.

Firefox 3.6.4 is available in more than 70 different languages and requires a G3, G4, G5 or Intel-based Mac, Mac OS X 10.4 or later and 128MB of RAM to install and run. If you’ve snagged the new version and have any feedback to offer about it, let us know in the comments.

Apple releases Mac OS X 10.6.4 update

Posted by:
Date: Tuesday, June 15th, 2010, 15:42
Category: News, Software

snowleopard

After months of anticipation, Apple released its Mac OS X 10.6.4 update for its Mac OS X 10.6 (“Snow Leopard”) operating system on Tuesday.

The update, which ranges in size from a few to several hundred megabytes, includes the following fixes and changes:

General fixes and improvements:
- Improves compatibility with some Braille displays
- Resolves an issue that causes the keyboard or trackpad to become unresponsive
- Resolves an issue that may prevent some Adobe Creative Suite 3 applications from opening
addresses issues copying, renaming, or deleting files on SMB file servers
- Improves reliability of VPN connections
- Resolves a playback issue in DVD Player when using Good Quality deinterlacing
- Resolves an issue editing photos with iPhoto or Aperture in full screen view
- Resolves an issue with Parental Controls Time Limits for Open Directory or Active Directory users
- Resolves a display sleep issue with MacBook Pro (Early 2010) computers
- Resolves an issue with MacBook Pro (Early 2010) computers in which the right speaker may sound louder than the left speaker
- Includes Safari 5.0; for more information about Safari 5.0, see this webpage

Fixes and improvements for Aperture 3:
- Adds tethered shooting support for additional digital camera models
- Addresses IPTC metadata compatibility issues

Fixes and improvements for external devices:
- RAW image compatibility for additional digital cameras
- Resolves an issue with using third-party USB web cameras
- Resolves an issue with noise when using some third-party FireWire audio devices
- Resolves pairing issues with Apple remotes

Mac OS X 10.6.4 requires Mac OS X 10.6 or later to install and run and can be downloaded via Mac OS X’s built-in Software Update feature.

Adobe releases Flash Player 10.1.53.64

Posted by:
Date: Friday, June 11th, 2010, 03:52
Category: News, Software

adobelogo

Late Thursday, Adobe officially released Flash Player 10.1.53.64, the newest version of its multimedia software for Mac OS X. The new version, a 7.4 megabyte download, offers a slew of security fixes detailed here with full (and extensive) release note changes documented here.

The new version is available for free and requires Mac OS X 10.5 or later to install and run.