There is a "battery service" defined in the standard. (At least for BLE, aka Bluetooth Smart, but I assume also for Bluetooth Proper, as well.)
While nobody is forced to implement it, or implement it correctly, It's there - and built into the software development kits for the Systems On a Chip. If your device uses a common coin cell and the default power handling, you can just turn it on in the build and have it in your application - and any Bluetooth (or BLE) central can use it.
The BLE one gives you its best guess of the percentage of battery life remaining as a number from 0 10 100.
Now some batteries (for instance, Lithium Thionyl Chloride) can't be measured accurately (or at all before the last 15% of their lifetime). So battery services for them tend to hand you bogus numbers, if there isn't a "gas guage" chip counting switching regulator cycles, and thus electrons, to make a halfway decent guess. But that approach gets less accurate as end-of-life approaches, when you really want it to get better as you approach the wall.
Use FreeBSD, no systemd and technically a truer Unix than linux anyways.
Why do you mention Free rather than Open? (Or Net, for that matter?)
Seriously: I was looking at porting a project from Ubuntu 14.04 LTS to OpenBSD rather than later Ubuntu releases for security (and licensing) - at least in part because 14* to 16* or later means going to systemd and trying to security audit it looks like a nightmare. The obvious candidate was Open, because of its security tightness and because it's just supporting one embedded app on one particular hardware platform, so not having the whole kitchen sink of drivers and apps isn't an issue.
Is FreeBSD just a better match for what you're doing? (Laptop?) Or is there something else I should be looking at when picking a distribution?
... the mainstream news media love to report on who tweeted what, and "who" is usually come celebrity cretin or venal politician.
I think it's a scream that they haven't YET caught on to one of the things Trump is doing with it.
His tweets aren't JUST about getting to his supporters unfiltered by the lamestream media. (Most of his supporters don't follow them. There are other ways for him to get the word out that doesn't have the same set of gatekeepers.)
Every time he wants to get something done without the newsies jumping on it or anyone organize real opposition to it, he posts some outrageous tweet about something else. "Here: Look at THIS shiny thing!" Then they all go off and flame him for a news cycle or two while he gets what he wants done.
With a long history, a very small number of infected machines, and no active exploitation, I'd guess it's something someone was playing with that he's abandoned long ago or which "escaped from the lab" but didn't get far.
One of the hazards of self-propagatng code is that it does so on its own. So if, while under development, it finds a net connection to a set of vulnerable machines, it's out and spreading. Like before the command-and-control is debugged and/or the payload is ready to do its dirty work. (Thus it may be much nastier than the author(s) inteded.)
If it's GOOD at spreading it quickly saturates the vulnerable population and comes to the attention of users and security experts. If it's BAD at spreading its escape might not be noticed by the author at all - or by anyone else for years, if at all.
400 machines and a decade before it's noticed seems about right.
There were some claims in the past made by many people, that Mac's don't get computer virus's.
Which is particularly funny since I was handed decompiled code to a Mac virus (actually a sneakernet worm) back in the original Mac days. (I don't recall if it was before there WERE IBM PCs, let alone clones, or if it was just before PC malware was known.)
For many years, practiclly the beginnng of their deployment, there were worms, viruses, etc. on both. But those for Mac tended to be (relatively) harmless pranks - an animated bug crawling up the screen, animated trains (with sound effects) running across the menu bar and around the room on the apple-talk networked boxen, "bomb" boxes that dodged the mouse when you tried to dismiss them - while those for PCs tended to be damaging to data.
Macs were easy. In order to simplify the user experience the OS looked for (and ran if found) new drivers whenever you inserted a plastic-case floppy. What could POSSIBLY go wrong with that? B-b
Most drugs just deteriorate into something useless but not necessarily dangerous, usually in a decaying exponentiial. A few drugs deteriorate into something toxic, or otherwise having different drug-like effects. Another few may react with their breakdown products to decay at a harder to predict non-linear rate.
IMHO it would be useful to identify, publicly, which are which - especially the ones that get toxic after a while. It would also be useful to have an estimate of how rapidly they degrade under various storage conditions.
That way people could avoid things that get dangerous with age, but use (at their own risk) longer-lived drugs, perhaps slightly raiding the dose, for long after the 95% effectiveness "expiration date".
Perfectly willing to ignore that the actual hacking that Democrats are concerned about was related to breaking into email accounts for Democrats, not elections computers...
Nobody on the R side is ignoring that. But what the Ds are trying to distract everybody from is that the alleged "Russian hacking" consists of exposing what the major Ds were actually saying to each other (about how they cheated Sanders out of a legitimate primary run, what contempt they had for the voters and how they lied to them, and so on).
If the Russians were really behind those leaks, and they did swing the election, it seems to me that the people involved deserve both a close encounter of the law-enforcement kind AND a Pulitzer Prize.
It is absurd to ignore how the GOP has been found by numerous courts to have deliberately targeted selected mechanisms of ID because the opposing voting base uses them,...
It's not absurd if:
- the opposing voting base uses them because they're easy to fake, AND
- the not-so-easy-to-fake alternatives are both easy to obtain (by any QUALIFIED voter) and free.... when the GOP is found by numerous courts to have engaged in... gerrymandering...
Gerrymadering is a two-team sport. If you don't believe the Ds also play a good game, take a look at California, just for starters.
Also: "... found by numerous courts..." cuts no ice when egregiously left-wing and activist judges are one of the grievances of both the Rs and the voters for them.
It's not completely clear to me from TLA whether this builds on BLE (Bluetooth Low Energy a.k.a. Bluetooth Smart), though the reference to the 4.0 level of the standard, the many instances of the word "Smart" in the article, that it's a mesh, and the nature of the protocols all suggest it's BLE.
If so, it will be interesting to see how they keep it from eating up the devices' batteries. BLE devices get a couple years out of a coin cell by spending about 99.5% of their time "asleep", drawing roughly three orders of magnitude less current (~5 uA rather than ~5 mA) than when awake and with the radio on. Typically only a clock using a watch crystal is running during that time.
(Yes, that 99.5% isn't rhetoric. An advertisement takes about 5 ms, so a configuration of one advert per sec comes out to a duty cycle of about 1/200.)
They get away with that because they have a distinction between centrals (which have line power or (like smartphones) big batteries with frequent recharging) and peripherals (little battery powered devices that must only sip electrons). Peripherals can transmit when they feel like it. But centrals have to spend a lot of time listening, and the receiver (which has a lot to do) is (counterintuitively) slightly more power hungry than the transmitter.
If you try to build a mesh network out of what were formerly peripherals, not only do they have to spend several times as much battery power forwarding other devices' messages than they do handing their own (if everybody is equally chatty), but if the scheduling isn't set up right (or while listening for new players) they may need to leave the receiver on for substantial periods listening to the crickets chirp. That would just KILL battery life.
So I await the opportunity to peruse this addition to the spec. with bated breath.
(But not held breath. Even without this, the BLE v4.1 standard was 2,841 pages of some of the crummiest prose I've had the misfortune to have to try to understand. And I may be the only person to successfully implement a T1/T2/T3 framer from just the Bell standards and a logic analyzer bitstream capture.)
Zigbee on the other hand performs well and has been growing by leaps and bounds.
And, as I hear it, BLE / "Bluetooth Low Energy" / "Bluetooth Smart" - a different networking protocol from original Bluetooth in the lower layers but sharing some of the upper layers, or at least the upper layer design approaches - was largely created (absorbed into the Bluetooth standard from its inventors, with their gleeful cooperation) in reaction to ZigBee's success.
I looked at your post again and I think maybe it WAS the same problem. (Mine was a Toshiba - satellite, I think - bought surplus from work that went to black-screen-on-login after it updated to Natty 11.4 and was still broken with Oneiric 11.10)
So here's my notes from the install.
== Sat May 19 ==
- Backed up critical part of home directory to white 4G thumb drive.
- Used "upgrade" button in update manager to go to new revision.
- It went to Natty. (11.04?)
- Broken:
- New workspace.
- Freezes once taskbar shows.
- Could get console login on pseudoterm ctl-alt-F1
- Console login prompted for another upgrade.
- Upgraded again (using command interface.) Went to onieric (11.10)
- Still frozen.
- Live CD can't see encrypted disk.
== Sun May 20. ==
- Much debugging:
- Initially thought it was mouse buttons. But:
- Mouse worked fine on login screen.
- Control-alt-delete, enter: Logs out. Screen flashes then
back to login.
- So it looks like a permission issue.
- Much looking around on net found stuff on it:
- Related to Nvidia driver:
- (compiz?) isn't changing permission somewhere like previous
workspace did so userspace stuff can't touch screen.
- User got past it by:
- Going to classic no-effects in login screen options.
- Uninstalling nvidia "recommended" driver in "additional drivers".
- Then fixed by installing (via Synaptic) and enabling
(in Jockey/additional drivers) xserver-xorg-video-nouveau
driver (which he reports as being faster than Nvidia's
proprietary driver.)
(Something about moving-aside/etc/X11/xorg.conf) == Mon May 21 21:47:14 PDT 2012 ==
- Continued debugging:
- Was able to get it working by selecting a 3D session.
- Tried disabling Nvidia's driver.
- This ended up with a system that didn't display X screen asking
for full-disk password.
- Got around that by rebooting, which got grub options to
try recovery mode and using that.
- Disabling driver apparently works by:
- putting nvidia in/etc/modprobe.d/blacklist-local.conf (only entry)
Each time a new build comes through the system boots into a black screen and that's the end of it.
There is/was a bug in some video drivers that caused the screen to come up black, though the system was otherwise working fine. (I ran into that several years ago installing Ubuntu on a Toshiba laptop. They had just gone to Unity and the chip in the laptop wasn't quite initialized correctly.) There was a workaround (with an argument to the bootloader?) for startup, to get an initial live screen, then another to make it work automatically and persistently.
Don't recall it. But I was able to find it on the net by googling with the laptop model and verbiage about the problem. (Since you're on tablets, if it's a similar problem it might be different in detail, so my experience wouldn't apply directly.)
If you've got some older tablets gathering dust, you might want to try installing a later-patch-release version of a recent release of some linux distro - and if they don't come up, google for the symptoms. You might end up breathing new life into them.
IMHO it's not that the developers are deliberately dropping support or killing older machines. It's just that, as they work on new stuff, sometimes they break older stuff and don't have enough thousands of different machines to discover it before release - so it goes out and gets fixed (if at all) only after somebody complains.
Laptops used to have full-sized keyboards and ouiji keys.
Now, in the quest for thinness, they have chicklet keys. (I thought we'd learned not to do that back in the early home computer days.) Not only do they work horribly, creating a typo storm, if your fingernails are not trimmed to the quick, but they have backlit keys that are mostly clear and painted/molded with a thin layer of plastic on the top. Use them a couple months and the opaque layer scrapes off, causing the common characters to have irregular white spots instead of illuminated letters.
Touchpads can be nice. But a giant, hypersensitive, touchpad on the palm rest, where you REST YOUR PALMS WHILE TYPING, causes the gui to go all wonky while you type. The cursor jumps back into the text you typed and your continued typing corrupts it. Windows get selected. Different tabs get selected. The slashdot "submit" button gets hit in mid-entry or mid-proofread! The selection goes out of the text entry box and twenty browser "keyboard accelerator" commands fire off before you realize what's happening.
(And why DO browsers have all these (apparently undocumented - or dig for it) lower-case-alphabetic "accelerator" actions, anyhow?)
Apparently they've standardized on this, across diverse manufacturers (or they're all using the same OEM/ODMs). I got a Toshiba (through work) a couple years back that had the problem. Then it went belly-up and the only linux-compatible replacement I could find at Fry's - a Lenovo - had THE SAME KEYBOARD and a different touchpad that was THE SAME SIZE, LOCATION, and HYPERSENSITIVITY.
We have a convection oven. I find frozen pizzas cook best with about 10 minutes of normal heat and 2 with the forced-convection fan on.
But you can't just switch modes. You have to clear it, then restart it in the other mode, which requires manually counting the temperature up from the default again, and remembering what temperature you're trying this time.
(interesting. You can enter them in the Comment: box using standard keyboard-entry hacks (such as "control-shift-u, hex representation, return" on linux). And if you preview they get mangled in the display but are still displayed correctly in the Comment: box.
I know stories are posted farther apart at night, but it's embarrassing to have stories three hours apart on a weekday afternoon. These editors suck.
Did you check the Firehose?
Maybe there wasn't anything else WORTHY of being posted.
When that happens I'd rather they DON'T post crummy junk articles just to make a quota.
And I bet, if they DID post such junk, we'd hear even more complaining about the quality of the editorial staff.
Once upon I time I was one of the sysops on an early conferencing system. You would not BELIEVE the amount of what we'd now call cyber-bullying that was directed at the sysops by people who wanted the site run THEIR way.
But what if... You don't use android or have anything related to Google on your phone?
Also: How is this displayed and the reply collected? Does it require the Chrome (or another) browser?
I haven't accepted the Chrome EULA on my Android phone (because it includes the Adobe Flash EULA, which in turn includes a lifetime non-compete, non-reverse-engineer provision).
HUH? This is a Conway alternative fact (aka Trumpian economics)
They're not compounding 1% per year daily. They're compounding one percent per three days every three days for 121 cycles.
One percent a year compounded annually for 121 years would also yield $3.33. But grocery stores don't have to wait that long.
If that's "Trumpian economics" it looks like Trump understands it somewhat better. Maybe that's how he turned a million or so he got from his dad into 3.5 billion - and then spent about the price of a pleasure yacht on starting up a successful run for the US presidency.
yes there has been previous similar therapies that had pervasive side effects like brain swelling that resulted in death
And (according to TFA) this one sometimes does that, too. But, in the (closely watched) experimental group, they were able to catch it and treat it in the patients where it occurred.
It turned out to be transient. So nobody died, and the effect went away once the cancer cells were cleared and the immune cells settled down to just guarding against recurrence.
It was a "cytokine storm", where the signalling fallout from the modified immune cells (raising the alarm that they had found a massive "infection" of their targets) provokes immune (and other) cells elsewhere into disease-fighting modes (which also release alarm signalling chemicals, potentially creating a runaway feedback loop) damaging other tissues or even starting a persistent auto-immune syndrome.
Previous developers of such therapies might want to look into them again. If they were having the same problem, and their modified cells only attacked things, like leukemia cells, that they can easily reach and quickly clear out (rather than something that would keep them attacking long-term or that's a vital part of the body), they, too, might have viable and marketable treatments.
Lesson Learned: Gold plated commodity things are still just commodity things.
The other lesson learned: "Fast nickels are better than slow dimes." This was an extreme case of "slow dimes" for cellphones.
Grocery stores know that one. You can run on razor thin profit margins if, on the average, you turn over your entire stock every three days or so. 121 (a year's worth) cycles of compound interest at one percent will more than triple the money invested in the stock. (Multiplies it by almost exactly three and a third.)
And the enviornmentalists and others have been pushing that since at least the 1960s. Much of the boomer generation (especially those who felt more personal responsibility) had few children or held off on starting families - many until they were no longer able.
Result: The current government cries of a "labor shortage" and the current iteration of the same left-wing segment of "leaders" uses it as an excuse to import large numbers of people - mainly from cultures where large families are desired and encouraged.
For the politicians: More votes, possibly swamping their political opposition. For the imported, the opportunity to have more children than they could support in their country of origin, and for them to have more resources to consume.
But for the environment it's back on the Malthusian treadmill - with more people burning more fuel and destroying more habitat.
These "pro-natalist" policies are how you know that, for all of their cries of global warming and ecological disaster, the politicians don't actually believe in it themselves, but are just using it as a tool to increase their own power and wealth.
... there's no agreed-upon way to pronounce the symbols for C++ stream insertion/extraction operators (e.g., the OP mentions that he just leaves those uniquely silent)
Most of those symbols had "hacker slang" pronounciations, back when C++ was new. They weren't universal, of course. (Different clutches of hackers would sometimes have variant vocabulary.)
Most of the symbols inherited pronounciations from C, of course. But insertion/extraction (in the clutch of hackers I hung with) inherited from the analogous single-angle-bracket versions in unix shells.
Some of the pronounciations I recall:
a = 3; (replacement) "a gets three" ~ "twiddle" ! "bang" (printer's term for exclamation point) | "pipe" (from unix shells) ^ "hat" or "carat". "to the" when used for exponentiation. << (left shift) "left-left" (Similarly "right-right" for >> as a shift operator) < "less than" <= "less (than) or equal" (Similarly for > and >=) a++ "a bumped" ++a "bumped a" (Similarly for -- as "unbump(ed)") a += b "a bumped by b" == "equals" && "and-and" || "or-or" !! "not-not" or "bang-bang" cout << "Hello, world!"; "'Hello, world!' gazinta cahwt" ("gazinta" = "goes into", from shells where "echo foo > a" might be pronounced "echo foo gazinta aay" Similarly "gazouta". Source apparently pre-computer electrical engineering slang for input and output ports in circuit analysis.)
Actually, only people who read poorly do that. People who read well decode printed words directly into mental concepts, rather than sounding them all out, only sounding out a word when it is unfamiliar in print.
That (essentially correct) observation led to the creation of the "Look-Say" method of teaching English and its replacement of "Phonics" in the public schools.
Look-Say attempted to skip the "learn new words by sounding them out" step and teach students immediately to use the faster words-as-a-chunk technique of good readers.
But that ended up crippling them, because it left them with no way to acquire new words. They knew the handfull they'd encountered in class as a set of pictograms but didn't have the "secret code" to parse somethig they hadn't seen before. Result: Mostly illiterate graduates whose reading was so painful to them that they did little, getting farther and farther behind.
Turns out that good readers of substantially phonetic languages start with sounding-out (Phonics-style). Then as they gain skill and experience they start recognizing progressively more words at-a-glance, falling back to sounding-out when they hit words for which they hadn't yet built a neural-net recognizer. Eventually the "speed-bump" words become so rare that they blaze along familiar vocabulary without appearing to sound-out at all. But new or rare words bring out the old toolset, rather than bringing them to a full stop.
There are a corresponding pair of methods for learning a "second (i.e. additional) language: The "Grammatical Method" (learn and practice the lnguage rules) and the "Audiolingual Method" (repeat the samples). The latter came from an attempt to emulate the rapid language acquisition of children by modeling their environent
Tested right after a series of courses, college students taught by either method score about the same. Tested a year or so later (if they haven't been re-exposed to the second language meanwhile) those taught by the Grammatical Method had a significant skill loss, while those taught by the Audiolingual Method were unable to emit any sentence they hadn't encountered in class. Oops!
Turns out that (unless you learn two or more languages as a child) the neural structures that make kids little language acquisition machines literally die off, in several stages (at the ends of age ranges called "critical periods") as the neurons that weren't used by the language learned are "pruned". Once this has happened, learning a new language isn't impossible. But it's more like recovering from a stroke.
What if... Those who are unwell were strictly forbidden to drink covfefe by their doctors ?
I hear that WAS the actual explanation behind the research results that led to the "one drink a day (or very moderate drinking) is better than alcohol abstinence" advice.
The coffee numbers look more like actual benefits, though. Which is not too surprising, given that coffee has a lot of chemicals in it that are known to be, or suspected of being, good for you in appropriate ways (such as antioxidants).
The fun part will be finding out which ones and by what mechanism they're helping out. It's a heck of a lot easier to do a big long-term study on a popular drink than to do a similarly high-quality study on each of the several thousand (known) biologically-active chemical compounds in the mix.
Slashdot Mirror
There is a "battery service" defined in the standard.
(At least for BLE, aka Bluetooth Smart, but I assume also for Bluetooth Proper, as well.)
While nobody is forced to implement it, or implement it correctly, It's there - and built into the software development kits for the Systems On a Chip. If your device uses a common coin cell and the default power handling, you can just turn it on in the build and have it in your application - and any Bluetooth (or BLE) central can use it.
The BLE one gives you its best guess of the percentage of battery life remaining as a number from 0 10 100.
Now some batteries (for instance, Lithium Thionyl Chloride) can't be measured accurately (or at all before the last 15% of their lifetime). So battery services for them tend to hand you bogus numbers, if there isn't a "gas guage" chip counting switching regulator cycles, and thus electrons, to make a halfway decent guess. But that approach gets less accurate as end-of-life approaches, when you really want it to get better as you approach the wall.
Use FreeBSD, no systemd and technically a truer Unix than linux anyways.
Why do you mention Free rather than Open? (Or Net, for that matter?)
Seriously: I was looking at porting a project from Ubuntu 14.04 LTS to OpenBSD rather than later Ubuntu releases for security (and licensing) - at least in part because 14* to 16* or later means going to systemd and trying to security audit it looks like a nightmare. The obvious candidate was Open, because of its security tightness and because it's just supporting one embedded app on one particular hardware platform, so not having the whole kitchen sink of drivers and apps isn't an issue.
Is FreeBSD just a better match for what you're doing? (Laptop?) Or is there something else I should be looking at when picking a distribution?
... the mainstream news media love to report on who tweeted what, and "who" is usually come celebrity cretin or venal politician.
I think it's a scream that they haven't YET caught on to one of the things Trump is doing with it.
His tweets aren't JUST about getting to his supporters unfiltered by the lamestream media. (Most of his supporters don't follow them. There are other ways for him to get the word out that doesn't have the same set of gatekeepers.)
Every time he wants to get something done without the newsies jumping on it or anyone organize real opposition to it, he posts some outrageous tweet about something else. "Here: Look at THIS shiny thing!" Then they all go off and flame him for a news cycle or two while he gets what he wants done.
With a long history, a very small number of infected machines, and no active exploitation, I'd guess it's something someone was playing with that he's abandoned long ago or which "escaped from the lab" but didn't get far.
One of the hazards of self-propagatng code is that it does so on its own. So if, while under development, it finds a net connection to a set of vulnerable machines, it's out and spreading. Like before the command-and-control is debugged and/or the payload is ready to do its dirty work. (Thus it may be much nastier than the author(s) inteded.)
If it's GOOD at spreading it quickly saturates the vulnerable population and comes to the attention of users and security experts. If it's BAD at spreading its escape might not be noticed by the author at all - or by anyone else for years, if at all.
400 machines and a decade before it's noticed seems about right.
There were some claims in the past made by many people, that Mac's don't get computer virus's.
Which is particularly funny since I was handed decompiled code to a Mac virus (actually a sneakernet worm) back in the original Mac days. (I don't recall if it was before there WERE IBM PCs, let alone clones, or if it was just before PC malware was known.)
For many years, practiclly the beginnng of their deployment, there were worms, viruses, etc. on both. But those for Mac tended to be (relatively) harmless pranks - an animated bug crawling up the screen, animated trains (with sound effects) running across the menu bar and around the room on the apple-talk networked boxen, "bomb" boxes that dodged the mouse when you tried to dismiss them - while those for PCs tended to be damaging to data.
Macs were easy. In order to simplify the user experience the OS looked for (and ran if found) new drivers whenever you inserted a plastic-case floppy. What could POSSIBLY go wrong with that? B-b
Most drugs just deteriorate into something useless but not necessarily dangerous, usually in a decaying exponentiial. A few drugs deteriorate into something toxic, or otherwise having different drug-like effects. Another few may react with their breakdown products to decay at a harder to predict non-linear rate.
IMHO it would be useful to identify, publicly, which are which - especially the ones that get toxic after a while. It would also be useful to have an estimate of how rapidly they degrade under various storage conditions.
That way people could avoid things that get dangerous with age, but use (at their own risk) longer-lived drugs, perhaps slightly raiding the dose, for long after the 95% effectiveness "expiration date".
Perfectly willing to ignore that the actual hacking that Democrats are concerned about was related to breaking into email accounts for Democrats, not elections computers ...
Nobody on the R side is ignoring that. But what the Ds are trying to distract everybody from is that the alleged "Russian hacking" consists of exposing what the major Ds were actually saying to each other (about how they cheated Sanders out of a legitimate primary run, what contempt they had for the voters and how they lied to them, and so on).
If the Russians were really behind those leaks, and they did swing the election, it seems to me that the people involved deserve both a close encounter of the law-enforcement kind AND a Pulitzer Prize.
It is absurd to ignore how the GOP has been found by numerous courts to have deliberately targeted selected mechanisms of ID because the opposing voting base uses them, ...
It's not absurd if: ... when the GOP is found by numerous courts to have engaged in ... gerrymandering ...
- the opposing voting base uses them because they're easy to fake, AND
- the not-so-easy-to-fake alternatives are both easy to obtain (by any QUALIFIED voter) and free.
Gerrymadering is a two-team sport. If you don't believe the Ds also play a good game, take a look at California, just for starters.
Also: "... found by numerous courts ..." cuts no ice when egregiously left-wing and activist judges are one of the grievances of both the Rs and the voters for them.
But thank you for playing straight-man. B-)
It's not completely clear to me from TLA whether this builds on BLE (Bluetooth Low Energy a.k.a. Bluetooth Smart), though the reference to the 4.0 level of the standard, the many instances of the word "Smart" in the article, that it's a mesh, and the nature of the protocols all suggest it's BLE.
If so, it will be interesting to see how they keep it from eating up the devices' batteries. BLE devices get a couple years out of a coin cell by spending about 99.5% of their time "asleep", drawing roughly three orders of magnitude less current (~5 uA rather than ~5 mA) than when awake and with the radio on. Typically only a clock using a watch crystal is running during that time.
(Yes, that 99.5% isn't rhetoric. An advertisement takes about 5 ms, so a configuration of one advert per sec comes out to a duty cycle of about 1/200.)
They get away with that because they have a distinction between centrals (which have line power or (like smartphones) big batteries with frequent recharging) and peripherals (little battery powered devices that must only sip electrons). Peripherals can transmit when they feel like it. But centrals have to spend a lot of time listening, and the receiver (which has a lot to do) is (counterintuitively) slightly more power hungry than the transmitter.
If you try to build a mesh network out of what were formerly peripherals, not only do they have to spend several times as much battery power forwarding other devices' messages than they do handing their own (if everybody is equally chatty), but if the scheduling isn't set up right (or while listening for new players) they may need to leave the receiver on for substantial periods listening to the crickets chirp. That would just KILL battery life.
So I await the opportunity to peruse this addition to the spec. with bated breath.
(But not held breath. Even without this, the BLE v4.1 standard was 2,841 pages of some of the crummiest prose I've had the misfortune to have to try to understand. And I may be the only person to successfully implement a T1/T2/T3 framer from just the Bell standards and a logic analyzer bitstream capture.)
Zigbee on the other hand performs well and has been growing by leaps and bounds.
And, as I hear it, BLE / "Bluetooth Low Energy" / "Bluetooth Smart" - a different networking protocol from original Bluetooth in the lower layers but sharing some of the upper layers, or at least the upper layer design approaches - was largely created (absorbed into the Bluetooth standard from its inventors, with their gleeful cooperation) in reaction to ZigBee's success.
I looked at your post again and I think maybe it WAS the same problem. (Mine was a Toshiba - satellite, I think - bought surplus from work that went to black-screen-on-login after it updated to Natty 11.4 and was still broken with Oneiric 11.10)
So here's my notes from the install.
==
Sat May 19
==
- Backed up critical part of home directory to white 4G thumb drive.
- Used "upgrade" button in update manager to go to new revision.
- It went to Natty. (11.04?)
- Broken:
- New workspace.
- Freezes once taskbar shows.
- Could get console login on pseudoterm ctl-alt-F1
- Console login prompted for another upgrade.
- Upgraded again (using command interface.) Went to onieric (11.10)
- Still frozen.
- Live CD can't see encrypted disk.
==
Sun May 20.
==
- Much debugging: /etc/X11/xorg.conf)
- Initially thought it was mouse buttons. But:
- Mouse worked fine on login screen.
- Control-alt-delete, enter: Logs out. Screen flashes then
back to login.
- So it looks like a permission issue.
- Much looking around on net found stuff on it:
- Related to Nvidia driver:
- (compiz?) isn't changing permission somewhere like previous
workspace did so userspace stuff can't touch screen.
- User got past it by:
- Going to classic no-effects in login screen options.
- Uninstalling nvidia "recommended" driver in "additional drivers".
- Then fixed by installing (via Synaptic) and enabling
(in Jockey/additional drivers) xserver-xorg-video-nouveau
driver (which he reports as being faster than Nvidia's
proprietary driver.)
(Something about moving-aside
==
Mon May 21 21:47:14 PDT 2012
==
- Continued debugging: /etc/modprobe.d/blacklist-local.conf (only entry)
- Was able to get it working by selecting a 3D session.
- Tried disabling Nvidia's driver.
- This ended up with a system that didn't display X screen asking
for full-disk password.
- Got around that by rebooting, which got grub options to
try recovery mode and using that.
- Disabling driver apparently works by:
- putting nvidia in
Each time a new build comes through the system boots into a black screen and that's the end of it.
There is/was a bug in some video drivers that caused the screen to come up black, though the system was otherwise working fine. (I ran into that several years ago installing Ubuntu on a Toshiba laptop. They had just gone to Unity and the chip in the laptop wasn't quite initialized correctly.) There was a workaround (with an argument to the bootloader?) for startup, to get an initial live screen, then another to make it work automatically and persistently.
Don't recall it. But I was able to find it on the net by googling with the laptop model and verbiage about the problem. (Since you're on tablets, if it's a similar problem it might be different in detail, so my experience wouldn't apply directly.)
If you've got some older tablets gathering dust, you might want to try installing a later-patch-release version of a recent release of some linux distro - and if they don't come up, google for the symptoms. You might end up breathing new life into them.
IMHO it's not that the developers are deliberately dropping support or killing older machines. It's just that, as they work on new stuff, sometimes they break older stuff and don't have enough thousands of different machines to discover it before release - so it goes out and gets fixed (if at all) only after somebody complains.
Laptops used to have full-sized keyboards and ouiji keys.
Now, in the quest for thinness, they have chicklet keys. (I thought we'd learned not to do that back in the early home computer days.) Not only do they work horribly, creating a typo storm, if your fingernails are not trimmed to the quick, but they have backlit keys that are mostly clear and painted/molded with a thin layer of plastic on the top. Use them a couple months and the opaque layer scrapes off, causing the common characters to have irregular white spots instead of illuminated letters.
Touchpads can be nice. But a giant, hypersensitive, touchpad on the palm rest, where you REST YOUR PALMS WHILE TYPING, causes the gui to go all wonky while you type. The cursor jumps back into the text you typed and your continued typing corrupts it. Windows get selected. Different tabs get selected. The slashdot "submit" button gets hit in mid-entry or mid-proofread! The selection goes out of the text entry box and twenty browser "keyboard accelerator" commands fire off before you realize what's happening.
(And why DO browsers have all these (apparently undocumented - or dig for it) lower-case-alphabetic "accelerator" actions, anyhow?)
Apparently they've standardized on this, across diverse manufacturers (or they're all using the same OEM/ODMs). I got a Toshiba (through work) a couple years back that had the problem. Then it went belly-up and the only linux-compatible replacement I could find at Fry's - a Lenovo - had THE SAME KEYBOARD and a different touchpad that was THE SAME SIZE, LOCATION, and HYPERSENSITIVITY.
We have a convection oven. I find frozen pizzas cook best with about 10 minutes of normal heat and 2 with the forced-convection fan on.
But you can't just switch modes. You have to clear it, then restart it in the other mode, which requires manually counting the temperature up from the default again, and remembering what temperature you're trying this time.
(interesting. You can enter them in the Comment: box using standard keyboard-entry hacks (such as "control-shift-u, hex representation, return" on linux). And if you preview they get mangled in the display but are still displayed correctly in the Comment: box.
Maybe he's sick.
My wife's sick. I'm sick. Our pets are sick. (Different things for the pets, but still...)
One reason gantt charts don't work as well as people think they should is that they never allocate time for plague.
I know stories are posted farther apart at night, but it's embarrassing to have stories three hours apart on a weekday afternoon. These editors suck.
Did you check the Firehose?
Maybe there wasn't anything else WORTHY of being posted.
When that happens I'd rather they DON'T post crummy junk articles just to make a quota.
And I bet, if they DID post such junk, we'd hear even more complaining about the quality of the editorial staff.
Once upon I time I was one of the sysops on an early conferencing system. You would not BELIEVE the amount of what we'd now call cyber-bullying that was directed at the sysops by people who wanted the site run THEIR way.
But what if ... You don't use android or have anything related to Google on your phone?
Also: How is this displayed and the reply collected? Does it require the Chrome (or another) browser?
I haven't accepted the Chrome EULA on my Android phone (because it includes the Adobe Flash EULA, which in turn includes a lifetime non-compete, non-reverse-engineer provision).
So does that mean I can't auth with Google?
HUH? This is a Conway alternative fact (aka Trumpian economics)
They're not compounding 1% per year daily. They're compounding one percent per three days every three days for 121 cycles.
One percent a year compounded annually for 121 years would also yield $3.33. But grocery stores don't have to wait that long.
If that's "Trumpian economics" it looks like Trump understands it somewhat better. Maybe that's how he turned a million or so he got from his dad into 3.5 billion - and then spent about the price of a pleasure yacht on starting up a successful run for the US presidency.
Maybe he was doing it for, you know, science, and not business?
Claiming he was doing "research on a book about hypocrisy in America" didn't keep Bernie Ward from being convicted of distributing child pornography.
yes there has been previous similar therapies that had pervasive side effects like brain swelling that resulted in death
And (according to TFA) this one sometimes does that, too. But, in the (closely watched) experimental group, they were able to catch it and treat it in the patients where it occurred.
It turned out to be transient. So nobody died, and the effect went away once the cancer cells were cleared and the immune cells settled down to just guarding against recurrence.
It was a "cytokine storm", where the signalling fallout from the modified immune cells (raising the alarm that they had found a massive "infection" of their targets) provokes immune (and other) cells elsewhere into disease-fighting modes (which also release alarm signalling chemicals, potentially creating a runaway feedback loop) damaging other tissues or even starting a persistent auto-immune syndrome.
Previous developers of such therapies might want to look into them again. If they were having the same problem, and their modified cells only attacked things, like leukemia cells, that they can easily reach and quickly clear out (rather than something that would keep them attacking long-term or that's a vital part of the body), they, too, might have viable and marketable treatments.
Lesson Learned: Gold plated commodity things are still just commodity things.
The other lesson learned: "Fast nickels are better than slow dimes." This was an extreme case of "slow dimes" for cellphones.
Grocery stores know that one. You can run on razor thin profit margins if, on the average, you turn over your entire stock every three days or so. 121 (a year's worth) cycles of compound interest at one percent will more than triple the money invested in the stock. (Multiplies it by almost exactly three and a third.)
There's another solution: Population control.
And the enviornmentalists and others have been pushing that since at least the 1960s. Much of the boomer generation (especially those who felt more personal responsibility) had few children or held off on starting families - many until they were no longer able.
Result: The current government cries of a "labor shortage" and the current iteration of the same left-wing segment of "leaders" uses it as an excuse to import large numbers of people - mainly from cultures where large families are desired and encouraged.
For the politicians: More votes, possibly swamping their political opposition. For the imported, the opportunity to have more children than they could support in their country of origin, and for them to have more resources to consume.
But for the environment it's back on the Malthusian treadmill - with more people burning more fuel and destroying more habitat.
These "pro-natalist" policies are how you know that, for all of their cries of global warming and ecological disaster, the politicians don't actually believe in it themselves, but are just using it as a tool to increase their own power and wealth.
... there's no agreed-upon way to pronounce the symbols for C++ stream insertion/extraction operators (e.g., the OP mentions that he just leaves those uniquely silent)
Most of those symbols had "hacker slang" pronounciations, back when C++ was new. They weren't universal, of course. (Different clutches of hackers would sometimes have variant vocabulary.)
Most of the symbols inherited pronounciations from C, of course. But insertion/extraction (in the clutch of hackers I hung with) inherited from the analogous single-angle-bracket versions in unix shells.
Some of the pronounciations I recall:
a = 3; (replacement) "a gets three"
~ "twiddle"
! "bang" (printer's term for exclamation point)
| "pipe" (from unix shells)
^ "hat" or "carat". "to the" when used for exponentiation.
<< (left shift) "left-left" (Similarly "right-right" for >> as a shift operator)
< "less than"
<= "less (than) or equal" (Similarly for > and >=)
a++ "a bumped"
++a "bumped a" (Similarly for -- as "unbump(ed)")
a += b "a bumped by b"
== "equals"
&& "and-and"
|| "or-or"
!! "not-not" or "bang-bang"
cout << "Hello, world!"; "'Hello, world!' gazinta cahwt" ("gazinta" = "goes into", from shells where "echo foo > a" might be pronounced "echo foo gazinta aay" Similarly "gazouta". Source apparently pre-computer electrical engineering slang for input and output ports in circuit analysis.)
Actually, only people who read poorly do that. People who read well decode printed words directly into mental concepts, rather than sounding them all out, only sounding out a word when it is unfamiliar in print.
That (essentially correct) observation led to the creation of the "Look-Say" method of teaching English and its replacement of "Phonics" in the public schools.
Look-Say attempted to skip the "learn new words by sounding them out" step and teach students immediately to use the faster words-as-a-chunk technique of good readers.
But that ended up crippling them, because it left them with no way to acquire new words. They knew the handfull they'd encountered in class as a set of pictograms but didn't have the "secret code" to parse somethig they hadn't seen before. Result: Mostly illiterate graduates whose reading was so painful to them that they did little, getting farther and farther behind.
Turns out that good readers of substantially phonetic languages start with sounding-out (Phonics-style). Then as they gain skill and experience they start recognizing progressively more words at-a-glance, falling back to sounding-out when they hit words for which they hadn't yet built a neural-net recognizer. Eventually the "speed-bump" words become so rare that they blaze along familiar vocabulary without appearing to sound-out at all. But new or rare words bring out the old toolset, rather than bringing them to a full stop.
There are a corresponding pair of methods for learning a "second (i.e. additional) language: The "Grammatical Method" (learn and practice the lnguage rules) and the "Audiolingual Method" (repeat the samples). The latter came from an attempt to emulate the rapid language acquisition of children by modeling their environent
Tested right after a series of courses, college students taught by either method score about the same. Tested a year or so later (if they haven't been re-exposed to the second language meanwhile) those taught by the Grammatical Method had a significant skill loss, while those taught by the Audiolingual Method were unable to emit any sentence they hadn't encountered in class. Oops!
Turns out that (unless you learn two or more languages as a child) the neural structures that make kids little language acquisition machines literally die off, in several stages (at the ends of age ranges called "critical periods") as the neurons that weren't used by the language learned are "pruned". Once this has happened, learning a new language isn't impossible. But it's more like recovering from a stroke.
What if... Those who are unwell were strictly forbidden to drink covfefe by their doctors ?
I hear that WAS the actual explanation behind the research results that led to the "one drink a day (or very moderate drinking) is better than alcohol abstinence" advice.
The coffee numbers look more like actual benefits, though. Which is not too surprising, given that coffee has a lot of chemicals in it that are known to be, or suspected of being, good for you in appropriate ways (such as antioxidants).
The fun part will be finding out which ones and by what mechanism they're helping out. It's a heck of a lot easier to do a big long-term study on a popular drink than to do a similarly high-quality study on each of the several thousand (known) biologically-active chemical compounds in the mix.