Related
As some of you may have heard Google has brought out Motorola. Although the deal isn't 110% it's getting there.
Google and Android seem to pride themselves in being open, which, Motorola and it's bootloader policy are not.
I know it's a shot in the dark but hopefully we as a community can get our case known with Google and hopefully for them to release the keys to our devices.
This thread is about ideas on how to put our case forward to Google, and I don't mean spamming their social networking accounts with "FREE TEH BOOTLOADER" at least, not yet. Ideally, I would like to be as formal as possible (such a writing up and getting you guys to sign an agreement about why you want the bootloader unlock, how it would effect our user experience as well as how it would embrace the Android way of thinking - even that we would sign away our right to a warranty).
What do you guy think?
reply
wid u mahn !!!!!
had exactly the same idea the moment i heard the news. I would propose some kind of petition. Also maybe we can add comments to the official anouncement in Google blog, in an educated and informative way.
in the past 5 months I tried the following:
HTC Hero, Galaxy Vibrant,Motorola Atrix 4G, My touch 4G, Nexus 1, Sony Ericsson X8, Blackberry torch, HTC HD7 & went back to Milestone (in fact I have 2 now)..
I must say that main advantage for Milestone is two things I admire:
- fancy material & great design
- brilliant developers like Kalabadan, Feeo & Lucka
Upon trying unlocked devices such as HTC devices I found out that even for such popular Cyanogen is not that advance compared to Kalabadan work (you can check it out through xda) meaning you need both futures to get perfections (good set specifications & brilliant developers)..
Google acquiring Moto is a great news hoping our brilliant developers to stick with it.
alijs said:
in the past 5 months I tried the following:
HTC Hero, Galaxy Vibrant,Motorola Atrix 4G, My touch 4G, Nexus 1, Sony Ericsson X8, Blackberry torch, HTC HD7 & went back to Milestone (in fact I have 2 now)..
I must say that main advantage for Milestone is two things I admire:
- fancy material & great design
- brilliant developers like Kalabadan, Feeo & Lucka
Upon trying unlocked devices such as HTC devices I found out that even for such popular Cyanogen is not that advance compared to Kalabadan work (you can check it out through xda) meaning you need both futures to get perfections (good set specifications & brilliant developers)..
Google acquiring Moto is a great news hoping our brilliant developers to stick with it.
Click to expand...
Click to collapse
Well Said brother Well said
a Representative should contact google
You guys need someone high ranked within XDA to prepare a short request concerning the milestone issue and send through the proper channels.
I don't know what are the proper channels, but they can be searched on google site.
In addition, I don't see why not to contact Google through G+.
Unlike Motorola, it is quite easy to contact the higher ups at Google.
Now, to the statement, any ideas on how we should start it?
Also, I would like to point out this;
"Once the acquisition is approved (later this year or early 2012), there’s one thing we know will happen to Motorola for sure: the company will continue to function just as it does now. Motorola CEO Sanjay Jha and his team will continue to lead Motorola independently from Google. Larry Page emphasized this over and over in both the blog post and conference call. “We will run Motorola as a separate business,” said Larry Page. Both companies will even have separate finance reports.
In other words, you can expect to see more of the same coming from Motorola — at least for the time being. Sadly, this means MOTOBLUR and locked bootloaders aren’t dying anytime soon. That might change in the long-term, once Google has more control over the company. But for now they’re here to stay."
http://androidandme.com/2011/08/new...ould-happen-to-motorola-after-google-buys-it/
DannyDroid said:
In other words, you can expect to see more of the same coming from Motorola — at least for the time being. Sadly, this means MOTOBLUR and locked bootloaders aren’t dying anytime soon. That might change in the long-term, once Google has more control over the company. But for now they’re here to stay."
Click to expand...
Click to collapse
That is really verry sad, I love the hardware that motorola builds but if there is no change in this politics my next device will be from someone else.
I still hope that there will be changes once the deal is done, I love my Milestone.
There is still hope out there.
Maybe we get some leak with signing tool or keys..
They had promised to unlock the bootloader at the end of 2011 before google got into the game. I did not believe them (or they would unlock it with 6-12 months further delay), but now just maybe they keep their promise and unlock the devices when they said they would...
DannyDroid said:
As some of you may have heard Google has brought out Motorola. Although the deal isn't 110% it's getting there.
Google and Android seem to pride themselves in being open, which, Motorola and it's bootloader policy are not.
I know it's a shot in the dark but hopefully we as a community can get our case known with Google and hopefully for them to release the keys to our devices.
This thread is about ideas on how to put our case forward to Google, and I don't mean spamming their social networking accounts with "FREE TEH BOOTLOADER" at least, not yet. Ideally, I would like to be as formal as possible (such a writing up and getting you guys to sign an agreement about why you want the bootloader unlock, how it would effect our user experience as well as how it would embrace the Android way of thinking - even that we would sign away our right to a warranty).
What do you guy think?
Click to expand...
Click to collapse
I agree and will support your idea. Count on me for any help.
Is it useful to build a facebook page with name: UNLOCK BOOT LOADER, MOTO!!!? If yes, I will do that.
alijs said:
in the past 5 months I tried the following:
HTC Hero, Galaxy Vibrant,Motorola Atrix 4G, My touch 4G, Nexus 1, Sony Ericsson X8, Blackberry torch, HTC HD7 & went back to Milestone (in fact I have 2 now)..
I must say that main advantage for Milestone is two things I admire:
- fancy material & great design
- brilliant developers like Kalabadan, Feeo & Lucka
Upon trying unlocked devices such as HTC devices I found out that even for such popular Cyanogen is not that advance compared to Kalabadan work (you can check it out through xda) meaning you need both futures to get perfections (good set specifications & brilliant developers)..
Google acquiring Moto is a great news hoping our brilliant developers to stick with it.
Click to expand...
Click to collapse
Agree!
_crAss_ said:
They had promised to unlock the bootloader at the end of 2011 before google got into the game. I did not believe them (or they would unlock it with 6-12 months further delay), but now just maybe they keep their promise and unlock the devices when they said they would...
Click to expand...
Click to collapse
Do you have any reference for their promise????
i'm with you guys.
There is a good chance that Motorola will change some of their policies by Google's influence, and we hope they start unlocking the bootloaders.
But i think a strong petition by the community will help alot.
Sent from my Milestone using XDA Premium App
_crAss_ said:
They had promised to unlock the bootloader at the end of 2011 before google got into the game. I did not believe them (or they would unlock it with 6-12 months further delay), but now just maybe they keep their promise and unlock the devices when they said they would...
Click to expand...
Click to collapse
Motorola never said such a thing. They did however say that start unlocking some handsets depending on unknown to the public factors.
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
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
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
Well... we are really grateful for this new Motorola been so attentive with us in order to provide the Kit Kat as fast as a Nexus device. But...
... as I'm reading about 4.4.1 and 4.4.2, these updates are major bug hunters, and not only a camera fix as "Google" says.
So, are Motorola working to implement this minor for us? Does anyone have an idea about it or can ask to Moto Care if there is any attempt from Moto about it?
The help desk from Moto here in Brazil is one step behind from US one cause we are partially receiving 4.4 by these days, so if 4.4 is something new to then to handle, imagine 4.4.2.
I made some research on news but unsuccessful.
This is likely why most other companies don't rush to release a new version of Android. They will go through all the effort of packaging, testing and releasing only to be screwed by Google a week later with a new update. I doubt the carriers like it either, as they like to test stuff.
Once something has been out for a bit and the major bugs are dealt with then it would be much easier to release. This is a bit of a flaw in how Google's android model works.
It would be much more ideal for Motorola to have adopted the Apple model where they release a new build and don't really care much what the carrier thinks.
I am sure someone at Motorola is already working with 4.4.2 but considering the number of carriers that don't have 4.4 yet it is hard to say what they will do. Maybe they will hold off on them and switch to a 4.4.2 build for the ones who haven't received 4.4 yet.
To keep up with the new android releases, the bloatware some carriers insist upon, builds for the different hardware models and then a huge number of different carriers must be quite the fun project to manage.
I heard that the 4.4.1 and 4.4.2 updates only had fixes for the nexuses devices and wont be pushed to any other kit kat devices
Kit kat blows. That's my scientific analysis. Doesn't matter what device section you go to.... You will read about a lot of bugs. They "almost" squashed flash. It locks some brands boot loaders... From what I recall. They are trying to stop root. They are trying to stop 3rd party battery analysis apps.... Etc... Etc. Basically they seem to be trying to squash development.... Oh... Unless you buy a special developer model of a brand. Lol
Anyway.... My point is... 4.4 is awful. Let's hope they do a better job with 5.0. And they stop leaning toward the apple philosophy of not letting people "play" with their phones.
Every device section I follow has threads about kit kat... And when will they get it. Then when they do, theirs tonnes of negative threads about it.
4.2.2.....the last best version. At this point.
Sent from my Moto X cell phone telephone...
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
I'll add.... The carriers play a big part in these shenanigans I'm sure.
Sent from my Moto X cell phone telephone...
dobbs3x said:
I heard that the 4.4.1 and 4.4.2 updates only had fixes for the nexuses devices and wont be pushed to any other kit kat devices
Click to expand...
Click to collapse
Not really... 4.4.1 was a big update regarding KitKat performance and bugfixes...
You can check the commits to see that they've changed A LOT of stuff in Android framework...
We definitely MUST have the 4.4.2 update... 4.4 is a bit laggy... 4.2.2 was much more stable...
kj2112 said:
Kit kat blows. That's my scientific analysis. Doesn't matter what device section you go to.... You will read about a lot of bugs. They "almost" squashed flash. It locks some brands boot loaders... From what I recall. They are trying to stop root. They are trying to stop 3rd party battery analysis apps.... Etc... Etc. Basically they seem to be trying to squash development.... Oh... Unless you buy a special developer model of a brand. Lol
Anyway.... My point is... 4.4 is awful. Let's hope they do a better job with 5.0. And they stop leaning toward the apple philosophy of not letting people "play" with their phones.
Every device section I follow has threads about kit kat... And when will they get it. Then when they do, theirs tonnes of negative threads about it.
4.2.2.....the last best version. At this point.
Sent from my Moto X cell phone telephone...
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
I'll add.... The carriers play a big part in these shenanigans I'm sure.
Sent from my Moto X cell phone telephone...
Click to expand...
Click to collapse
I think your science is off. SSDD when it comes to Android releases. Same exact posts sprouted up when Gingerbread was released...
Sent from my XT1060 using Tapatalk
And to each their own.
Sent from my Moto X cell phone telephone...
kj2112 said:
Kit kat blows. That's my scientific analysis. Doesn't matter what device section you go to.... You will read about a lot of bugs. They "almost" squashed flash. It locks some brands boot loaders... From what I recall. They are trying to stop root. They are trying to stop 3rd party battery analysis apps.... Etc... Etc. Basically they seem to be trying to squash development.... Oh... Unless you buy a special developer model of a brand. Lol
Anyway.... My point is... 4.4 is awful. Let's hope they do a better job with 5.0. And they stop leaning toward the apple philosophy of not letting people "play" with their phones.
Every device section I follow has threads about kit kat... And when will they get it. Then when they do, theirs tonnes of negative threads about it.
4.2.2.....the last best version. At this point.
Sent from my Moto X cell phone telephone...
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
I'll add.... The carriers play a big part in these shenanigans I'm sure.
Sent from my Moto X cell phone telephone...
Click to expand...
Click to collapse
Buy a Developer edition so you have a unlocked boot loader. If you buy retail expect it to be locked down and lucky if a exploit is found.
Travisdroidx2 said:
Buy a Developer edition so you have a unlocked boot loader. If you buy retail expect it to be locked down and lucky if a exploit is found.
Click to expand...
Click to collapse
I have the Rogers version... I'm all unlocked.
I was talking about devices in general. Google and the carriers are making it tough on people to unlock... Root... Etc.... On many devices.
I have zero problems with my Moto X. I was knocking 4.4 and the direction Android in general seems to be heading.
Sent from my Moto X cell phone telephone...
There is a reason that Google, manufacturers and carriers are making devices more and more secure. There is demand for it. People don't want insecure devices that someone can randomly access. Or, the want a secure phone that is good for both personal and business use. While you say it's bad, it isn't. I'm not sure why you think a secure device is a bad thing, or why you expect the initial software release to be bug free. I don't think there has been an Android release yet that hasn't seen a few quick incremental updates just after initial release to fix bugs.
Also, 4.4.1 and 4.4.2 are more than just "Nexus updates". Sure, the updates mainly apply to Nexus phones because they're the only ones running 4.4.0 really, other than the Moto X. There is a lot of stuff fixed that will apply to all devices running the software, not just Nexus phones.
The HTC One GPE 4.4.2 rollout is in progress, so it's definitely coming to non-Nexus phones.
imnuts said:
There is a reason that Google, manufacturers and carriers are making devices more and more secure. There is demand for it. People don't want insecure devices that someone can randomly access. Or, the want a secure phone that is good for both personal and business use.
Click to expand...
Click to collapse
To add to that, Google also has an obligation to fix root exploits (and they are exploits on locked devices; Nexus devices will always be developer devices at heart) now that they offer TV Shows and Movies in the Play Store. Some app developers (game developers usually) also had to implement nasty DRM because of pirating, which sucks because a lot of games have to "check-in" to verify the license; so, if you don't have internet at the time of check-in, you don't get to play. The more Google can control on MAINSTREAM devices, the better for their long term contracts with studios (music, movies, television) and publishers (magazines, books).
I used to NEED root, but the Moto X actually changed my mind about that.
Steve-x said:
It would be much more ideal for Motorola to have adopted the Apple model where they release a new build and don't really care much what the carrier thinks.
Click to expand...
Click to collapse
No, it wouldn't have because no other mobile OEM in the world has the kind of sway with carriers that Apple has. Apple blew open the mobile industry. Don't forget that. As much as I love android, those are the facts. Sure, I'd love for that to change sooner rather than later. You can see small battles over this happening all the time. N7 2013 has the chips for VZW LTE bands. VZW suddenly decided not to activate N7s on their network. A customer would essentially have to nag and harass VZW to get it activated. Or, you could take an already activated LTE VZW sim and just pop it in.
There are many battles being waged that you may not be aware of. It's unlikely someone will win the war soon. But join the battle by voting with your wallet.
kj2112 said:
Kit kat blows. That's my scientific analysis. Doesn't matter what device section you go to.... You will read about a lot of bugs. They "almost" squashed flash. It locks some brands boot loaders... From what I recall. They are trying to stop root. They are trying to stop 3rd party battery analysis apps.... Etc... Etc. Basically they seem to be trying to squash development.... Oh... Unless you buy a special developer model of a brand. Lol
Anyway.... My point is... 4.4 is awful. Let's hope they do a better job with 5.0. And they stop leaning toward the apple philosophy of not letting people "play" with their phones.
Every device section I follow has threads about kit kat... And when will they get it. Then when they do, theirs tonnes of negative threads about it.
4.2.2.....the last best version. At this point.
Sent from my Moto X cell phone telephone...
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
I'll add.... The carriers play a big part in these shenanigans I'm sure.
Sent from my Moto X cell phone telephone...
Click to expand...
Click to collapse
This is simply not true. Following the history of previous Android release, the .0 release always came with a lot of small bugs. Otherwise, there won't be any subsequent point releases. For example, 4.2 was released on 11/13/2012, just 14 days later, there was a 4.2.1 release.
rockingondrums said:
No, it wouldn't have because no other mobile OEM in the world has the kind of sway with carriers that Apple has. Apple blew open the mobile industry. Don't forget that. As much as I love android, those are the facts. Sure, I'd love for that to change sooner rather than later. You can see small battles over this happening all the time. N7 2013 has the chips for VZW LTE bands. VZW suddenly decided not to activate N7s on their network. A customer would essentially have to nag and harass VZW to get it activated. Or, you could take an already activated LTE VZW sim and just pop it in.
There are many battles being waged that you may not be aware of. It's unlikely someone will win the war soon. But join the battle by voting with your wallet.
Click to expand...
Click to collapse
I never said it was realistic, but I would prefer it if it were possible. My carrier doesn't even sell the Moto X, I had to buy one from another carrier and unlock it. No developer edition or motomaker in Canada either.
We certainly don't want to turn this thread towards apple but I'm pleased to say I am 100% apple free and also 100% cellphone contract free.
Steve-x said:
... I'm pleased to say I am 100% apple free and also 100% cellphone contract free.
Click to expand...
Click to collapse
Nice! I'm working on it: I suspended my VZW accounts, trying out tmo prepaid. I can't lie though, I'm very interested in seeing the effects of the bandwidth improvements vz made in my area. Another local xda user posted a speedtest screen that was 3x the performance of vz at it's peak. Maybe I'll borrow a sim from a friend...
Steve-x said:
I never said it was realistic, but I would prefer it if it were possible. My carrier doesn't even sell the Moto X, I had to buy one from another carrier and unlock it. No developer edition or motomaker in Canada either.
We certainly don't want to turn this thread towards apple but I'm pleased to say I am 100% apple free and also 100% cellphone contract free.
Click to expand...
Click to collapse
That's exactly what I did. Wanted to replace my s2...and buy a phone outright and say goodbye to contacts. I'm on telus. Did a tonne of reading, reviews and articles and XDA of course. Was between the G2, HTC one and the moto x. Decided on the X. And couldn't be happier.
For the Rogers version, unlocked sim, then boot loader... And rooted. The phone blows me away.
Sent from my Moto X cell phone telephone...
Jason.DROID said:
I used to NEED root, but the Moto X actually changed my mind about that.
Click to expand...
Click to collapse
Quoted for truth.
It'd mind blowing to me... I have no interest in rooting. For the first time... Ever.
Sent from my MotoX, using TapaTypo
HTC one Google play edition just got 4.4.2. http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
Sent from my XT1058 using XDA Premium 4 mobile app
This is just stupid:
kj2112 said:
Kit kat blows. That's my scientific analysis. Doesn't matter what device section you go to.... You will read about a lot of bugs.
Click to expand...
Click to collapse
You read about a lot of bugs everywhere.
They "almost" squashed flash.
Click to expand...
Click to collapse
Gosh, imagine that, an incompatible and unsupported app doesn't work. Bad Google, bad! You should be designing your OS to work with random unsupported apps that are no longer in development!
It locks some brands boot loaders... From what I recall.
Click to expand...
Click to collapse
You recall wrong.
They are trying to stop root.
Click to expand...
Click to collapse
You know that rooting on non-dev phones is executing a security exploit, right? That it's a vulnerability in the phone? That leaving it open would actually be the worst thing to do?
Basically they seem to be trying to squash development.... Oh... Unless you buy a special developer model of a brand. Lol
Click to expand...
Click to collapse
Everything about your "scientific analysis" is wrong. Go back to the drawing board.