Related
I posted the petition link on the Sony Ericsson UK and global Facebook sites and got the following reply from SE:
“Hi Mark, Thank you for your feedback regarding the Sony Ericsson X10’s Android upgrade.
We appreciate your feedback regarding this and have passed this on to the relevant department. We can confirm that this is something our developers are currently looking into and will provide further information once this is available.
Regards,
The Sony Ericsson Facebook Team
”
There is hope guys
That does sound promising. To be fair, they couldn't have missed the huge reaction from their customers. Well over2000 responses to the petition already and it's only been a couple of days. Looking brighter?
-------------------------------------
Sent from my X10i
Hopefully that is the reason that the incremental upgrade which was due "a couple of weeks" from May 5th has not materialised. Hopefully their best bods are focussing on seeing if 2.2 is a possibility....
No doubt their developers have X10 phones andthemselves would like their phones to be running 2.2...
cashaw said:
Hopefully that is the reason that the incremental upgrade which was due "a couple of weeks" from May 5th has not materialised.
Click to expand...
Click to collapse
... dont worry about that, this update was part of development for X10mini (pro), so we should see it in the next weeks.
and yes, 2.1 and NO 2.2 (froyo) brings only bad vibes for SE (and their future)
Something tells me that although the response sounds promising SE won’t change from their original plan. The 2000+ votes (As good as this is) only accounts for a fraction of the x10 owners out there.
Leaving out Froyo until a completely new line of phones can be used as a sell tool and a reason to adopt any new android phones they release where as if the x10 get the 2.2 now the new line would have to have more hardware advances to prove their worth increasing cost. Judging the hardware cut backs SE made with its flagship device most people can predict or assume the next wave of SE android phones will follow suit.
The petition needs to reach beyond the blogs to really make a difference, If the Japanese got wind of the petition and signed up that would really open SE eyes and i'm sure the speed increase of 2.2 would be enough to get them on board. Any ideas how?
"Most truths we're once deemed blasphemies"
At the moment the link is also twittered strongly think that makes the difference.
almaqdad said:
I posted the petition link on the Sony Ericsson UK and global Facebook sites and got the following reply from SE:
“Hi Mark, Thank you for your feedback regarding the Sony Ericsson X10’s Android upgrade.
We appreciate your feedback regarding this and have passed this on to the relevant department. We can confirm that this is something our developers are currently looking into and will provide further information once this is available.
Regards,
The Sony Ericsson Facebook Team
”
There is hope guys
Click to expand...
Click to collapse
No hope.
Just a standard message ...
Where did you see hope there?
Well, it is something that should have been done. Since this is the best SE phone in a long time, with a potential to get better.
So if they are choosing to apply this update... Then I would assume that I would be even more satisfied with my phone. But right now, is the thing that annoys me the most.. That I can't buy applications here in Norway yet.
And I can do it in Morocco, and that country isn't on the list either.
All I can say that 2.2 finally provides bluetooth functionality for voice dial.
In places where it is illegal to hold a cellphone while driving, voice dialing using bluetooth is an extremely useful function. Android devices have been lacking this since 1.5 cupcake. Google finally added full bluetooth functionality on 2.2. I hope SE does the right thing and updates the X10 to reflect this.
It is very annoying when Apple updates the Iphone constantly and Android phones are stuck on whichever hardware manufacturer schedule to make its phone unique (e.g. sense, timescape, touchflow).
I think Google has the correct idea of separating future updates from the unique modifications that the manufacturers want. But for that to happen, all phones have to reach 2.2. first.
i work in a bar in malmö, sweden which the nearest city to where se have a rather huge campus there, anyway, i got a saw a japenese guy with an x10 and told him that we have the same phones, i told him that the x10 really needs froyo to be updated onto it and he told me that it will prob be on it sooner than you think.
he explained to me that they knew about people crying out for 2.1 and well get it sooner aswell!!
is there light at the end of the tunnel??
The petition needs to reach beyond the blogs to really make a difference said:
"Most truths we're once deemed blasphemies"[/b]
Click to expand...
Click to collapse
Here to reach them,but we still someone to translate in japanesse for us,ill try to find someone on my day off.
http://xperia-fan.jp/community
And here the official Japanesse twiter
http://xperia.twinavi.jp/
I've asked a mate of mine (who's a 5th dan Shotokan Karate!!) to see if he can do it, or ask one of his Japanese contacts to do it for us.. will let you know if I have any luck.
Great i just use google translator on the site.....my lol We really need a real Japanesse speaker
but it tell me they are in the same boat then us at least ,seems they getting 2.1 to eventually.
OSAnroid OS version 1.6 release with time. Worldwide, the latest version is 2.0 or 2.1 was announced and has been released.
Xperia is the OS version yet, it seems to be positively considered.
Since October 2010 presentation of the model in summer 2010 Android OS 2.1 to upgrade to announced that.
発売時の搭載OSAnroid OS バージョン1.6。世界的には、最新バージョンは2.0や2.1が発表されたり、発売されています。
XperiaのOSバージョンアップは未定ですが、前向きに検討されているようです。
2010年夏モデルの発表会で2010年10月以降にAndroid OS 2.1へバージョンアップをすることを発表しました。
visitador02 said:
All I can say that 2.2 finally provides bluetooth functionality for voice dial.
In places where it is illegal to hold a cellphone while driving, voice dialing using bluetooth is an extremely useful function. Android devices have been lacking this since 1.5 cupcake. Google finally added full bluetooth functionality on 2.2. I hope SE does the right thing and updates the X10 to reflect this.
It is very annoying when Apple updates the Iphone constantly and Android phones are stuck on whichever hardware manufacturer schedule to make its phone unique (e.g. sense, timescape, touchflow).
I think Google has the correct idea of separating future updates from the unique modifications that the manufacturers want. But for that to happen, all phones have to reach 2.2. first.
Click to expand...
Click to collapse
They are still lacking the AVRCP profile update. It is still stuck on v1.0.. when the latest version is v1.4
Yep. I bought an MW600 as it was advertised that it's fully compatible with X10, but after three months of emails flying around, SE concluded that it's not fully compatible due to Android's limitation on AVRCP profile.
For MW600 to work fully with X10, we need AVRCP 1.3 or above!!
Maybe we can stress SE to roll out an update for security reason? These few days, Malware, backdoors and trojans in official market place became hot topic.
And quote from CNET :
At least 50,000 people had downloaded the apps in question, according to enthusiast site AndroidCentral. However, many of those potentially infected may have been protected by staying current with the latest Android updates. AndroidCentral notes that Google actually patched its source code to prevent this type of exploit for users running Android 2.2.2 or higher and that the vulnerability doesn't exist at all in Gingerbread, aka Android 2.3.
Click to expand...
Click to collapse
Reports: Google yanks infected Android apps
Chances might be slim, but it worth a try?
Anyone know a way to contact SE regarding this issues(security/android version update)? Or would like to help get this message to them?
Posted on Xperia X10 Official community forum. Any other site, email to send the message to them?
could work if we tell them that this can somehow damage their fw or idk
alankstiyo said:
could work if we tell them that this can somehow damage their fw or idk
Click to expand...
Click to collapse
The attack is an exploit, they have to patch it.
You need to do a full system wipe and reset your phone completely, the data wipe and reset from settings may not be enough. This means ODIN, RUU's, .sbf files or a trip to your carrier store if this is beyond your capabilities.
Click to expand...
Click to collapse
But then what about product id/IMEI/IMSI and our privacy (some of us do have paypal, google account :gmail, contacts,checkout/bank apps).
For those of you wondering what phones will and will not get Gingerbread, or the tards (or just diehard wishful thinkers) that think Verizon will just skip right over FroYo and go to Gingerbread, this is an official quote from Verizon:
"Google's just-announced Gingerbread software is generating buzz in the media.
Initially, it is not available on the Verizon Wireless lineup of Android phones.
BUT ... we're working with Google as they release source code for device manufacturers to begin integration. We are also assessing which devices will get Gingerbread within the coming months.
Stay tuned - more information will be available soon."
So that means, they won't even begin ASSESSING what phones receive the updates for MONTHS. Not days, not weeks, MONTHS. So those hoping to see Gingerbread anytime soon, well, sorry to burst your bubble, but its not happening. Those thinking FroYo was delayed to bake its bug fixes into Ginger, well, they'd have to delay it for months. Lets hope this is not the case....
Don't ask where I got the quote from....'tis not your concern
No
Sent from my SCH-I500 using XDA App
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
Click to expand...
Click to collapse
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Who really cares about gingerbread anyway. I'm very satisfied with DJ05 update, roms/kernals/themes. I can now wait patiently for froyo and... not even concern myself with when/where gingerbread will be released.
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
imnuts said:
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
Click to expand...
Click to collapse
Samsung has code obviously, without it, they couldn't have built the Nexus S. And I doubt Google builds the "Nexus" software because of all the little nuances of the code interacting with drivers and so forth (RIL ring a bell????), but I could be wrong, I don't work for either Google or Samsung.
I doubt the other OEM's have any builds running yet, as evidenced by the very first reference to builds, where they say that they are working with OEM's AS GOOGLE releases source code for them to integrate into their phones, but people can take it for what they wish.
I just put the quote out there verbatim. Do with it what you will.
mexiken said:
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Click to expand...
Click to collapse
Actually I don't know how many times this has been said. Google releases their OS source not so long after their press release. It is the OEMs who have to release their kernel for us to develop anything. We've had 2.3 code for awhile now but we don't have kernel. They just released Nexus One kernel like yesterday so they'll get it pretty soon. People, Google's OS code and OEM kernel are two different things. We always had code source pretty fast at hand.
The fact that I'm super-skeptical of these unsourced-but-supposedly-from-Verizon quotes aside, I think imnuts has a point here.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months.
Click to expand...
Click to collapse
According to the rules of grammar, he's right. The order matters: since the clause "will get gingerbread within the coming months" comes after "which devices," not "we are assessing," it refers to the former. Had the quote been "We are also assessing within the coming months which devices will get Gingerbread," then it would be the other way around.
But that aside, even more importantly, saying a process will happen "within the coming months" doesn't mean that the process won't start for months. It means something is likely to be ongoing and could be done within one month, six months, or anything in between (or longer). Ultimately, that's the kind of wording people use when they want to remain intentionally vague, and we really can't read a timeline one way or the other from it. Especially when it comes to mobile carriers and software updates.
mexiken said:
There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ????
Click to expand...
Click to collapse
Well, for starters, Samsung obviously has had the 2.3 source code for quite some time considering they have a Gingerbread phone coming out tomorrow. We also know Motorola has the 3.0 code seeing as how they're working on at least one already-functional Honeycomb device. The only one we can say definitely doesn't have 2.3 is LG, because they said so (though they also said 2.3 required a 1ghz processor in the same breath, which turned out to be a complete lie, so it's hard to trust them). But clearly, AOSP gets the code just a tad later than at least some OEMs do.
What is the point of this?
The idea of this is to convince htc to unlock the bootloaders and disable the NAND protection on their phones
Why should I support this?
Unlocking the bootloader and disabling the NAND protection will allow users to keep their phones up to date using custom roms such as CM7. Take the htc wildfire for example. In december 2010, HTC released a 2.2 update for the wildfire. However, hidden in this update was a new bootloader which could not (and still can not as of the 15th may 2011) be modified. It is unlikely that HTC will release another update for this phone, meaning that users are going to be stuck on this rom. The reason? So HTC can sell new phones. However what this is doing is putting users off buying HTC's devices since rival companies have announced that the users can easily unlock the bootloaders on their devices.
To support the campaign please sign the petition at http://goo.gl/uIeqv and you can like us on facebook at http://goo.gl/e1CqN and you can see updates on my blog at http://goo.gl/KdpFr
We got featured on androidspin http://goo.gl/DryCd and eurodroid http://goo.gl/4SNf8
Well the ceo of htc announced this
Cellphones, Mobile Software
HTC officially dissolves locked bootloader policy
By Sean Hollister posted May 26th 2011 9:25PM Breaking News
The homebrew community may mourn HTC's Thunderbolt, Incredible S, Sensation and EVO 3D, but the company's controversial policy of locking bootloaders is no more. Following a tease yesterday, HTC CEO Peter Chou has decreed from on high -- namely, HTC's Facebook page -- that future devices will be open.
There has been overwhelmingly customer feedback that people want access to open bootloaders on HTC phones. I want you to know that we've listened. Today, I'm confirming we will no longer be locking the bootloaders on our devices. Thanks for your passion, support and patience.
We're holding out hope that this policy will also be retroactive, but this is very welcome news regardless. Ball's in your court, Motorola.
Source
http://www.engadget.com/2011/05/26/htc-officially-dissolves-locked-bootlader-policy/
I just had some bad news : requesting open bootloader for X10
Code:
SEAnswers Sony Ericsson Global
@hagisbasheruk There are no plans for that as of now.
So what do you say, do we get unlocked bootloader ?
No UNLOCKED bootloader as of now, doesn't rule out a future unlock though so mabey we need a new petition started to get this feature for our great developers on here.
Bear in mind that there will be no special sony erricson features on the 2.3.3 they are dropping all that. So my feeling says it might be unlocked.
Also I emailed sony netherlands a week a go with the same question about the bootloader of 2.3.3. They said 2.1 was the final version. I think they only know how to random press the keyboard and hit enter.
Yeah, half of these places you contact have no idea. In fact sometimes we probably know more than them!
Don't put your hope into this, one the GB update hasn't released yet, not everyone in the company knows about it (yet).
SE already stated that the bootloader will not be unlockable for the X10 due to contracts and legal obligations already in place with 3rd party vendors.
even if you [SE] unlock the bootloader after the 2.3, then the bootloader can be unlocked for 1.6 and 2.1 devices leaving 3rd party apps (at&t bloatware, moxier, etc) vulnerable.
svtfmook said:
SE already stated that the bootloader will not be unlockable for the X10 due to contracts and legal obligations already in place with 3rd party vendors.
even if you [SE] unlock the bootloader after the 2.3, then the bootloader can be unlocked for 1.6 and 2.1 devices leaving 3rd party apps (at&t bloatware, moxier, etc) vulnerable.
Click to expand...
Click to collapse
Yes just like we won't get a 2.3 update. They announced 2.3 after the bootloader unlocking program. So im sure we get unlocked.
PlayGunsta said:
Yes just like we won't get a 2.3 update. They announced 2.3 after the bootloader unlocking program. So im sure we get unlocked.
Click to expand...
Click to collapse
uh, read SE's blog, it's listed specifically. all new devices will get bootloaders unlocked. X10, x10 mini, x8, etc, will not due to existing contracts in place and legal obligations.
they are going to update to 2.3 due to google's recent news release about pushing manufacturers to continue development on existing devices and stopping them from abondoning the user base.
so yes, SE previously stated that GB wouldn't come to the X10, but google is pushing manufactures to continue updates when possible on devices.
it has nothing to do with sony's abilities, but rather their obligations.
svtfmook said:
uh, read SE's blog, it's listed specifically. all new devices will get bootloaders unlocked. X10, x10 mini, x8, etc, will not due to existing contracts in place and legal obligations.
they are going to update to 2.3 due to google's recent news release about pushing manufacturers to continue development on existing devices and stopping them from abondoning the user base.
so yes, SE previously stated that GB wouldn't come to the X10, but google is pushing manufactures to continue updates when possible on devices.
it has nothing to do with sony's abilities, but rather their obligations.
Click to expand...
Click to collapse
So what, they can surprise us just like always.
svtfmook said:
uh, read SE's blog, it's listed specifically. all new devices will get bootloaders unlocked. X10, x10 mini, x8, etc, will not due to existing contracts in place and legal obligations.
Click to expand...
Click to collapse
It may not be true but don't you think this is the reason why only the Generic unlocked X10s are getting the update. There are no plans to update carrier locked X10s..
PlayGunsta said:
So what, they can surprise us just like always.
Click to expand...
Click to collapse
not legally, which means unlikely.
The bootloader has been bypassed anyway, why does this even matter?
Because it's way better then just having it bypassed.
Do you actually believe that Sony Ericsson will give you info about something that they not have made official yet? You can ask them anything and they will give you a similarly answer. You will see that the bootloader will be unlocked.
Sent from my Sony Ericsson Xperia™ phone
realunited123 said:
It may not be true but don't you think this is the reason why only the Generic unlocked X10s are getting the update. There are no plans to update carrier locked X10s..
Click to expand...
Click to collapse
Thats not true. The Swedish phonecompanys 3, Telia and Telenor will be able to update their branded 2.1 to 2.3.3.
Sent from my X10i using XDA App
webbsmurfen said:
Thats not true. The Swedish phonecompanys 3, Telia and Telenor will be able to update their branded 2.1 to 2.3.3.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Thats true but you must take in that Swedish companies/ carrier is not as the companies / carriers in the states and we have only asked the custom service on those carrier so nothing is for shore yet.
Sent from my Sony Ericsson Xperia™ phone
I think we need proof.
First there wouldnt be 2.1. Now there is.
First there wouldnt be 2.3, there will be.
That are the only facts where you can resource your data out.
Several attempts of me trying to get a clear awnser from SE failed. They allways tell you something else.
aR_ChRiS said:
Because it's way better then just having it bypassed.
Click to expand...
Click to collapse
Oh really, why exactly is it better?
The reason we wanted the bootloader cracked was to custom kernels, this is possible through bypass.
If the bootloader was cracked/open, we'd have the exact same kernels with the exact same progress/bugs as we do now. I fail to see the benefit, but I might be missing something.
If anything, bypass is better, as if something goes REALLY wrong then you can still revert back to stock quite easily.
To me it smacks of just wanting to say that it's been cracked as some sort of nerd "status" symbol, although if anyone can prove otherwise then fair enough
Xperia84 said:
Thats true but you must take in that Swedish companies/ carrier is not as the companies / carriers in the states and we have only asked the custom service on those carrier so nothing is for shore yet.
Sent from my Sony Ericsson Xperia™ phone
Click to expand...
Click to collapse
I asked them both. (In this case, Telenor and SE. Sorry about cut n paste)
Confirmed directly by Google -
"As such, we asked if history would repeat itself with these new carrier Nexus devices. "I don't think we're going to do that. There is carrier testing that has to happen—you can't get away from that—but we're trying to have our updates be frequent," Burke said. "I think the carriers are learning and realizing that's a feature they want. So I think these are getting more efficient and they're getting better at it."
So it sounds like carrier Nexus devices will lag behind the unlocked versions, as they will have an additional carrier testing step. The hope this year is that the carriers wise up and won't delay things too much, but the potential for a delay is there."
http://arstechnica.com/gadgets/2014...talks-to-android-execs-about-the-upcoming-os/
Don't expect quick updates on Verizon
Eh, there will be stock rooted flashable updates available. :good:
Considering how abysmal the "testing" on the 4.3+ update for the S3 was....I don't think that testing will find much of anything...and considering how quickly Samsung redid the update and it got back to consumers, that delay will only be days rather than months.
Maybe.
Easy fix.... root and rom duh.
Did you take expect anything different?
Well at least we know AT&T, T-Mobile & Sprint probably won't have delays because there were none on the Nexus 5
It's very possible that the OTA won't go out to any N6 until testing is complete. I guess we'll see when the phone starts shipping if there are different build versions for each carrier. My gut says no. Let's not be alarmists quite yet.
I wouldn't be surprised if the carrier-branded N6's have locked bootloaders that cannot be unlocked.
But that is a feature of Nexus devices....
There isn't much about this Nexus that is like the past several iterations. Don't be surprised if it has a carrier logo stamped on it too.
Who's to say the Nexus 5 didn't have delays? Let's say Google only announced the new os when it was cleared to be pushed? Moto x phones and HTC phones require testing and they seem to get software updates out pretty fast now on verizon. As Aaron Rodgers once said after getting beat by the Lions. Relax.
Just unlock and flash stock google otas?
ECrispy said:
Confirmed directly by Google -
"As such, we asked if history would repeat itself with these new carrier Nexus devices. "I don't think we're going to do that. There is carrier testing that has to happen—you can't get away from that—but we're trying to have our updates be frequent," Burke said. "I think the carriers are learning and realizing that's a feature they want. So I think these are getting more efficient and they're getting better at it."
So it sounds like carrier Nexus devices will lag behind the unlocked versions, as they will have an additional carrier testing step. The hope this year is that the carriers wise up and won't delay things too much, but the potential for a delay is there."
Don't expect quick updates on Verizon
Click to expand...
Click to collapse
The part that you bolded was written by Ars Technica, not stated by Google. Nowhere in that article does Burke confirm that updates will be delayed. In fact, he says that he basically says that he doesn't believe that what happened with the Galaxy Nexus will happen again with the Nexus 6. Read the paragraphs before and after the paragraph you quoted for context.