Need browser feature that removes all cookies created by tab when tab is closed. Have ability to add exceptions for sites where you want the cookies to persist (like banking, slashdot, etc).

Does anything like that exist?

Incognito mode is great and all but I need exceptions to handful of sites where I want the cookies to persist.

My family switched from Android phones to iPhones a few months ago. Bought iPhones 5S $150 ea new. Had to do additional carrier unlock for $30 (it was locked to Sprint, I'm on super cheap T-Mobile MVNO). Can't beat that price.
5SE may have better camera and CPU but I don't see a need for that. 5S is still snappy and is not lagging.

The reason I switched, in case anyone is interested, is because Google is shit: https://code.google.com/p/andr...
Are you fucking kidding me Google? It's been a year since this regression was reported and noone gives a shit. My option was to downgrade to Android 4 and live with security holes, fix it myself or toss the phone.
Fixing it myself is an OK option but I'm too old for that shit.

LibreSSL patches today:

Avoid an infinite loop that can occur when verifying a message with an unknown hash function OID.
Diff based on OpenSSL.
Fixes CVE-2015-1792 (however, this code is not enabled/built in LibreSSL).
ok doug@ miod@

Avoid a potential out-of-bounds read in X509_cmp_time(), due to missing length checks.
Diff based on changes in OpenSSL.
Fixes CVE-2015-1789.
ok doug@

Avoid an infinite loop that can be triggered by parsing an ASN.1
ECParameters structure that has a specially malformed binary polynomial field.
Issue reported by Joseph Barr-Pixton and fix based on OpenSSL.
Fixes CVE-2015-1788.
ok doug@ miod@

I'm sorry, but Nexus 7 slow charging is anything but a rare problem. Run a search maybe? Google doesn't care. It's not charger problem and it's not a cable problem. The problem is either software or charger circuit. I just don't have time to hack this POS hardware, software to get it working.

I also have the charging problem on my original Nexus 7 as well as other headaches -- no TRIM support with encrypted partitions, super slow. Not really using that Google garbage anymore. Bought iPad Mini with retina and never looked back. I guess I'm too old for this hacking shit to get it working.

It's not just Nexus 7. Google seems to fuck up everytime they do a software update. I also have Nexus 4 and after 5.1 OTA upgrade device displayed error and was bricked. Not an issue for me as I can just go and install factory image wia fastboot but I did a search and a lot of users are hitting this issue and they don't know anything about fastboot or installng android sdk just to fix Googles failure to QA crap they are releasing.

Wi-Fi stopped reconnecting in sleep mode since 5.0 on my Nexus 4. It just seems that Google keeps breaking functionality with every update.
I actually opened an issue in their tracker for this as it kinda is important for me https://code.google.com/p/andr...
I'd go back to 4.4.4 but of course they had to make encrypted data partition backwards incompatible.

I'm not buying an Android device ever again.

https://code.google.com/p/andr...

This is ridiculous.

I'm fed up with issues I've had with Google Nexus line Android devices:
1) Nexus 7 first gen. Enable encryption and device becomes superslow due to not having a proper fstrim support.
2) Galaxy Nexus. No more updates after 4.3, not even security updates.
3) Nexus 4. This recent dialer issue. I'm still getting updates but what good are they if they only break things that worked before?

Honest real life application:

Producer-consumer with lock-free implementation.
Producer thread (or threads) queues to linked list atomically (insert at head using compare-and-exchange).
Consumer thread periodically empties the list by exchanging head pointer with NULL (compare-and-exchange). To make this list FIFO, consumer will now need to reverse the list.

Why not doubly linked list? Because we want a lock-free implementation for scalability.

Hint: you can still see the onld screen with new permissions marked as NEW by scrolling all the way down in app description to PERMISSIONS and clicking on"View details".

But I completely agree with you. Totally lame move by Google. I want to see this screen when I press the update button. Config option for advanced users would be sufficient.

Gentoo doesn't keep the source in the repository, but it has the hashes.
from /usr/portage/app-crypt/truecrypt/Manifest:

DIST truecrypt-7.1a.tar.gz 1949303 SHA256 e6214e911d0bbededba274a2f8f8d7b3f6f6951e20f1c3a598fc7a23af81c8dc SHA512 b5e766023168015cb91bfd85c9e2621055dd98408215e02704775861b5070c5a 0234a00c64c1bf7faa34e6d0b51ac71cd36169dd7a6f84d7a34ad0cfa304796a WHIRLPOOL 5e7f4360746a30639aea96eaf4deac268289c111c0efa96f50487527f0406499 2c26ad4c8ae0fd565d80e77f0ce8add82b03930d877fe5adedc8a733b482fe38

(the filter did not like awful long strings of letters so I added spaces to WHIRLPOOL and SHA512 hash strings.

Did you actually measure it (adrobench storage read/write test for example) and did not find any difference?
I'm assuming not and since Nexus 5 is fast to begin with there isn't any *noticable* difference.

Only recently (KitKat release) Google added TRIM support for encrypted volumes. Without that the performance difference between unencrypted (with TRIM) and encrypted (no TRIM) was very noticable after device was used for some time.
Unlucky for owners of older devices (1st gen Nexus 7, Galaxy Nexus) it does not work. This problem is very serious on 1st gen Nexus 7, to the point where it becomes unusable if encryption is used: https://code.google.com/p/andr...

No, android does not have full device encryption unfortunately. Only the encryption of /data partition. In most cases this should be sufficient though.

I'm not sure about external sdcard for devices that have it. I have Nexus so emulated sdcard is part of /data and it gets encrypted. If that is not the case with external sdcard, tough luck.

Also, doesn't look like google particularry cares about older devices and device encryption. See this issue for example (TRIM support on encrypted volume): https://code.google.com/p/andr...
I'm not holding my breath to ever get this resolved for my 1st gen Nexus 7.

Recent Jellybean versions require adb authentication. You have to accept adb client's private key from the phone and the phone has to be unlocked before you can do so.

You can disable this "feature" with a hammer. It's pretty straightforward and I've done that with my Visa Paywave cards. Punching the hole will also work but I'm not sure if such card will be accepted by merchants.
If your credit card has both RFid (like Visa Paywave) and chip/pin contacts, destroying RFid chip will also most likely destroy chip/pin interface because they would likely be packaged on the same chip.

You can turn the chip off with a hammer.

Tracfone SIM cards only work in Tracfone phones.
There are cheaper pay as you go GSM plans, for example Spotmobile ($0.10/min, min recharge $5 every 120 days, uses T-Mobile and AT&T networks).