summaryrefslogtreecommitdiffstats
path: root/base/ios
Commit message (Collapse)AuthorAgeFilesLines
* Change "high RAM" level for iOS devices from 250 MB to 500MB.lliabraa@chromium.org2013-12-112-3/+3
| | | | | | | | | | All supported devices have at least 256MB so this change aims to keep the method relevant. BUG=327736 Review URL: https://codereview.chromium.org/99473011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@240194 0039d316-1c4b-4281-b951-d872f2087c98
* Fix threading in ScopedCriticalActionstuartmorgan@chromium.org2013-11-222-14/+44
| | | | | | | | | | | | | | | | The locking code doesn't actually work as written, because if the expiration has already fired, but not started running EndBackgroundTask, when the destructor runs, then both the lock and the task ID are pointers into a deallocated object, and potentially garbage. To fix it, move the logic to a ref-counted inner object, so that the expiration handler will keep the object alive. BUG=321667 Review URL: https://codereview.chromium.org/81513003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236669 0039d316-1c4b-4281-b951-d872f2087c98
* [iOS] Adds a version check function for iOS 7.rohitrao@chromium.org2013-06-292-2/+9
| | | | | | | | | BUG=None TEST=None Review URL: https://chromiumcodereview.appspot.com/18171002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209314 0039d316-1c4b-4281-b951-d872f2087c98
* mac: Replace base::mac::ScopedCFTypeRef with base::ScopedCFTypeRef.thakis@chromium.org2013-06-241-6/+6
| | | | | | | | | | | | | | | | | This CL was created fully mechanically by running git grep -l base::mac::ScopedCFTypeRef | xargs sed -i -e 's/base::mac::ScopedCFTypeRef/base::ScopedCFTypeRef/g' git commit -a -m. git clang-format HEAD^ --style=Chromium git commit -a -m. git cl upload -t $TITLE BUG=251957 TBR=mark@chromium.org Review URL: https://codereview.chromium.org/16917011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@208245 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of strings headers in base/.avi@chromium.org2013-06-101-2/+2
| | | | | | | | | | BUG=247723 TEST=none TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/16344006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205309 0039d316-1c4b-4281-b951-d872f2087c98
* Move sys_string_conversions to base/strings.brettw@chromium.org2013-02-072-2/+2
| | | | | | | | This updates callers in base but I left a forwarding header so I can the rest in pieces (there are >300). Review URL: https://codereview.chromium.org/12213061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@181345 0039d316-1c4b-4281-b951-d872f2087c98
* Remove testing for iOS5+ as this is now the minimal version supported.qsr@chromium.org2012-12-212-7/+0
| | | | | | | | | | BUG=None R=stuartmorgan@chromium.org Review URL: https://chromiumcodereview.appspot.com/11661006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@174398 0039d316-1c4b-4281-b951-d872f2087c98
* Changing device ID when device type changes.qsr@chromium.org2012-12-202-1/+32
| | | | | | | | | | | | | | | Because Device id is stored in user preferences, it can cross devices through backup/restore. To mitigate this problem, the device type is also stored in the preferences so that the id is reset when the type changes. R=stuartmorgan@chromium.org BUG=None TEST=Start with a first device, startup sync, enable session syncing. Backup the device, and restore it to another device that is not of the exact same type (iPhone4 to iPhone5 for example). Check that you can see the session from one device on the other one. Review URL: https://chromiumcodereview.appspot.com/11640044 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@174167 0039d316-1c4b-4281-b951-d872f2087c98
* Fixing identifier for device returning a 0 identifierForVendor.qsr@chromium.org2012-12-132-11/+80
| | | | | | | | | R=stuartmorgan@chromium.org Review URL: https://chromiumcodereview.appspot.com/11576008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172888 0039d316-1c4b-4281-b951-d872f2087c98
* Adding utility method to test the version of the OS.qsr@chromium.org2012-10-055-3/+82
| | | | | | | | | | | | | | | This had method to check which version of the OS the application is running. It also changes the ID generation mechanism to use identifierForVendor on iOS6 so that the ID are persisted across application reinstallation. BUG=None TEST=None R=stuartmorgan@chromium.org,mark@chromium.org Review URL: https://chromiumcodereview.appspot.com/11031066 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160414 0039d316-1c4b-4281-b951-d872f2087c98
* Implements iOS device util methods.chenyu@chromium.org2012-08-073-0/+244
| | | | | | | | | | | | Utility methods in this package provides IOS device-specific information. BUG=NONE TEST=NONE Review URL: https://chromiumcodereview.appspot.com/10818023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150324 0039d316-1c4b-4281-b951-d872f2087c98
* Add APIs to protect critical tasks on iOS.chenyu@chromium.org2012-08-012-0/+102
On iOS, once an application goes into the background, it receives no CPU cycles until it is moved to foreground. At any time the OS may kill the application, but the application itself is never told or given any chance to clean up. Thus the time before going into the background is critical to ensure certain tasks have chance to complete. Luckily, an application may ask for a little more time when going into the background by calling certain methods that let the OS know it wants to perform some short-lived work in the background. This cl provides APIs to protect critical tasks in this case. - A class is provided to mark the beginning and end of a critical task for iOS. - A wrapper around a task is introduced that annotates that a class is "critical". Right now we have the wrapping code for iOS and it is just a no-op for other platforms. BUG=NONE Review URL: https://chromiumcodereview.appspot.com/10835032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149422 0039d316-1c4b-4281-b951-d872f2087c98