| || |
Re: How to do the 4.1.2 Jelly Bean update without a hitch
Okay, I'll tell you exactly how so. You wrote:
Originally Posted by KSoD
There is only 6 steps at best for the update.
1. Load Kies 2. Update Kies 3. Remove SD Card 4. Put phone in download mode 5. Tools>Firmware Upgrade and initialization 6. Type in Model and Serial as seen on the back under Battery All done.
Notwithstanding that it should have been "[t]here are only 6 steps...", I nevertheless wrote, in response, that said steps were (just categorically, I meant) wrong; and my reason was (and remains) because it's positively not right for everyone... with "everyone" being the operative word. There may, indeed, be only those six steps required for at least some users -- who knows, maybe even most -- but many others will end-up wishing they'd followed my steps. And so, then, it's just prima facie folly to suggest that those six steps are right for everyone, as you suggested. That was my point.
And the reason for that is my more overarching point that as long as there's a risk of failure which could have been avoided by simply following my steps, then said steps should always be followed; even if some of them may, for a given user's phone, in a given moment, not actually be necessary... just as a pilot checks-out more on a plane during pre-flight than he knows he really needs to, in order to be safe.
For some phones -- many, even, I dare say -- my steps would, indeed, be overkill; but for all phones, at least, they will nevertheless work. Your steps, on the other hand, will not... not, at least, for all phones. That was my point. I'm sorry you're so offended and upset that you cannot see that.
Of course, as I made crystal clear in my original (and I think at least one other, besides this one) post, here: If the user rooted his/her phone, and flashed a custom ROM, then all bets, regarding at least my steps, are off. I'm not addressing that kind of user, here. That's your kind of user. And if you had more carefully read my words, instead of rushing through them, and being so blindly angered by them that you just had to take me on, here, then you'd have noticed that. Careful, careful, careful, young man. And then you wonder why I have so little respect for your work.
And, by the way, don't be so impressed with everyone at XDA. Yes, there are some serious experts there -- really high-end, make-the-hair-stand-up-on-the-back-of-your-neck good -- but there are also people there, as there are here, clearly, who don't even know what they don't even know...
...and so insensibly assail those who do. Be careful not to be like them... er... oh... wait... I'm sorry: That ship has already sailed, I guess.
And one other thing, just for the record: The external SD card does not need to be removed for an OS update/upgrade... at least not if one does a GSM reset first, like my steps prescribe; but even if one doesn't , as it turns out. Again, with your witchcraft... yikes!
And that, right there, makes questionable, pretty much all else that you have to say. Really. It's just so facially outrageous that... well.. it's a wonder anyone reads any further. If you were in a lecture hall, and the person speaking about some scientific topic suddenly threw in that something or another about it is only true, or will only work, if one speaks an incantation over it while hopping around in circles on one foot wearing a pink boa and purple beads, you'd stand-up and leave. Insisting that a newly-OS-updated/upgraded phone needs "settling" or "stabilizing" time -- especially days worth of it -- is just... well... I can't even find the words for how outrageous it is. Witchcraft, witchcraft, witchcraft. Gimmee a feakin' break.
Originally Posted by KSoD
Oy. [sigh] Media scanning and all the rest that you mention takes seconds to minutes, then it's done. It either works, right away, or it doesn't. It doesn't, in any case, take days. It's not a new car engine which needs to be "broken in" (or a voodoo doll, that needs to "season," which I only mention because that seems to be the sort of thing you're into). If it doesn't work pretty much right away, then something's wrong. And no amount -- especially days worth -- of "settling" or "stabilizing" will fix it. Granted, if most of the 16GB of internal/pseudo-external storage is full of media, and if most of, say, a 32GB external card is similarly full, then, yes, media scanning could take several minutes; actually, a whole buncha' minutes, in fact. No argument, here. But not "days." Or even hours. C'mon.
Originally Posted by KSoD
Geez. [shakes head in disbelief]
As to battery: In my other posts, here (which, in your anger, you're clearly not reading), I've talked about the battery issue; and how a post-OS-update/upgrade battery recalibration may be necessary... is likely, in fact. The phone will not recalibrate the battery by itself. At best, it will average its readings, over time, to the point that they become within a barely acceptable range of accuracy (your observation of which, it now occurs to me, may be why you thought there was "stabilizing" going on), but the bottom line is that most batteries need to be recalibrated after an OS update/upgrade, if there's to be any prayer of both proper battery use, as well as accurate reporting by the phone of battery level. To that end, I provided, in another post (#47, I believe), the precise steps for doing that, to wit:
That's what I wrote about batteries in post #47; here, and it's dead-on accurate (unlike your witchcraft). Either do it or don't, it matters not to me.
Recalibrating a Galaxy-class/family phone battery:
- Connect the phone to the charger with the phone powered on, and allow the phone to charge until it shows 100%.
- Disconnect the phone from the charger, and power it off.
- Reconnect the phone to the charger with the phone powered off, and allow the phone to charge until the battery indicator shows 100%.
- Disconnect the phone from the charger and power it on.
- Once the phone is powered completely on, power it off again and reconnect it to the charger until the battery indicator shows 100%.
- Disconnect the phone, power it on, and use it.
My personal recommendation is to do those steps, then use the phone normally for three days, then re-perform said steps. Repeat the steps, then, for any given battery a minimum of four (4) times per year.
If you are constantly swapping batteries in and out of phones -- and especially if you don't perform proper shut-downs of the phone each time, before so doing -- then all bets are off. At that
point, how the phone both uses batteries, and reports their levels, could be all over the map!
However, even once one has one's phone battery properly calibrated, there could still be an entire raft of reasons why the phone seems to use more battery after an OS update...
...chief among them that an OS update restores a phone to its old-battery-sucking ways. Phones, as shipped from the factory, are set to auto-sync everything in the background, constantly. They're set with their screens too bright. They're set with battery-sucking wallpapers. Etc.
All that stuff needs to be turned-off in order to eek the most battery life out of any phone... most off all a battery hog like the Note!
I also wrote, in that same post #47, under the heading "Some battery-saving tips:," a comprehensive list of things one may do to reduce battery usage. They, too, are all dead-on accurate; and if people will actually use them, and not count on the phone to "settle" or "stabilize," they, I promise, will experience greater battery life.
It might be worthy of note, at this point, that at least my stuff, around here, includes no witchcraft; and so for that reason, and because its prima facie helpfulness is recognizable to even an everyday, non-technical end-user (er... you know... other than you, apparently), I'll wager that readers who just want to be helped around here will get more from it than they've gotten from your witchcraft-laden stuff...
...and that, it seems, is what's so sticking in your craw. If so, then my simple advice to you is to just grow up, fortheloveofgod. Sheesh!
I never wrote that it's the method which causes boot loops. You need to read more carefully; and, as long as I'm at it, you all need to read all of my postings, here, and take them as a whole, and get the complete picture, because one thing I'm beginning to notice, here, is that now I'm repeating, obviously because you're all so self-interested that you can't be bothered to read any posts other than either your own, or replies thereto. I'm providing a lot of useful information here -- every bit of it more useful than suggesting pure witchcraft with such ridiculous notions as it taking days for such things as "settling" or "stabilizing," whatever that even means -- and you, for one, are missing it because you can't get past being called on your nonsense by someone who actually knows what he's talking about. Take a giant step back and try to see the big picture, forgodsake. But back to my point...
Originally Posted by KSoD
What I said was that it's the failure to use my method -- chiefly the GSM reset immediately before performing the OS update/upgrade using KIES -- from the outset, which can result in a phone not being in the precise factory-new state used by Samsung and AT&T engineers during OS update/upgrade testing; and so, then, a statistically unacceptable probability of failure is introduced. My steps eliminate that probability of failure, even if, for a given users, some of said steps may not be necessary. If you had ever actually been paid, in life, to help people; and if you didn't want your time wasted, you'd understand this notion:
Better to perform steps to the completion of a task which will eliminate all possibilities of all manner of problems -- even those which may not actually exist for a given device on which said task is being performed -- than to take shortcuts from the outset and discover, upon only perceived completion, that there were problems, after all, which simply could have been eliminated by better and more all-inclusive procedure from said outset.
Anyone who has ever worked in an IT department understands this. They would also recognize, in you, the kind of end-user who just can't understand how IT works, or the importance and necessity of procedure, and the importance of avoiding that which is only anecdotal... or, worse, which is witchcraft.
Finally, if you were a more careful reader -- and more mature and experienced, too, I'll wager -- you would have understood that my boot loop story was but an example: Only one (1) possible outcome of failing to follow my steps. A broad generalization, then, such as you made, may simply not be inferred from it by a reasonable person. Of course, you're showing your reasonableness, here, to be in question, so I guess I shouldn't be surprised. Again: Careful reading, young man. Give it a try. It'll make you seem less foolishly youthful and arrogant.
Oy. Again with the uncareful reading. A word of advice: When you're pissed-off at someone in a place like this, like you clearly are with me, force some calm on yourself, and slow down at least enough to really and truly comprehend, as you read your opponent's words, so that you don't fire back things which make you look foolish. Of course that ship, for you, in this case, has already sailed... but I'm just sayin'.
Originally Posted by KSoD
Anyway, that you know how to do all those things qualifies you, indeed, to help a person who has done those same things. In fact, I think one of my points, here, regarding my advice, is that if a person has rooted and generally just gone down that road, then as far as my advice is concerned, they're on their own; and so, then, such as yours is all with which they're left. I think I was pretty clear about that.
My overarching point, though (and you'd know this if you had been reading my other posts, here), is that people like you -- and those over at XDA -- need to realize that normal, everyday end-users generally don't want to become techno-geeks who get their rocks off on electronically (or physically, either) breaking-open the phone, and getting past restrictions imposed by Samsung and AT&T, and getting into the bowels of the thing, and making changes. So doing may make it so that cooler things may be done to and with the phone by your likes, but it also makes the phone entirely too high-maintenance for the likes of the typical, non-technical, everyday end user who just wants the damned thing to work! Rooting and flashing custom ROMs is not the road that such users should be taken down (hence my calling it the "primrose path")...
...and what you techno-geeks don't realize is that when normal, everyday end-users get into places like this and ask questions, they'll presume both that such as you know what they're talking about, and also have their best interests at heart, and next thing they know, they've done something to their phones, on such as your recommendation, which ultimately harms them. And by that, I mean true, objective, palpable and real-world harm. You guys, in your arrogance, just don't seem to realize that. You've lost your sense of what it's like to not be as technically hip as you've all become. And so you get into places like this and recklessly -- yes, that's the right word -- toss around solutions which no non-technical, everyday, end-user should ever even know about, much less try! You think that because you're all geeks, that everyone should both understand you, and do as you do. If you all had more experience with normal, everyday, non-technical end-users, you'd be more responsible!
And so, then, such as you become the last kind of person to whom such normal, everyday, non-technical users should ever listen. That was my point. It's not that you don't know what you're talking about when it comes to rooting and flashing custom ROMs. Rather, it's that that kind of expertise is useless -- nay, even objectively harmful -- to the non-technical, everyday end-user. And such as you should be more responsible, and better stewards of the knowledge; and should just help people who only want the OS update/upgrade on their non-rooted phones to work the first time...
...which my steps are guaranteed to accomplish. Your steps, yes, will work for at least some of them, no argument, here! But if their phones have become altered at the OS level -- which includes, in some cases, simply settings/configuration text files -- such that said phones' OS's are no longer precisely as they were shipped from the factory (which many poorly-written apps can cause); or if any of the OS files have become corrupted, then only my steps will ensure (and that's the operative word, "ensure") a successful OS update/upgrade the first time out.
That being the case, then why not just adopt my steps every time out so that whether or not there's a problem, the outcome will still always be the same? (a rhetorical question)
That's my whole point, here: That we should perform the steps that will ensure success regardless what the phone's been through.
Your way only works if the phone, in its weeks, months or years of use, somehow didn't get its OS fundamentally changed or damaged. However, the longer the phone's been in use, the lower the likelihood of that. After all, even if no app changed anything -- not even settings/configuration items -- at the OS level (which, of course, is ridiculous to assume), OS files can still become corrupted. File corruption must always be presumed, regardless the OS... be it Windows, iOS, Linux, Chrome, etc. Mass storage devices -- be they mechanical or solid state -- routinely corrupt files. Only someone who has fallen on his/her head too many times in life would argue with that.
And so, why in the world would anyone intentionally perform the OS update/upgrade steps that you've prescribed, knowing that so doing introduces an unacceptably-high risk of failure...
...when simply doing it my way (which way, more than anything else, simply prescribes performing a GSM reset before performing your steps) will ensure that the phone is first returned to the precise state that Samsung and AT&T engineers used when testing the very OS update/upgrade that one is attempting? (again, a rhetorical question)
Yet you see the logic of witchcraft like "settling" and "stabilizing." [sigh] Oy. [shakes head in disbelief]
Originally Posted by KSoD
I'm sorry: Did you mean "...because I have 25+ years..."? Just checking. If you're going to contract, then please appropriately use an apostrophe, Mr. Close-is-good-enough. You're not a Mac user, by any chance, are you? (another rhetorical question)
Originally Posted by KSoD
And did you mean "...too knowledgeable..."? That one should be self-explanatory.
It's convoluted logic, in any case. It's not that you're so knowledgeable about Android phones which makes you unqualified to help people -- at least normal, everyday, non-technical people -- fix them. On the contrary, it's that that expertise has helped you to forget what it's like to be a normal, everyday, non-technical Android phone user... else you'd never prescribe leading them down the primrose path of rooting and custom ROM flashing.
As for how you help people with Windows PCs, I have to suspect that you've forgotten the same sort of thing with them, too. Moreover, no number of years of mere "use" of a PC qualifies anyone to fix anything, or to help anyone beyond really basic, "here, click on this instead" kinda' stuff.
Everyone thinks s/he's a damned expert... I've seen it my entire career; and have spent a good deal of it cleaning-up after them and their messes. When you've got pushing 40 years of not merely computer use, but ongoing formal training, certifications, and more time fixing computers, for a hefty fee, than actually using them, then maybe you can deign to match techno-wits with the likes of me. Until then, how 'bout you just show at least a little respect. I don't think that's asking too much. I've certainly paid, after all, my dues.
And I'm sorry -- no, really... I am -- that that so ticks you off, but have you and my other critics, here, even bothered to notice what you're all doing? And how insensibly ridiculous it is? Fortheloveofgod, all I did, here, was prescribe a method of OS updating/upgrading that will ensure success, regardless what's happened to the phone during its use; a method that I now realize maybe I should have added that I figured-out after watching so many people in other forums complain that their OS update/upgrade turned their phones into slow and/or error-prone dogs; or, worse, bricked them...
...and, even more importatnly, a method that I discussed on the phone two years ago... er... wait... lemmee think... yeah, right around two years ago... maybe a month or two, either way... with one of the AT&T engineers who works directly with the Samsung engineers in Japan, and who agreed with every last bit of my logic and procedure. Before that, I had run it past a Samsung second-tier support person, and got the same response. But, what I'm herein indenting (and even, what the heck, changing the color of) immediately below, to set it off from the rest of what I'm herein writing, is the really important part, for our purposes, here:
Perhaps I should also have added, here, that when I asked the AT&T guy why a GSM reset is not prescribed as part of an OS update/upgrade, he replied that they had talked about that, but decided that since it wipes the phone, and that end-users tend to be too stupid (his word, not mine) to know how to protect themselves (via backup) from the consequences of that, they'd just take their chances on that most users' phones have not had their OS's sufficiently goofed-up, through normal use (due to bad apps changing things they shouldn't, or OS file corruption) that the OS update/upgrade would fail. And for those for whom it does fail, there's always the AT&T Device Support Center.
Plus, he added, AT&T, at least (and he said he couldn't speak for Samsung, but he bet me a case o' Moosehead that if he got one of its engineers on the phone and asked him/her to comment, s/he'd agree) doesn't really want end-users to know how to do a GSM reset. I then asked him if he thought a plain, ol' reset, of the type that one may access from the phone's "settings" area would do as a pre-requisite to an OS update/upgrade, and he said unquestionably "no," at least for phones that actually need any kind of factory reset in order to increase the statistical likelihood of a successful OS update/upgrade. He said that for phones like that, only the GSM reset is sufficiently rigorous.
I then asked him if the kind of reset one may achieve by simultaneously holding-down the both power and volume-rocker buttons during boot-up would do, and he said that at least that one would be better; but that AT&T doesn't really want end-users to know about that, either. When I pointed-out that gabazillions of us already know about at least the power-button-volume-rocker method (and a lot also know about the GSM reset), he said he understood that, but that it comes down to a question of what AT&T's willing to support, and so, therefore, what it's willing to officially reveal, in writing, anywhere.
He confessed, then, that it was easier for AT&T to just hope that as many OS updates/upgrades as possible would go smoothly because, in the end, most phones wouldn't really need a factory reset; and to just refer those for whom the OS update/upgrade didn't go well, because the phone really should have been factory reset prior to said update/upgrade, to the AT&T Device Support Centers. That's why said centers don't like to do OS updates/upgrades for someone who walks in and says that s/he hasn't even tried it yet. Said centers only want to help those who tried, but ran into problems...
...just exactly as I explained in other posts, here.
Please... I beg of you (and especially ol' "ebulldog," here): Pause for a moment and fully grasp what he told me. That, in the end, is why AT&T and Samsung don't include any kind of factory reset in the OS update/upgrade instructions!
I'm sorry I didn't earlier share all that. Perhaps if I had, then you and others would have had more respect for my prescribed steps. There's always a method to my madness. People who know me and my work understand that.
For some reason, you seem to have so much invested in your steps being right that you refuse to see my AT&T-approved/endorsed (albeit entirely unofficially, and only verbally, during an informal phone call) logic; and so you assail me for it. You're so angry and caught-up in being right, seemingly at all costs, that you're not even carefully reading -- either that to which you're responding, or my other words around here, either -- and so you're just making yourself look even more foolish. Stop. Take a giant step back. Read everything I've written, and get the big picture!
Or... wait! Do you have a problem with someone prescribing steps that will more likely result in success? Do you actually want the OS updates/upgrades of non-technical end-users, who don't have your kind of expertise to get them out of trouble, to fail? Is that what's going on, here? Is your sense of self-worth, as a human being, so tied-up in your ability to seem like the almightly techno-geek expert to the lowly non-technical people that that's why you're arguing all this nonsense here? Please tell me that that's not it!
I prescribed steps that would keep non-technical end-users from having to come into places like this and complain that their OS updates/upgrades had failed, and that, as a consequence, their phones were worse. Had you and your likes not insensibly challenged those steps, just, it seems, for challenging's sake, I would never have posted another word, here (other than, of course, if someone asked me a question about them). And if they, who subsequently read this thread, would simply follow my steps, they will never have to come back here to it and, worse, make a posting asking for help which, in turn, results in them being told to engage in witchcraft by the likes of you.
End-users like you (and that's all you are, you know; you're just an end-user who dabbles in the bowels of things and thinks, therefore, he knows what he's talking about) are dangerous. And they can't stand -- seriously, it keeps them awake at night -- whenever someone who knows more than they do calls them on their foolishness... as you're so clearly illustrating. Such as you don't even know what you don't even know; and are loathe to defer to those, like me, who have forgotten more than you'll ever know. Such as you, then, are actually dangerous... perhaps to yourselves, but certainly to non-technical, everyday, end-users who just want their stuff to work, and who don't want to have to get mired down in the techno-geekiness of any of it.
Yeah... right. I'll tell ya' what, Sparky: Come to work for me for a week on real IT and telephony problems. I'll pay you triple-time for every hour of regular time, and sextouple time for every hour of overtime. If you're as good as you say (and you, me and God know you're not, but, what the heck, I'll play), then you can keep it. But if you get stumped as quickly as I suspect you will, then you have to give me back all but normal regular-time and normal overtime pay...
Originally Posted by KSoD
...and, you know what, you'll also have to buy my wife flowers, and apologize to her for wasting her husband's precious time. I may even make you apologize to a priest for engaging in witchcraft. [grin] (just kidding on that last one)
Of course I have... what's wrong with you?! I may have been born at night, but I wasn't born last night! What, exactly do you think I've been doing with my nearly 40 years in IT? Hmm? (yet another rhetorical question; and telling about you, it is, indeed,l that I have to keep labeling them so you won't be confused) C'mon! Get serious.
Originally Posted by KSoD
See, this is how I know that you're just a neophyte. People project onto others their own infirmities, and, in this case, bad habits...
...as you just did with your "[y]ou have not even tried my process to know if it even works." Maybe that's a mistake you'd make, but it's not one that I'd ever make. Not on a bet!
<parenthetical_aside>Hmm. You know, Asian and Native American (and many other, actually) cultures may really be onto something, after all, with the whole "respect your elders" thing. But, alas, now I digress. Sorry.</parenthetical_aside>
You don't know me (thankgod, I'm now thinking). You don't know that I would never get into a forum like this -- even using a pseudonym (note that I use my own real name) -- and proffer something which I have not first both tested and proved. If I haven't, then I label it so, by surrounding it with phrases that make it clear that I'm speculating. There's even evidence of that very thing in other postings of mine in this very thread...
...er... oh... yeah... I forgot: You've not been reading those. Pity. You're the one who's looking dumb, here, because of it.
[sigh] Ayai yai... yet more uncareful reading. It's a spectacle, I tell you. [downward looks, shaking head]
Originally Posted by KSoD
Forgetting rooting, for a moment: Your steps are fine for any phone which, miraculously, has somehow operated for however long it has operated without its OS files (including, in some cases, merely settings/configuration text files) becoming somehow altered from poorly-written apps messing with them, or damaged from good, old-fashioned file corruption.
What you're not getting -- in fact, what you seem to be intentionally and intransigently refusing to get, seemingly just for its sake -- is this:
If I could somehow know that those things didn't happen to a given phone, then I would happily just perform the OS update/upgrade, using KIES, without first GSM resetting, like you prescribe. But my time, at least, is more valuable than that. I don't have the time to troubleshoot the OS update/upgrade after it fails, somehow. I'd rather just perform the steps, from the outset, which will ensure that the OS update/upgrade succeeds, regardless what the phone's been through; and even if some of those steps turn-out to not actually be necessary for a given phone.
What part of that rock-solidly-sound procedure, which any seasoned IT person would recognize as the only way to do it, can you not understand? (yet another rhetorical question)
Please get down off your high horse, and curb your anger at me which is clearly blinding you. Please. What it's doing to how you look, here, is now becoming hard to watch... even for your opponent (I, you see, do not engage in schadenfreude).
Wh... wha... wait... what? Do my eyes deceive me? Did I just read you extoling the virtues of intentionally violating the phone's and AT&T's provision of service's "Terms of Service" (TOS) agreement, to which you agreed and, by said agreement, are legally bound; then restoring the phone to factory state just to fool AT&T about it? And, worse, your actually being proud of that?
Originally Posted by KSoD
Did I just read that, here? You you freakin' kiddin' me?
So, then, that's really what we're dealing with, here, isn't it: A hacker mentality, and bygod proud of it. Do I have that about right? (yet another rhetorical questions, since we all know the answer)
Of course, I've known that about you from the outset of our little exchange, here, hence the palpable disdain that you've sensed; however, I was just trying not to so directly call you on it. But, man-oh-man, have you ever you ever stepped in it, now! Yikes! (Okay, okay... maybe that was at least a little schadenfreudic. Ya' got me on that one.) [grin]
Two old friends of mine who used to be local county deputy prosecutors (one of whom is now a state assistant attorney general, and the other a deputy federal prosecutor), used to always say that if criminals weren't both so stupid and arrogant, law enforcement would not catch anywhere near as many as they do. Thanks for so cogently illustrating their point, here...
...not that I'm saying you're a criminal (though, as my next paragraph explains, maybe you are); but what I am saying is that those who break the rules often tend to stupidly get all proud of themselves about it, especially if they're hangin' with the wrong crowd the questionable values system of which reinforces it. And so they end-up not being able to keep shut their mouths, and they start to brag; or, worse, their sense of right and wrong becomes so skewed that they can no longer realize that they're proffering illegality, and so think nothing of it that they so do right out in the open, for all to see. If criminals couldn't be counted on to stupidly be that way, and do that kinda' stuff, is my friends' point, then law enforcement would catch only a fraction of those whom they actually catch. And so, your so deftly illustration that is that for which I was thanking you. Thank you!
Rooting a phone probably isn't a crime... though because it bears an FCC ID number, it may actually be; but it's most likely a mere civil matter between the user and AT&T, pursuant to the TOS. However, using a rooted phone, very strictly technically speaking, actualy is a crime... a federal one, as it turns out, because the airwaves are regulated by the Federal Communications Commission (FCC), and not just any device out there is allowed to use them. Change how the device works, and cause it to deviate from its FCC approvals, and, technically, the device is illegal to use on FCC-regulated airwaves. Of course, few, to my knowledge, have ever actually ever been prosecuted for such a thing (nor, I'm guessing, is it likely that one ever would, except in a situation where law enforcement needed a predicate offense to use to then get warrants for more serious things), but I'm just sayin'.
What it all says about you, though, my arrogant young friend, is no small thing. Integrity means doing the right thing even when no one's watching. You, sir, are clearly integrity-challenged. That, along with your inability to carefully read, and your being so blinded by your anger that you can't concede anything -- and your dabbling in witchcraft... let's not forget that -- tells both me and the reader, here, pretty much everything we all need to know about you. Sadly. Your transparency, too, has been hard for even your opponent to watch.
Credibility is important... in fact, it's kinda' almost all there is, in life. You've now lost yours... at least here. The reason you use a pseudonym, here, is now more understandable. I really, then, in any case, shouldn't even finish replying to your words, here; but, alas, the anally-retentive in me just can't leave it unfinished. So...
See... now this is just your anger talking: Your finally breaking down to a rambling rant, because you're just so pissed off. Again, some advice in your future debates: Stay calm, read carefully, make sure that you're actually responding to what was actually written (and/or what even the most rudimentary reading between its lines clearly evidences), and make sure you're bygod right. You seem to be employing none of those skills, here... to your peril.
Originally Posted by KSoD
Er.. oh... wait... I'm sorry... um.... was I... I mean... was I supposed to have gotten your permission to do that? Oops. My bad.
Originally Posted by KSoD
Actually, yes I do. How do you think this game is played? You can't post that which told me everything I needed to know about your "knowledge, expertise or level of talking to any user," and then deprive me of actually benefitting from it. You proffered witchcraft, for godsake. Res ipsa loquitur.
Originally Posted by KSoD
And you insisted that your six steps work for everyone; that they're all that anyone could ever possibly need! That, even without my explaining why it's inaccurate, is just a prima facie ridiculous thing to write.
No... I'm sorry: I think you provided us all with pretty much everything we needed to know to be wary of you. And, again, you project onto others your inability to infer and intuit. Maybe with some years under your belt, you'll develop the skill.
Oh, yeah... and you've now also shown yourself to be dishonest, and integrity-challenged, to boot.
No surprise, there, I posit.
Yeah... right. You see, Sparky, one thing that getting old -- and not being asleep at the switch at any point along the way -- helps one to do in life is recognize crap comin' down the pike before it's even fully presented. Don't worry, you'll develop the skill, too, in time. Of course, if you don't actually develop better skills, become more introspective and self-examining, and develop a little integrity, just as a person, then you'll likely never recognize any of it as crap because you won't actually see it as crap... since, after all, that's pretty much all you offer. Integrity-challenged people are kinda' relegated to that in life, I've noticed. Pity.
Originally Posted by KSoD
It only took, then, one post... at least for me. I'm old and wise, remember. Been there. Done that. And all that kinda' stuff. I've been challenged, for pushing four decades -- longer, usually, than my challengers have even been alive -- both in forums like this where the bravdo of your likes is enhanced by pseudonymous anonymity, and in real life where the end-user knows just enough to get himself/herself in trouble, as you've herein done, and is too stupid to realize it (as I fear you've herein demonstrated that you are; but I'll leave that to the reader), and so thinks s/he can step-up and make a case.
Of course, in your case, the whole "settling" and "stabilizing" thing was a huge tip-off. Thanks for that help.
Then there's all else that you've herein written since your one post on which you so chastise me for judging, which pretty much proves-out all of said judgement. I, too, love being right. I just don't make it the entire point. Take a lesson.
Thanks, though, for all that help, too. Regarding it, though, a bit more advice, if you'll permit me (and, what the heck, even if you won't): Become familiar, in life, with the concept of falling on one's own sword. It will, with any luck, help you to avoid so thoroughly doing it again, as you've so thoroughly done it, here. The lessons just aboud, don't they?
Wise-up, young man. I've eaten your likes for breakfast since, I dare say, you were but a twinkle in your parents' eyes; and I had finally actually gotten good at it while you were still in diapers. And even if that's not technically accurate (because you're actually older than that), your behavior, here, nevertheless makes still relevant the salient point.
Hope that helps...
...though I'm obviously under no illusion that you'll actually think so. Nor, really, do I care.