1. New font

2. Flatter, translucent look

3. Improved Notification Centre

4. Better Spotlight

5. AirDrop and Handoff

6. Flatter, faster Safari

7. Draw in Mail

8. Call with Messages

9. Cross platform iCloud Drive

10. Instant Hotspot

1. These are the thinnest iPhones yet!

With a thickness of

0.27 inches for the iPhone 6

0.28 for the iPhone 6 Plus.

2. We’re also talking of an impressive display

1334 by 750 pixels (326 pixels per inch, or over one million pixels, slightly higher than 720p) for the iPhone 6.

1920 by 1080 pixels (401 pixels per inch, or over two million pixels, and native 1080p) for the iPhone 6 Plus.

3. Of course, both are bigger too

6.22 inches high by 3.06 inches wide (the iPhone 6 Plus)

5.44 inches high by 2.64 inches wide (the iPhone 6)

4. Good news: both will have zippier processors

The A8 chip, Apple’s second-gen 64-bit offering with some 2 billion transistors,

5. Their batteries just got much better

it do up to 80 hours of audio

14 hours of video

up to 24 hours of talk time over 3G

16 days of standby

6. All hail the new cameras

The camera that changed photos now does the same for video.

1080p HD at 60 fps, slo-mo at 240 fps

7. Faster wireless. Far and wide

With faster LTE — up to 150 Mbps — iPhone 6 users can experience faster download and upload speeds

Up to 3x faster Wi‑Fi

8. Security. Right at your fingertip

Your fingerprint. Your iPhone.

9. Your wallet. Without the wallet

More secure payments.

Keep your purchases private.

The major credit cards. With the same major benefits.

10.The biggest iOS release ever

iPhone comes with an amazing collection of apps.

Over one million apps. Infinite possibilities.

Start on your iPhone. Finish on your Mac or iPad.

Whatever developers do next, you can be sure it will be big.

iOS 8 includes more than 4,000 new APIs for developers.

1) App Extensions

2) Touch ID Authentication

3) Home Kit Framework

4) Handoff

5) Unified Storyboards for Universal Apps

6) Health Kit Framework (In Build Health App)

7) Interactive Notification

8) QuickType Keyboard

9) Family Sharing

10) PhotoKit

Manual Camera Controls

Photos Framework

Sharing options

Photo Editing

Custom Actions

11) Games


Scene Kit

Sprite Kit

AV Audio Engine

12) Swift

13) iCloud Drive

Document-Related Data Migration

Cloud Kit

Document Picker

14) WiFi Calling

15) Safari credit card scanning

A few things missing from iOS 7:

The ten thing that are no more available in iOS 7.0.

1) UIDevice uniqueIdentifier is probably the most notable of all these. It was deprecated back in iOS 5 but as of iOS 7, it is just flat out gone. Xcode won’t even compile if you try to call it. However, if any existing app on the device does call it, the returned value will no longer be the UDID but instead NSUUID.

2) MAC Address. This one goes hand in hand with the uniqueIdentifier. Apple really doesn’t want you getting at any kind of ID that will uniquely identify a device. If you try to get the MAC Address on iOS 7 you will only get back 02:00:00:00:00:00.

3) libsyscall gethostuuid .This one is part of Core Bluetooth. Apple is being very loud and clear: if you want any kind of unique ID use identifierForVendor, advertisingIdentifier, or CFUUID.

4) UIViewController wantsFullScreenLayout In iOS 7, all view controllers are full screen.

5) UIColor scrollViewTexturedBackgroundColor and the like are now deprecated. UIColor objects that provided background textures for earlier versions of iOS are gone.

6) MapKit has deprecated the entire MKOverlayView class in favor of the new MKOverlayRenderer now available in iOS 7.The existing overlay views have been replaced with an updated set of overlay renderer objects that descend from the MKOverlayRenderer class.

7) CoreLocation has deprecated CLRegion in favor of CLCircularRegion. The CLRegion class continues to exist as an abstract base class that supports both geographic and beacon regions.

8) The Audio Session API in the Audio Toolbox framework is deprecated. Apps should use the AVAudioSession class in the AV Foundation framework instead.

9) The UUID property of the CBCentral class is deprecated. To specify the unique ID of your central objects, use the identifier property instead.

10) Many drawing additions to the NSString class are deprecated in favor of newer variants.

1) Control Center (Some things should be only a swipe away. And now they are.)
2) Notification Center (Today is all about you.)
3) Multitasking (While you multitask, it dose, too.)
4) Camera (All the right formats. Right at your fingertips.)
5) Photos (Life is full of special moments. So is your photo library.)
6) AirDrop (Drop everything.)
7) Safari (With things out of the way, there’s way more web.)
8) iTunes Radio (Hear where your music takes you.)
9) Siri (You’re going to like what you hear. And see.)
10) App Store (Find the right app for wherever you are.)
11) Find My iPhone (And if you can’t, at least there’s this.)
12) iOS in the Car (Best passenger ever.)
13) Mail
14) Weather
15) Messages

Property Attributes Indicate Data Accessibility and Storage Considerations
Use Accessor Methods to Get or Set Property Values
01. atomic //default
02. nonatomic
03. strong=retain //default
04. weak= unsafe_unretained
05. retain
06. assign //default
07. unsafe_unretained
08. copy
09. readonly
10. readwrite         //default
01. atomic 
-Atomic means only one thread access the variable(static type).
-Atomic is thread safe.
-but it is slow in performance
-atomic is default behavior
-Atomic accessors in a non garbage collected environment (i.e. when using retain/release/autorelease) will use a lock to
ensure that another thread doesn’t interfere with the correct setting/getting of the value.
-it is not actually a keyword.
Example :
@property (retain) NSString *name;
@synthesize name;
02. nonatomic
-Nonatomic means multiple thread access the variable(dynamic type).
-Nonatomic is thread unsafe.
-but it is fast in performance
-Nonatomic is NOT default behavior,we need to add nonatomic keyword in property attribute.
-it may result in unexpected behavior, when two different process (threads) access the same variable at the same time.
@property (nonatomic, retain) NSString *name;
@synthesize name;
Suppose there is an atomic string property called “name”, and if you call [self setName:@”A”] from thread A,
call [self setName:@”B”] from thread B, and call [self name] from thread C, then all operation on different thread will be performed serially which means if one thread is executing setter or getter, then other threads will wait. This makes property “name” read/write safe but if another thread D calls [name release] simultaneously then this operation might produce a crash because there is no setter/getter call involved here. Which means an object is read/write safe (ATOMIC) but not thread safe as another threads can simultaneously send any type of messages to the object. Developer should ensure thread safety for such objects.
If the property “name” was nonatomic, then all threads in above example – A,B, C and D will execute simultaneously producing any unpredictable result. In case of atomic, Either one of A, B or C will execute first but D can still execute in parallel.
03. strong (iOS4 = retain )
-it says “keep this in the heap until I don’t point to it anymore”
-in other words ” I’am the owner, you cannot dealloc this before aim fine with that same as retain”
-You use strong only if you need to retain the object.
-By default all instance variables and local variables are strong pointers.
-We generally use strong for UIViewControllers (UI item’s parents)
-strong is used with ARC and it basically helps you , by not having to worry about the retain count of an object. ARC automatically releases it for you  when you are done with it.Using the keyword strong means that you own the object.
@property (strong, nonatomic) ViewController *viewController;
@synthesize viewController;
04. weak (iOS4 = unsafe_unretained )
-it says “keep this as long as someone else points to it strongly”
-the same thing as assign, no retain or release
-A “weak” reference is a reference that you do not retain.
-We generally use weak for IBOutlets (UIViewController’s Childs).This works because the child object only
needs to exist as long as the parent object does.
-a weak reference is a reference that does not protect the referenced object from collection by a garbage collector.
-Weak is essentially assign, a unretained property. Except the when the object is deallocated the weak pointer is automatically set to nil
Example :
@property (weak, nonatomic) IBOutlet UIButton *myButton;
@synthesize myButton;
Imagine our object is a dog, and that the dog wants to run away (be deallocated).
Strong pointers are like a leash on the dog. As long as you have the leash attached to the dog, the dog will not run away. If five people attach their leash to one dog, (five strong pointers to one object), then the dog will not run away until all five leashes are detached.
Weak pointers, on the other hand, are like little kids pointing at the dog and saying “Look! A dog!” As long as the dog is still on the leash, the little kids can still see the dog, and they’ll still point to it. As soon as all the leashes are detached, though, the dog runs away no matter how many little kids are pointing to it.
As soon as the last strong pointer (leash) no longer points to an object, the object will be deallocated, and all weak pointers will be zeroed out.
When we use weak?
The only time you would want to use weak, is if you wanted to avoid retain cycles
(e.g. the parent retains the child and the child retains the parent so neither is ever released).
05. retain = strong
-it is retained, old value is released and it is assigned
-retain specifies the new value should be sent -retain on assignment and the old value sent -release
-retain is the same as strong.
-apple says if you write retain it will auto converted/work like strong only.
-methods like “alloc” include an implicit “retain”
@property (nonatomic, retain) NSString *name;
@synthesize name;
06. assign 
-assign is the default and simply performs a variable assignment
-assign is a property attribute that tells the compiler how to synthesize the property’s setter implementation
-I would use assign for C primitive properties and weak for weak references to Objective-C objects.
@property (nonatomic, assign) NSString *address;
@synthesize address;
07. unsafe_unretained
-unsafe_unretained is an ownership qualifier that tells ARC how to insert retain/release calls
-unsafe_unretained is the ARC version of assign.
@property (nonatomic, unsafe_unretained) NSString *nickName;
@synthesize nickName;
08. copy
-copy is required when the object is mutable.
-copy specifies the new value should be sent -copy on assignment and the old value sent -release.
-copy is  like retain returns an object which you must explicitly release (e.g., in dealloc) in non-garbage collected environments.
-if you use copy then you still need to release that in dealloc.
-Use this if you need the value of the object as it is at this moment, and you don’t want that value to reflect any changes made by other
owners of the object. You will need to release the object when you are finished with it because you are retaining the copy.
@property (nonatomic, copy) NSArray *myArray;
@synthesize myArray;
09. readonly
-declaring your property as readonly you tell compiler to not generate setter method automatically.
-Indicates that the property is read-only.
-If you specify readonly, only a getter method is required in the @implementation block. If you use the @synthesize directive in
the @implementation block, only the getter method is synthesized. Moreover, if you attempt to assign a value using the dot syntax,
you get a compiler error.
@property (nonatomic, readonly) NSString *name;
@synthesize name;
10. readwrite 
-setter and getter generated.
-Indicates that the property should be treated as read/write.
-This attribute is the default.
-Both a getter and setter method are required in the @implementation block. If you use the @synthesize directive in the implementation
block, the getter and setter methods are synthesized.
@property (nonatomic, readwrite) NSString *name;
@synthesize name;

iPhone 4 iOS 5 not receiving MMS all the time:

1)Go To Settings>General>Network>Cellular Data Network
and put this settings

My MMS Settings are:
APN: wap.voicestream.com
MMS Proxy:
MMS Max Message Size: 1048576


APN: wap.cingular
MMSC: mmsc.cingular.com
MMS Proxy:
MMS Max Message Size: 614400

Now in Settings>Messages you can get MMS Messaging ON over here.


Get every new post delivered to your Inbox.

Join 34 other followers