Page 11 of 113 FirstFirst ... 891011121314 ... LastLast
Results 251 to 275 of 2801
Like Tree829Likes
  1. #251  

    Default Re: DROID BIONIC Jelly Bean Update

    The only reason I put up with the BS from VZW is that I live in a kind of remote area and I have friends with all the other major carriers and not one of them has as good of reception and signal as VZW. Lots of times when out on the river or lake fishing or somewhere hunting they have no service at all and I will have better than half. Only one or two places I have been that I have no signal and usually only have to move a few feet and have it again. It is so much of an issue with other carriers that I will not leave VZW for that reason alone.
    perkdog65 likes this.
  2. #252  

    Default Re: DROID BIONIC Jelly Bean Update

    So wait, I don't understand why if our update is ready we are not getting it before the other phones. Our phone was the first one out, and should be the first to be updated. That's crappy customer service imo.
  3. #253  

    Default Re: DROID BIONIC Jelly Bean Update

    LMAO. We've always been the last of OMAP4 phones to get updated. And it looks like the build was rejected so a new one has been started. And I'm told something else went down over the weekend so I don't know what the current status is. Right now the Bionic build 98.72.17 is being tested but I have no idea if that build will survive. I guess Moto and VZW have different definitions of "completed".


    Samsung S4 Google Play Edition
  4. #254  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by viper8315 View Post
    I don't post here much, mostly read. I think I echo a lot of people in this area though. Just go away dude, I'm going to use the traditional response, go buy a phone with a fruit label on it, maybe that will make you happy.

    To everybody else, sorry guys, just have a low tolerance for the whiners in here.
    Holy crap, my phone said you made this post in 1981! DROID BIONIC Jelly Bean Update-uploadfromtaptalk1360595965165.jpg
  5. #255  

    Default Re: DROID BIONIC Jelly Bean Update

    The Bionic may be the red headed step child of Verizon, but I love it the way it is on ICS. Much of what I've heard about JB wouldn't be of much benefit to me. I'm sure it would be nice, but no skin off my back if it doesn't come.
  6. #256  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by Mooncatt View Post
    The Bionic may be the red headed step child of Verizon, but I love it the way it is on ICS. Much of what I've heard about JB wouldn't be of much benefit to me. I'm sure it would be nice, but no skin off my back if it doesn't come.
    I have the same opinion. JB would be sweet if and when we get it. It's still being tested so there's at least some hope that it'll come eventually. But if it doesn't, and they choose to focus their attention on newer phones, I'd consider that just fine. I still think we'll see JB. When? I have no idea at this point. Honestly, given that I'm seriously considering leaving the VZW nest at some point this year, I'm looking toward Moto's newer phone scheduled to come out in July. That X phone is going to be a beast, and will NOT be tied to one carrier. Bring it on I say.


    Samsung S4 Google Play Edition
  7. #257  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SirGeorgeKillian View Post
    Holy crap, my phone said you made this post in 1981!
    Lol, nice! My flux capacitor actually worked!
  8. #258  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SamuriHL View Post
    I have the same opinion. JB would be sweet if and when we get it. It's still being tested so there's at least some hope that it'll come eventually. But if it doesn't, and they choose to focus their attention on newer phones, I'd consider that just fine. I still think we'll see JB. When? I have no idea at this point. Honestly, given that I'm seriously considering leaving the VZW nest at some point this year, I'm looking toward Moto's newer phone scheduled to come out in July. That X phone is going to be a beast, and will NOT be tied to one carrier. Bring it on I say.
    Do you have any insider information about the Xphone that would excite us and give us hope?
  9. #259  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by zachthebomb13 View Post
    Do you have any insider information about the Xphone that would excite us and give us hope?
    Yes, but, I can't share it here. It's going to be a monster of a phone.


    Samsung S4 Google Play Edition
  10. Thread Author  Thread Author    #260  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SamuriHL View Post
    Yes, but, I can't share it here. It's going to be a monster of a phone.
    Monster of a phone?

    I hope it comes DROID RAZR M/RAZR i -sized. I don't need gigantor in my pocket.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
  11. #261  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by Ry View Post
    Monster of a phone?

    I hope it comes DROID RAZR M/RAZR i -sized. I don't need gigantor in my pocket.
    Don't worry....5" edge to edge. Maybe. I meant monster in terms of what it's going to bring to the table. Moogle isn't screwing around on this one. It's the first Moto phone where Google was involved in the design. If that doesn't excite you guys, not much will.


    Samsung S4 Google Play Edition
  12. Thread Author  Thread Author    #262  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SamuriHL View Post
    Don't worry....5" edge to edge. Maybe. I meant monster in terms of what it's going to bring to the table. Moogle isn't screwing around on this one. It's the first Moto phone where Google was involved in the design. If that doesn't excite you guys, not much will.
    Oh I'm excited. It'll probably be my next.

    But engineering-wise, Motorola had/has a homerun with the RAZR M/i design. I would hate to have them lose that by playing the size game everyone else is playing.

    I really hope that this "X" is a Google phone that still has the soul of Motorola.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
    davevdb likes this.
  13. #263  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by Ry View Post
    Oh I'm excited. It'll probably be my next.

    But engineering-wise, Motorola had/has a homerun with the RAZR M/i design. I would hate to have them lose that by playing the size game everyone else is playing.

    I really hope that this "X" is a Google phone that still has the soul of Motorola.
    We'll see. AFAIK the final design isn't finished yet. All I can tell you is to watch Google I/O. It'll be an exciting time.


    Samsung S4 Google Play Edition
  14. Thread Author  Thread Author    #264  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by zachthebomb13 View Post
    On another note, I think I remember reading somewhere that Motorola's new phones will be built a little different, where Motoblur will be skinned on top of stock Android, instead of baked into it. Is that true, will it work, and does that make it possible for upgrades to come quicker?
    This rumor will never die because fans of stock won't let it.

    Upgrades won't come any quicker IMO because the skin (vs. baked in) on top would still have to be certified to work. Example: if Sense was just a launcher, HTC would still have to verify that the Jelly Bean version would work with the supposed Key Lime Pie version. Updates still won't be immediate.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
  15. #265  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by Ry View Post
    This rumor will never die because fans of stock won't let it.

    Upgrades won't come any quicker IMO because the skin (vs. baked in) on top would still have to be certified to work. Example: if Sense was just a launcher, HTC would still have to verify that the Jelly Bean version would work with the supposed Key Lime Pie version. Updates still won't be immediate.
    Actually this is more than rumor. Google wanted it to work like this but the stupid carriers won't allow it. The idea is that the skins could be released via an update mechanism like the play store. The mfg would get the main OS done without their skin, and those that wanted it could update to a vanilla OS....with the benefit of getting it sooner. Those who want the skin could either hold off til it's done, or they could get it when it's ready. The carriers are what killed this idea. Morons.


    Samsung S4 Google Play Edition
  16. Thread Author  Thread Author    #266  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SamuriHL View Post
    Actually this is more than rumor. Google wanted it to work like this but the stupid carriers won't allow it. The idea is that the skins could be released via an update mechanism like the play store. The mfg would get the main OS done without their skin, and those that wanted it could update to a vanilla OS....with the benefit of getting it sooner. Those who want the skin could either hold off til it's done, or they could get it when it's ready. The carriers are what killed this idea. Morons.
    I'd like to think OEMs killed this as well. That instantly removes parts that make a Samsung phone a Samsung phone.

    If I was running HTC, Motorola, Samsung, or LG, I'd want my phones to look and feel different than my competitors. We'll have to agree to disagree on this one, but I have to think the OEMs want both their hardware and software to stand out regardless if carriers force them to or not.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
  17. #267  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by Ry View Post
    I'd like to think OEMs killed this as well. That instantly removes parts that make a Samsung phone a Samsung phone.

    If I was running HTC, Motorola, Samsung, or LG, I'd want my phones to look and feel different than my competitors.
    You fail to realize the bigger issue. Skins are great. Security problems aren't. When it takes you a year to get an update onto a phone (cough cough ICS Bionic anyone?) that's not a good situation. Security problems are becoming a bigger and bigger issue for Android. We need updates sooner. If we're waiting for an update because the company has to ensure compatibility with their skin, well, that's not good for anyone. I'd prefer they forego the skin, get us the update, and update the skin after that's done. One of the biggest reasons I'm going with an unlockable phone in the future is so I don't have to wait for the MFG's to do updates. I'm going for stock AOSP...security fixes will be a LOT faster that way.


    Samsung S4 Google Play Edition
  18. Thread Author  Thread Author    #268  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by snowwy66 View Post
    they'll never get it right.

    after all. the phone was 9 months late in being release. it's been discontinued for awhile now. and come july and august if that ends up being the actual release date.

    well, i'm eligible for upgrade in may. i have absolutely noooooo intentions of keeping the phone past that point.

    in fact.d it'll probably get thrown against the wall the minute i step in the door.
    IIRC, the phone was not 9 months late in being released. It was more like 2 or 3. The phone was announced at CES in January and was supposedly going to come out in June/July. June/July to the September release isn't 9 months.

    9 months after the announcement, we got a completely different phone. The Bionic at CES was Tegra-powered. Issues with Tegra and LTE caused them to scrap it.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
  19. Thread Author  Thread Author    #269  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SamuriHL View Post
    You fail to realize the bigger issue. Skins are great. Security problems aren't. When it takes you a year to get an update onto a phone (cough cough ICS Bionic anyone?) that's not a good situation. Security problems are becoming a bigger and bigger issue for Android. We need updates sooner. If we're waiting for an update because the company has to ensure compatibility with their skin, well, that's not good for anyone. I'd prefer they forego the skin, get us the update, and update the skin after that's done. One of the biggest reasons I'm going with an unlockable phone in the future is so I don't have to wait for the MFG's to do updates. I'm going for stock AOSP...security fixes will be a LOT faster that way.
    IMO, security problems are what should drive the speed of updates. Curious, which security issues have been addressed in each Bionic update? Security is an issue and should be on the OEMs to update/patch/fix with the carriers ASAP.

    That still doesn't change the thought that OEMs want their products to be different. After all, that's part of the openness and beauty of Android. Anyone can take the AOSP source and build their own product. If Google starts mandating things like "no UI changes" or "make your interface an easily removable skin", Google might as well take Android and close it off.

    In the end, and this is the bigger picture IMO - "skinned" Android or not Google is still getting what it wants out of the end/final-users.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
  20. #270  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by Ry View Post
    IMO, security problems are what should drive the speed of updates. Curious, which security issues have been addressed in each Bionic update? Security is an issue and should be on the OEMs to update/patch/fix with the carriers ASAP.

    That still doesn't change the thought that OEMs want their products to be different. After all, that's part of the openness and beauty of Android. Anyone can take the AOSP source and build their own product. If Google starts mandating things like "no UI changes" or "make your interface an easily removable skin", Google might as well take Android and close it off.

    In the end, skinned Android or not, Google is still getting what it wants out of the end/final-users.
    Every version of the OS has new security updates. JB focused a lot on security. Most people focus on what they can see and give a hearty "meh big deal" when compared to ICS. However, in terms of security, quite a bit was done under the covers to protect from rogue apps. They scan apps you install in JB. You wanna know what would differentiate an MFG right now? Not a skin. That's just nonsense that 99% of users either don't care about or actually wish they could remove. What would differentiate a MFG is to provide timely updates. Something closer to a nexus experience. Imagine how popular Moto phones would be if they dropped a new OS update 6 weeks after Google publishes it. They have great hardware. No one cares all that much about motoblur, however. They do care that updates are NOTORIOUSLY slow. Why do you think Google killed webtop? It's because that added to the amount of time it took to get updates out. SIGNIFICANT time. Motoblur isn't as bad, but, it still takes time. Fortunately Moto was somewhat smart and made motoblur universal. So they only have to do it once per OS version and it works on all phones with minor tweaking. Still, I'd rather kill that and get a plain Android phone that simply rocks hardware wise. What made the OG Droid great? The skin? Oh right, it was a GED. No skin. Yet it's still considered one of the best phones in history. How come that is if it had no skin?


    Samsung S4 Google Play Edition
  21. #271  

    Default Re: DROID BIONIC Jelly Bean Update

    Great debate guys! Love hearing both side of this one. I am personally in the "no skin out of the box" camp. If hardware manufacturers want to differentiate, do it with the hardware, not the skin. I'd rather have the new OS updates more quickly.
  22. Thread Author  Thread Author    #272  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SamuriHL View Post
    Every version of the OS has new security updates. JB focused a lot on security. Most people focus on what they can see and give a hearty "meh big deal" when compared to ICS. However, in terms of security, quite a bit was done under the covers to protect from rogue apps. They scan apps you install in JB. You wanna know what would differentiate an MFG right now? Not a skin. That's just nonsense that 99% of users either don't care about or actually wish they could remove. What would differentiate a carrier is to provide timely updates. Something closer to a nexus experience. Imagine how popular Moto phones would be if they dropped a new OS update 6 weeks after Google publishes it. They have great hardware. No one cares all that much about motoblur, however. They do care that updates are NOTORIOUSLY slow. Why do you think Google killed webtop? It's because that added to the amount of time it took to get updates out. SIGNIFICANT time. Motoblur isn't as bad, but, it still takes time. Fortunately Moto was somewhat smart and made motoblur universal. So they only have to do it once per OS version and it works on all phones with minor tweaking. Still, I'd rather kill that and get a plain Android phone that simply rocks hardware wise. What made the OG Droid great? The skin? Oh right, it was a GED. No skin. Yet it's still considered one of the best phones in history. How come that is if it had no skin?
    The OG DROID was a great seller mostly because it had a killer marketing campaign behind it. The rest of the Verizon DROID line (outside of maybe the DROID RAZR) never received that kind of love. Look at the Nexus One, Nexus S, Galaxy Nexus, and Nexus 4. Critically acclaimed phones by the Android community, but nowhere near the popularity of say a Galaxy S3.

    The reverse argument could also be made. "99%" don't really care about stock Android or OEM interfaces. The general buying public has hardly any idea of the Android version codenames. The general buying public hardly cares about removing the OEM's customizations to get back the "stock" Android look. They just need a phone that plays Angry Birds and connects to Facebook.

    I'll draw some parallels to hardware and micro USB charging. All phones not made by Apple use micro USB charging. This has been the case for years now. I was at Starbucks last week and overheard this:

    Samsung phone user: "Hey do you happen to have a Samsung charger or cable?"
    Motorola phone user: "Nope. I just have the cable for my phone."

    I stepped in here and mentioned that they both follow a standard and the Motorola micro USB cable will work on a Samsung phone.

    These users are the kinds of users that I expect to not care about stock Android. Unfortunately, they're buying power far exceeds the buying power of you and me - the ones that actually do care.

    Again, I respect your opinions and truly appreciate the help, guidance, and insights you give but any OEM going stock Android won't instantly solve their Android sales problems (HTC, Motorola, LG, Sony).
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
  23. #273  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by gwhizkids View Post
    Great debate guys! Love hearing both side of this one. I am personally in the "no skin out of the box" camp. If hardware manufacturers want to differentiate, do it with the hardware, not the skin. I'd rather have the new OS updates more quickly.
    I see both sides of it. I'm not opposed to skins, necessarily. I just think that it's ridiculous to hold up an update so they can work on their skin. Release it later when it's done. There's no reason that the non-skinned version of an update couldn't be offered as an "advanced update". Meaning you go in and set a setting on your phone to receive non-skinned updates, and you get them. Those that don't set that option will only get the update when the skinned version is ready. Phones would only be sold with the skinned version. I don't see how this is a bad idea. Everyone wins with that model. Yet the carriers complained. Ok, well, ONE carrier complained....


    Samsung S4 Google Play Edition
  24. Thread Author  Thread Author    #274  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,195 Posts
    Global Posts
    7,202 Global Posts

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by SamuriHL View Post
    I see both sides of it. I'm not opposed to skins, necessarily. I just think that it's ridiculous to hold up an update so they can work on their skin. Release it later when it's done. There's no reason that the non-skinned version of an update couldn't be offered as an "advanced update". Meaning you go in and set a setting on your phone to receive non-skinned updates, and you get them. Those that don't set that option will only get the update when the skinned version is ready. Phones would only be sold with the skinned version. I don't see how this is a bad idea. Everyone wins with that model. Yet the carriers complained. Ok, well, ONE carrier complained....
    Sure, one carrier may have complained, but I still have trouble believing that OEMs were okay with the concept that their interfaces (and the work they put into them) like TouchWiz, Sense, and MotoBlur (pre-Google) could be easily removable.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums
  25. #275  

    Default Re: DROID BIONIC Jelly Bean Update

    Quote Originally Posted by Ry View Post
    The OG DROID was a great seller mostly because it had a killer marketing campaign behind it. The rest of the Verizon DROID line (outside of maybe the DROID RAZR) never received that kind of love. Look at the Nexus One, Nexus S, Galaxy Nexus, and Nexus 4. Critically acclaimed phones by the Android community, but nowhere near the popularity of say a Galaxy S3.

    The reverse argument could also be made. "99%" don't really care about stock Android or OEM interfaces. The general buying public has hardly any idea of the Android version codenames. The general buying public hardly cares about removing the OEM's customizations to get back the "stock" Android look. They just need a phone that plays Angry Birds and connects to Facebook.

    I'll draw some parallels to hardware and micro USB charging. All phones not made by Apple use micro USB charging. This has been the case for years now. I was at Starbucks last week and overheard this:

    Samsung phone user: "Hey do you happen to have a Samsung charger or cable?"
    Motorola phone user: "Nope. I just have the cable for my phone."

    I stepped in here and mentioned that they both follow a standard and the Motorola micro USB cable will work on a Samsung phone.

    These users are the kinds of users that I expect to not care about stock Android. Unfortunately, they're buying power far exceeds the buying power of you and me - the ones that actually do care.

    Again, I respect your opinions and truly appreciate the help, guidance, and insights you give but any OEM going stock Android won't instantly solve their Android sales problems (HTC, Motorola, LG, Sony).
    The problem with this is that because of all these stupid customizations, it costs the MFG's a lot of money to update phones. The Thunderbolt just last week got ICS. Think about that for just a minute. They JUST GOT ICS. The issue is people don't care about updates....right up to the point where a massive security hole F's them royally. Then the public will be screaming and asking why those security holes weren't patched. This hasn't happened, so, MFG's and carriers have been beyond apathetic about getting updates out. During the 18 month life cycle of an Android phone, you'll be LUCKY to see one major OS update. Most phones never see 2. And it's unheard of for a phone to get 3 OS updates. So they need to do one of two things. Sell a phone as ONE OS only and continue to patch that OS as new security problems are found, or, they need to update those phones to newer versions of the OS that have been patched sooner. Running an out of date OS with security holes is asking for trouble. They're just lucky nothing massively bad has happened so far, but, it's bound to happen. When a million android phones get hacked due to a security hole, then you'll hear the screams. At that point, skins won't mean a damn thing to anyone. The lack of updates are going to kill this OS WAY faster than lack of customizations from MFG's IMO.

    - - - Updated - - -

    Quote Originally Posted by Ry View Post
    Sure, one carrier may have complained, but I still have trouble believing that OEMs were okay with the concept that their interfaces (and the work they put into them) like TouchWiz, Sense, and MotoBlur (pre-Google) could be easily removable.
    I can only speak for Moto on this one. I know for a fact they want blur to die. VZW wouldn't let them.


    Samsung S4 Google Play Edition
    Thanked by:
Page 11 of 113 FirstFirst ... 891011121314 ... LastLast

Similar Threads

  1. How to force a Nexus s Jelly Bean update July 23, 2012
    By clico in forum Google / Samsung Galaxy Nexus
    Replies: 8
    Last Post: 09-26-2013, 12:15 PM
  2. Predictions on when the AT&T GS3 will get Jelly Bean update?
    By saintforlife in forum AT&T Galaxy S3
    Replies: 43
    Last Post: 11-08-2012, 08:16 AM
  3. Jelly bean update
    By rob25 in forum Sprint Nexus S 4G
    Replies: 271
    Last Post: 09-24-2012, 06:53 PM
  4. i9020T Jelly Bean Update
    By autoappforum in forum T-Mobile Nexus S
    Replies: 10
    Last Post: 08-02-2012, 06:09 AM
  5. A question about Galaxy Nexus Jelly Bean Update!
    By 1aziz in forum Google / Samsung Galaxy Nexus
    Replies: 8
    Last Post: 07-23-2012, 12:02 PM

Posting Permissions

B