Related
So we all know Nodo was a bit of a mess and a lot of people got the update at different times, some had to wait months.
What confuses me is that with the Mango beta it works on any device, regardless of country or carrier... So why does the official updates need to be sent to the carrier first for them to release?
Why can't Microsoft just release 1 update, like they did for the beta, to go on all phones at the same time.. Or is that what they plan on doing this time round?
Because the carriers have MS by the short and curlies.
The carriers do (semi-legitimately) need to test the phone + OS combo on their networks. This is, generally, for the customers' benefit.
The beta was delivered direct from MS because it was a beta. There are probably clauses in contracts allowing this.
Also although the beta works on our devices, it still has to go to the hardware manufacturers, even before the carriers, to build/improve the custom drivers. This hopefully should improve the experience for end users (even further than what we've currently got).
Casey
The reason the OEMs and carriers need it is that when something goes wrong or when people ask about something, they wouldn't have any time to prepare for it - which they do now. Learn about new features and such.
Well, WP7 will be officially released in my region with Mango, and one of my largest fear is that people wont reject it because there is about 10 good apps in total, due to developers give about zero ****s about the new regions.
OndraSter said:
The reason the OEMs and carriers need it is that when something goes wrong or when people ask about something, they wouldn't have any time to prepare for it - which they do now. Learn about new features and such.
Click to expand...
Click to collapse
In which case it would have been better for OEMs and Carriers to work with the betas like normal developers have so that when the official release is ready there's not much delay... I hope this has been the case.
Im here at work and got me thinking bout the rumoured news bout Google releasing the JB 5.0 sometime this fall or workingnto release Q1 2013. News from AndroidPolice...too lazy to link it.
Im just thinking that these updates are happening way to fast. Some phones are yet to receive their ICS and yet JB is just around the corner. Also, new phones with quad will be released early/late spring..? with ICS and for some they will have to wait for another good amount of time for JB. We know that Samsung etc are never on the dot when releasing updates.
I kinda miss the days of Windows OS when they actually make you wait 2/3yrs for a new OS release. Just kinda makes it worthwhile.
All im saying is, that Google should wait until the supported phones have been updated to ICS and give them time to enjoy it. For others they will have to spend an extra money to buy the latest phone with ICS. Not really fair.
Ok im goin back to working...lol...sorta
Until we start seeing apps that don't work on somewhat new OS's I don't see it as a problem. For the most part, apps being put out now are still compatible with Froyo so why should people on Froyo care? Yes it sucks to get a new phone and not have the newest OS but what do you expect Google to do? With apple releasing yearly releases as well they need to keep up.
Google has been releasing yearly OS updates for a while now. Why the concern all of a sudden? Also, probably not worth getting worked up over unreliable rumors.
Sent from my Galaxy Nexus
I think one release a year is fair. With all thats evolving in the mobile landscape, an update interval any more than that will risk falling behind the competition.
A yearly update is not just to change things around for the heck of it, but to aim to improve the user experience. If the Android team has good work ready to be released, I don't see why they should hold it back because manufacturers can't get their act together. This is why we have the Nexus phones.
I completely disagree. Google's yearly release cycle means that they are always working on making Android better. Since a new major OS release comes every year, I am guaranteed to have a modern phone with a modern OS every year if I continue buying Nexii.
In my opinion it is certainly a good thing.
I dont agree with this. Wait 2-3 years for new features and fixes while other OS's (iOS and Windows Mobile) continue to have yearly updates? No thank you.
For the majority of people, whatever current Android they are on is more than enough for them. If you want to stay on the bleeding edge, you get a Nexus device.
JB probably will not be as big as an upgrade as it was from GB to Honeycomb or ICS.
How is Fall of 2012 or Q1 of 2013 too fast? It's not even spring yet. ICS was announced and released in November, I think. That is a full year, at least, in between OS changes. I think that 1 year in between OS updates is perfect. Why would you want to be stuck on an old OS when new, better features are always a good thing?
You're pretty much saying that you wouldn't mind still being on Eclair or Froyo right now. I don't know about you, but I think ICS is light years ahead of both of those OS's.
Hardware obsolescence will eventually halt fragmentation on its own. Most consumers roll over their device at the end of a contract anyway, that's just 2 years or 3 in some markets. Anyone that holds on to a phone for over three years either doesn't care about bleeding edge updates, they're happy with an old device anyway, or they've extended their device's life via custom roms. In other words, If it is January 2013 and you're still on Eclair then a) you probably don't know what 'Eclair's is and b) you're not losing any sleep over being excluded from updates.
I don't see a huge problem with the android market being 'fragmented' over 2-3 versions. It's all just optics: Android haters trumpet the fragmented platform while advocates brush it off. It shouldn't halt or slow down progress, and if it does then Google risks stagnation.
Its not that Google is going too fast, its that the other manufacturers are going too slow. 1 OS release a year shouldn't be a crazy schedule.
Am I reading this right - so you think technology advances too fast and wants it to slow down because YOU can't catch up?!
OP, please tell me that you are kidding.
Edit: I'm not flaming but simply shocked by the logic and argument.
Yes please get back to work already, sorry but I don't agree with your opinion, blame the carrier's and manufacturers as well.
Sent from my Galaxy Nexus using XDA App
ragnarokx said:
Google has been releasing yearly OS updates for a while now. Why the concern all of a sudden? Also, probably not worth getting worked up over unreliable rumors.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
The problem with these "hard and fast" Android updates is that is accelerates device obsolescence. Of the hundreds of Android handsets out there, only a dozen or two actually get these new OS'.
This isn't a problem you see in iOS devices, but it's certainly an issue with android.
Sent from my Transformer TF101 using Tapatalk
EP2008 said:
The problem with these "hard and fast" Android updates is that is accelerates device obsolescence.
Click to expand...
Click to collapse
Obsolescence? So which Gingerbread device can't make calls/text/access the market/use apps after ICS is released?
Just because some other devices do things faster/different doesn't make your device obsolete. And please, look up the word 'obsolete' first before tossing it around.
I think I partially understand and agree with OP's point.
It is not the yearly update that causes concerns, but it is the rate that creates so much hardware junk that counts.
For example, Apple's 3GS still can use recent iOS, at least it is upgradable, though you wont enjoy the speed or new features etc, but you still can use your old hardware with new iOS.
For Android, one year later you phone/tablet may already be "NOT ABLE TO UPGRADE TO NEW OS" , ICS, in this case.
Too many Device Spamming there. I think it is not Google's issue, it is , somewhat the Manufacturer's issue.
Because Nexus S still able to upgrade to ICS, Nexus One , sorts of (please correct me if I am wrong!)
But thanks to million android phone manufacturers, they locked down the system and make it proprietary in certain sense. and not upgradable to future OS because they don't know their current "Feature" will or will not be shoot down by Google's future updates.
Im actually coming from the Atrix which had an announcement from Motorola that ICS release would be sometime Q3 but that would depends if there is a delay or not. I decided to put myself into a contract and decided to get the Gnex since it had the latest offering of ICS. The Atrix ICS is still running on beta.
I agree that yearly updates will improve the user experience/fixes but then again we are but a small community here on XDA that are keen into rom/mod our phones. That is even if we have Devs willing to give time and effort in regards to leak updates. If ever we dont then we are sol. Im just thinking more about the general public who has no idea or would careless bout having a modified rom but are just interested in receiving the updates in a timely manner. Also, wat if ur current phone will not be included for any more OS release? the easiest way would be to purchase the latest and up to date phones.
If lets say that my collegues are getting the ICS for their SGS2 this Q2/Q3. Then JB will be released Q4/Q1 2013. The Google phones will be updated by either official or leak. Also i cant find the link but there was a stat released i few weeks ago stating that there are only 1% or 2% of phones that are currently running ICS.
Its frustrating for an average user having to sit next to a person with the latest OS release and wondering when they will get theirs.
For me, since im on ICS i dont care but when i was using my Atrix i had to settle for a mediocre beta ICS. :banghead:
@jiwengang - Thank you! Im glad someone here at least partially gets my point.
...now to get back to doin some real work.
I agree with others in that it's the hardware manufactures that are the problem, not Google.
1 year OS updates are fine. We just don't need 20 damn variations of the same phone from the same manufacture within that same year. The manufactures can't support all the different hardware configurations they are spewing out in a timely manner, so it takes ages to get updates, if you get them at all.
Dang manufactures need to focus more, stop trying to one up each other every 2 weeks. And support what they release more timely.
MilkPudding said:
Am I reading this right - so you think technology advances too fast and wants it to slow down because YOU can't catch up?!
OP, please tell me that you are kidding.
Edit: I'm not flaming but simply shocked by the logic and argument.
Click to expand...
Click to collapse
Not everyone has either the same knowledge or bottomless pocket that they can sport the latest and greatest phones. I still have a friend who I recently just flashed his SE X10 with GB 2.3.5. Though SE mentioned bout an ICS upgrade sometime in the future of who knows when.
Similar to the PC industry. A gamer will build a pc gamer rig with i9/FX with crossfire/sli etc...If you look at it now, the hardware has reached its peak. You can pretty much play any games these software companies throw at you. It is now the software ie: Games, trying to play catch up and entice gamers with more 'extra' dazzling features or effects to maximize ur hardwares potential. Back then, it was the other way around
If u use a console then its a different story.
Yes, it is shocking. Not everything works as smoothly as butter like ICS.
Yearly release / change of Android OS makes really senses to me.
I don't think I can wait for 2-3 years for an update / release.
that's why I got a nexus!
sent from my Nexus Prime
You are really losing focus as to what Jellybean actually is. All it is is an updated Ice Cream Sandwich. Yes, ICS was a huge jump from Gingerbread, because of the tablet/phone unification so there were major changes with the UI. That probably won't be the case with the next update. But if you remember the jump from froyo to gingerbread that wasn't a big deal huh? Googles cute little names cause too much confusion with consumers that don't understand software updates. 4.0.1, 4.0.2, 4.0.3...just updates.
Ripped from /r/android. Found this to be quite interesting. Apparently the OEMs don't really control if their devices get support for new android versions or not.
http://www.reddit.com/r/Android/comments/1j13xd/how_oems_havent_announced_43_updates_for_the/
https://plus.google.com/116988351660148062102/posts/MHhMo7X1fbF
Shen Ye said:
To all the people complaining about how OEMs haven't announced 4.3 updates for the devices:
• OEMs do not get the Android source code directly from Google.
• The SoC vendors are provided the code from Google, where they make a board support package (BSP) which contains drivers and optimisations etc.
• The BSPs are then passed on to the OEMs, which they use to develop updates for their devices.
OEMs are currently waiting for the silicon vendors to decide which SoCs they will support in making a 4.3 BSP for, because their update support is heavily dependent on this.
For example, Qualcomm recently decided to drop development for a 4.2.2 BSP on their S3 SoCs, which is why HTC had turn around and say they were dropping support for the One S. This also caused Sony to drop update development for the Xperia S, SL, Acro S and ION (all S3 SoCs).
Everyone remembers the Thunderbolt and Sensation (LTE variants) which used the Scorpion MSM8655, which Qualcomm dropped support for, so OEMs had to drop future updates for.
Samsung is an exception, they're their own devices' silicon vendors when it comes to Exynos. But they also had to drop support for their S2 LTE variants which were using the Qualcomm Scorpion SoC.
Sure, it's not the perfect system, but it's how it works in the industry right now.
Click to expand...
Click to collapse
This doesn't sound right if there's people bringing unofficial 4.2.2 updates to said devices. If some guy that that doesn't even have a job with android developing can do it, I think a multimillion dollar OEM can.
Ascertion said:
This doesn't sound right if there's people bringing unofficial 4.2.2 updates to said devices. If some guy that that doesn't even have a job with android developing can do it, I think a multimillion dollar OEM can.
Click to expand...
Click to collapse
True, but none of those 4.2.2 ports have kernel source code, and therefore none of them truly work 100% with no bugs whatsoever. Correct me if I'm wrong, but I believe devs use prior kernel sources and modify them to work with newer android versions (for instance, I had ICS via CM9 on my droid incredible 2, but it never worked 100%).
Yay, time to send hate-mail to Qualcomm.
Sent from my buttered S3
User "iamadogforreal" had an interesting reply:
iamadogforreal said:
This is OEM apologia. In the real world, these OEMs are the customers and boss around the chip makers. Not the other way around, like this blogger is claiming. If OEMs cared about updates then they'd put that in their contracts and pressure the chip makers to do them. Instead, this becomes a convenient excuse (collusion?) for OEMs to stop making those expensive updates, especially when you're 4 months from launching another flagship phone.
Funny how the Nexus line doesn't have this problem. Gee, maybe google just is getting lucky with niceguy SoCs? No, google puts this in their contracts.
Honestly, if you think the SoC guys are telling the world's biggest companies like Sony or Samsung to **** off and to tell your customers to **** off, then you're incredibly naive. Android fans need to keep pressuring these companies to deliver timely updates and to commit to a two year update cycle, at least. Articles like these don't do us any service and only exist to validate that awful status quo.
Click to expand...
Click to collapse
Let's get this out of the way first, nobody here is stupid, we know the L Release is never going to come to the Galaxy Nexus officially. So let's talk about the community. I just have one basic question for our talented devs, what are the odds that a port of L will be able to come to the Gnex and if so, what kind of time frame are we looking at here?
Does the Cyanogenmod team do developers previews like this one? We might see it from them.
I'm sorry, but this post is exactly what I expected to see today.
so lets get it out of the way.
SURE
we COULD see some 5.0 aosp love(via custom development)
MAYBE.
time frame?
when.source drops, give it a few months at most I'd say
source isn't even CLOSE to ready yet though.
SOOO
let's ALSO look at the past.
which nexus devices, after Google officially dropped support, are STILL ABLE AND ARE running LATEST android version?
ALL of them right?
stability and such isn't a factor for this question, it's IF IT CAN/DOES run newest aosp in SOME FORM.
so I'd say YES gnex WILL see 5.0 in SOME usable form. but asking for ANY "time frame"at THIS POINT since SOURCE ISN'T AVAILABLE YET is kinda pointless.
maybe though, just maybe, there are ALREADY some people at work on getting those "preview" things ported. no matter WHAT, patience and not asking for timeframe/eta is key here
I don't normally do +1 style posts, but I am also greatly interested in knowing this as well.
I imagine it is largely going to depend on how much of the underlying kernel and driver interaction changes. I remember on my prior phone, a Droid X which has been and is still locked down, it was generally impossible to get past ICS because of the major underlying changes in JB and not being able to get those on the DX. Granted the Nexus doesn't have this limitation but drivers aren't likely to be further updated and if the kernel goes too far forward it is unlikely to see compatible driver versions for GNex hardware.
EDIT: I should probably say modules instead of drivers. I'm primarily a Windows person PC-side.
Put it this way my 4 year old HTC Desire can run Kitkat then i would be amazed if we didn't end up with some pretty good builds of "L".
ashclepdia said:
I'm sorry, but this post is exactly what I expected to see today.
so lets get it out of the way.
SURE
we COULD see some 5.0 aosp love(via custom development)
MAYBE.
time frame?
when.source drops, give it a few months at most I'd say
source isn't even CLOSE to ready yet though.
SOOO
let's ALSO look at the past.
which nexus devices, after Google officially dropped support, are STILL ABLE AND ARE running LATEST android version?
ALL of them right?
stability and such isn't a factor for this question, it's IF IT CAN/DOES run newest aosp in SOME FORM.
so I'd say YES gnex WILL see 5.0 in SOME usable form. but asking for ANY "time frame"at THIS POINT since SOURCE ISN'T AVAILABLE YET is kinda pointless.
maybe though, just maybe, there are ALREADY some people at work on getting those "preview" things ported. no matter WHAT, patience and not asking for timeframe/eta is key here
Click to expand...
Click to collapse
Thanks for replying! I figured since I looked pretty thoroughly and didn't see a thread for it and thought that having at least one place for Gnex owners to talk about the L release for us wouldn't be a bad thing. I in no way meant to be one of those people who constantly bugs the devs about ETA's, I just meant what were could be expecting in the general sense. Thanks for the reassurance about us getting it, I've just been burned before about support with previous devices when they got past official support. But those weren't Nexii so I didn't know what to expect.
Brettbesa said:
Thanks for replying! I figured since I looked pretty thoroughly and didn't see a thread for it and thought that having at least one place for Gnex owners to talk about the L release for us wouldn't be a bad thing. I in no way meant to be one of those people who constantly bugs the devs about ETA's, I just meant what were could be expecting in the general sense. Thanks for the reassurance about us getting it, I've just been burned before about support with previous devices when they got past official support. But those weren't Nexii so I didn't know what to expect.
Click to expand...
Click to collapse
yea sorry about my tone in that reply mostly too
I'm usually not the one to fly off ranting towards other users actions, at least not on xda(i do #AshRants elsewhere lol)
your question was a valid one, and I know where you coming from when it comes to nom nexus devices and their lack of support, I had a droid x2 that was ORIGINALLY SCHEDULED BY MOTOROLA to have ICS update. which for some reason they just didn't follow through on. Their REASON they said was that "android 4.0+ would not improve functionality of this device"...aka "we don't feel like fixing all the bugs we gave you already with shotty gingerbread releases, and we aren't going to allow you to unlock the device or give you usable kernel source so screw off",...back when moto didn't gaf about the dev communities. they have made huge strides towards mending that relationship. just couldn't believe they had the gall to say 4.0 wouldn't improve the first dual core android device running a tegra2 chipset. bah. ramblings now again from ash.
but yea reason I kinda went off in that reply was mostly cuz I hoped all the other people who were already drooling at the chance to post the exact same things would slow down and think instead first it wasnt intended as a personal attack towards you or to start any flamewar on the subject. and judging by your reply you didn't take offense to it anyways, so :thumbsup: :good: we all on the same page anyways.
personally, I haven't seen much of the IO stuff about L, I saw mostly design changes, and would like to know more details about it's new features so I'll be digging around YouTube today for recaps and such.
but I'm almost certain that if we don't get some kinda official rom like CM, OMNI, SHINY, PA, etc... building L based.roms for us, then some of our awesomely talented devs will at LEAST get us able to look like we have it, along with SOME if not z MOST functionality of L.
ashclepdia said:
I'm sorry, but this post is exactly what I expected to see today.
Click to expand...
Click to collapse
I also think you guys should be patient. Your life won't be (that limited if there won't be a port of the coming up Android L to our Galaxy Nexus. Just relax.
As some have already pointed out, we're unlikely to see Android 5 "officially" ported to our GNex, for pretty much the same reason that we don't have an official 4.4 release for our phone. From ArsTechnica:
"Our talk with Burke shed some light on some more obscure topics too, including the lack of an Android 4.4 update for the Galaxy Nexus. Google's official line was that the company only supports hardware for 18 months after release, which it still mentions in its official Nexus update support document. As was speculated at the time, though, the decision was tied to Texas Instruments' exit from the consumer SoC market (TI's OMAP chip powered the Galaxy Nexus as well as other prominent Android-based hardware like the first Kindle Fires).
"It was a really extraordinary event," he said. "You had a silicon company exit the market, there was nobody left in the building to talk to."
Click to expand...
Click to collapse
TI stopped development for the GNex SoC at Android 4.1. Google and others worked hard to support it for 4.2 and 4.3, but the official TI software was broken by 4.4. The reason that we even have 4.4 custom ROMs is because some kind-hearted person, perhaps a TI insider, released beta or engineering sample software for the SoC. But as we've found, it's not the most stable
have a great weekend,
john
You could all complain about TI stopping development and blaming them. The Google Glass uses a not to different TI SOC compared to the GNex has a 3.4 kernel and runs 4.4.2
Now please understand that Google simply ditched us for reasons other than TI stopped developing SOC bla bla bla.
akash3656 said:
You could all complain about TI stopping development and blaming them. The Google Glass uses a not to different TI SOC compared to the GNex has a 3.4 kernel and runs 4.4.2
Now please understand that Google simply ditched us for reasons other than TI stopped developing SOC bla bla bla.
Click to expand...
Click to collapse
Plus if they didn't drop support after two years android would have alot more bugs in general.
DR3W5K1 said:
Plus if they didn't drop support after two years android would have alot more bugs in general.
Click to expand...
Click to collapse
I don't get your logic. And its not like 4.3 is flawless. HD video playback on this device (GNex) lags.
+ if Google themselves show a bad example to OEMs on how long to update devices, expect OEMs to not update devices older than a year. And this makes the whole "android doesn't get timely updates" into a new issue where "android doesn't get updates after a year+ at best".
GNex will never die!
(3.5 yrs going strong bby, and thanks to vanir+dirtyv f2fs running better than ever)
latenightchameleon said:
GNex will never die!
(3.5 yrs going strong bby, and thanks to vanir+dirtyv f2fs running better than ever)
Click to expand...
Click to collapse
Indeed. There will likely be somebody out there building from the latest source for this device as long as it's possible to do so, and possibly even if it isn't.
akash3656 said:
Now please understand that Google simply ditched us for reasons other than TI stopped developing SOC
Click to expand...
Click to collapse
Out of curiosity, what would those reasons be?
jsage said:
Out of curiosity, what would those reasons be?
Click to expand...
Click to collapse
That's up for you to imagine....
Money, profit, greed? You pick which one. Or make your own reasons.
akash3656 said:
That's up for you to imagine....
Money, profit, greed? You pick which one. Or make your own reasons.
Click to expand...
Click to collapse
Well, I guess when simple facts aren't sufficient then fantasy must be more believable.
wow
some of these replies were brutal, sheesh
gray bishop said:
some of these replies were brutal, sheesh
Click to expand...
Click to collapse
Honest perhaps. It's pretty simple really. The new OS (4.4) has a new kernel. The new kernel requires new drivers. Neither TI (OMAP SoC) nor ImgTec (PowerVR GPU) will supply those drivers.
Yes, an engineer at TI "released" a blob last fall. But it was not release-quality, it was beta-quality. Not everything is a conspiracy; we've just reached the end of the official support road.
On the other hand if one is inclined to run on the bleeding edge and stability is not their primary concern, there are any number of KitKat custom ROMs in which one can indulge.
have a great evening,
john
jsage said:
Honest perhaps. It's pretty simple really. The new OS (4.4) has a new kernel. The new kernel requires new drivers. Neither TI (OMAP SoC) nor ImgTec (PowerVR GPU) will supply those drivers.
Yes, an engineer at TI "released" a blob last fall. But it was not release-quality, it was beta-quality. Not everything is a conspiracy; we've just reached the end of the official support road.
On the other hand if one is inclined to run on the bleeding edge and stability is not their primary concern, there are any number of KitKat custom ROMs in which one can indulge.
have a great evening,
john
Click to expand...
Click to collapse
Ah crap I didn't mean to thank you. Anyway, yea sure remember all those OEMs you blame and all have given everything you've said to a certain product. GOOGLE GLASS. And go and check what SOC Google Glass uses.
Now have fun.
Why Motorola is not responding to the Moto G5 Plus Update?
Not even updated their update history page with Moto G5 Plus!
Poor quality mobiles Xiaomi is also giving MIUI 9.5 after just 3 or 4 months, what's up with Motorola
amarz1981 said:
Poor quality mobiles Xiaomi is also giving MIUI 9.5 after just 3 or 4 months, what's up with Motorola
Click to expand...
Click to collapse
in america, we make sure phones stay within certain spec so the dont cause cancer and polute air traffic with noise. said certifications take time to tes, because it takes more then a month or two to finish. it impresses me how fast they do it, too, seeing as the cancer would take years of normal use to surface. sorry our government cares about us too slowly for you.
i don't think we moto g5+ users wilp get oreo update. We should stop thinking about this. and Should Think of buying new phones with better specs.
solomon.rajan said:
Why Motorola is not responding to the Moto G5 Plus Update?
Not even updated their update history page with Moto G5 Plus!
Click to expand...
Click to collapse
Moto Updated update history....now moto g5 plus receive june security patch...not oreoo
https://support.motorola.com/us/en/Solution/MS130095
Can't moderators just delete useless threads? it will be easier and the discussion would be over.
Mod Edit: Threads deemed "useless" by some, may not be useless to others.
Best thing to do if you find a thread "useless" is to no longer participate in that thread.
Ogre6473 said:
First, don't be rude. That will get you nowhere.
Second, Motorola doesn't have to update a damn thing. They can't be sued for not updating just because at one point they said they were considering it. They also never said when. They could keep cranking out phones and in two years claim that they're still looking into it.
Considering they can't even fix their headphone jack issue, I doubt we'll get Oreo.
Click to expand...
Click to collapse
they can be sued, they never said they were considering the update, it is in the CONFIRMED list to be updated..
(just saying, i'm not in favor of any attack to the comñany, just clarifying things)
Ogre6473 said:
First, don't be rude. That will get you nowhere.
Second, Motorola doesn't have to update a damn thing. They can't be sued for not updating just because at one point they said they were considering it. They also never said when. They could keep cranking out phones and in two years claim that they're still looking into it.
Considering they can't even fix their headphone jack issue, I doubt we'll get Oreo.
Click to expand...
Click to collapse
You can be sued for false advertising
They can't be sued for not doing the update because it's not false advertising, nor are they under any contractual obligations
An advertisement is used to sell a product or service. Companies change their mind on updates and upgrades all the time. It's not illegal because the product wasn't sold with the promise of that upgrade.
Example: Every time there's a game developers conference, or CES or E3 there's promises of various kinds made by Sony and Microsoft, trailers for epic looking games etc. They even have working demos, yet many never see the light of day. How many times have they or the developers been sued for not releasing a planned product? Zero.
Ogre6473 said:
They can't be sued for not doing the update because it's not false advertising, nor are they under any contractual obligations
An advertisement is used to sell a product or service. Companies change their mind on updates and upgrades all the time. It's not illegal because the product wasn't sold with the promise of that upgrade.
Example: Every time there's a game developers conference, or CES or E3 there's promises of various kinds made by Sony and Microsoft, trailers for epic looking games etc. They even have working demos, yet many never see the light of day. How many times have they or the developers been sued for not releasing a planned product? Zero.
Click to expand...
Click to collapse
The product was sold with the promise of the software upgrade, as Motorola has stated multiple times that the g family has a policy for one major upgrade. Your example doesn't make much sense, game developers don't sell the game saying it will have a feature and then not include it. You obviously can't sue for them not releasing a planned product, unless you pre-order it and never receive a refund.
* * * THREAD CLEANED * * *
Please do not make generalizations or comments regarding ANY race, or ethnicity.
Not only is it a violation of Forum Rules, it is poor character to make general statements about an entire race/culture.
Whether or not it is intended to be offensive, comments of this nature have ZERO tolerance in Xda, as everything we do here focuses on development and devices, not race or ethnicity.
There will be no further warnings. Regardless of the intention to not be offensive, further comment(s) will result in the account of the author(s) being restricted or removed.
Be kind, be respectful, be helpful.
Thank you.