Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Don't know if this has been posted before, but my college teacher works at Kraft as a part time sys admin and he told me that they already have the image of 4.0 on their [Kraft] servers (but he doesn't have access to it). He said it will be released on April 8 :)

edit: just to clarify. Apple preloaded the 4.0 image on the Kraft servers so that the entire Kraft employee base (many get iPads for free, my teacher one of them, as well as iPhones) won't hammer the iTunes servers on release day. I'm assuming they do this with most big corporations that do business with Apple.
 
I agree - "Touch OS" could work. Although they would lose the effect of hinting at OS X (the halo effect, you know).
I have always assumed that given the popularity of the iPhone OS-devices, Apple would eventually make iPhone OS and OS X share more and more features in terms of "look and feel", so as to nudge people in the direction of the Mac.

What do you guys think? Aren't we already seeing this trend in both OS'es?

Well if they are going to push on with the yearly release model that is very popular in software circles these days then...

Well the defining Product of the company is the software OS X it seems to drive everything anyway.
So why not just "Apple OS 2010/2011/2012/......"

With the product family:-(just don't use the word Editions)
Server 2010 ($499.99)
Developer 2010 ($99.99)
Mac 2010 ($29.99)
iPad 2010 ($19.99)
iPod 2010 ($9.99)
iPhone 2010 (free)
 
Changes I'd like to see to the lock screen include being able to decline a call and still be able to use the phone. When my phone is locked, if someone happens to call you answer via the unlock slider. If you press the sleep button to decline the call, the slider will still answer the call.

First press of the sleep button silences the ringer, second press declines the call.
Next time, when posting features you hope they add, make sure it doesn't already have it.
 
The iPhone can not multi-task. Running multiple (background) processes, including services associated with native apps, is not multi-tasking.

umm, yes it is... the OS multitasking... The definition of multitasking is running multiple processes "at the same time". Just because it only allows one front app at a time, doesn't mean the OS isn't multitasking, it just means you aren't multitasking.
 
If 4.0 covers running custom apps in parallel, they will have to limit it in some way. No offense to developers but I'm convinced that less than 5% of all apps are behaving good in the sense that no memory is wasted and the cpu stays cool. There are these nice tools to monitor an apps activity on the phone but I'm sure most of the developers either do not check them or do not have time to do so.

There MIGHT be some custom apps which will be allowed to stay running. But how to decide which one?

One thing would be: Let the user choose. Then every complaint about short battery life can go to the custom-app-developers. But I'm sure, this will block sales in the near future. And I predict if this is the case, users will all have running at least 10 apps in parallel as they forget to quit them. So the solution would be that the user can choose, which application remains when pressing the home button and which one does not. But this is task-managing and I doubt that Apple wants the users to deal with that.

Another solution would be that apple employees check the app after a submission whether it is a green light (clean memory consumption and cpu sleep while inactive) or a red light (busy, memory hog) according to internal guidelines which are not known to anybody. This would have the effect that people start thinking about optimization but I hightly doubt that it will have the desired effect. Even for developers producing high quality apps, this will be a pain.

My prediction is: There is a 25% chance of getting "multitasking". It would be nice in some way but Apple will assure, it is much nicer without and will have no serious impact on how to handle content.

Just my thoughts.
 
My prediction is: There is a 25% chance of getting "multitasking". It would be nice in some way but Apple will assure, it is much nicer without and will have no serious impact on how to handle content.

Just my thoughts.

My prediction is: - there are too many people using the original iPhone and the 3g, so apple will release os4 with loads of whizzy woo new features, but it will run like a dog on the old hardware
this will gently encourage people to upgrade to 4g
 
Mail - it's impossible to receive mail if there isn't a service running in the background.
Safari - reqiured to keep pages loaded in memory so they don't have to refresh when you re-launch the browser.
Phone - required to receive phone calls.
iPod - required to play music in the background.
Voice Memos - allows you to continue to record when returning to the home screen.

None of these are multi-tasked; they are background processes.

Would you say that the phone app is open because you can receive a call at any time? No.

Alternatively, would you say the phone app is open if you are on a call and return to the home screen? Yes.

That's the difference I'm talking about. The iPhone OS has a lot of background processes, including some native apps. These processes monitor the sensors, wait for phone calls, send SMS messages, connect to WiFi networks, detect button presses and touch events/gestures, check for email, auto-dim and lock the screen, update the date/time, etc.

The iPhone only has two instances of multi-tasking: remaining on a call while in other apps and double-clicking the home button for iPod controls.

Having two or more apps open is not the definition of multi-tasking, it's only one example. It's impossible to have this advanced mobile OS without any kind of multi-tasking. And if you can't see app it doesn't mean that it's not multi-tasking. The screen is simply to small to implement it the way you could see. On Pre you switch by flicking, on iPhone it looks like you closed the app with home button, but it's just the way it works for now. open iStat and you will see that Safari or other Apple apps run at all times.
 
Why? If it's compatible with the 3G, then there is no reason for it not to be compatible with the original iPhone. The 3G and original iPhone have identical specs (CPU speed, RAM, Camera).

Because the Original iPhone is likely to have reached the end of its support cycle from Apple. It has remained in support despite being superseded twice now. My guess is that the third supersession will find it dropping out of support officially, as by then all AppleCare on all original iPhones will have ended.
 
Oh and App developers should be forced to save state. That shouldn't be an option. It is irritating to use an app (say GTA:CW) get a phone call, switch to said call, deal with it, switch back to GTA:CW and find myself back at a safe house with all my progress lost. It appear that very few of the games I have actually save where you are (it seems like none of them do).

Technically, we are required to save state, they just let it slide because it's an obnoxious problem in object oriented code-you basically have to make a super object that knows about every state variable in the app or a separate set of functions that know how to restore state without re-triggering the other behavior. It's much easier (though perhaps more expensive) to save out the app's memory to disk, assuming they're doing memory management correctly, and read the memory back in at a later time, and pretend nothing happened.. Unfortunately, that can some times be more memory than the user has available on their cramped early-model iPhone, it takes large amounts of time, and counts against your limited total #of writes for the flash memory.


Besides, "Photos" doesn't even save state, so don't get on our backs yet!

(is no one asking for a search mode in "Photos")
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_1_3 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7E18 Safari/528.16)

notromeel said:
How can multitasking work with a lousy 256mb of ram in both the 3GS and even the ipad. Multitasking relies heavily on ram. It would be a disaster in my opinion. Maybe in some new hardware versions, but in the current crop we will be back to iphone 1.0 slowness. :(

True dat.

Except that jailbroken 3gs' can run lime 10 apps at once without slowing down. But don't let facts get in the way of your hating.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_1_3 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7E18 Safari/528.16)



Except that jailbroken 3gs' can run lime 10 apps at once without slowing down. But don't let facts get in the way of your hating.

They can run 200 too, if they don't consume resources. But don't let facts get in the way of your worshipping :)
 
One for All

Because the Original iPhone is likely to have reached the end of its support cycle from Apple. It has remained in support despite being superseded twice now. My guess is that the third supersession will find it dropping out of support officially, as by then all AppleCare on all original iPhones will have ended.

I hope that 4.0 will support all iDevices.

That said, the first two iPhone and iPod Touch hardware generations have 128MB RAM which may not be enough for a satisfactory 3rd-party-App-multitasking solution (even with a decent hardware paging implementation).

Therefore I expect no 3rd-party-App-multitasking on the 1st and 2nd generation hardware.

Supporting all iDevices keeps the developer story clear, benefits the environment (prolonging product life), and gets Apple yet more publicity and goodwill (support for "old" products is almost unheard of in the mobile industry).

Finally, support for old iDevices is good, because they are often handed down to our siblings and children -- and they therefore serve as 'gateway drugs' to hook new users into Apple's ecosystem :)
 
Time to enable "hidden" FM transmitter/receiver !

Remember that...
http://gizmodo.com/5200034/next-generation-iphone-may-have-fm-transmission-capabilities

Wouldn't tomorrow be the perfect moment to unveil iPhone/iPod's new ability to receive FM, instant record, tag songs (think iPod nano), buy them on iTunes directly OTA; but also receive RDS-based traffic info that'll feed Maps app and upcoming GPS nav apps; and allow iPod/iPhone to broadcast audio directly to the car stereo via FM (in countries where it is permitted)...

BTW does iPad also boast an FM receiver/transmitter like its older brother ?


Apart from that, 4.0 would be great if it could add:
- SMS delivery report
- SMS character count (think French accents... e.g. typing ê needs unicode encoding thus 1 SMS is counted every 70 characters!)
- SMS groups
- Wifi sync of iTunes
- Downloads podcasts over Wifi or 3G
- Screen rotation lock (via a gesture...)
- Enhanced search in contacts
- Use of iPad photo connection kit and keyboard accessories with iPhone/iPod touch
- Accessibility settings that don't put in negative colours the wallpaper
- native iChat running in background (instead of AIM third-part app...)
- tethering iPhone with iPad Wifi (dream on, man...)
- for fun, an "iPod with clickwheel" emulator with an on-screen clickwheel and teh ability to play Sonic, Pole Position or iPod Quiz (good times...)
 
when do u think they gonna release first "beta" for testing to developers? I'm really excited to try it out on my 3GS ( also hope the HW gonna be enough..)
:eek:
 
when do u think they gonna release first "beta" for testing to developers? I'm really excited to try it out on my 3GS ( also hope the HW gonna be enough..)
:eek:

Highly probable we might get a beta tomorrow, but with Apple, you never know. Less than 24 hrs to find out :)
 
Basics I want:

More than 5 minutes before auto lock.
A way to jump to the last screen of apps.
A way to have apps update automaticlly. The whole process is manual and it's 2010 ffs.
 
Because the Original iPhone is likely to have reached the end of its support cycle from Apple. It has remained in support despite being superseded twice now. My guess is that the third supersession will find it dropping out of support officially, as by then all AppleCare on all original iPhones will have ended.

This isn't a legitimate reason. The original iphone and the iphone 3G share the same SoC, and they still continue to sell the 3G. For the original iphone to not be supported anymore, they'd have to stop supporting all 3G models as well. The only thing they could do is artificially prohibit the upgrade on the grounds that it doesn't have a 3G radio or some other inconsequential feature.
 
Another solution would be that apple employees check the app after a submission whether it is a green light (clean memory consumption and cpu sleep while inactive) or a red light (busy, memory hog) according to internal guidelines which are not known to anybody. This would have the effect that people start thinking about optimization but I hightly doubt that it will have the desired effect. Even for developers producing high quality apps, this will be a pain.

Might work if the OS itself didn't have a memory leak ;-)
And, wow if you want to talk power consumption, I've got three words for you: WiFi, GPS, 3G.

(Ok, to be fair, the memory leak was in 2.1)
 
A way to have apps update automaticlly. The whole process is manual and it's 2010 ffs.

Yeah, I mean totally: you have to uncompress the zip format and then type in the paths for the individual bundle components. Then I have to perform an MD5 (or whatever) hash of the binary and compare it to the signed certificate to verify no changes have been made. Then I have to parse the info.plist file to check for supported url schemas and record the paths to the launch images. Finally, you have to pull out photoshop and mask the icon edges for rounded corners, then composite a glossy curvy gradient on top of them...

Oh wait, by "manual" you meant you have to tell the computer "Yes, I want this app/all apps updated."

You have no idea what's it's doing to update an app; that's what we call "automatic."
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_1_3 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7E18 Safari/528.16)

Prom1 said:
I'm betting on.......

1. Limited Multi-Tasking

2. iBooks for the iPhone

3. Updated UI look to match iPad

1. on new hardware ONLY; I'm 100% positive on this.
2. indeed. There is nothing wrong with iPhone as the screen is sufficient.
3. Not really necessary or properly feasible. The apps rotating hiding side menu bars, sure I'm all for it. But the UI ... not sure what you mean. I thought iPad was fashioned after iPhone.

I think there'll be something VERY interesting for us in store; something familiar, yet more of something spectacular. Until the core PIM apps are updated to be in sync with one another I'm sticking with my Berry.

There are probably a couple of dozen people max who are 100% sure what is in os 4, and you are not one of them (or if you are, you're about to be unemployed)
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_1_3 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7E18 Safari/528.16)

Prom1 said:
I'm betting on.......

1. Limited Multi-Tasking

2. iBooks for the iPhone

3. Updated UI look to match iPad

1. on new hardware ONLY; I'm 100% positive on this.
2. indeed. There is nothing wrong with iPhone as the screen is sufficient.
3. Not really necessary or properly feasible. The apps rotating hiding side menu bars, sure I'm all for it. But the UI ... not sure what you mean. I thought iPad was fashioned after iPhone.

I think there'll be something VERY interesting for us in store; something familiar, yet more of something spectacular. Until the core PIM apps are updated to be in sync with one another I'm sticking with my Berry.

There are probably a couple of dozen people max who are 100% sure what is in os 4, and you are not one of them (or if you are, you're about to be unemployed)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.