Database Develop

Do you want Froyo on your Milestone? Join the TwitterBomB cause!

Well, lets get serious, honestly, we need to do something about our milestones and froyo...
So I got this idea where all of us milestone users around the world demand motorola at the same day to upgrade our phones to froyo, or else, we won't buy motorola anymore, and we will start campaining about not buying any other motorola android devices with a locked bootloader.
So, what should we do?
We bomb their twitters accounts (Motodev, Motomobile, lorifraleigh,mlabowicz) twitting something "we want froyo on our milestones and we want it now! wake up and do something about it! #twitterbomb".
How do we do it?
We all do it by the last week of this mont, everyday, sereral times a day, ask everyone you know to retweet your #twitterbomb, we need to put the pressure on motorola.
So put it in your calendars, set an alarm so we dont forget it, lets twitter bomb motorola, foward this thread, share it on twitter, let everyone knows about it, we have until monday to join people to our cause!
Do you know any emails account from motorola offcials we can use? post them and i will share them here!

Btw, the month is AUGUST 2010

I would do a second tweet: "Open the freaking bootloader!! Why the hell Droid is not closed and Milestone is??!?".
That would sure solve all of our problems.
Thanks.
Anthonws.

Im sure their answer will be something like we forgot to do it, sorry we ****ed up... or maybe to get you hoocked
Sent from my A853 using XDA App

the reason why Droid hasn't a signed bootloader is well known...
Google had to work on the Droid it self... so they had to be able to flash their own roms into it, making Motorola unlock the Device!
Milestone was completely made by Motorola it self read NO Google Navigation by Default, instead MotoNavi...

The reason is nothing like that,where did you come up with it?
The reason why the droid is unlocked,is because apple has the rights for multitouch in the u.s.,so motorola unlocked the bootloader,so that users can enable multitouch themselves.milestone has multitouch support out of the box.thats the one and only reason for it.a little research never harms.
Google maps are also present.
Google navigation isnt available outside the u.s. yet in general.things are simple.dont get comfused.
Sent from my Milestone using Tapatalk

vagelisda said:
The reason is nothing like that,where did you come up with it?
The reason why the droid is unlocked,is because apple has the rights for multitouch in the u.s.,so motorola unlocked the bootloader,so that users can enable multitouch themselves.milestone has multitouch support out of the box.thats the one and only reason for it.a little research never harms.
Google maps are also present.
Google navigation isnt available outside the u.s. yet in general.things are simple.dont get comfused.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Whoa cool down buddy, it's just a phone... LOL
You may be right, but it is also correct that Google worked on the Droid for several months before release.
BTW ..Google Navigation is available in Canada and many other countries, where have you been? The Milestone only comes with MotoNav so you gotta install Google Maps Navigation manually from the market.

Yeah. Because spamming them really is gonna help.
What is this, /b/?

I think Spamming like this will never help. Company like Motorola ,which is spread all over the world with hundreds of categories of products, do not need to pay attentions to any such spamming or shouting.
Do you people really think that just by spamming like this on twitter will make whole world stop buying motorola range of products? certainly not. Like dsixda said Its Just a Phone, lolz.
2.1 updates are still coming to many devices. May be they are still doing some R & D on Froyo on Milestone and will release whey they confirm the stability and power consumption, etc. As per some unreliable(?) sources, Froyo is coming to Milestone in Q3, i.e. upto end of Sept 2010. Click here
https://service.o2online.de/portal/...ostpaid&hwid=4510+020109+00&tid=N-HWO-H-NC-20
On above page see "Besonderheiten" paragraph and find the line "Webkit Browser - durch Android 2.2 Update Flash-fähig". Though in german you can easily know whats written. If one Milestone gets Froyo, surely all will get. You just need patience.
I EVEN SUSPECT THIS TWITTERBOMB IDEA, May be you already know that Froyo is coming in Q3, and you are asking to bomb in last week of this month. It seems it will be easier for you to claim the credit of Froyo on Milestone in Sept coz you asked to bomb in last week of Aug 2010. LOLZ just kidding, dont mind it.
I am also doubtful that why twitter will keep quiet to spamming. There are high chances of your twitter accounts be suspended/closed after such spamming. So be careful.
lolz

I would really like to know what pisses you guys off having 2.1 installed? Only because of JIT, Tethering and the likes?
I'm just happy that Motorola still releases bug fixes for the Milestone (as another company leaves its customers supportless in terms of upgrades => see HTC Tattoo)...
Regarding the unlocking of the bootloader I'm also of the opinion that it should be unlocked...

I'm not to bothered about 2.2 but I want 3.0. Motorola should update the milestone as it is their flagship (I think that term is correct) device juat like the htc desire is htc's.
Sent from my Milestone using XDA App

To the OP: It'd be MORE MATURE instead to ask the Twitter account @ MotoMobile and Motorola when and if they are going to have the Milestone update. If lots of people ask (not "Twitter bomb") it would make them realize there is a lot of interest out there. I don't want us to stoop to the level that makes them think all XDA'ers are silly children who don't deserve 2.2.
The "I want my 1 point 6" campaign for the Rogers HTC Dream (Android 1.5) was successful enough on Twitter that Rogers decided to offer Dream users a free Magic which would be upgraded to 2.1 in the future.

afaik, the "I want my 1 point 6" campaign was for both the Magic and the G1/Dream
and they're still wauting for an upgrade to anything above 1.5 on their Magic
so i dont know if that can be called a success...
in Belgium, where i bought my Magic, they're still on 1.5 as well
upgraded to the Milestone (unbranded, i'm starting to learn) about a month ago, expecting it to be one of the first phones to be upgraded to 2.2, only to find out Motorola wasnt even sure if they would update the Milestone at all!

JarlSX said:
afaik, the "I want my 1 point 6" campaign was for both the Magic and the G1/Dream
and they're still wauting for an upgrade to anything above 1.5 on their Magic
so i dont know if that can be called a success...
in Belgium, where i bought my Magic, they're still on 1.5 as well
upgraded to the Milestone (unbranded, i'm starting to learn) about a month ago, expecting it to be one of the first phones to be upgraded to 2.2, only to find out Motorola wasnt even sure if they would update the Milestone at all!
Click to expand...
Click to collapse
Fair enough, but they did get a free new HTC Magic and got to keep their Dreams, plus they were "promised" the Magic would get the 2.1 update eventually.
Anyways, straying away from topic...

[Dev Poll]

Without an unlocked boot loader, which would allow for a custom kernel, we will never see substantial development on the Atrix.
Lack of (the ability to run) custom kernels prevents many of the modifications that have made Cyanogenmod and other popular ROMs appealing. (including overclocking, enhanced power management and screen color adjustments just to name a few)
The best we could hope for (without an unlocked bootloader) would be a stock version of android, devoid of all things Blur.
Luckily the latter will happen sooner rather than later, imo.
Like some other posters said, we still have hope. There are three main sources of unlocking the bootloader, I will list them here in the order I feel they are likely to actually happen chronologically:
1. Information gleaned from the LG Optimus 2X will directly translate into an unlocked bootloader on the Atrix:
If unconfirmed rumors are to be believed, the LG Optimus 2X, which runs the same Tegra 2 SOC (system on chip) as the Atrix, has already had its bootloader unlocked. With a European March release eminent (its only available in South Korea currently) it could only be a small matter of time before the same methods used to unlock the 2X fall into our hands.
2. Out of the box thinking by Developers leads to exploiting the bootloader:
Inquisitive and risky developers here at XDA have been laying waste to bootloaders and the like for years now. The Tegra 2 System On a Chip Platform is still very much in its infancy, it stands to reason that there are quite a few vulnerabilities hiding just under the surface awaiting the prodding minds of credit hungry devs.
3. Motorola makes good on their "promise" and gives us the keys to the castle:
Motorola has alluded to the possibility of releasing their secure grasp on our most prised dual core phone. Rest assured it won't literally be "keys" they give us, and more likely they will provide a flashable development bootloader accessible as a download to registered developers.
What method do you think will happen, first?

I think we may learn something from the Optimus 2X.

im feeling pessimistic about this. im not thinking its going to get cracked. hope im wrong though

The Devs always win, why would Moto release the software? Because they feel like it? Sorry they are worried about one thing and that is the bottom line, they wont do anything to help a small portion of their customer base.

You need to have an option for "DG will figure it out"

if anything we'd learn we should learn that from the XOOM, no ?
LG use the tegra 2 and all, but different company do ( lock ) things differently

oFUNGUSo said:
im feeling pessimistic about this. im not thinking its going to get cracked. hope im wrong though
Click to expand...
Click to collapse
Unfortunately I'm in line with you. It doesn't seem like there's any motivation for Motorola to release the keys, and from past history with their devices cracking the bootloader does not look promising.
It's a shame because this is a very good phone that just needs a little tweaking (removing Blur).

There has to be some way without the keys.. I don't know what, but it can't require just those. We need to get other developers to look at the Atrix. Like I said in the other thread, jimmydafish and maybe even koush could help DG try to find some way to bring ROMs. Even if they don't fully unlock it, just do it similar to the droid x.
Atrix4G Rooted!

the poll results speak truth.
*sad face*
its dumb too because i returned my craptivate to get this phone, and now i wont be able to do all the same cool stuff to it.
i guess i have 20 more days where i could return this and either go to the crappy again, or inspire. im juggling the idea, but the dual core, large ram and good battery life are making me lean towards just keeping this phone.....oh and the fact taht the GPS works when the crappy didnt

oFUNGUSo said:
the poll results speak truth.
*sad face*
Click to expand...
Click to collapse
You sir are no economist!
But seriously... if you look at the results, an overwhelming majority believe that we will in one way or another obtain an unlocked bootloader:
66.18% of all voters think it will happen, while only 33.82 think it never will.

Have faith in the DEVs, I'm voting on option 2!

it won't be cracked, it's almost impossible, but the droid x wasn't doomed because it still has greats rom. No unlocked bootloader only means no custom kernels, not roms.
i would like those 100+ people that signed the petition about at&t's block of hsupa instead post on motorola's twitter accounts all day. the only way we MAY get an unlocked bootloader would be for moto to do it.

jruweaver said:
Have faith in the DEVs, I'm voting on option 2!
Click to expand...
Click to collapse
what if one of those DEVs is the ony who actually told me, and i quote:
"it wont get cracked"

oFUNGUSo said:
what if one of those DEVs is the ony who actually told me, and i quote:
"it wont get cracked"
Click to expand...
Click to collapse
I guess it depends on which dev said it.

Designgears told me more than once, and everyone else in the IRC channel that we more than likely will not be able to unlock it. Never said it was impossible, but the thing that checks the kernel and recovery, whatever it is, is lower than the bootloader, that is why the bootloader is only signed.

Out of curiosity is it possible at all to OC without cracking the boot loader and loading a new kernel? I'm pretty sure it's not but just double checking.
Sent from my MB860 using Tapatalk

DemonWav said:
Designgears told me more than once, and everyone else in the IRC channel that we more than likely will not be able to unlock it. Never said it was impossible, but the thing that checks the kernel and recovery, whatever it is, is lower than the bootloader, that is why the bootloader is only signed.
Click to expand...
Click to collapse
Ohhh boy.. That does not sound good at all What to do, what to do?

Give up. It's tilting windmills without a leak from within moto.

I think you mean tilting at windmills, in reference to Don Quixote tilting his lance at a windmill thinking it was an enemy.

All literary references aside, even with a "leak from within moto" the chances of unlocking the bootloader are negligible.
We had all of the documentation and files from Motorola for the Droid devices including efuse implementation and emulation on unsecured hardware, all of component files themselves for both secured and unsecured hardware and all of the firmware builds.
None of it helped unlock the bootloader. We even have the methods and tools for setting and blowing the fuses with RadioComm.
It is irrevocable once set and we have been told that Motorola themselves cannot "unlock" them. All they can do is replace the chip with an unsecured one.

has motorola confirmed no ics for bionic?? attached email

This is a copy and paste of the email i received with identifying information removed. other then that it is un altered except for the part i underlined
We have not heard from you concerning your request for support in the 48 hours since we sent you a response. Consequently, we have changed the status of your question to SOLVED.
*Discussion Thread
* Via Email ()
03/11/2012 05:38 PM
Dear "",
Thanks for reaching out to Motorola. I’ve reviewed your e-mail and I’m ready to help.
We do apologize for the inconvenience. Regarding your concerns, Motorola's primary focus is the security of our end users and protection of their data, while also meeting carrier, partner and legal requirements. The Droid Bionic and a majority of Android consumer devices on the market today have a secured bootloader.
In reference specifically to eFuse, the technology is not loaded with the purpose of preventing a consumer device from functioning, but rather ensuring for the user that the device only runs on updated and tested versions of software. If a device attempts to boot with unapproved software, it will go into recovery mode, and can re-boot once approved software is re-installed. Checking for a valid software configuration is a common practice within the industry to protect the user against potential malicious software threats. Motorola has been a long time advocate of open platforms and provides a number of resources to developers to foster the ecosystem including tools and access to devices for developers via Motodev at http://developer.motorola.com.
For the Android 4.0, at this time, we do not have any information if the phone will be updated to Android 4.0.
With your data connectivity concerns, please provide us with the following information so that we can assist you better.
1. Serial number of your device. On the phone's home screen go to Settings > About phone > Status > IMEI number.
You may also follow the link below on how to locate the serial number of your device.
https://motorola-global-portal.custhelp.com/app/utils/guided_assistant/g_id/446
2. Software version of the phone.
On the phone's home screen go to Settings > About phone > System version
3. Your Contact number.
We hope that you find this information useful and we look forward to assisting you in the future.
For information about Motorola products and services, please visit us at http://www.motorola.com/
Thank you for contacting Motorola e-mail support.
Best Regards,
""
*Customer By Web Form
03/09/2012 11:57 AM
Why didn't you unlock the Bionic's Bootloader with the last update. You have promised to make motorola's bootloaders unlockable. I started my cell phone adventure with motorola. I have had other phones also, Nokia, HTC, LG. But I wanted to go back to my roots and go back to motorla. Now I see that was a mistake. I had the original droid for my first android phone. Then I went to the HTC Droid Eris, HTC Droid Incredible, Samsung Fascinate, and now your piece of crap Droid Bionic. I have never had a phone that was so flawed. Not to mention you released the Razr just a couple months after the Bionic. I am now screwed. I have a worthless phone that still drops data even after you put out an update that was supposed to fix that issue for the next 2 years. I am going to be forced to return to HTC for my cellular needs. And in the process of changing over I will have to now spend over $500 Because of your locked bootloader, I now cannot make the modifications needed to make the phone useable for my needs and also I cannot fix your mistakes in the programming to make the phone stable. Now for my last question / segustion. Since the RAZR has been released, I know you will not make putting android 4.0 on the Bionic a priority. When will you be releasing the android 4.0 update for the Bionic?? Also, when you do, if you do finally release android 4.0 for the Bionic I segust that you make the bootloader unlockable. This way I am no longer restricted and forced to use your flawed software. Google's Android OS is a Open Source Project. Who are you to close it and restrict its usage and capabilities. In doing so you have forced the public to use a piece of equipment that is flawed with no way or means of correcting the issues.
To be honest, I cannot believe that Google has not reamed your asses and filed law suits against the companies that lock their bootloaders and do not offer a way to unlock. Even if it voids the manufacture warranty the option should still be there. Android is Open Source and why do you have the right to restrict it?!
To sum this up.
1: I want an explanation on your bootloader and I want it unlocked. (Believe me I am not the only one)
2: When will Android 4.0 be released on the Bionic?
3: Statement: I am about to leave Motorola for good. I have had the worst experience ever with this phone and I am now on my third phone which is on its way just because you cannot fix your Data Drop issue. I require a reliable phone for work and this phone has been all but that.
Thank You
""
""

I'm not really sure how "we do not have any information" qualifies as confirming anything.
This is the link for their ICS upgrade schedule:
https://forums.motorola.com/pages/00add97d6c
If you read the descriptions for each stage, they state that the early stage does not guarantee an update. The comment in the response email was a carefully prepared legal statement to avoid hinting at anything.
I would be surprised if we don't see an ICS update, though it's always possible that it wont happen.

For the Android 4.0, we do not have any information if the phone will be upgraded at this time.
In that statement they used if instead of when. That says to me that they promised ics and advertised the phone as ics upgradeable and now don't know if they are going to do it or not. The key word in this is if. If and when are 2 totally different words. The original question was when and they comeback with ( no info if phone will be upgraded.) It raises questions.
Side note: they advertise a phone as ics upgradeable, but once you buy it you find out that its not even available to download. One must wait and hope and prey that their device is not forgotten about because in just 3 months time a newer phone has been released. I'm not new to smartphones or rooting or roms. I know I have to wait before I even buy the phone but the general public that just uses phones and has no idea what rooting is has no idea that they are going to have to wait for the upgrade and have to worry that they will even get the upgrade. Bad advertising and miss leading I say. (Rant Over)
Sent from my XT875 using Tapatalk

Im pretty sure they will release ICS for Bionic. I mean all the newer Motorola Devices (I.E RAZR, Droid 4, Xyboard) run essentially the same hardware in different form, the Omap 4430. Assuming those phones get 4.0 then so should Bionic :s

Ask them this: What percent of revenue does each new Android product represent?
Then imagine what it would be like to reduce their earnings by the lose of one of those products such as the Bionic.
It all about the money!

Motorola's customer service has often said things contrary to the truth. Since the site still says an update is on the way, I tend to believe the site.

All there website says is evaulation and planning.. That does not mean much. It could stay evaluation and planning for the next year. How long does it honestly take to evaluate and plan? No developing stage yet? Wow... Look at the developers that are building ROMs across the spectrum for various phones and brands and yet Motorola can't even get a grip just on there own phones... stepping off my soapbox.

Quoting directly from the link provided to the Motorola site: "As previously communicated, DROID RAZR, DROID RAZR MAXX, DROID 4, DROID BIONIC, DROID XYBOARD 8.2 and 10.1, and MOTOROLA XOOM WiFI + 3G/4G will be upgraded to ICS. Additional details on timing for these products will be shared at a later date."

--

Since I purchased this phone SPECIFICALLY BECAUSE it was advertised as it would be getting a version of ics 4.0, they will have to refund my money so I can get a phone that does run ics. It was critical to my purchase decision.
Do I hear a class action coming if they don't?
Personally I think they will release an ics upgrade as they have said and continue to say. Probably 2nd quarter this year. Development of mass stability is VERY difficult.
Sent from my bionic using my fingers...

Well I don't know if you guys/gals saw, but there was a leaked screenshot from a Best buy computer that shows the Razr and the Maxx receiving its ICS on the 4th of April. This was also confirmed by several emails that went out from Verizon stating there was going to be a software upgrade soon. Its typical they update the new phone first, but maybe its a sign we will get our update soon.
Sent from my DROID BIONIC using Tapatalk 2 Beta-4

Ya I saw it. Still not the bionic. If we get it I say it will be Oct or Nov before the bionic gets it and that's if it gets it.
Sent from my XT875 using Tapatalk

I think we'll get it, but definitely not anytime soon.
Sent from my XT875 using Tapatalk

Glad I've been running ICS for a couple months
Sent from my CM9 4.04 powered DROID BIONIC using Tapatalk 2 Beta-5

flascrnwrtr said:
Glad I've been running ICS for a couple months
Sent from my CM9 4.04 powered DROID BIONIC using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
How's that running? I've heard there's a lot of bug in CM9 on the Bionic. That's why I went to Eclipse instead.

flascrnwrtr said:
Glad I've been running ICS for a couple months
Sent from my CM9 4.04 powered DROID BIONIC using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
It's not fully-functioning ICS, and you have no video camera, no hw accel, half the games probably don't work right, etc.
I bet the devs we have would be able to port the RAZRs ICS to Bionic faster than Moto could develop it....

priddyma said:
It's not fully-functioning ICS, and you have no video camera, no hw accel, half the games probably don't work right, etc.
I bet the devs we have would be able to port the RAZRs ICS to Bionic faster than Moto could develop it....
Click to expand...
Click to collapse
For me, I don't play games on my phone and since I work in film/TV, I don't shoot video with my phone either. What I do have is everything else, rock solid data and stable wifi. I haven't gone to my unsafe side since mid-Feb. My point was, you can have a very usable version now and, with the release of the official and full RAZR version, we will have a complete version for our Bionics, whether moto releases one or not.
Sent from my XT875 using Tapatalk 2 Beta-5

The Bionic is definitely getting the ICS update, just don't know when. I spoke to my cousin when I switched to Verizon to get some info on some phones since he's a developer for Motorola. He was able to get me a Bionic and told me that it will definitely get ICS. He just doesn't have a date for it since right now he's testing ICS on the Razr Maxx.

The list of Verizon and Moto ICS updates has been reviewed and revised a couple times, Bionic making the cut each time. I see it definitely getting the update. As far as Razr and Bionic go theres not a significant difference in source, which helps the Bionic out a lot when it comes to ICS
Sent from my Transformer TF101 using Tapatalk 2

NO ICS For Us :(

Just checked the updated Motorola page... looks like this device is stuck at android 2.3 forever.
That really sucks, it's gotta be the 512mb memory that's in the device. I knew that would possibly be an issue when I first got the phone. Maybe we can put more pressure on moto to unlock our bootloader so we can get a fully functional ICS (even if it's hacked) on our devices.
Check the link:
http://forums.motorola.com/pages/00add97d6c

PFFFFFFFFFFFFF

I just saw this as well, very disappointing. I wish they would open up development to the community on devices they no longer plan on upgrading/supporting. I know it will never happen...but I can dream

Droid4 and Bionic get the ICS
maybe Hashcode or some one try to do what he can, and pull out from this phones something for us and for CM9 on D3

niko99 said:
Droid4 and Bionic get the ICS
maybe Hashcode or some one try to do what he can, and pull out from this phones something for us and for CM9 on D3
Click to expand...
Click to collapse
Just got a response back from hash regarding this on twitter:
" @danifunker @dhacker29 I have 1 more trick up my sleeve for the D3. And if that doesnt work, then ill drop back to cm7.2 or something. "
Let's hope the tweak works out... but either way I think I could live with CM 7.2, although I would REALLY love running ICS on this phone.

What ever happened to Kexec for the D3? I'll sacrifice a core for a new kernel that could even OC that one to 1.2.

I started to believe that motorola doesn't want anyone to buy motorola products.

calash said:
I just saw this as well, very disappointing. I wish they would open up development to the community on devices they no longer plan on upgrading/supporting. I know it will never happen...but I can dream
Click to expand...
Click to collapse
Sure would be nice if they would just open up phones when they started considering them legacy devices. Other than 4G which I don't particularly need anyway, the D3 is a great phone that could keep going for a long, long time just like my D1 did (I skipped the D2 and went directly from 1 to 3).
Part of the reason the D1 lasted me so long was that I could keep getting updates for it from Cyanogen. In fact I still have it. Though its no longer on the Vzw network I can test various things on it like security software, remote wipes etc over WiFi.
Verizon is probably against unlocking the D3 because they don't want to have the support issues and that's probably why we will never see it. How many people on these forums do you hear about that are constantly returning/exchanging phones that they have managed to kill through tweaking? Then its those same people who complain the loudest when the Motorola and the carriers won't unlock the phones. So, while I wish it was not so, we will probably never see them unlocked unless someone finds a way to hack them. Motorola isn't going to help and particularly VZW is not going to help.

danifunker said:
Just checked the updated Motorola page... looks like this device is stuck at android 2.3 forever.
That really sucks, it's gotta be the 512mb memory that's in the device. I knew that would possibly be an issue when I first got the phone. Maybe we can put more pressure on moto to unlock our bootloader so we can get a fully functional ICS (even if it's hacked) on our devices.
Check the link:
http://forums.motorola.com/pages/00add97d6c
Click to expand...
Click to collapse
HTC just released the HTC Desire C with a 600Mhz processor and 512MB ram. It runs Android 4.0
If they can do it with that, surely Motorola can too

ChristianPreachr said:
HTC just released the HTC Desire C with a 600Mhz processor and 512MB ram. It runs Android 4.0
If they can do it with that, surely Motorola can too
Click to expand...
Click to collapse
It's possible that the HVGA screen on that device needs far less memory - HVGA is 480x320 which is 70% less pixels to push than the qHD on the Droid 3. Also, Moto is pretty terrible at software, Blur runs a lot slower and chews up a lot more memory than a lot of its competitors.
What Moto should do is release a plain vanilla, non-blur ICS as an optional upgrade. I have to think that would take a minimal amount of time to port vanilla ICS to the Droid 3 if there is no need to get it working with Blur - just need the drivers which should be substantially similar to Droid 4.
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
ratman6161 said:
Sure would be nice if they would just open up phones when they started considering them legacy devices. Other than 4G which I don't particularly need anyway, the D3 is a great phone that could keep going for a long, long time just like my D1 did (I skipped the D2 and went directly from 1 to 3).
Part of the reason the D1 lasted me so long was that I could keep getting updates for it from Cyanogen. In fact I still have it. Though its no longer on the Vzw network I can test various things on it like security software, remote wipes etc over WiFi.
Verizon is probably against unlocking the D3 because they don't want to have the support issues and that's probably why we will never see it. How many people on these forums do you hear about that are constantly returning/exchanging phones that they have managed to kill through tweaking? Then its those same people who complain the loudest when the Motorola and the carriers won't unlock the phones. So, while I wish it was not so, we will probably never see them unlocked unless someone finds a way to hack them. Motorola isn't going to help and particularly VZW is not going to help.
Click to expand...
Click to collapse
Couldn't they just do what HTC did - online based bootloader unlock tool, which builds a list of unlocked IMEIs which are then voided of their warranty, and people calling for support will be checked against this list. Of course, the most enterprising guys with bricked phones will try to change their IMEI sticker, but that wouldn't match their Verizon account records.

This is so sad... Cant believe that Dual Core Processor phone is not eligable to receive Ice Cream Sandwich... Media shall be contacted, so they could make fun from Motorola... I'm never going to buy Motorola products again.. Ever.

Rlin5741 said:
What Moto should do is release a plain vanilla, non-blur ICS as an optional upgrade. I have to think that would take a minimal amount of time to port vanilla ICS to the Droid 3 if there is no need to get it working with Blur - just need the drivers which should be substantially similar to Droid 4.
Click to expand...
Click to collapse
Im pretty sure all we need is a compatible kernel and hashcode will take care of the rest. If Motorola could do that, it can extend the life of our phones.
Sent from my XT860 running ICS

Time to do some more Facebook trolling, I may even make an account over on the Motorola forums and do some spamming/trolling.
In July 2011 when I bought my phone there were 2 new Motorola smartphones out there the Droid 3 and Droid X2. Both had dual core processors and felt mid-high end at the time. But somehow an Android OS upgrade that was released less than 6 months after the Droid 3 was released is skipped by Motorola.
This was my first Android phone and I bought it because I wanted a keyboard and really liked the feel of a friends OG Droid. The OG was probably built better but I have still been mostly satisfied with the Droid 3 hardware wise. But I just can't see myself buying another Motorola device. I will have to see what is out there in 2013 when I upgrade, hopefully some nice QWERTY non Motorola devices.

Damn it Verizon
This is the Fourth phone that I've had from Verizon that has been abandoned before the end of it's life cycle. Although I am sure this is Motorola's fault I will curse Verizon for all time and remember to get the latest and greatest for top dollar right off the bat to ensure that I will get updates when dealing with a cell phone company or maybe get a landline and tell jerks like Verizon to stick it where the sun don't shine. The real pisser is that I am finding this out the day after I spent the money that could have been used to buy out my contract. Color me angry and frustrated.
I'm going to start reading up about custom roms for this phone I might as well since support is all but gone from this model.

Return the phone and tell them you want out. Can be done.
Sent from my DROID3 using xda premium

spunker88 said:
Time to do some more Facebook trolling, I may even make an account over on the Motorola forums and do some spamming/trolling.
In July 2011 when I bought my phone there were 2 new Motorola smartphones out there the Droid 3 and Droid X2. Both had dual core processors and felt mid-high end at the time. But somehow an Android OS upgrade that was released less than 6 months after the Droid 3 was released is skipped by Motorola.
This was my first Android phone and I bought it because I wanted a keyboard and really liked the feel of a friends OG Droid. The OG was probably built better but I have still been mostly satisfied with the Droid 3 hardware wise. But I just can't see myself buying another Motorola device. I will have to see what is out there in 2013 when I upgrade, hopefully some nice QWERTY non Motorola devices.
Click to expand...
Click to collapse
Please don't troll that forum. The mods there aren't actualy affiliated with moto like you think.
I did some of this back in the day about the d2 and learned the hard way.
Sent from my DROID3 using xda premium

Development is going to be good!

Alot of Developers have bought this phone!! development for Xperia T / TX and V is going to be good! so far we have 2 elite developers 2 recog developers,, correct me if i am wrong

FXP have 4 members
Bin4ry, Defer, Kali, Jerpelea

Codeworkx!
Tilal6991 too for paranoid android

Gok for kernel is gonna be beast.

Lol @ 4. Good start but not exactly a lot. Yet.
...

Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
well this is my first sony device, but looks promising, if sony stays open and doesn't screw up like samsung did, even if they are on updates, we'll have CM team for regural updates. actually, i hope this is first device i'll have for more than a year.
we'll see.
Sent from my Xperia T

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.

I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.

^aha your right
hello developer!

i think xperia t will get popular because it is the bond phone and the tx looks great in terms of design so it will get popular

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah. The Infuse was a less popular device, and as a result, the developer community was highly cooperative for a while. Unfortunately, the device itself was a nightmare to work with so it was ditched by many. Although, interestingly enough, now that some of the worst aspects of this device development-wise have been identified, the Infuse is becoming kind of fun to work with again.
In the case of the T - all evidence seems to indicate that it's going to be a highly pleasant device to work with, AND if it's not a super-popular device, it may have a more pleasant development community than some of the more popular devices.
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.

AvRS said:
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
Click to expand...
Click to collapse
I will have to decide on December 1st what phone I'm going to myself.
I personally understand the appeal of a quieter forum where the same issues aren't asked every couple of minutes.. Once or twice, I've actually had trouble finding a solution wading through the, "How do I ________" and most of them had the response, "do a search" :silly:
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah.... there are a lot of ungrateful members. I find myself in an awkward position because, I'm not skilled enough to develop a ROM but, I'm know I'm reliant on whatever XDA puts out to stay up to date with the latest ROMs.
Entropy512 said:
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
Click to expand...
Click to collapse
If I were in a position to take that stance, I would myself.
[/QUOTE]
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
[/Quote]
That unfortunately isn't really entirely an option for me. I'm on a family plan and have no capability of getting out of it at the moment. I don't have enough data to make 16 gigs with no SD card feasible.
I really got lucky when my Captivate had identical hardware to the Nexus S and Samsung was actually good about supporting the devs.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
Click to expand...
Click to collapse
Do you think that may have some weight on why Google decided to hop to LG for a Nexus device?
Either way, it sounds like I'll be on the Xperia TL or LG Optimus G this upgrade. The decision isn't exactly becoming easier to make though. At least I managed to scratch off the HOX+

i chose xperia phones becase developers say they are not hard to develop , i have an xperia ray and i have a buttload of roms to choose from... i cant decide so i need to fash every 2week!! (flashaholic :l)

also because sony provides solution for bootloader unlock

Here's what I know so far for the TL. Keep in mind none of this is official, and it is preliminary, so could change.
1) The bootloader will NOT be unlockable on any device that has an active SIMlock. e.g. any device sold on AT&T with a contract subsidy is not going to have an unlockable bootloader. This is almost 100% definite.
2) The bootloader should be unlockable for users who pay full price for the device from AT&T, e.g. anyone who can receive an immediate SIM unlock with AT&T's policies. That said, while AT&T says that any person with a full-price device should be able to immediately remove SIMlocks, often it's a major hassle, and I worry that the bootloader unlock "allowability" process will be even less integrated. Don't count on unlocking your bootloader if you purchase full-price directly from AT&T.
3) Sony may sell the device directly (again - they MAY do it, it's not guaranteed), direct-purchase devices will almost surely have an unlockable bootloader (Not guaranteed, but very likely).

Well,TX seems doesn't support for the rom made to T:crying:

niuzhd said:
Well,TX seems doesn't support for the rom made to T:crying:
Click to expand...
Click to collapse
of course not. It's a different device

Coming from laggy XS, now holding TX,
Sony is doing it right this time, TX design and ICS are so smooth, fast and bug free( at least haven't encounter any yet), TBH I don't have any intention to flash Rom or wait for update (JB).
Sent from my LT29i using xda app-developers app

Waiting for my first room tanks all
Envoyé depuis mon LT30p avec Tapatalk