i thought it went back to the app after the call was done, or if you declined...
overall it does, sometimes it just goes back to the app yet not necessarily where you left off.
I'm talking about refining it I suppose.
That is the fault of the application developer: they are meant to detect the unload (or in 4.0 being suspended to the background) and save enough state to come back to where they were.
overall it does, sometimes it just goes back to the app yet not necessarily where you left off.
I'm talking about refining it I suppose.
That is the fault of the application developer: they are meant to detect the unload (or in 4.0 being suspended to the background) and save enough state to come back to where they were.
Its a larger flaw with the OS. You shouldn't be taken from your current app without it asking first.
I agree in that it is a flaw with the OS and not a fault of the developer. Just yesterday for example, I decided to try a Texas Hold'Em game with a friend that we could play connected via Bluetooth. I received a call and it disconnected us. That is not the developers fault. There is no reason Apple can't implement this since simultaneous data/voice is possible.
You do know that its a phone right? the primary function is to make and accept calls. The phone app takes precedence over anything else and therefore is going to fill your screen when a call is coming in.