Good job on your responses. It must get exhausting, I certainly am reading some of the dim posts in this thread.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Benchmark Suggests iPhone 7 Plus Has 3GB RAM
- Thread starter MacRumors
- Start date
- Sort by reaction score
It's like baking a cake. The engineers have to balance things like power consumption, with memory size (density, module counts and whatnot) and costs. Over or under-doing anyone of them could ruin what they were working toward.
Background refresh doesn't do what you think it does which is periodically waking up the device to fetch data vs keeping an interactive TCP socket connection open in the background. And, enabling keep-alive won't prevent iOS from killing SSH sessions in the background. Why guess and be wrong when you can download any SSH app including free ones and see the limitation for yourself?
I do not compare iOS and android...two different OSs.....big differences in features....
Except it's not. It's just saving and restoring app state and not running in the background. Plus, that particular test you're referring to doesn't happen in real life but was contrived to bypass iOS 3 minute background suspended app kill timer. If they had actually taken time to use the apps the background suspended apps would exceed 3 minutes, get killed from memory and reload. BS for the uninformed.
https://developer.apple.com/library...p.html#//apple_ref/doc/uid/TP40007072-CH5-SW2
Last edited:
https://developer.android.com/training/basics/activity-lifecycle/recreating.html
What were you saying?
Well,
a) Because I already have Transmit on my iPad, since I fairly frequently have a need to test connections externally and do so from the cellular network
b) Just to make sure I am not misspeaking I enabled ssh on my Mac, used Transmit on the iPad to login, switched to Safari and surfed the forum before returning after 13 minutes. During that time I occasionally monitored the socket on the Mac with netstat, noting that it remained in ESTABLISHED state throughout. Guess what happened when I switched back to Transmit on the iPad? Can you guess? I think you can. It was exactly where I left it with the session still alive. It did not reconnect, it did not need to
Right back at ya
[doublepost=1473373789][/doublepost]
Can you point out the place in the seemingly unrelated link you posted that you imagine supports your post? The word "minute" doesn't even appear on that page.
Don't you mean Prompt for SSH and not Transmit? This is what Panic, the developer of Prompt SSH, has to say. 10 minutes is for iOS 6 and older and 3 minutes for iOS 7 and newer.
https://library.panic.com/general/ios-background/
How long can I stay connected when the app is running in the background?
We’ve designed our apps to maintain server connections for as long as possible. iOS policies permit up to 10 minutes of background time after the app is suspended or the device is locked. In practice this time can vary, but we request as much time as the system will allow.
When a background transfer is in progress you should see a notification to re-open the app before the connection is terminated. If this isn’t being displayed, please check to make sure that notifications for the app are enabled in theSettings.app.
[doublepost=1473374887][/doublepost]
Android does both, state suspend/restore for apps that don't need to run in the background and also allow apps that need to run in the background to run in the background. Really simple boys. Put an active SSH session in the background on Android/Linux/Windows/MacOS and it continues to run indefinitely. Do the same on iOS 7+ and it gets killed after 3 minutes.
Here's a good free iOS version.
https://itunes.apple.com/us/app/reflection-for-unix-ssh-client/id920472514
No, I mean Transmit. Two things to address here: -
- The page you link doesn't say anything about 3 minutes for iOS 7 and newer
- I just remained connected for 13 minutes with no transfers in progress. netstat doesn't lie and the socket remained established, no TIME_WAIT or any other state indicating reconnection.
Netstat on the server side (Mac) doesn't reflect the state of the client side (iPad). You might want to brush up on how TCP works and the difference between Prompt and Transmit apps then come back.
vSSH states the same iOS limitations.
https://itunes.apple.com/us/app/vssh/id527244258
- Background work (up to 3 minutes for iOS 7, up to 10 minutes for iOS 5/6, alert on timeout)
Patronising, especially misguided patronizing, makes you look insecure.
Connections not being kept alive on the ipad would enter TIME_WAIT quite quickly on the Mac.
I have both Prompt and Transmit. As I said I enabled SSH on the Mac and used Transmit to establish a connection. I assumed you had the knowledge to understand that that meant an SFTP connection. It seems you saw SSH and thought it could only mean a terminal session. Your bad.
Any other ways you care to expose your ignorance?
3GB sounds like a nice balance in the 7 Plus. I was disappointed that the iPad Pro 9.7 only has 2, feels a bit stingy but it's fine for my needs.
I've got BBC iPlayer downloading some TV programs while I read this thread and it definitely pauses after a few minutes. Is this a limitation of the OS or a decision made by the app programmers?
I've got BBC iPlayer downloading some TV programs while I read this thread and it definitely pauses after a few minutes. Is this a limitation of the OS or a decision made by the app programmers?
Wow 3GB of RAM in an iPhone? Androids will need to start coming with 8GB of RAM in order to keep up.
If the client silently drops the connection the server would still show 'established' until TCP timeout.
If you work in IT and your boss asks you to SSH into router/switch and you SFTP instead you'd be fired.
You might want to look in the mirror buddy.
Oh my. You really don't have a clue, do you? You think TCP connections just go from established to closed with no intermediate state? I'm not even sure you do believe that, but you've argued yourself into a corner and will say anything, no matter how absurd.
Fortunately that's in no way relevant to this thread or scenario in any way. The object of the exercise was to see if an iOS app would maintain a TCP connection and stay alive for more than the 3 minutes you said it would. It did. This wasn't even a vaguely effective strawman.
You are spectacularly bad at this.
Apple never specifies technical information to the Audience during the Keynote, in order to not create any confusion and with time constraints.
Might as well not boast about 256gb storage... or the processor... or the GPU... or.....
I didn't hear anything about "pencil" support on the iPhone 7 as suggested by cook.
Except it is... Have you looked at the comparisons between phones? The iPhone runs circles around most Android devices out there. Why stuff a device with RAM that greedy app makers will take advantage of and be lazy with, thus hampering the performance of older devices?
A lot of new people here or trolls, not sure which - Apple never announces RAM.
