In a previous life I dealt with Verizon Wireless and AT&T small business services. We had some questions about issues we were having with their respective data networks. VZW was straight forward and very willing to work with us. The AT&T account rep was clueless, and I had to wander over to broadbandreports.com to escalate an issue. The issue was escalated to some sort of "executive" support that consisted of "Why the fuck do you want me to call you?" and I just kinda gave up at that point.
AT&T's residential service was worse for me. The place I'm at now originally had about eight lines on it, so there was a DAML... which meant no DSL or 56k dialup. Thankfully I had nice, expensive long-distance service because they slammed me when I signed up for voice service. Unfortunately, AT&T flat refused to offer DSL on the line to the ISP I wanted to use. So, yeah, I had to quite literally beg AT&T through broadbandreports (then dslreports.com) to provide service. Eventually they relented. Best they could do was G.DMT (no ADSL2, no U-Verse in this neck of the woods). Now that ISP is a proper CLEC and offers unthrottled ADSL2 w/ proper POTS service I'm AT&T free... I couldn't be happier. But AT&T, well, I've gotten countless calls and letters from them pleading with me to return.
Look, I've had problems with VZW, and they were bad (some were illegal actions on VZW's part). But I've never once been forced to resort back channels to get the problems fixed. Likewise I've friends that use Sprint (back in the days when they'd charge you to call customer service) and T-Mobile. Nobody even comes close to being as consistently bad as PacBell/SBC/AT&T. With AT&T to get any level of decent support I've got to go to broadbandreports and whine until a sympathetic tech has the time to respond. AT&T can fucking rot for all I care.
As for Virgin Mobile, I've been with them for about ten months now. So far so good. The coverage has definitely taken a dip since Sprint started carrying the iPhone. I've got an Optimus V and it's a great little phone and I've been working with a few people to firm up a port of CyanogenMod to it (wanna talk frustrating, try getting this stuff integrated into the Cyanogen tree). Better cell and GPS radios than my friends' Motorola Triumphs.
Mod parent the fuck up. People like sleek, "sexy" designs. This comes at a price. Swapping hard drives on a MacBook Air is going to be far more difficult than on a Mac Pro.
That said, ease of service comes and goes with Apple products. Ever try to get at the hard drive of an iBook? I gave up after about forty screws. Try it on a "classic" MacBook. Three captive screws and a pull tab. Easy as pie. I just replaced the top case on said MacBook when the keyboard died. I'm not happy that the keyboard/trackpad/case are all one piece (plastic welded together), but it was actually a pretty easy repair (and the iFixit guide got a number of key details wrong).
On the plus side I now have fifteen extra upper cases...
In reality, what's happened is that Google, recognising the need for larger apps and data, has increased the size of downloads from the Market as Expansion files. They did this so they could track when large in-game downloads were completing, because unscrupulous dvelopers were using large/slow downloads to make sure the user had no opportunity to finish the download before the refund period expired. Now the Market tracks that the user has completely finished downloading large applications, then starts the refund period. Most newer devices should download expansion files automatically, but older ones download them when you first run the application.
Say what? Depending on your device, you've gotta run the app to get the expansion packs in the first place because the market doesn't push the expansion files. OTOH if the market/were/ responsible for pushing and installing the expansion files, wouldn't that make it easier for Google to track and then determine when your grace period should start? Conversely, why on earth would Google include the download time in your grace period?
Seems a bit archaic to me, because instead of having a single place to deal with updates, you've now got two. Instead of one bit of code to maintain (market app on the phone) there are now two (market app and the developer's app) that need to handle essentially identical tasks. Scratch that, it seems a lot archaic and like there are far more permutations to deal with than in iOS land.
I'd say screen resolution is the/easiest/ thing to work around. With Android, you've got all sorts of problems with inconsistent behaviour between different versions. Prior to 2.3 (Gingerbread), you couldn't put assets in an APK larger than about a megabyte and the app installer won't clean up after data that you put in the officially sanctioned directory on the sd card. Trivial stuff when you're trying to bundle potentially large graphics files I guess. With Gingerbread, Google broke the Expandable ListWidget class. As far as screen resolutions go, there are predefined ways to handle the different sizes and densities. It's actually pretty flexible and one of the more intuitive things about Android development. Other than the list of acceptable values itself being something of a moving target, it's not/so/ bad.
As for the free development suite, you get what you pay for. I certainly much prefer XCode to Eclipse, to the extent that I use NetBeans to do development instead. Of course, the hot new SDK broke some minor things like incremental builds with NB. Previous versions of the Linux SDK shipped with broken versions of gcc that wouldn't compile the kernel properly (okay app devs don't worry about this, but it goes to show how chaotic the Android ecosystem is), and the supposedly supported MacOS X lacks support for various things like dexopt (OS dev) or Google TV support. Yeah, okay, I'm still chaffed that Google refuses to integrate SDK support for other free, open, non-Linux, UNIX-like operating systems and just writes sloppy code.
Linux as the required SDK platform is a bonus only if you're already using it.
I was about to ask if you were thinking of the TabHost bug where clearAllTabs() will randomly provoke a crash. But a quick DuckDuckGo search turned up a bunch of other mysterious bugs with the Android tab bits. My favorite was issue #12359 where the fix is a couple of lines, and it would be an easy fix were Google to not mark their classes as final (thus preventing you from subclassing them). Unfortunately the proper fix is to roll your own copies. The official Google response was to ignore the problem and tell everyone to stop using ActivityGroups (which are useful in tabs) and start using Fragments (introduced in Android 3.0).
Google applies their hands off approach to updates and support to both hardware (as evidenced by all the fairly new phones that don't ever get updates) and software. I'm pretty sure Google never fixed the broken widgets in Android 2.3, leaving developers to completely reinvent even rudimentary pieces of the Android framework.
QA in Android is a freaking mess, I'm not surprised that the Battleheart team gave up on it.
Except this wasn't a failing in Ruby (or Rails). As TFA pointed out, the vulnerability had already been discovered and fixed. The problem was that the voting software was using a custom version of the library in question... based on an older, insecure version no less. While TFA mentions checking the file extension should help remedy the problem, doing something as simple as URL encoding the filenames would work as well (and prevent escape characters from popping up in the filename).
Perhaps you can do that/now/. When it was rolled out, no you couldn't adjust or disable "What's Hot". As for the shifting privacy, funny thing. After I deleted my Google Plus account, I accidentally searched for github instead of going to github.com. Turns out all the/private/ comments I'd made with the/deleted/ account were still indexed by Google and now being shown in my search results. I tried recreating the account, but the comments remained inaccessible outside of my search results. Does that qualify as totally awesome?
Interesting. I deleted my Google Plus account because the information was less relevant to me. The tipping point was the "What's Hot" feature. Upon deployment I started seeing completely irrelevant posts in my news feed. Posts from people I didn't know, people I didn't care about, and people that didn't know anyone in my circles. Naturally, the "What's Hot" project lead was very proud of his work and posted about it to his Google Plus profile... and naturally I posted on some of his Google Plus posts to the effect that I'd love to be able to remove the irrelevant chaff. Turns out he blocked me, so I couldn't see or access any of his posts... but Google Plus decided it was worth my while to continue sending me notifications of other people commenting on this guy's posts. I'd never seen anything quite so unpleasant from Facebook.
Where are the coal versions of Fukushima and Chernobyle? Surely you can point to tens of examples easily as coal has been in use much longer and on a larger scale.
When you fry a computer module, you replace the module. They're expensive, but it's doable. Failure while updating the firmware is definitely not unheard of, and that's one of the big reasons that BMW specs very expensive battery chargers (Deutronic branded last I checked).
status.dreamhost.com = dreamhoststatus.com = down when they bork one of their core routers. After last year, I'd sure hope that they've put the status blog and corporate e-mail on a separate network. Pretty sure that they've been too busy posting pictures of cat anuses to have bothered changing anything tho. Phone support/is/ available, but you've got to plead for a call back via e-mail. That's all fine and dandy except for the fact that it's all on one network. A single point of failure is a single point of failure. You can't plead via e-mail for a callback when they can't read their e-mail. But, hey, tech support via twitter makes everything better, yeah?
I don't like DreamHost because they're unprofessional, I took my business elsewhere because they don't know wtf they're doing.
Well, someISPsare. Just depends on how they structure things legally. Should it be easier for ISPs to stand up and refuse to censor and snoop on their customers? IMO, yes. However, AFAIK, AT&T still retains common carrier status despite their well documented spying efforts, so...
Not doing any manner of scheduling for intrusive maintenance is not simply a tactic to scare away high maintenance customers, it's a tactic to scare away paying customers. You wanna know what's even less professional? Not having any phone support in the first place, and then not having any e-mail support or publicly available system status because everything's on the same network. A single point of failure isn't a tactic to "scare off the clueless, high-maintenance market" it's a hallmark of someone who doesn't know what they're doing.
The anger and misunderstanding probably comes from the way that DreamHost uses their system status blog to talk down to and make fun of their customers. DH is a mickey mouse operation if I've ever seen one. If they're owning up to the FTP/SSH database being compromised, there's probably more to it. I haven't used DreamHost in almost six years, and I didn't have a hard time talking clients into switching away after their last spate of self-inflicted downtime (and nonchalant manner in which they dealt with intrusive maintenance).
More to the point, storing hashes of passwords doesn't guarantee security... and there's no indication that they actually stored the passwords in a secure manner.
Failed to create "marketable products"? I was merely responding to your assertion that they created only compact cameras (which is patently false).
As far as marketable items, their DLSRs were plenty marketable (as were Fuji's) until the people making the bodies (Canon, Nikon) caught up. Hell, Kodak made digital backs for all sorts of cameras (including a variety of SLRs) for a while. So, sure, they don't make digital backs or DSLRs anymore but they sure sell the guts to the camera manufacturers. While they're not volume sellers like compact cameras, the Leica M9, Pentax 645D, and assorted Hasselblad backs are probably quite profitable for Kodak. The Hasselblad CFV-50 runs about $17,000. I suspect somewhere in there is a bit more profit for Kodak than they would have made off of a $200 camera. With a consumer camera they incur development and marketing costs for the whole system. Selling sensors to high end camera manufacturers cuts out the marketing cost, and a lot of the unnecessary faff. Sensors are expensive yet physically small.
Compact cameras are, of course, loss leaders for the more expensive cameras (be they superzoom/bridge, DSLR, rangefinder, or whatever). Dunno what Kodak is still making camera-wise, but this was relevant when they were making pro-grade digital cameras.
Indeed. Kodak cameras sucked so much that the Associated Press and Canon put their names on various models. Their sensors sucked so much that Leica uses them for their M9. Kodak failed in a lot of ways, but they definitely didn't fail to innovate or turn out quality products. Let's not forget that the first commercially-available DSLR was a Kodak camera. Let's also not forget that compact cameras are essentially loss leaders to get people hooked on a brand name.
Last time I used it? Long enough ago that disabling ads wasn't an option. Also, while CMStats is definitely opt-out (and I don't opt out of it), I've not seen anything to allow someone to opt-out of the tracking in ROM Manager. Oh, and bricking phones? That wasn't a result of using the wrong ROM (AFAIK). One way to ensure you can't get into recovery mode is to use ROM Manager to flash a bum recovery image. Lots of ways for things to go wrong.
Given the fuss over Carrier IQ, I'm not sure why a closed source app like ROM Manager should be given any leeway for tracking its users (by default).
Whatever. I've made a point of not including it in my CM builds because it's of little to zero use.
Really? My experience was that the unpaid version of ROM Manager had ads which blocked key UI bits, making it nearly impossible to download anything. ROMs were only available on certain days with the free version, oh, and it had a nasty habit of bricking phones. Sure, I'd much rather fix the code than whine... but ROM Manager is closed source.
Did I mention ROM Manager also phones home? Dunno how frequently, but it manages to spew backtraces into the logs when it fails to phone home. You're right, perhaps it's not bloatware... maybe it's just spyware? Either way, I made sure it's not installed on my phone.
Slashdot Mirror
*shrug*
In a previous life I dealt with Verizon Wireless and AT&T small business services. We had some questions about issues we were having with their respective data networks. VZW was straight forward and very willing to work with us. The AT&T account rep was clueless, and I had to wander over to broadbandreports.com to escalate an issue. The issue was escalated to some sort of "executive" support that consisted of "Why the fuck do you want me to call you?" and I just kinda gave up at that point.
AT&T's residential service was worse for me. The place I'm at now originally had about eight lines on it, so there was a DAML... which meant no DSL or 56k dialup. Thankfully I had nice, expensive long-distance service because they slammed me when I signed up for voice service. Unfortunately, AT&T flat refused to offer DSL on the line to the ISP I wanted to use. So, yeah, I had to quite literally beg AT&T through broadbandreports (then dslreports.com) to provide service. Eventually they relented. Best they could do was G.DMT (no ADSL2, no U-Verse in this neck of the woods). Now that ISP is a proper CLEC and offers unthrottled ADSL2 w/ proper POTS service I'm AT&T free... I couldn't be happier. But AT&T, well, I've gotten countless calls and letters from them pleading with me to return.
Look, I've had problems with VZW, and they were bad (some were illegal actions on VZW's part). But I've never once been forced to resort back channels to get the problems fixed. Likewise I've friends that use Sprint (back in the days when they'd charge you to call customer service) and T-Mobile. Nobody even comes close to being as consistently bad as PacBell/SBC/AT&T. With AT&T to get any level of decent support I've got to go to broadbandreports and whine until a sympathetic tech has the time to respond. AT&T can fucking rot for all I care.
As for Virgin Mobile, I've been with them for about ten months now. So far so good. The coverage has definitely taken a dip since Sprint started carrying the iPhone. I've got an Optimus V and it's a great little phone and I've been working with a few people to firm up a port of CyanogenMod to it (wanna talk frustrating, try getting this stuff integrated into the Cyanogen tree). Better cell and GPS radios than my friends' Motorola Triumphs.
Well there go my mod points. The Mustang II was based on the Pinto chassis. Search for exploding.
Mod parent the fuck up. People like sleek, "sexy" designs. This comes at a price. Swapping hard drives on a MacBook Air is going to be far more difficult than on a Mac Pro.
That said, ease of service comes and goes with Apple products. Ever try to get at the hard drive of an iBook? I gave up after about forty screws. Try it on a "classic" MacBook. Three captive screws and a pull tab. Easy as pie. I just replaced the top case on said MacBook when the keyboard died. I'm not happy that the keyboard/trackpad/case are all one piece (plastic welded together), but it was actually a pretty easy repair (and the iFixit guide got a number of key details wrong).
On the plus side I now have fifteen extra upper cases...
At this point, with the release of Android 4.0, legacy devices account for 60% of all Android devices in use.
In reality, what's happened is that Google, recognising the need for larger apps and data, has increased the size of downloads from the Market as Expansion files. They did this so they could track when large in-game downloads were completing, because unscrupulous dvelopers were using large/slow downloads to make sure the user had no opportunity to finish the download before the refund period expired. Now the Market tracks that the user has completely finished downloading large applications, then starts the refund period. Most newer devices should download expansion files automatically, but older ones download them when you first run the application.
Say what? Depending on your device, you've gotta run the app to get the expansion packs in the first place because the market doesn't push the expansion files. OTOH if the market /were/ responsible for pushing and installing the expansion files, wouldn't that make it easier for Google to track and then determine when your grace period should start? Conversely, why on earth would Google include the download time in your grace period?
Seems a bit archaic to me, because instead of having a single place to deal with updates, you've now got two. Instead of one bit of code to maintain (market app on the phone) there are now two (market app and the developer's app) that need to handle essentially identical tasks. Scratch that, it seems a lot archaic and like there are far more permutations to deal with than in iOS land.
Well, on the plus side, it's not like services worked very well on Android prior to 4.0. I was (and still am) amazed that there's no way to gracefully stop a background "service".
Bullshit.
I'd say screen resolution is the /easiest/ thing to work around. With Android, you've got all sorts of problems with inconsistent behaviour between different versions. Prior to 2.3 (Gingerbread), you couldn't put assets in an APK larger than about a megabyte and the app installer won't clean up after data that you put in the officially sanctioned directory on the sd card. Trivial stuff when you're trying to bundle potentially large graphics files I guess. With Gingerbread, Google broke the Expandable ListWidget class. As far as screen resolutions go, there are predefined ways to handle the different sizes and densities. It's actually pretty flexible and one of the more intuitive things about Android development. Other than the list of acceptable values itself being something of a moving target, it's not /so/ bad.
As for the free development suite, you get what you pay for. I certainly much prefer XCode to Eclipse, to the extent that I use NetBeans to do development instead. Of course, the hot new SDK broke some minor things like incremental builds with NB. Previous versions of the Linux SDK shipped with broken versions of gcc that wouldn't compile the kernel properly (okay app devs don't worry about this, but it goes to show how chaotic the Android ecosystem is), and the supposedly supported MacOS X lacks support for various things like dexopt (OS dev) or Google TV support. Yeah, okay, I'm still chaffed that Google refuses to integrate SDK support for other free, open, non-Linux, UNIX-like operating systems and just writes sloppy code.
Linux as the required SDK platform is a bonus only if you're already using it.
I was about to ask if you were thinking of the TabHost bug where clearAllTabs() will randomly provoke a crash. But a quick DuckDuckGo search turned up a bunch of other mysterious bugs with the Android tab bits. My favorite was issue #12359 where the fix is a couple of lines, and it would be an easy fix were Google to not mark their classes as final (thus preventing you from subclassing them). Unfortunately the proper fix is to roll your own copies. The official Google response was to ignore the problem and tell everyone to stop using ActivityGroups (which are useful in tabs) and start using Fragments (introduced in Android 3.0).
Google applies their hands off approach to updates and support to both hardware (as evidenced by all the fairly new phones that don't ever get updates) and software. I'm pretty sure Google never fixed the broken widgets in Android 2.3, leaving developers to completely reinvent even rudimentary pieces of the Android framework.
QA in Android is a freaking mess, I'm not surprised that the Battleheart team gave up on it.
You must not be familiar with the San Francisco Crime Lab. Or how the fallout impacted the people involved.
Except this wasn't a failing in Ruby (or Rails). As TFA pointed out, the vulnerability had already been discovered and fixed. The problem was that the voting software was using a custom version of the library in question... based on an older, insecure version no less. While TFA mentions checking the file extension should help remedy the problem, doing something as simple as URL encoding the filenames would work as well (and prevent escape characters from popping up in the filename).
Perhaps you can do that /now/. When it was rolled out, no you couldn't adjust or disable "What's Hot". As for the shifting privacy, funny thing. After I deleted my Google Plus account, I accidentally searched for github instead of going to github.com. Turns out all the /private/ comments I'd made with the /deleted/ account were still indexed by Google and now being shown in my search results. I tried recreating the account, but the comments remained inaccessible outside of my search results. Does that qualify as totally awesome?
It may never be the same as Facebook, but Google is sure as hell trying to turn it into a Facebook clone.
Interesting. I deleted my Google Plus account because the information was less relevant to me. The tipping point was the "What's Hot" feature. Upon deployment I started seeing completely irrelevant posts in my news feed. Posts from people I didn't know, people I didn't care about, and people that didn't know anyone in my circles. Naturally, the "What's Hot" project lead was very proud of his work and posted about it to his Google Plus profile... and naturally I posted on some of his Google Plus posts to the effect that I'd love to be able to remove the irrelevant chaff. Turns out he blocked me, so I couldn't see or access any of his posts... but Google Plus decided it was worth my while to continue sending me notifications of other people commenting on this guy's posts. I'd never seen anything quite so unpleasant from Facebook.
Oh well.
Where are the coal versions of Fukushima and Chernobyle? Surely you can point to tens of examples easily as coal has been in use much longer and on a larger scale.
You mean like Centralia, Brennender Berg (it's been burning for over three hundred years), or Kingston Steam Plant?
When you fry a computer module, you replace the module. They're expensive, but it's doable. Failure while updating the firmware is definitely not unheard of, and that's one of the big reasons that BMW specs very expensive battery chargers (Deutronic branded last I checked).
status.dreamhost.com = dreamhoststatus.com = down when they bork one of their core routers. After last year, I'd sure hope that they've put the status blog and corporate e-mail on a separate network. Pretty sure that they've been too busy posting pictures of cat anuses to have bothered changing anything tho. Phone support /is/ available, but you've got to plead for a call back via e-mail. That's all fine and dandy except for the fact that it's all on one network. A single point of failure is a single point of failure. You can't plead via e-mail for a callback when they can't read their e-mail. But, hey, tech support via twitter makes everything better, yeah?
I don't like DreamHost because they're unprofessional, I took my business elsewhere because they don't know wtf they're doing.
Well, some ISPs are. Just depends on how they structure things legally. Should it be easier for ISPs to stand up and refuse to censor and snoop on their customers? IMO, yes. However, AFAIK, AT&T still retains common carrier status despite their well documented spying efforts, so...
I'd be hard pressed to believe you've dealt with anyone other than DreamHost. When I failed to renew my service with them it was because their hosting was glacial. It could barely keep up with a lightly used PHP image gallery. That was years ago. When I migrated clients away from DH last year it was because of chronic downtime. "Oops we fucked up" is great, and it's honest. It's also not something you want to keep seeing. "Oops we fucked up, but your worthless blogs about your kittens' trousers are safe" is /not/ something you want to see, ever. We're suffering a DDoS... no... wait... we don't know how to fix our Cisco equipment... is not something you want to see ever. Certainly it's not something you want to keep seeing
Not doing any manner of scheduling for intrusive maintenance is not simply a tactic to scare away high maintenance customers, it's a tactic to scare away paying customers. You wanna know what's even less professional? Not having any phone support in the first place, and then not having any e-mail support or publicly available system status because everything's on the same network. A single point of failure isn't a tactic to "scare off the clueless, high-maintenance market" it's a hallmark of someone who doesn't know what they're doing.
The anger and misunderstanding probably comes from the way that DreamHost uses their system status blog to talk down to and make fun of their customers. DH is a mickey mouse operation if I've ever seen one. If they're owning up to the FTP/SSH database being compromised, there's probably more to it. I haven't used DreamHost in almost six years, and I didn't have a hard time talking clients into switching away after their last spate of self-inflicted downtime (and nonchalant manner in which they dealt with intrusive maintenance).
More to the point, storing hashes of passwords doesn't guarantee security... and there's no indication that they actually stored the passwords in a secure manner.
Failed to create "marketable products"? I was merely responding to your assertion that they created only compact cameras (which is patently false).
As far as marketable items, their DLSRs were plenty marketable (as were Fuji's) until the people making the bodies (Canon, Nikon) caught up. Hell, Kodak made digital backs for all sorts of cameras (including a variety of SLRs) for a while. So, sure, they don't make digital backs or DSLRs anymore but they sure sell the guts to the camera manufacturers. While they're not volume sellers like compact cameras, the Leica M9, Pentax 645D, and assorted Hasselblad backs are probably quite profitable for Kodak. The Hasselblad CFV-50 runs about $17,000. I suspect somewhere in there is a bit more profit for Kodak than they would have made off of a $200 camera. With a consumer camera they incur development and marketing costs for the whole system. Selling sensors to high end camera manufacturers cuts out the marketing cost, and a lot of the unnecessary faff. Sensors are expensive yet physically small.
Compact cameras are, of course, loss leaders for the more expensive cameras (be they superzoom/bridge, DSLR, rangefinder, or whatever). Dunno what Kodak is still making camera-wise, but this was relevant when they were making pro-grade digital cameras.
Indeed. Kodak cameras sucked so much that the Associated Press and Canon put their names on various models. Their sensors sucked so much that Leica uses them for their M9. Kodak failed in a lot of ways, but they definitely didn't fail to innovate or turn out quality products. Let's not forget that the first commercially-available DSLR was a Kodak camera. Let's also not forget that compact cameras are essentially loss leaders to get people hooked on a brand name.
If by never really made DSLRs you mean invented the DSLR, OKAY.
West Oakland isn't that small.
Last time I used it? Long enough ago that disabling ads wasn't an option. Also, while CMStats is definitely opt-out (and I don't opt out of it), I've not seen anything to allow someone to opt-out of the tracking in ROM Manager. Oh, and bricking phones? That wasn't a result of using the wrong ROM (AFAIK). One way to ensure you can't get into recovery mode is to use ROM Manager to flash a bum recovery image. Lots of ways for things to go wrong.
Given the fuss over Carrier IQ, I'm not sure why a closed source app like ROM Manager should be given any leeway for tracking its users (by default).
Whatever. I've made a point of not including it in my CM builds because it's of little to zero use.
Really? My experience was that the unpaid version of ROM Manager had ads which blocked key UI bits, making it nearly impossible to download anything. ROMs were only available on certain days with the free version, oh, and it had a nasty habit of bricking phones. Sure, I'd much rather fix the code than whine... but ROM Manager is closed source.
Did I mention ROM Manager also phones home? Dunno how frequently, but it manages to spew backtraces into the logs when it fails to phone home. You're right, perhaps it's not bloatware... maybe it's just spyware? Either way, I made sure it's not installed on my phone.