Good of you to do the investigating SOS. However, lthough not AT ALL thrilled with the sound of the T5, I would have to agree with mhammann about at least SOME of the negativity.
As Confucious said, "It's all bull****."
Point 2: This is the most disturbing to me. The whole point of FLASH is "keeping it." A hard reset does NOT delete anything protected by JackSafe (I've tested it twice!). I have said all along that this isn't "true flash" but rather "borrowed flash" - and like an SD Card can go south, so can this. NOT good at all!!
Point 4: I'm not surprised the T5 "may" have conflicts with BBVFS and would defend the T5 on this point. BBVFS has had bugs all along!! There were conflicts in restoring portions of TealMaster, TealLock and others, supposedly fixed in 2.15 but I wasn't taking chances. A failed restore was the reason I switched to CardBackup (jkware). I wouldn't use BBVFS to restore a dishtowel, T5 or not.
Point 5: I can attest to Point #5 probably being incorrect - I remember clearly seeing that the heap was 16MB - I remember noticing because I use TealMover's ability to "tweak" an app's request from the default 3300 bytes. I upped MobileDB(3,300 > 6,000), Agendus (3,300 > 6,500) and Acid (7,168 > 8,500) with good results - I couldn't do that if the "max" was 4MB - and I'm sure they haven't "gone down" on the T5.
Point 7: Battery life will NEVER be enough. More "real estate" to search through, ROM, RAM, Flash, faster processor, bigger screen on ALL the time instead of just when "slider is open" on a T3 -- all reasons for battery life to be all over the place. BT on/off, beaming on/off, degree of brightness all play a role - I read (on the link recommended by mhamann) about 5 hours; I get at least that on my T3 and would probably get more on the T5 because I'm "power stingy." I can NEVER understand people complaining about battery life on the T3, T5 or anything else - carry a cigarette lighter/wall charger and/or a "Pwer to Go" thingie, and be done with it. I haven't drained mine YET using it "most of the day," on and off. If someone does, then they'll have to stop and take a breath and recharge it. Life is hard.
Point 9: The calendar bug is also VERY bothersome and more proof that P1 pre-release stuff too soon for testing, too little for marketing and too late for users' needs. I've had enough "calendar crap" with Agendus to have to deal with an INTERNAL one as well . . . Jesus, P1 -- have a couple of RedBulls and TEST it first, okay??
Point 11: Hotsync is bound to be slower because there's more to HotSync; I doubt it's dramatic, and even if so, what the hell -- my T3 syncs in around 16 seconds, 30 seconds if lots of Bonsai and Docs2Go changes. So that goes to 47 seconds? Are we really all that busy? Besides, with the drag and drop USB virtual thing, a lot of hotsyncing could be avoided altogether.
Somewhere between the careful, perhaps pessimistic view most of us are taking (me included), and mhamanns terrific optimism, lies the truth. It's probably not the nightmare some claim, but it's certainly not the sharpest knife in the shed either. I was originally THRILLED with the sound of the T5 because it was perhaps "last shot" at a landscape OS5 model, but got a little gloomy after some investigating about the definition of "flash."
It depends on what your definition of "is" is.
WHEN IN DOUBT, VOTE WITH YOUR WALLET.
T3 lads . . . . T3. They're gettin' cheaper!! Sprat, Flash and go!! CardBackup! TealStuff! Bonsai! AcidImage! FindHack! SnapCalc! MobileDB4!
There's an AWFUL LOT RIGHT WITH THE WORLD, and for that matter "right with Palm." I just don't think the "newest and greatest" . . . . .
is.