1password does this on iOS and supposedly lastpass does too (though I haven't checked yet. Read about it today.)
I will try 1password today. Thank you!
Let us know how it works. My understanding with all of these password managers (I use KeePass) is that you need to use a password to open the app if it has been closed. Once the app is open, you can use TouchID rather than your password. If this has changed it would be a good thing.
Please read andrei article.That's not true. Also, you can change the governor and other settings to change how many cores are used and when. One of the huge benefits to rooting.
Myth. No longer so.Potentially, Exynos 7420 is still better in multicore performance, but apple single core performance will negate most of that for all but benchmarks most likely.
The way 1Password works is that you have to enter your password after (a) your phone has been rebooted, or (b) you haven't used TouchID to enter 1Password within a month. In other words, point A is the only one that will affect most people. There was a bug when 1Password's TouchID implementation first came out that had it request the password way too much, but that was fixed awhile ago. To note, 1Password is free on iOS now, but you still have to pay for the Windows/Mac application. I think I was able to find a 25% discount code when I bought it.
To note, I used to use KeePass before I bought 1Password. Also, if you do upgrade, do not get rid of KeePass. I did have a few instances of logins from KeePass that did not import correctly into 1Password. Once I found and fixed any of the logins, they were fine, but I would've been stuck without having KeePass lingering.
Myth. No longer so.
http://anandtech.com/show/9518/the-mobile-cpu-corecount-debate/4
The way 1Password works is that you have to enter your password after (a) your phone has been rebooted, or (b) you haven't used TouchID to enter 1Password within a month. In other words, point A is the only one that will affect most people. There was a bug when 1Password's TouchID implementation first came out that had it request the password way too much, but that was fixed awhile ago. To note, 1Password is free on iOS now, but you still have to pay for the Windows/Mac application. I think I was able to find a 25% discount code when I bought it.
To note, I used to use KeePass before I bought 1Password. Also, if you do upgrade, do not get rid of KeePass. I did have a few instances of logins from KeePass that did not import correctly into 1Password. Once I found and fixed any of the logins, they were fine, but I would've been stuck without having KeePass lingering.
whereas IOS is a realtime OS
Which a) isn't true (and you would have to be a fool to try and argue the contrary) and b) is nothing to do with a realtime-capable OS.which never stutters.
Fingerprints are more secure than PIN codes and passwords when used by themselves, and done well (that is, making it impossible to access the information remotely); they're tied to you, and they're not easily faked. That's why Apple Pay uses only fingerprints for authentication.
When used alongside PINs and passwords, they're different -- they're for convenience. They don't add security, but they encourage everyday users to lock their phone where they might otherwise throw caution to the wind.
Huh. Everything I've read about fingerprint sensors points at them being trivial to exploit/subvert (and I don't mean for anyone with access and inclination to use a sharp knife!). I can't say I've read up on that particular topic in say the last couple of years, but on the flipside I haven't heard of any innovations on the topic that make sensors more difficult to fool.
You can technically use fake fingerprints to trick these readers, but that usually involves lifting prints from the phone and using them to create a gel mould. If you're in the position where this is a genuine threat, you're probably a spy... and the initial fingerprint check isn't going to be your only line of defence.
Citation needed; an OS regarded as realtime capable is one that has to be able to guarantee response times in real time. It's not a trait typically required of an OS as most users' needs are "as quick as the platform can manage it", and guaranteeing a data stream's delivery.
https://en.wikipedia.org/wiki/Comparison_of_real-time_operating_systems
Notice the lack of big-name operating systems on that list, including iOS.
Which a) isn't true (and you would have to be a fool to try and argue the contrary) and b) is nothing to do with a realtime-capable OS.
Huh. Everything I've read about fingerprint sensors points at them being trivial to exploit/subvert (and I don't mean for anyone with access and inclination to use a sharp knife!). I can't say I've read up on that particular topic in say the last couple of years, but on the flipside I haven't heard of any innovations on the topic that make sensors more difficult to fool.
Myth. No longer so.
http://anandtech.com/show/9518/the-mobile-cpu-corecount-debate/4
Want to bet on who wins the browser benchmarks when the 6s plus gets its full review?
It's not as if the iPhone 6 won every single browser benchmark. It's usually just the newest phone at the time that wins the benchmark, as you'd expect.
Sure, but the exynos has it beat on multicore. If their theory on multicore being better in web browsing specifically holds up the 6s should lose. The iphones typically do very well though, which is why i'm skeptical.
Sure, but the exynos has it beat on multicore. If their theory on multicore being better in web browsing specifically holds up the 6s should lose. The iphones typically do very well though, which is why i'm skeptical.
I think the only reason Android uses 8 cores for web browsing is because web sites are so inundated with various trackers and other java script being served up, that multiple threads can be created to handle them in parallel to cut down on the load time.
However, with Apple releasing content blocker functionality, that particular use case becomes a lot less relevant. I'd be willing to be that if you blocked all of that stuff on Android, the core utilization would drop significantly for web-browsing.
In that type of scenario, having two powerful cores is going to outperform more, less powerful cores. Also, given Apple's more restrictive approach to multi-tasking, there's even less of a need for additional cores, where as Android is better equip to take advantage of them.
There are already some reports showing how much the content blockers speed up load times, but I'd bet that the flip side of this is significantly reducing the thread count to quickly load the page.
I wish more people would try Windows Phone. Better than iOS and Android. The app selection would be better if more people got on the platform. Hopefully Windows 10 universal apps fixes this problem.
I wish more people would try Windows Phone. Better than iOS and Android. The app selection would be better if more people got on the platform. Hopefully Windows 10 universal apps fixes this problem.
But it's not. It's just not.
There are nice touches in Windows phones, like Cortana and live tiles... but even if you think they're better, they're not so significantly better that they would get you to leave an iPhone or Android phone. There are a number of features you're giving up, too, like Handoff (Apple's ability to pick up an app where you left off as you switch platforms) or Google Now.
And simply speaking, the hardware and software selection is just too far behind for any software advantages to matter. Microsoft effectively abandoned flagship devices after it launched the Lumia Icon/930, and it's only coming back nearly two years later with the Lumia 950/950 XL. And like it or not, there's a vicious circle with apps. People don't write Windows phone apps because there aren't many phones, so they don't write many apps, so... Microsoft can't just tread water with good-enough devices and updates, it has to do something so fundamentally different that the momentum heads in the opposite direction.