The US didn't start using this blacklist until a few months ago.
I'm not sure why TFA says "Wednesday" - over on XDA, people with corrupt IMEIs started complaining 2-3 months ago.
(On Samsung devices, if the EFS partition gets corrupted, it'll be regenerated with a "test IMEI", which all European carriers block but US carriers allowed until recently. The test IMEI is blacklisted. Some shady characters were intentionally corrupting TO the test IMEI to prevent AT&T from detecting their device as a smartphone and all started whining when their hack caused their device to be 100% blocked as stolen.)
Yup. I think manufacturers fail to see that in today's day and age, "Average Joe User" doesn't trust the marketing bullshit - he goes to his techie friend.
If the techie friend doesn't like HTC because of HTC's bootloader locking policies, Average Joe won't buy HTC.
In some ways, when making a recommendation, knowing a device has that "way out" if the manufacturer abandons/screws up a device is critical to me feeling comfortable recommending a phone. I will never recommend a phone with a locked bootloader that is not fully unlockable to any family member or friend, even if they never do put custom firmware on it, I know that at least there will be an escape route for them if the manufacturer fucks up in the future.
Most locked down???? Um, Sony has a far better bootloader unlocking program than HTC (none of that "unlocked but S-ON" bullshit you get from HTC), they are one of the largest contributors to AOSP, they have the ONLY non-Nexus phone in AOSP with the Xperia S, they open-sourced their sensor HAL with DASH, and actively cooperate with the CyanogenMod team to facilitate CM bringups on their devices. (As in, Alin Jerpelea has received quite a decent number of phones for free from them, and they provide answers to technical questions from him.)
The disadvantage, of course, is they don't have the clout to force through unlockable bootloaders against the carrier's wishes like Samsung does. Samsung is about the only manufacturer that has been able to get away with an unlocked/unlockable bootloader on a SIM-locked phone. (Carriers see a locked bootloader as an extra layer of defense. I think this is stupid since they have a FUCKING SIGNED CONTRACT enforcing the contract subsidy terms regardless of technical measures... But carriers suck big fat donkey balls.)
Yeah... To my knowledge, there aren't any solar powered aircraft out there that have gone beyond the "research project" phase. I don't think there is a solar-powered aircraft in existence that can carry a human... Right now, the state of the art in solar powered aircraft is "keeps itself in the air with negligible cargo" - the payload limit being, at most, a comms relay and maybe some data collection stuff (airborne camera, etc.). Even that has worked, at best, in a place like Arizona or Hawaii on a good day.
It looks like since I last looked at solar-powered craft, someone has actually achieved a manned solar-powered aircraft. That aircraft took two months to go 6,000 km. The last solar-powered craft to make the headlines was the Helios, which did so by getting torn apart in winds/turbulence that would have, at most, turned on the "fasten seat belts" sign in any passenger airliner.
Battery-powered electric aircraft (which are charged before flight) are still just barely practical for a short-range civil aviation aircraft, and to my knowledge not a single one has become certified by any aviation approval authority as anything beyond an "experimental" aircraft - which are a LONG way away from being permitted for commercial passenger operation.
Yeah... I have been avoiding the RPi due to Broadcom's long history of treating the open source community like shit... This is something I NEVER expected to see coming from them.
It would be interesting to hear the non-dubbed version... Originally it might have been decent acting. However, the original dialog was overdubbed with new dialog. What you hear are NOT the actors' words!
That's the big difference... Nothing about "Innocence of Muslims" encouraged anyone to go murdering Muslims...
Do you see thousands of Jews protesting Sacha Baron Cohen's works or those of Mel Brooks because they can be considered insulting to Judaism? No. A few complain, but no massive outpourings of rage and no one was murdered.
Do you see people rioiting and murdering people because of Piss Christ or South Park Jesus? Nope.
It's an unofficial winzip kang... Winzip kangs NEVER manage to make it to the finish line, it's simply impossible.
You know, it's the perfect opportunity for a new maintainer to create a device try and to try and patch support into the kernel... But if no one has even bothered to do that it's not good.
Bringing up CM10 on the device won't be difficult - Getting N7100 working as well as I9300 wouldn't be difficult at all. It's just that none of the current maintainers with Exynos experience have any desire to do it again. We don't want to support Samsung by making their devices more attractive to a given market when they just jerk us around on a constant basis.
However, prospects for CM11 and further are extremely poor unless someone completely new takes up the task of being a proper maintainer.
git is a great tool, however it is extremely poorly suited for handling binary files in the way this project is using.
The CyanogenMod project recently encountered issues with getting locked out of some repos temporarily because they were simply too big and driving too much traffic - in almost all cases, the culprits were device trees that contained prebuilt kernel binaries instead of using the inline kernel building process that has been strongly encouraged for quite some time.
As a result of the most recent lockout issues, placement of prebuilt kernel binaries in the device tree has gone from "strongly discouraged" to "banned".
The only place in which your statement is valid is the AR6k fiasco on the Tab 7 Plus and Tab 7.7 - These DO have a driver that is dual-license GPL and BSD from Atheros, Samsung chooses BSD. While it is insanely frustrating, I can't throw Samsung under the bus for GPL noncompliance with this one. However, I can for bcmdhd.
The complete lack of any signature checking of/system when flashing images with Odin makes rooting Samsungs child's play.
I have to give Samsung credit - while working with the Exynos platform is a nightmare for a Cyanogenmod device maintainer, their lenient bootloader locking policies are unsurpassed.
He works for Samsung USA. Samsung Korea is the one controlling nearly anything Exynos-related. The situation for Qualcomm and OMAP-based Samsungs is quite a bit better - While it seems he doesn't have the authority to use any source code outside of what is available from CAF, the fact is he has a high degree of familiarity with these devices and hence knows how to get the CAF stuff to work VERY well. (The USA guys have, historically, primarily worked with Qualcomm-based devices.)
The CM Exynos maintainers do have a contact within Samsung Korea, but nearly all of the time when our contact forwards requests to the relevant department, the answer is either "no" or it is a blatant lie. (See the above comment about the Note 10.1 GPL compliance issues - the OSRC guys actually had the balls to claim that the UEALGB build, which was preinstalled on every Note 10.1 sold in the USA for at least one month, was a "leak" and hence they didn't have to provide source that matched it.) Our contact DOES care and wants to make a difference, but their management and the other departments within Samsung Mobile are completely noncooperative.
Wrong. If you look at the history of CM bringups, kernel source is a small part of the equation.
I have no idea why this was able to make Slashdot. Really, since when is an Android manufacturer doing the utterly bare legal minimum of what they are required to do by the GPL newsworthy? Do we even know if they're even complying with the GPL with this release? (See below...)
As to CyanogenMod on Note 2 - It's not going to happen unless a new maintainer steps up to the plate. None of the current Exynos maintainers have any intention on purchasing any additional non-Nexus Exynos devices. We're tired of Samsung's constant GPL violations (Frequently, their source releases do NOT match that of shipped devices - for example none of the source releases for the Note 10.1 produce a viable BCM4334 driver for wi-fi.) and of their total lack of cooperation with the open source community.
Take a look at the omapzoom (TI) reference platform source. Take a look at CodeAurora (Qualcomm) reference platform source. Then take a look at the Insignal git repos, or one of Hardkernel's 2GB tarballs. Note that of the two latter examples (both for Exynos), neither has a respository with any git history. They also don't even remotely match anything that is in Samsung's shipped devices in addition to being vastly outdated. If you use the Hardkernel or Insignal hardwarecomposer source code on a device, and then completely delete hwcomposer, you will see ZERO DIFFERENCE in behavior!
Background: I am the CyanogenMod co-maintainer for the AT&T Galaxy S II (SGH-I777), International Galaxy Note (GT-N7000), and Note 10.1 (GT-N8013). The GT-N8013 is my last non-Nexus Exynos device as I'm tired of working with an undocumented platform with no source code and broken hacked-up binaries. On a regular basis, the quality of CM on Exynos devices lags months behind OMAP and Qualcomm devices due to this. I'd like to, for once, be able to actually maintain a device that's in good shape and start focusing on adding new features, instead of constantly fighting massive bugs due to the lack of documentation of Samsung's blobs. (Of which we have FAR more to deal with than OMAP or Qualcomm devices.)
Yup. It's next to impossible for anyone (even a person that knows they're there) to identify the antennas for Verizon's cell site on top of Cornell's Barton Hall.
Of course, the rather distracting Force12 HF antenna belonging to W2CXM helps a bit... But even without the Force12, the Verizon antennas (sector antennas painted to match the stone of the building) are nearly impossible to spot.
In any built-up area it's really easy to hide a cell site.
Problem with your argument is, the places where the carriers are bitching about insufficient spectrum (and the first places they roll out new bands) are densely populated cities.
He's probably talking about a TRIGA. Far less fuel/lighter fuel, but it's still gonna be a bitch to swim down and remove it. If you fall in, drowning is a bigger worry than radiation.
You got shafted... When I toured the Ward Lab at Cornell (during one of the last 2-3 years of its operation before it got shut down), we did get to stand at the top of the pool and look down.
And you're right - even in 1999, there was, at most, a badge-swipe lock on the door.
Slashdot Mirror
Radio power usage is probably 70-90% of a device's standby power usage.
So it'll be great for standby time/background data power costs, not so much when the screen is on.
The US didn't start using this blacklist until a few months ago.
I'm not sure why TFA says "Wednesday" - over on XDA, people with corrupt IMEIs started complaining 2-3 months ago.
(On Samsung devices, if the EFS partition gets corrupted, it'll be regenerated with a "test IMEI", which all European carriers block but US carriers allowed until recently. The test IMEI is blacklisted. Some shady characters were intentionally corrupting TO the test IMEI to prevent AT&T from detecting their device as a smartphone and all started whining when their hack caused their device to be 100% blocked as stolen.)
Yup. I think manufacturers fail to see that in today's day and age, "Average Joe User" doesn't trust the marketing bullshit - he goes to his techie friend.
If the techie friend doesn't like HTC because of HTC's bootloader locking policies, Average Joe won't buy HTC.
In some ways, when making a recommendation, knowing a device has that "way out" if the manufacturer abandons/screws up a device is critical to me feeling comfortable recommending a phone. I will never recommend a phone with a locked bootloader that is not fully unlockable to any family member or friend, even if they never do put custom firmware on it, I know that at least there will be an escape route for them if the manufacturer fucks up in the future.
Most locked down???? Um, Sony has a far better bootloader unlocking program than HTC (none of that "unlocked but S-ON" bullshit you get from HTC), they are one of the largest contributors to AOSP, they have the ONLY non-Nexus phone in AOSP with the Xperia S, they open-sourced their sensor HAL with DASH, and actively cooperate with the CyanogenMod team to facilitate CM bringups on their devices. (As in, Alin Jerpelea has received quite a decent number of phones for free from them, and they provide answers to technical questions from him.)
The disadvantage, of course, is they don't have the clout to force through unlockable bootloaders against the carrier's wishes like Samsung does. Samsung is about the only manufacturer that has been able to get away with an unlocked/unlockable bootloader on a SIM-locked phone. (Carriers see a locked bootloader as an extra layer of defense. I think this is stupid since they have a FUCKING SIGNED CONTRACT enforcing the contract subsidy terms regardless of technical measures... But carriers suck big fat donkey balls.)
Yeah... To my knowledge, there aren't any solar powered aircraft out there that have gone beyond the "research project" phase. I don't think there is a solar-powered aircraft in existence that can carry a human... Right now, the state of the art in solar powered aircraft is "keeps itself in the air with negligible cargo" - the payload limit being, at most, a comms relay and maybe some data collection stuff (airborne camera, etc.). Even that has worked, at best, in a place like Arizona or Hawaii on a good day.
It looks like since I last looked at solar-powered craft, someone has actually achieved a manned solar-powered aircraft. That aircraft took two months to go 6,000 km. The last solar-powered craft to make the headlines was the Helios, which did so by getting torn apart in winds/turbulence that would have, at most, turned on the "fasten seat belts" sign in any passenger airliner.
Battery-powered electric aircraft (which are charged before flight) are still just barely practical for a short-range civil aviation aircraft, and to my knowledge not a single one has become certified by any aviation approval authority as anything beyond an "experimental" aircraft - which are a LONG way away from being permitted for commercial passenger operation.
That's not really a multimedia SoC - it has no GPU.
It doesn't have a PVR subcomponent, so it manages to be fully open-source by not having a GPU... Which is the component that is usually closed-source.
This announcement is the first example of a GPU with open source support.
Yeah... I have been avoiding the RPi due to Broadcom's long history of treating the open source community like shit... This is something I NEVER expected to see coming from them.
I'll be ordering a Pi tonight.
Except they already digitize these channels - they just must preserve them "in the clear" without encrypting them.
There are many places in this country that the OTA signal is not reliable unless you have a massive antenna due to LOS issues.
It would be interesting to hear the non-dubbed version... Originally it might have been decent acting. However, the original dialog was overdubbed with new dialog. What you hear are NOT the actors' words!
That's the big difference... Nothing about "Innocence of Muslims" encouraged anyone to go murdering Muslims...
Do you see thousands of Jews protesting Sacha Baron Cohen's works or those of Mel Brooks because they can be considered insulting to Judaism? No. A few complain, but no massive outpourings of rage and no one was murdered.
Do you see people rioiting and murdering people because of Piss Christ or South Park Jesus? Nope.
One other thing is, to participate on discussions on a page, you must "like" it.
So some of those liberals that "like" him may have "liked" him for the purposes of trolling the page.
It's an unofficial winzip kang... Winzip kangs NEVER manage to make it to the finish line, it's simply impossible.
You know, it's the perfect opportunity for a new maintainer to create a device try and to try and patch support into the kernel... But if no one has even bothered to do that it's not good.
Bringing up CM10 on the device won't be difficult - Getting N7100 working as well as I9300 wouldn't be difficult at all. It's just that none of the current maintainers with Exynos experience have any desire to do it again. We don't want to support Samsung by making their devices more attractive to a given market when they just jerk us around on a constant basis.
However, prospects for CM11 and further are extremely poor unless someone completely new takes up the task of being a proper maintainer.
As to reverse engineering - we're sick and fucking tired of reverse engineering things to find single-line code differences when Samsung could have just given us a goddamned header file - https://github.com/CyanogenMod/android_device_samsung_galaxys2-common/blob/jellybean/overlay/include/hardware/gps.h#L273 - that one fucking field took most of a week to figure out.
git is a great tool, however it is extremely poorly suited for handling binary files in the way this project is using.
The CyanogenMod project recently encountered issues with getting locked out of some repos temporarily because they were simply too big and driving too much traffic - in almost all cases, the culprits were device trees that contained prebuilt kernel binaries instead of using the inline kernel building process that has been strongly encouraged for quite some time.
As a result of the most recent lockout issues, placement of prebuilt kernel binaries in the device tree has gone from "strongly discouraged" to "banned".
WRONG. The bcmdhd driver IS GPLv2.
See https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/blob/jellybean/drivers/net/wireless/bcmdhd/bcmsdh_linux.c as one example.
The only place in which your statement is valid is the AR6k fiasco on the Tab 7 Plus and Tab 7.7 - These DO have a driver that is dual-license GPL and BSD from Atheros, Samsung chooses BSD. While it is insanely frustrating, I can't throw Samsung under the bus for GPL noncompliance with this one. However, I can for bcmdhd.
The complete lack of any signature checking of /system when flashing images with Odin makes rooting Samsungs child's play.
I have to give Samsung credit - while working with the Exynos platform is a nightmare for a Cyanogenmod device maintainer, their lenient bootloader locking policies are unsurpassed.
He works for Samsung USA. Samsung Korea is the one controlling nearly anything Exynos-related. The situation for Qualcomm and OMAP-based Samsungs is quite a bit better - While it seems he doesn't have the authority to use any source code outside of what is available from CAF, the fact is he has a high degree of familiarity with these devices and hence knows how to get the CAF stuff to work VERY well. (The USA guys have, historically, primarily worked with Qualcomm-based devices.)
The CM Exynos maintainers do have a contact within Samsung Korea, but nearly all of the time when our contact forwards requests to the relevant department, the answer is either "no" or it is a blatant lie. (See the above comment about the Note 10.1 GPL compliance issues - the OSRC guys actually had the balls to claim that the UEALGB build, which was preinstalled on every Note 10.1 sold in the USA for at least one month, was a "leak" and hence they didn't have to provide source that matched it.) Our contact DOES care and wants to make a difference, but their management and the other departments within Samsung Mobile are completely noncooperative.
Wrong. If you look at the history of CM bringups, kernel source is a small part of the equation.
I have no idea why this was able to make Slashdot. Really, since when is an Android manufacturer doing the utterly bare legal minimum of what they are required to do by the GPL newsworthy? Do we even know if they're even complying with the GPL with this release? (See below...)
As to CyanogenMod on Note 2 - It's not going to happen unless a new maintainer steps up to the plate. None of the current Exynos maintainers have any intention on purchasing any additional non-Nexus Exynos devices. We're tired of Samsung's constant GPL violations (Frequently, their source releases do NOT match that of shipped devices - for example none of the source releases for the Note 10.1 produce a viable BCM4334 driver for wi-fi.) and of their total lack of cooperation with the open source community.
Take a look at the omapzoom (TI) reference platform source. Take a look at CodeAurora (Qualcomm) reference platform source. Then take a look at the Insignal git repos, or one of Hardkernel's 2GB tarballs. Note that of the two latter examples (both for Exynos), neither has a respository with any git history. They also don't even remotely match anything that is in Samsung's shipped devices in addition to being vastly outdated. If you use the Hardkernel or Insignal hardwarecomposer source code on a device, and then completely delete hwcomposer, you will see ZERO DIFFERENCE in behavior!
Background: I am the CyanogenMod co-maintainer for the AT&T Galaxy S II (SGH-I777), International Galaxy Note (GT-N7000), and Note 10.1 (GT-N8013). The GT-N8013 is my last non-Nexus Exynos device as I'm tired of working with an undocumented platform with no source code and broken hacked-up binaries. On a regular basis, the quality of CM on Exynos devices lags months behind OMAP and Qualcomm devices due to this. I'd like to, for once, be able to actually maintain a device that's in good shape and start focusing on adding new features, instead of constantly fighting massive bugs due to the lack of documentation of Samsung's blobs. (Of which we have FAR more to deal with than OMAP or Qualcomm devices.)
After my experience with a Huawei S7 - Regardless of spying paranoia, this is the only valid thing to do with a Huawei product.
Yup. It's next to impossible for anyone (even a person that knows they're there) to identify the antennas for Verizon's cell site on top of Cornell's Barton Hall.
Of course, the rather distracting Force12 HF antenna belonging to W2CXM helps a bit... But even without the Force12, the Verizon antennas (sector antennas painted to match the stone of the building) are nearly impossible to spot.
In any built-up area it's really easy to hide a cell site.
Problem with your argument is, the places where the carriers are bitching about insufficient spectrum (and the first places they roll out new bands) are densely populated cities.
How is it that Europe has no problems using their existing spectrum allocations, while the USA seems to be resorting to insane band fragmentation?
The European 2100 MHz band isn't THAT big...
He's probably talking about a TRIGA. Far less fuel/lighter fuel, but it's still gonna be a bitch to swim down and remove it. If you fall in, drowning is a bigger worry than radiation.
You got shafted... When I toured the Ward Lab at Cornell (during one of the last 2-3 years of its operation before it got shut down), we did get to stand at the top of the pool and look down.
And you're right - even in 1999, there was, at most, a badge-swipe lock on the door.
Based on the description, it sounds like that reactor had pressurized coolant.