While Sprint has been the largest user of CarrierIQ, with the most invasive CIQ installations in devices, AT&T was starting to put it on their phones too. For example, the Samsung Infuse 4G Gingerbread leaks from September to November carried a CIQ installation that was quite invasive. All evidence of CIQ is gone from the latest UCKL2 leak.
Similarly, while the original UCKH7 build for the Galaxy S II did not have CIQ, all leaks from October and November had it start to appear - but it was removed before the official UCKK6 update that just started getting rolled out to users earlier this week.
Carrier IQ (the company) = smoking crater. Their largest user is dropping them like a hot potato, and their fastest growth market (AT&T devices) is also ditching them.
Canadians are still screwed - Rogers seems silent in terms of CIQ. They actually had the balls to claim they don't use it, even though it was clearly there in the UXKG3 firmware release for the Samsung Infuse in that country.
Maybe the fact that if they did have such software, people would have found it?
Seriously, it isn't like people just "discovered" CarrierIQ hiding a few weeks ago - the only thing new is that it made it to the right news outlets and the news went viral.
Developers on XDA have been aware of CIQ (and removing it when found in custom ROMs) for months. If Verizon had anything even remotely similar, people would have found it by now.
There were a lot of problems, but one of them was the fact that due to one unit leaking, it made access to nearby units far more difficult, resulting in more severe problems at those units.
Blame Verizon, not Samsung. Verizon is almost as bad as AT&T about holding back updates.
To see that the blame lies squarely with the carrier, look at the AT&T Captivate vs. the Samsung GT-I9000 (International Galaxy S) - These phones were so close that I9000 kernels could be successfully run on the Captivate without any modifications (not even recompiling the source with a different defconfig!) All you had to do was change one keylayout file for full functionality.
Yet despite this - the Captivate got Froyo after the I9000 got Gingerbread!
Even with good optics, the physical sensor is just too small to perform well.
8MP in a smartphone sensor is just way too much except in bright daylight.
It's why Canon DROPPED the pixel count of their flagship P&S cameras from 14 megapixels down to 10 when going from the G10 to G11 - (or was it G9 to G10?) - photographers complained about the poor noise performance and dynamic range of the 14MP sensor.
People need to figure out that plastic != cheap/flimsy.
Properly chosen plastics can be EXTREMELY durable (think ABS and Delrin) - and past Samsungs show it. They "feel" flimsy because they're light - but the plastic has enough flex not to dent OR crack, and the lightness means it has less momentum when it hits something.
But again - not everyone can choose plastics properly. For example, third-party battery covers for Samsung devices (such as those required for extended batteries) are often made of a clearly different formula than the original plastic, and as a result they'll crack in situations the original cover handles with ease.
Yup. If it weren't for the coverage and band support issue, I probably would've swapped to T-Mobile long ago.
The problem is that any non-subsidized phone you might buy doesn't support their 3G bands, and at least back in 2008, ANY phone you bought would not work AT ALL for at least 15 miles from my place of work/employment. It was so bad that putting a T-Mobile SIM into an unlocked AT&T phone would cause that phone to be blacklisted with AT&T's towers for about 15 minutes, even after putting an AT&T SIM back in.
As another replier has said, once you place one 600MW plant there, it becomes easier to put another one nearby.
Just make sure to have a decent amount of separation - Fukushima would not have been such a problem if it didn't have 4 reactors built as close to each other as possible, with 2 more in extremely close proximity.
Probably rule of thumb should be twice the distance between the furthest Fukushima units from each other - that way if one unit has a problem, it doesn't cause the problems managing nearby units that Fukushima had.
Then why is it that drilling on a massive scale didn't occur until after the Energy Policy Act of 2005 was passed, exempting drilling companies from the Safe Drinking Water Act?
CLEARLY something is different - otherwise the regulatory changes in 2005 would have been a no-op instead of causing a major boom in drilling activity.
Energy Policy Act of 2005 - specifically the Halliburton Loophole exemptions to the Safe Drinking Water Act.
Fracking for gas didn't "take off" until that loophole was passed - so clearly SOMETHING they are doing is different that the loophole enables them to do.
The problem is that the same exemption allows them to hide what they are doing.
Hyrdrofracking for gas is an extremely recent development - at least in the form currently used. It was not legally possible to use the current methods of hydrofracking until the Halliburton Loophole exemptions to the Clean Water Act were pased as part of the Energy Policy Act of 2005.
CM releases have their own issues due to the fact that many things have to be reverse engineered to do a device bringup.
I'm talking about lightly modded stock ROMs. For example, on the AT&T Galaxy S II, bloatware forced into/system by AT&T is clearly proven to cause problems.
For example, if you even look at the AP Mobile widget the wrong way, it'll start eating insane amounts of data - enough to eat up your 2GB allowance and then some all by itself. So a widget that AT&T *added* and you *cannot remove without root* is driving many customers into data overages.
AT&T's testing must be utterly shit-poor to not have caught this problem.
Samsung's software is quite good - Touchwiz is the least intrusive of the vendor skins.
Now the carrier bloat they don't have the balls to keep off of their devices, THAT is a different story. The AT&T Galaxy S II (SGH-I777) is the least mangled of the Samsungs, and even it has some major problems not present in its nearly-identical international older brother (GT-I9100).
And the fact that it takes people on XDA a matter of days to find and fix many of the issues in manufacturer releases.
Two words that the mobile industry doesn't seem to understand: Beta Test
Users would not be so angry about delayed upgrades if we were allowed to test betas. Also, if carriers ran beta tests properly, users would be less unhappy with carrier firmwares. (For example, the data-eating AP Mobile widget on AT&T-originated Samsung devices would either be fixed or gone.)
I can understand carrier certification delays for network interfaces to a small degree - but the truth is that nowadays on any properly designed phone, the radio baseband firmware and the applications processor firmware are well isolated from each other. You don't HAVE to go fucking around in the radio baseband every time you touch the applications processor - the usual end result of this is lots of regressions.
Wi-Fi - utter bullshit. The PC industry has no problem deploying driver updates without recertification of all devices targeted by the driver. Bluetooth - utter bullshit, same deal as with WiFi - the PC industry has no problem with this.
F104s? Seriously, you're bringing up news that is on the order of 30-50 years old, talking about an aircraft that has been out of service for 7 years in ALL countries?
They may be looking good compared to other portable game systems - but honestly, the portable game system market is facing tough competition from smartphones and higher-end MP3 players that run smartphone OSes (such as iPod Touch, and the Samsung Galaxy Player series)
They also have a positive void coefficient (think Chernobyl), which is why there are none in the USA.
The only reason they don't scare the shit out of me despite this is because, as I understand it, they change reactivity far more slowly than graphite-moderated water-cooled units such as at Chernobyl. Also, if the core does go Chernobyl, instead of igniting lots of superheated graphite, the core will just blow out the coolant channels and wind up mixing with the moderator - which is fortunately nonflammable and capable of cooling the core.
There's also the question of net energy efficiency, given how much energy is required to enrich heavy water.
Slashdot Mirror
While Sprint has been the largest user of CarrierIQ, with the most invasive CIQ installations in devices, AT&T was starting to put it on their phones too. For example, the Samsung Infuse 4G Gingerbread leaks from September to November carried a CIQ installation that was quite invasive. All evidence of CIQ is gone from the latest UCKL2 leak.
Similarly, while the original UCKH7 build for the Galaxy S II did not have CIQ, all leaks from October and November had it start to appear - but it was removed before the official UCKK6 update that just started getting rolled out to users earlier this week.
Carrier IQ (the company) = smoking crater. Their largest user is dropping them like a hot potato, and their fastest growth market (AT&T devices) is also ditching them.
Canadians are still screwed - Rogers seems silent in terms of CIQ. They actually had the balls to claim they don't use it, even though it was clearly there in the UXKG3 firmware release for the Samsung Infuse in that country.
Sprint (or at least their OEMs) are working on updates that remove it, such as the EL13 leak for the Epic 4G Touch.
Maybe the fact that if they did have such software, people would have found it?
Seriously, it isn't like people just "discovered" CarrierIQ hiding a few weeks ago - the only thing new is that it made it to the right news outlets and the news went viral.
Developers on XDA have been aware of CIQ (and removing it when found in custom ROMs) for months. If Verizon had anything even remotely similar, people would have found it by now.
Either that or the drone was considered low-value enough not to even merit having access to the P codes.
If it didn't have P code access, chances are likely there isn't much of real value for the Iranian reverse engineers.
There were a lot of problems, but one of them was the fact that due to one unit leaking, it made access to nearby units far more difficult, resulting in more severe problems at those units.
Blame Verizon, not Samsung. Verizon is almost as bad as AT&T about holding back updates.
To see that the blame lies squarely with the carrier, look at the AT&T Captivate vs. the Samsung GT-I9000 (International Galaxy S) - These phones were so close that I9000 kernels could be successfully run on the Captivate without any modifications (not even recompiling the source with a different defconfig!) All you had to do was change one keylayout file for full functionality.
Yet despite this - the Captivate got Froyo after the I9000 got Gingerbread!
Even with good optics, the physical sensor is just too small to perform well.
8MP in a smartphone sensor is just way too much except in bright daylight.
It's why Canon DROPPED the pixel count of their flagship P&S cameras from 14 megapixels down to 10 when going from the G10 to G11 - (or was it G9 to G10?) - photographers complained about the poor noise performance and dynamic range of the 14MP sensor.
People need to figure out that plastic != cheap/flimsy.
Properly chosen plastics can be EXTREMELY durable (think ABS and Delrin) - and past Samsungs show it. They "feel" flimsy because they're light - but the plastic has enough flex not to dent OR crack, and the lightness means it has less momentum when it hits something.
But again - not everyone can choose plastics properly. For example, third-party battery covers for Samsung devices (such as those required for extended batteries) are often made of a clearly different formula than the original plastic, and as a result they'll crack in situations the original cover handles with ease.
Yup. If it weren't for the coverage and band support issue, I probably would've swapped to T-Mobile long ago.
The problem is that any non-subsidized phone you might buy doesn't support their 3G bands, and at least back in 2008, ANY phone you bought would not work AT ALL for at least 15 miles from my place of work/employment. It was so bad that putting a T-Mobile SIM into an unlocked AT&T phone would cause that phone to be blacklisted with AT&T's towers for about 15 minutes, even after putting an AT&T SIM back in.
I don't know about the GNex, but sideloading hacks were confirmed to get Google Wallet working for the non-Sprint Nexus S.
Nope. Try Best Buy.
Note that it's called the Galaxy Player in the US, I think internationally it's called the Galaxy S Wifi or something.
It's RIAA/MPAA math.
As another replier has said, once you place one 600MW plant there, it becomes easier to put another one nearby.
Just make sure to have a decent amount of separation - Fukushima would not have been such a problem if it didn't have 4 reactors built as close to each other as possible, with 2 more in extremely close proximity.
Probably rule of thumb should be twice the distance between the furthest Fukushima units from each other - that way if one unit has a problem, it doesn't cause the problems managing nearby units that Fukushima had.
Then why is it that drilling on a massive scale didn't occur until after the Energy Policy Act of 2005 was passed, exempting drilling companies from the Safe Drinking Water Act?
CLEARLY something is different - otherwise the regulatory changes in 2005 would have been a no-op instead of causing a major boom in drilling activity.
Except that wells that have run clean for decades started showing signs of contamination within months of drilling commencing.
Dimock, PA had clean water for decades in their wells - not any more.
Evidence that this is different?
Energy Policy Act of 2005 - specifically the Halliburton Loophole exemptions to the Safe Drinking Water Act.
Fracking for gas didn't "take off" until that loophole was passed - so clearly SOMETHING they are doing is different that the loophole enables them to do.
The problem is that the same exemption allows them to hide what they are doing.
Hyrdrofracking for gas is an extremely recent development - at least in the form currently used. It was not legally possible to use the current methods of hydrofracking until the Halliburton Loophole exemptions to the Clean Water Act were pased as part of the Energy Policy Act of 2005.
CM releases have their own issues due to the fact that many things have to be reverse engineered to do a device bringup.
I'm talking about lightly modded stock ROMs. For example, on the AT&T Galaxy S II, bloatware forced into /system by AT&T is clearly proven to cause problems.
For example, if you even look at the AP Mobile widget the wrong way, it'll start eating insane amounts of data - enough to eat up your 2GB allowance and then some all by itself. So a widget that AT&T *added* and you *cannot remove without root* is driving many customers into data overages.
AT&T's testing must be utterly shit-poor to not have caught this problem.
Simple solution to that - design a phone properly so it can't be bricked by your betas.
For example, in the case of Samsung, don't include boot.bin or sbl.bin in your beta flash package - BOOM, no-risk beta.
Samsung's software is quite good - Touchwiz is the least intrusive of the vendor skins.
Now the carrier bloat they don't have the balls to keep off of their devices, THAT is a different story. The AT&T Galaxy S II (SGH-I777) is the least mangled of the Samsungs, and even it has some major problems not present in its nearly-identical international older brother (GT-I9100).
And the fact that it takes people on XDA a matter of days to find and fix many of the issues in manufacturer releases.
Two words that the mobile industry doesn't seem to understand:
Beta Test
Users would not be so angry about delayed upgrades if we were allowed to test betas. Also, if carriers ran beta tests properly, users would be less unhappy with carrier firmwares. (For example, the data-eating AP Mobile widget on AT&T-originated Samsung devices would either be fixed or gone.)
I can understand carrier certification delays for network interfaces to a small degree - but the truth is that nowadays on any properly designed phone, the radio baseband firmware and the applications processor firmware are well isolated from each other. You don't HAVE to go fucking around in the radio baseband every time you touch the applications processor - the usual end result of this is lots of regressions.
Wi-Fi - utter bullshit. The PC industry has no problem deploying driver updates without recertification of all devices targeted by the driver.
Bluetooth - utter bullshit, same deal as with WiFi - the PC industry has no problem with this.
F104s? Seriously, you're bringing up news that is on the order of 30-50 years old, talking about an aircraft that has been out of service for 7 years in ALL countries?
In some cases, cancer could suddenly "crop up" again - but usually, if it returns, it's because you THINK it was completely wiped out but it wasn't.
They may be looking good compared to other portable game systems - but honestly, the portable game system market is facing tough competition from smartphones and higher-end MP3 players that run smartphone OSes (such as iPod Touch, and the Samsung Galaxy Player series)
They also have a positive void coefficient (think Chernobyl), which is why there are none in the USA.
The only reason they don't scare the shit out of me despite this is because, as I understand it, they change reactivity far more slowly than graphite-moderated water-cooled units such as at Chernobyl. Also, if the core does go Chernobyl, instead of igniting lots of superheated graphite, the core will just blow out the coolant channels and wind up mixing with the moderator - which is fortunately nonflammable and capable of cooling the core.
There's also the question of net energy efficiency, given how much energy is required to enrich heavy water.