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
Related
We’ve been hard at work on CM9 since Google released Android 4.0 (Ice Cream Sandwich) into the wild last month, and things are slowly starting to come together. Google did a great job with ICS and added some really awesome features which in some cases replace or deprecate functionality that we had in CM7, so we are reevaluating all of our customizations. A number of devices are already up and running with CM9, and the focus is currently on getting as many devices ready as we can. The first devices (besides the Nexus S, which you can already get from Koush’s section on ROM Manager) that we’ll have ready will mostly likely be devices based on OMAP4, MSM8660/7X30, and Exynos. We also have some Tegra2 tablets in the pipeline such as the Galaxy Tab 10.1 and Asus Transformer. Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. I don’t want to make any promises at this time, but that is the plan. And sorry Droid1 owners, we’re dropping support for you. Time to upgrade.
What do you recommend if we have to keep our Droid1?!?
I have no philosophical problem with the Droid1 not having the latest and greatest CM ROM. I can get along without CM7 on the Droid1, since I will be going that way with my Droid Bionic "real soon now". (I'm kinda, sorta, used to this class of support, since I have about 6 Win XP/Pro boxes and a SBS 2003 server here on my SOHO network. All the current best boxes for me and my digital nerds are dual booted running top end Win7 and several flavors of Linux.
So, what is the last build that we should use, how long will it be supported and will security fixes be available?
Thanks,
/s/ BezantSoft
aoidcool said:
And sorry Droid1 owners, we’re dropping support for you. Time to upgrade.
Click to expand...
Click to collapse
And you plan to make this seem official... How? If the CyanogenMod developers actually said that, I might have a few unkind remarks about forced hardware upgrades to share.
For the record, I am not complaining about the lack of official CM9 support, the fact that ICS on the Droid1 would likely be a slow/buggy/needless upgrade, or anything along those lines.
What I might complain about is that the Droid1 is the most recent Android phone I would buy. Nothing newer has an unlocked bootloader, a better physical keyboard (well, minus the Nokia N900, but that's not without its issues either), a comparable screen, and the second-hand advantage: No carrier contract/spying or data plan required (Google Voice over WiFi FTW), cheaper than dirt for mobile software development, and wide availability (unlike certain Maemo/MeeGo phones).
Until a developer phone appears that meets my stingy requirements, I will continue using my Droid and experimenting with Linux software on it. I only wish that waiting for other people to do what I should be doing was easier, secure in my knowledge that someone else in the world cares about the same things I care about. What can I say, I'm lazy.
TL;DR: Telling people to upgrade when they don't have a choice is counterproductive IMHO.
gTan64 said:
And you plan to make this seem official... How? If the CyanogenMod developers actually said that, I might have a few unkind remarks about forced hardware upgrades to share.
For the record, I am not complaining about the lack of official CM9 support, the fact that ICS on the Droid1 would likely be a slow/buggy/needless upgrade, or anything along those lines.
What I might complain about is that the Droid1 is the most recent Android phone I would buy. Nothing newer has an unlocked bootloader, a better physical keyboard (well, minus the Nokia N900, but that's not without its issues either), a comparable screen, and the second-hand advantage: No carrier contract/spying or data plan required (Google Voice over WiFi FTW), cheaper than dirt for mobile software development, and wide availability (unlike certain Maemo/MeeGo phones).
Until a developer phone appears that meets my stingy requirements, I will continue using my Droid and experimenting with Linux software on it. I only wish that waiting for other people to do what I should be doing was easier, secure in my knowledge that someone else in the world cares about the same things I care about. What can I say, I'm lazy.
TL;DR: Telling people to upgrade when they don't have a choice is counterproductive IMHO.
Click to expand...
Click to collapse
That first post is a quote from the cm blog. So it is 100% true.
VISION 1.5Ghz
I think a kang will show up sooner or later. There are plenty of other interesting OMAP3 devices (Nook Color for one) which should get ports, and OMAP3 doesn't have to lose 60-100MB of RAM to the radio, so with compcache and good tuning 256MB might actually be enough.
It really depends on if OMAP3 HW accell can work fully under ICS. If the Nook Color runs well, so should the Droid...
gTan64 said:
What I might complain about is that the Droid1 is the most recent Android phone I would buy. Nothing newer has an unlocked bootloader, a better physical keyboard (well, minus the Nokia N900, but that's not without its issues either), a comparable screen, and the second-hand advantage: No carrier contract/spying or data plan required (Google Voice over WiFi FTW), cheaper than dirt for mobile software development, and wide availability (unlike certain Maemo/MeeGo phones).
Click to expand...
Click to collapse
so your complaint has nothing to do with software development, but with handset manufacturers. What does that have to do with CM saying they won't support what amounts to a 1st gen device?
TL;DR: Telling people to upgrade when they don't have a choice is counterproductive IMHO.
Click to expand...
Click to collapse
but you do have a choice. either upgrade, or you're stuck with whatever they've already built.
:|
Well, someone'll port ics to this 3 year old POS i'm stuck with for another year.
I'd rather have a current os that doesn't run well than a outdated os that does.
Sent from my Nook Tablet using Tapatalk
Mr. Argent said:
I'd rather have a current os that doesn't run well than a outdated os that does.
Sent from my Nook Tablet using Tapatalk
Click to expand...
Click to collapse
Why????
Sent from my VS910 4G using xda premium
Having no money for a off-contract phone and not being able to upgrade for a year, I have to do something to keep my original droid usable for a year. I find knowing there's a major update available and not getting it due to hardware issues annoying when the g1 got it (even if it was a laggy mess, at least it's not 2.3), which impacts it being what I consider usable.
(Also, I don't want ics launcher. Beneath the veneer of modernity it's still that stale old gingerbread.)
Sent from my nook tablet (eagerly awaiting a bootloader workaroiubd and ics) using Tapatalk.
Mr. Argent said:
Having no money for a off-contract phone and not being able to upgrade for a year, I have to do something to keep my original droid usable for a year. I find knowing there's a major update available and not getting it due to hardware issues annoying when the g1 got it (even if it was a laggy mess, at least it's not 2.3), which impacts it being what I consider usable.
(Also, I don't want ics launcher. Beneath the veneer of modernity it's still that stale old gingerbread.)
Sent from my nook tablet (eagerly awaiting a bootloader workaroiubd and ics) using Tapatalk.
Click to expand...
Click to collapse
I'm in the same boat as you, I have no upgrade for a year. so i'm stuck with my D1. and i agree with your other statement a g1 can handle it yet no one is making an attempt in porting it to the D1 on top of that a 6 year old htc windows mobile phone has it with like 134mb of ram. and yet the droid still has no port whatsoever
....and Droid 3 is missing. Could still be coming down the pipeline, but it looks like we are out of luck for the first wave (not that surprising).
http://news.verizonwireless.com/news/2012/03/bl2012-03-06.html
I know I have forwarded this theory before - but at first glance, the list does only have devices (among all manufacturers) that are well over 512MB of RAM - I think Dinc2 is the lowest at 768MB. I may be wrong - don't have all specs memorized.
Rlin5741 said:
I know I have forwarded this theory before - but at first glance, the list does only have devices (among all manufacturers) that are well over 512MB of RAM - I think Dinc2 is the lowest at 768MB. I may be wrong - don't have all specs memorized.
Click to expand...
Click to collapse
It's because the people at motorola that make these decisions don't even know what RAM is and haven't even heard of kernel or XDA-forums.
They think... Hm..1024 is more than 512.. lets not give 512 mb phones ICS.
If they'd at least unlock the damn bootloaders so people like hashcode can do it for them ffs
Part of me wants to never buy another motorola device, but this keyboard is just too nice. Motorola does a good job on the hardware but between the bloatware and the locked bootloader the software part can be disappointing. So we have an os released less than 6 months after our device was released and motorola basically says screw you. Verizon is just the messenger here.
Sent from my DROID3 using Tapatalk
Some of those phones are almost the same hardware as the droid 3 so I'm hoping that those vzw roms can at least be reverse engineered to figure out what's still missing in the cm9 alpha, like the camera.
Sent from my DROID3 using Tapatalk
I want the hardware acceleration front facing camera and face unlock.... then I will jump ship from stock on my xt860.
Sent from my A100 using xda premium
Reporting the full Motorola update schedule site: https://forums.motorola.com/pages/00add97d6c
interesting that bionic and d4 are still listed as evaluating. But even in best case, that droid 3 is only left out of the ics fun for the first rollout (vzw does say more updates are coming, and droid 2 did get updates almost 2 years after release), it looks like it will be a while - even some brand new devices that were in the vzw press release are scheduled for q3...
spunker88 said:
Part of me wants to never buy another motorola device
Click to expand...
Click to collapse
Our only hope is the Google takeover of Moto will change their bootloader policy. This then, I can't bring myself to buy another Moto phone.
By the time it comes to the Droid 3, it will be upgrade time...
Droid 3 is one of the best phones with android and qwerty and motorola dont plan to update to ICS?? Motorola in software decisions sucks!!! They never listened to the users
DRELUXOID said:
Some of those phones are almost the same hardware as the droid 3 so I'm hoping that those vzw roms can at least be reverse engineered to figure out what's still missing in the cm9 alpha, like the camera.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
The big constraint is going to be the locked bootloader.
It don't mean that droid 3 will never has ICS... just it not going to be on this first group... I'm sure in a couple of months we will see it on the list.
rblanca said:
It don't mean that droid 3 will never has ICS... just it not going to be on this first group... I'm sure in a couple of months we will see it on the list.
Click to expand...
Click to collapse
Well if they wait much longer:
A) people have upgraded to a newer phone
B) all people who actually care about having ICS rather than gingerbread already use hashcode's ICS
DoubleYouPee said:
Well if they wait much longer:
A) people have upgraded to a newer phone
B) all people who actually care about having ICS rather than gingerbread already use hashcode's ICS
Click to expand...
Click to collapse
I think that in Q1 of 2013 we might have an oficial ICS support, i don't believe sonner than that...
First it's motorola who decide, if our droid 3 can have ICS, then VZW if it will have.
Motorola should still be evaluating if ICS will going to run fine on our Droid 3 and if it's they will update his "ICS Update Schedule" and VZW his own.
Cya
rblanca said:
I think that in Q1 of 2013 we will have an oficial ICS support, i don't believe sonner than that...
First it's motorola who decide, if our droid 3 can have ICS, then VZW if it will have.
Motorola should still be evaluating if ICS will going to run fine on our Droid 3 and if it's they will update his "ICS Update Schedule" and VZW his own.
Cya
Click to expand...
Click to collapse
Well I don't think it'll take hashcode 'nd crew 1 year to fix hw codecs/video recording and some bug fixes
DoubleYouPee said:
Well I don't think it'll take hashcode 'nd crew 1 year to fix hw codecs/video recording and some bug fixes
Click to expand...
Click to collapse
Neither myself, I just talking about an Oficial ICS support by Motorola...so cheers to Hashcode!
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
Anyone try to unlock their phone yet?: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I'm trying, but apparently didn't have the Android SDK installed on this machine, so...
I am on vacation and don't have a spare phone on me to test it. Do people still read the bionic forums. I haven't been on XDA in months until i saw android central announce the unlock tool. Can someone test this and get back to us? This would really help development on our seemingly forgotten about bionics.
Sorry, but the Bionic is not on the list. Perhaps they will add it in the future, but I wouldn't hold your breath!
Currently Supported Devices ( Taken from: https://developer.motorola.com/products/bootloader/ )
The following devices are part of our initial roll out of the bootloader unlock program; additional devices will be added progressively.
Photon Q 4G LTE Sprint
Other Supported Devices
Previous devices released with an unlockable bootloader, and supported through Motodev at the following URL: https://developer.motorola.com/products/bootloader/
Motorola RAZR developer edition
Europe
Motorola XOOM Verizon
Motorola XOOM Wifi Worldwide
LOL...Apparently I kinda still read these forums.
I haven't had any luck yet, but I literally just sat down to give it a shot. I don't think I have my driver(s) set up right, but we'll see.
Edit: Just saw the post above. Bummer. When I was trying to view the supported devices earlier, the webpage barfed. Well, here's hoping they decide to add the Bionic to that very short list.
I hope they add us, but I'm not holding my breath. Given they way Moto & VZW have mismanaged this one, I'll be surprised if they ever mention the Bionic again after the ICS OTA. Getting lapped by the D4 has all but convinced me that they would just like to forget the Bionic ever happened.
When they do completely stop supporting it, it would be nice of them to unlock it and let the few remaining devs run wild. This was marketed as a flagship phone and came at a flagship's price, so just once I'd like to see it treated as something other than a redheaded stepchild.
And another one leaks. Same deal as 242...Security doesn't allow downgrade to 905 yada blah blah. This is getting old now. We've been on ics leaks since June and no ota in sight. House of Bionic has support for 244 for those who've already jumped to 235+. Those on 232 should continue to wait. At this point those on 232 are pretty much getting as much use out of it as they did 905. Maybe even more so. Lol.
Sent from my Xoom using Tapatalk 2
I think at this rate those of us on the Bionic will see Key Lime Pie out on the Nexus before we see ICS.
It's certainly getting to that point. If this build gets rejected then it's going to be October before we have any hope of seeing ota. Ugh!
Sent from my Xoom using Tapatalk 2
I am not that certain the Bionic will see ICS officially. Maybe there will declare it at EOL and quit.
Reason #2 why I will never, never, never buy another Moto device of any sort. This is totally absurd.
Has nothing to do with Moto. This is 100% on VZW. Moto has put out _9_ builds that VZW has rejected. *9*! That's unheard of. The ONLY issue left to fix is the stupid flash thing which NO moto ICS build works properly with. It's ridiculous but it's not Moto's fault.
Underwater Mike said:
Reason #2 why I will never, never, never buy another Moto device of any sort. This is totally absurd.
Click to expand...
Click to collapse
In the future, Motorola will be offering developer editions of their phones so that is my reason for continuing to remain with them, along with the quality of build typically being superior to the other companies (I say typical, as in not being 100% but for the most part).
With them releasing developer editions, this shouldn't be a problem anymore because it basically will turn all of their future devices into nexus's as far as being able to develop for.
Sent from my DROID BIONIC using Tapatalk 2
smokedkill said:
In the future, Motorola will be offering developer editions of their phones so that is my reason for continuing to remain with them, along with the quality of build typically being superior to the other companies (I say typical, as in not being 100% but for the most part).
With them releasing developer editions, this shouldn't be a problem anymore because it basically will turn all of their future devices into nexus's as far as being able to develop for.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
And let's not forget the most important aspect. Right in the middle of our ICS update being developed, Google went in and cleaned house at Moto. You can't deny that Moto is going to be a very different company moving forward with Google now owning them and installing an ex-Google ceo as the new Moto ceo. We're already starting to see massive changes and I for one think it's going to get a lot better. I'm on board with a new dev device from Moto as soon as they release the one I want. Samsung lost that bet with me back in July. The Samsung unicorn never materialized. Moto already has the devices up on the unlock page so we're not talking unicorns here. The RAZR M dev phone is up for preorder and I think coming this week. So, let's forget about the old Moto run by an idiot and focus on what direction Google is pointing the ship now.
I agree. I watched their press conference on YouTube and they definitely seemed like a new company. They specifically mentioned people wanting to tinker with their phones and changing things. It's been no secret that google follows the development community, especially considering some of the newer features of android were originally developed by the root community back in the old days of android (2009-2010).
On a side note, did anyone read about how nobody who works at apple actually uses SIRI (at least none of their developers). I found it amusing since I've seen the apple fanboys brag about SIRI. I think google and Android manufacturers should look into suing apple over some of the things they took from Android, such as voice search and folders. If you ask a fanboy, I'm sure they would tell you that android stole those from apple as well, even if we did have them first.
Sent from my DROID BIONIC using Tapatalk 2
smokedkill said:
On a side note, did anyone read about how nobody who works at apple actually uses SIRI (at least none of their developers). I found it amusing since I've seen the apple fanboys brag about SIRI. I think google and Android manufacturers should look into suing apple over some of the things they took from Android, such as voice search and folders. If you ask a fanboy, I'm sure they would tell you that android stole those from apple as well, even if we did have them first.
Click to expand...
Click to collapse
Share a link... I'd love to read about that bit of news.
A curiosity about this release... Some folks (including myself) found out that tethering was borked, even with FoxFi, after a certain leak release version. I'm not sure which one but I know tethering wasn't working for me on .232 and it doesn't work on my install of Liquid ICS 1.5 ROM, but I started from scratch and put .223 back into my non-safe side and FoxFi worked. Any idea if .244 still blocks tethering?
The obvious answer would be "yes" if we follow the logic that some version after .223 blocked it, but I just wanted to make sure
FoxFi hasn't stopped working for me in any of the builds. Still kicking for me in 244, as well.
Its in the article on USA today about a former executive talking about the siri commercials detracting from the product. I believe it made other news outlets also. I'll see if I can find a link.
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 07:32 PM ---------- Previous post was at 07:29 PM ----------
Vnvjeep said:
Share a link... I'd love to read about that bit of news.
Click to expand...
Click to collapse
Here is a link. The part about apple employees not using it is near the end.
http://mashable.com/2012/09/10/ex-apple-exec-pull-siri-ads/
Sent from my DROID BIONIC using Tapatalk 2
.244 change log
-the boring 2 has been changed to an awesome 4
-new "chiwawa barking dog" default ringtone
-phone now actually taste like a ice cream sandwich
-leaves breath minty fresh
ROFLMAO! That about sums it up.
Its VZW causing the delay
SamuriHL said:
Has nothing to do with Moto. This is 100% on VZW. Moto has put out _9_ builds that VZW has rejected. *9*! That's unheard of. The ONLY issue left to fix is the stupid flash thing which NO moto ICS build works properly with. It's ridiculous but it's not Moto's fault.
Click to expand...
Click to collapse
I agree, this is 100% VZW. My Motorola Xoom tablet received Android 4.1 back in July, because they did not have to go through VZW to release to the field. The XOOM and Bioinc run the exact same processor.
LMDude said:
I agree, this is 100% VZW. My Motorola Xoom tablet received Android 4.1 back in July, because they did not have to go through VZW to release to the field. The XOOM and Bioinc run the exact same processor.
Click to expand...
Click to collapse
Actually they don't. The Bionic uses an OMAP 4400. Nonetheless, VZW is what's holding up the OTA. Moto has done everything they can do to try to please them. I mean, how do you fix a problem with a plugin that's never going to get another update by the people who made it? It's clear that Adobe would have to fix it on their end not on Moto's. So it's just stupid.
SamuriHL said:
Actually they don't. The Bionic uses an OMAP 4400. Nonetheless, VZW is what's holding up the OTA. Moto has done everything they can do to try to please them. I mean, how do you fix a problem with a plugin that's never going to get another update by the people who made it? It's clear that Adobe would have to fix it on their end not on Moto's. So it's just stupid.
Click to expand...
Click to collapse
I value your opinion SamuriHL so let me ask you this. Is VZW's delay why you have chosen to go down the can never go back path (.235-.244)? I've been sitting idle at .232 and I'm ready to move on. Now with the news that we will get JB OTA at some point should I just wait another month for the ICS OTA or do what you have done down the leaked path. Do you think we'll get JB leaks too? I don't mind making the jump but I have to live with this phone for at least another 14 months and honestly i don't think I'll need to upgrade when the time comes. I'm pretty darn content with the Bionic. I just don't want to go down this road to end up at a dead end. Can we keep going forward?
zoompastu said:
I value your opinion SamuriHL so let me ask you this. Is VZW's delay why you have chosen to go down the can never go back path (.235-.244)? I've been sitting idle at .232 and I'm ready to move on. Now with the news that we will get JB OTA at some point should I just wait another month for the ICS OTA or do what you have done down the leaked path. Do you think we'll get JB leaks too? I don't mind making the jump but I have to live with this phone for at least another 14 months and honestly i don't think I'll need to upgrade when the time comes. I'm pretty darn content with the Bionic. I just don't want to go down this road to end up at a dead end. Can we keep going forward?
Click to expand...
Click to collapse
I can't give you any guarantees. Please understand that point as it's VERY important to what I say next.
I chose to originally go to the 235+ path because at the time I THOUGHT I was within a couple weeks of getting a new Samsung S3 Developer phone (what I now call the Samsung unicorn). However, I also wrote the House of Bionic and knew that I could keep moving forward as new leaks came out. Little did I know there'd be so many to test my code on. LOL! The HoB is pretty rock solid at this point....literally being "tested" by hundreds of users. But the warning about 235+ holds...we can't go back to any builds pre-235. That includes 905 which is a very big deal since all ICS updates ONLY update 905. The HoB will flash what parts of 905 it can (system, preinstall, webtop) and then the boot img of the update you're trying to install which allows us to move forward. And in fact allows us to move down, as well. Just no further down than 235. I bring that up for a reason. A lot of us have gone to 244 and we like it. A lot. But should VZW decide to OTA 242, as an example, those of us that have moved forward would be screwed without the ability to move back to 242 to get back on the OTA path. The HoB can do that for us. So I'm not personally concerned with my own phone getting back to the OTA path. Once we get a new ICS FXZ we'll be fine regardless. My warnings are for people that haven't been as blessed as I have to learn from some of the best people in our community. I like to make sure that others have options. Which is why I recommend the majority of people stick with 232. Unless you know the risks, and understand what the process does to your phone to move from one update to another (hint...it involves soft bricking until the update you're trying to install is successfully applied....not for the faint of heart since there's no FXZ safety net to fall back on should something go wrong), then 232 is the "safest" place to be. It gives you ICS but gives you the option of FXZ'ing back to 905 and taking the OTA should you need to go that route. Those on 235+ have only one option available to them...And that is the process I outlined that Matt Groff gave to us for moving between updates. I'm confident enough in the code and method that I believe it'll work. Now, go read the very first line of this post again, cause it's an important point to understand.
SamuriHL said:
I can't give you any guarantees. Please understand that point as it's VERY important to what I say next.
I chose to originally go to the 235+ path because at the time I THOUGHT I was within a couple weeks of getting a new Samsung S3 Developer phone (what I now call the Samsung unicorn). However, I also wrote the House of Bionic and knew that I could keep moving forward as new leaks came out. Little did I know there'd be so many to test my code on. LOL! The HoB is pretty rock solid at this point....literally being "tested" by hundreds of users. But the warning about 235+ holds...we can't go back to any builds pre-235. That includes 905 which is a very big deal since all ICS updates ONLY update 905. The HoB will flash what parts of 905 it can (system, preinstall, webtop) and then the boot img of the update you're trying to install which allows us to move forward. And in fact allows us to move down, as well. Just no further down than 235. I bring that up for a reason. A lot of us have gone to 244 and we like it. A lot. But should VZW decide to OTA 242, as an example, those of us that have moved forward would be screwed without the ability to move back to 242 to get back on the OTA path. The HoB can do that for us. So I'm not personally concerned with my own phone getting back to the OTA path. Once we get a new ICS FXZ we'll be fine regardless. My warnings are for people that haven't been as blessed as I have to learn from some of the best people in our community. I like to make sure that others have options. Which is why I recommend the majority of people stick with 232. Unless you know the risks, and understand what the process does to your phone to move from one update to another (hint...it involves soft bricking until the update you're trying to install is successfully applied....not for the faint of heart since there's no FXZ safety net to fall back on should something go wrong), then 232 is the "safest" place to be. It gives you ICS but gives you the option of FXZ'ing back to 905 and taking the OTA should you need to go that route. Those on 235+ have only one option available to them...And that is the process I outlined that Matt Groff gave to us for moving between updates. I'm confident enough in the code and method that I believe it'll work. Now, go read the very first line of this post again, cause it's an important point to understand.
Click to expand...
Click to collapse
I understand completely. One thing I just learned was If lets say .244 (or .242 as you used as an example) is the OTA release then we are back on the path as long as our version matches the current verizon version. Or did I totally miss interput that. HoB script is Awesome and is what I've used for moving from .2233-.232 and I fully trust myself to use these tools properly to move forward. Sounds like you're in the know of where to locate updates and are a reliable member of the Bionic XDA Community. Since there MAY be a way for us to move forward I think I'll take the plunge this weekend when I have some down time. Thank You