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
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
It seems to me that this phone has reached death. All the forums seemed to have died (here,droidhive,rootzwiki,android-den(which hasn't really taken off) and where ever else) and quite frankly I'm disappointed. There really hasn't been any steps forward in ICS since I don't even know when (hw codecs/bluetooth/whatever else). Unfortunately I'm still 9 months away from upgrading.
I don't mean to sound like I'm complaining because I really do appreciate all of the dev work thus far(Hashcode, sparkyman, and others are the shiz), but its like we've hit a brick wall. ICS isn't complete and won't be and gingerbread doesn't seem good enough. I am grateful of everyones work. I just wish more Could be done.
Sent from my XT862 using xda app-developers app
This was my first android phone and obviously a mistake. Not that I should have gotten an iprison(I am anti I everything). I hope progress can be made. At this point though I'm sure Motorola Was and Is a mistake and I should have known better previously owning a Q9C.
Sent from my XT862 using xda app-developers app
This should be in general
Sent from my XT860 using xda premium
Endoroid said:
This should be in general
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
why? It's about the development - the phone itself isnt dead.
But I agree. I was hoping to use this phone for 2 years (using 0.5 year now). I thought that eventually, we'd get ICS like we deserve. Guess not . I'm not sure how fast/supported this phone will be using gingerbread in 1.5 year
and except Droid 4 and RAZR MAXX..what other options we've got?!
galaxy no way (too big and overrated), and HTCs are all the same: big and no qwerty. nothing to get out of the crowd...like RAZR MAXX.
i used to be a fan of HTC, since S710 days..but now i'm bored by their lack of originality. no qwerty and no good processors for the small ones (<4" display).
not really dead everyone just faced the fact that ics will not happen for the d3 and blame the lack of ram for it..although we have proven that the d3 does and can handle ics and it does improve it no dev will continue to develop it due to the locked bootloader and the work involved to write all new kernals and bypasses fir it..there are 2 great gb roms in development..team haters (my fav) and mavrom{my 2nd fav}..both development crews hang out on droidforums stop by say hi and give their roms a whirl
Because its not development, its venting about our forgotten phone. And while I feel the same as you, its still not development
Sent from my XT860 using xda premium
I noticed the same thing but dont really mind.
Im on a ATT contract for another year and 4 months or so.
Ive always wanted a droid and got the droid 3 because it works on att. It has to be the best sliding keyboard phone out their, and beats using any virtual keyboard IMO.
Even if development isnt strong, we have got it better then a lot of other phones. We have stable gingerbread roms and we can overclock it.
The Droid 3 is still a good phone and i know il be getting a good year of use out of it. .. hopefully then keyboard phones come back to life...
But i never used to post really on these forums but seeing they are kind of dead, i decided to become as active as i can to help around.
Is the droid three dead? Yes, in a way. The phone's bootloader is locked. This is the ONLY thing that is stopping any major developments on the Droid 3. If Moto, or google at this point, decided to unlock the phone... We would have Ice Cream sandwich 100% working (provided that they released the source code as well), and we would be eagerly looking forward to Jelly Bean. I often go on the Google+ Google account and harass them, I know I won't win but I am always hoping for a miracle.
As it stands now, there is a large chance that I will leave Verizon when my contract is up. Their handling of this phone as well as their pocketbooks has left a bad taste in my mouth. After 6/28/2012 (my birthday of all things), any phone being upgraded via contract will LOOSE their UNLIMITED data. You will have to purchase phones off contract to be able to keep your unlimited plan (It's only like $400 for a good android phone). Not only that, you will be charged a $30 fee just to upgrade.
So in conclusion:
Our phone is on life support. We are getting by with such developers as TeamHaters, Maverick, and Hashcode (who's still realasing AOKP updates for our phones), who are doing an excellent job keeping our phones working the best they can with what they have. Until there is a cure for our Bootloader issue... Our phone is stuck in intensive care, and Patch Adams is their to annoy the hell out of it.
Does anyone think googles new PDK will help our device? its supposed to allow low level api for easier porting of android to hardware. Think this could bring around any fixes? Ofcourse the bootloader will be locked but it mite make the making of kernels not take 6-8 months as hash said and help him out.
Sent from my DROID3 using Tapatalk 2
jesusishere said:
This is the ONLY thing that is stopping any major developments on the Droid 3. If Moto, or google at this point, decided to unlock the phone... We would have Ice Cream sandwich 100% working (provided that they released the source code as well), and we would be eagerly looking forward to Jelly Bean.
Click to expand...
Click to collapse
*sigh* I hate to be the one that has to come in and burst everyone's bubble every time someone makes this argument, but the problem is not the locked bootloader. If the bootloader was unlocked, we'd be in the same exact position. Hashcode has stated this several times. We'd still be without hardware codecs, we'd still be having Bluetooth issues, we'd still have all the same issues because they're all a matter of hardware limitations or lack of documentation on certain parts of the proprietary hardware.
Pokelover980 said:
*sigh* I hate to be the one that has to come in and burst everyone's bubble every time someone makes this argument, but the problem is not the locked bootloader. If the bootloader was unlocked, we'd be in the same exact position. Hashcode has stated this several times. We'd still be without hardware codecs, we'd still be having Bluetooth issues, we'd still have all the same issues because they're all a matter of hardware limitations or lack of documentation on certain parts of the proprietary hardware.
Click to expand...
Click to collapse
It's the combination between the bootloader and the source code
Sent from my XT862 using xda premium
jesusishere said:
It's the combination between the bootloader and the source code
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
It's more of a "TI doesn't support hardware codecs for devices >1GB data". TI doesn't release source code for those binaries and isn't obliged to, so that's not really an argument that should be made. It's simply that our phone was cursed from release.
EDIT: And as of now I can no longer say "our phone" as I jumped ship to the Razr... goodbye, Droid 3 community, you will be missed...
When Ics gets released this year for droid it is getting better
Sent from my DROID3 using XDA
Nope, it's not, because ICS isn't going to be released to D3. This is it, for better or worse.
Rocking with my M3 and XDA app
AragornPE said:
Nope, it's not, because ICS isn't going to be released to D3. This is it, for better or worse.
Rocking with my M3 and XDA app
Click to expand...
Click to collapse
who cares. I had ICS on a device before and its not that different besides a different interface .. after using ICS i prefer gingerbread's layout..
Juicy555 said:
who cares. I had ICS on a device before and its not that different besides a different interface .. after using ICS i prefer gingerbread's layout..
Click to expand...
Click to collapse
ICS is majorly different from previous releases under the hood. It uses a different kernel; things have been made more efficient; the APIs have been updated to allow for more possibilities for app developers; certain parts of how the system overall operates have undergone drastic resigns; etc.. All of this came at the price of needing better hardware to incorporate new features, but I say it was well worth it and is a very large difference even without the interface changes.
Pokelover980 said:
*sigh* I hate to be the one that has to come in and burst everyone's bubble every time someone makes this argument, but the problem is not the locked bootloader. If the bootloader was unlocked, we'd be in the same exact position. Hashcode has stated this several times. We'd still be without hardware codecs, we'd still be having Bluetooth issues, we'd still have all the same issues because they're all a matter of hardware limitations or lack of documentation on certain parts of the proprietary hardware.
Click to expand...
Click to collapse
but anyway hashcode would be able to trial and error approach without deeming the device unusable (loading kernels, and modules and stuff)
it would certainly help to have an unlocked bootloader.
but without source of course it would be time consuming and without knowing when it would have success
bogdan_wrc said:
galaxy no way (too big and overrated), and HTCs are all the same: big ...
Click to expand...
Click to collapse
This thing is a brick in my pocket compared to galaxy line and most htc phones, check out the quad core HTC One X w/beats audio or the galaxy note etc for "originality" but seems like all manufacturers are using a very similar forum factor. I agree the qwerty is nice to have but it doubles the size of the phone as well(unless maybe desire z) so you kind of have to choose.
Willis111 said:
This thing is a brick in my pocket compared to galaxy line and most htc phones, check out the quad core HTC One X w/beats audio or the galaxy note etc for "originality" but seems like all manufacturers are using a very similar forum factor. I agree the qwerty is nice to have but it doubles the size of the phone as well(unless maybe desire z) so you kind of have to choose.
Click to expand...
Click to collapse
I came from one of those phones and dont mind the difference. In fact the keyboard is one of the best features ive had on any of my smartphones. And a 4" is perfect for me, coming from a 4.5" screen.
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
Click to expand...
Click to collapse
That's a very narrow perspective. There are lots of reasons one might want to flash a ROM or kernel; the "one size fits all" mentality of other vendors such as Apple and Microsoft need not apply here. Custom ROMs open the door to different features that the OEM might not have considered or wanted to spend time on, and allow the creativity of the general public to enhance the phone in ways that are unique to them or only fits a certain niche that wouldn't be profitable for a big company to try and cater to. It certainly isn't just about "fixing issues".
Though custom ROMs certainly aren't the only feature I would look for in a phone, I might hesitate before buying a phone that little support or, even worse, a locked bootloader with no current workaround or hack for the simple reason that even if there's nothing I'm interested in today, there might be something cool that I want to try out tomorrow.
MaxCarnage said:
there might be something cool that I want to try out tomorrow.
Click to expand...
Click to collapse
If you had bought something like the Moto X one year ago, what feature made by the ROM developers on the Nexus 4 would you really want to try out?
I've been debating this myself. I have a Nexus 5 now that I'm testing with TMO prepaid for a month. So far, the phone is really nice and as you said, the level of development is astounding. BUT, I have to leave VZW in order to keep the phone. That's very hard to do when I get a hefty discount on the service and still have unlimited data. I can get LTE pretty much everywhere I go. With TMO, I'm lucky to get Edge data in some places or even a signal at all inside buildings.
I love the look and feel of the X. It's is a great piece of hardware and with the Dev edition, I could stay on VZW. I also like the fact that it runs basically stock Android along with additions that are actually useful and well done. The dev community is very limited though and will most likely stay that way. Moto was quick to get the 4.4 update out but it remains to be seen if that pace will continue. You would hope so but nothing is guaranteed. The X2 may be out next year putting the update schedule for the current model on the back burner.
I had the original Nexus One and the Galaxy Nexus. I've always been a diehard AOSP guy. Every phone I've owned in between has always been on a custom AOSP based ROM in order to get close to that Nexus experience. I'm attracted to custom ROMs not because they fix bugs, but because they allow me to always stay on a current version of Android (no waiting for carrier updates) and add some nice features to the basic AOSP design. Custom kernels can also improve overall performance and battery life even if you decide to stay stock otherwise. The Nexus line will always have the edge in this regard.
I wanted to be blown away with the N5 and content with TMO but I'm second guessing my decision each day.....
darkgoon3r96 said:
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Click to expand...
Click to collapse
I am running the N5 stock and have no reason to root or flash a custom Rom. Never thought I would say that about my phone but I am actually content with the N5 the way it is. There are some cool features that devs add in but then you get sucked into this never ending flashing frenzy which I have been in for years.
It is good to actually enjoy the phone now and keep the software on it for more then a few days. lol
Anyway, the screen alone on the N5 is enough for what I consider a big step up from the Moto X. I have friends with Moto X's which I actually recommended to them since they are on Verizon and it was being offered for free on contract. I do think it is a great phone with some great features. Not enough there to sway my decision to get one over a N5 though.
I do applaud Motorola for their unbelievable quick update and I bet we start to see some other maunfacturers start stepping up their game as well. We have seen this recently with HTC also.
The question to ask yourself is what is important to you. Another good thing with the Moto X is it generally stocks with the stock Android feel so it almost resembles Nexus software.
Bottom line, when I turn on my N5 after playing with the Moto X, the Moto X does not in any way make me want to buy one for myself.
---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------
fallingd0wn said:
I've been debating this myself. I have a Nexus 5 now that I'm testing with TMO prepaid for a month. So far, the phone is really nice and as you said, the level of development is astounding. BUT, I have to leave VZW in order to keep the phone. That's very hard to do when I get a hefty discount on the service and still have unlimited data. I can get LTE pretty much everywhere I go. With TMO, I'm lucky to get Edge data in some places or even a signal at all inside buildings.
I love the look and feel of the X. It's is a great piece of hardware and with the Dev edition, I could stay on VZW. I also like the fact that it runs basically stock Android along with additions that are actually useful and well done. The dev community is very limited though and will most likely stay that way. Moto was quick to get the 4.4 update out but it remains to be seen if that pace will continue. You would hope so but nothing is guaranteed. The X2 may be out next year putting the update schedule for the current model on the back burner.
I had the original Nexus One and the Galaxy Nexus. I've always been a diehard AOSP guy. Every phone I've owned in between has always been on a custom AOSP based ROM in order to get close to that Nexus experience. I'm attracted to custom ROMs not because they fix bugs, but because they allow me to always stay on a current version of Android (no waiting for carrier updates) and add some nice features to the basic AOSP design. Custom kernels can also improve overall performance and battery life even if you decide to stay stock otherwise. The Nexus line will always have the edge in this regard.
I wanted to be blown away with the N5 and content with TMO but I'm second guessing my decision each day.....
Click to expand...
Click to collapse
Why not go to a MVNO that uses AT&T towers? Would still be much chepaer then Verizon and they offer much better coverage then T-Mo.
[email protected] said:
I am running the N5 stock and have no reason to root or flash a custom Rom. Never thought I would say that about my phone but I am actually content with the N5 the way it is. There are some cool features that devs add in but then you get sucked into this never ending flashing frenzy which I have been in for years.
Click to expand...
Click to collapse
Don't you want to improve the Audio and the battery life by trying out the kernels and the mods made here?
Anyway, the screen alone on the N5 is enough for what I consider a big step up from the Moto X.
Click to expand...
Click to collapse
I assume you mean resolution? I was under the impression that 1080p and 720p are not that different under daily usage?
It all comes down to your habits. I love flashing new ROM's, I sometimes try multiple ROM's per week. So for me, development means a lot. It's why I switched from the S4 to the N5. The S4 just received 4.3 and was locked down by Knox. Plus, with the N5 being an unlocked phone, you can flash any ROM on any carrier, so you won't ever have to drool over another carrier's ROM.
mjs2011 said:
It all comes down to your habits. I love flashing new ROM's, I sometimes try multiple ROM's per week. So for me, development means a lot. It's why I switched from the S4 to the N5. The S4 just received 4.3 and was locked down by Knox. Plus, with the N5 being an unlocked phone, you can flash any ROM on any carrier, so you won't ever have to drool over another carrier's ROM.
Click to expand...
Click to collapse
I also flash a ton of ROMs every week and also used to enjoy it, but I am getting tired of it now... I want to live life more than flash ROMs (if that makes sense)
darkgoon3r96 said:
If you had bought something like the Moto X one year ago, what feature made by the ROM developers on the Nexus 4 would you really want to try out?
Click to expand...
Click to collapse
Anything and everything. The top reason I don't even consider not getting a Nexus device anymore is the development scene. Look, you're viewing the huge development community on the Nexus line as people who are "fixing" a "broken" stock image. That's not really true. The stock image is perfectly fine. The developers are merely making things that they deem better than how stock handled it. For instance, a developer might think that the on-screen buttons are too large on stock, taking up way too much screen real-estate. They would then develop a way to remove it, but still be able to navigate. They might make something like PIE controls. Now, I may agree that the buttons really are too large, but I like the nav bar. So I might just resize it, instead of working around it.
I guess the point I'm making is, all of those modifications you see to "improve" the stock image are there to "improve" it, but what counts as an "improvement" is completely subjective. There are different people in the world with vastly differentiating opinions about things, so they will make something to improve something else as they see fit. The development sections here on XDA are merely huge repositories of any modification that anyone who was willing to make, made. Looking at them all as collectively-required flashable improvements isn't how it should be viewed. That's the beauty of having a large development community. You can pick and choose, depending on your personal opinions, which modifications are improvements and flash them. Another way to think of it is cookie-cutter vs modular. Do you want a phone that appeals the masses,;a one-size fits all, or a phone that is completely customizable?
darkgoon3r96 said:
Don't you want to improve the Audio and the battery life by trying out the kernels and the mods made here?
Click to expand...
Click to collapse
Battery life has been great on stock for me. Absolutley no complaints here. I have ran so many custom kernels on prior phones and never saw a large boost in battery from them. Lots of times it would actually be worse.
The speaker volume can definitley use a boost and the camera needs some fixing. I know there is some dev work for both of these issues but I am going to hang a little and see if Google fixes it. If not, I might think about rooting solely for those 2 things. If Google fixes it, absolutley no reason for me to root this time around.
Anyway, as a prior flashoholic there is no better phone then a Nexus for people who like to flash Roms and like every feature on the sun. No other phones custom Roms work as good as they do on a Nexus.
Development is like the first determining factor for me when buying phones.
darkgoon3r96 said:
I assume you mean resolution? I was under the impression that 1080p and 720p are not that different under daily usage?
Click to expand...
Click to collapse
Screen size. A 5" screen starts the sweet spot for a device that uses on-screen buttons. I always felt shorted on prior 4.7" screens with on screen buttons. Like there wasn't enough viewing real estate. Sure you can remove the on-screen buttons but then you would need something that always to longer to activate then the actual buttons being present.
I also think the quality and colors of the N5 screen are just gorgous.
darkgoon3r96 said:
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Click to expand...
Click to collapse
I just got rid of my moto x for the N5 for this very reason. The moto x is a great device and probably the best carrier controlled device to date.
That being said, it drove me nuts to be locked down with a locked bootloader and no development. Knowing the n5 is open and has all the Dev support means I have control over MY phone, not AT&T and not Motorola.
After dealing with the locked down s4, I promised myself I would never get another device without an unlockable bootloader. I caved when the moto x came out and as I said it's one amazing device but at the end of the day, I'll be sticking with nexus devices from here on out.
To me it's not worth giving up that freedom but for you it may not matter.
Sent from my Nexus 5
Development totally cones into it for me. One of the biggest considerations.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
brooksyx said:
Development is like the first determining factor for me when buying phones.
Click to expand...
Click to collapse
rootSU said:
Development totally cones into it for me. One of the biggest considerations.
Click to expand...
Click to collapse
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
capathy21 said:
That being said, it drove me nuts to be locked down with a locked bootloader and no development. Knowing the n5 is open and has all the Dev support means I have control over MY phone, not AT&T and not Motorola.
Sent from my Nexus 5
Click to expand...
Click to collapse
If I do get the Moto X, then I will get the Developer Unlocked model.
brooksyx said:
Development is like the first determining factor for me when buying phones.
Click to expand...
Click to collapse
Same here, after my first Nexus phone, I could never go back to a phone that didn't have a strong dev. community behind it. For me; tablets and phones are as much about the journey of playing with ROM/kernel/mods as they are a communication device.
darkgoon3r96 said:
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
If I do get the Moto X, then I will get the Developer Unlocked model.
Click to expand...
Click to collapse
No stock rom mod can touch the stability and features of cyanogenmod. It is the only way to do anroid. In fact I prefer iOS over stock android. But CM is awesome.
brooksyx said:
No stock rom mod can touch the stability and features of cyanogenmod. It is the only way to do anroid. In fact I prefer iOS over stock android. But CM is awesome.
Click to expand...
Click to collapse
To be honest, CM's future plans SERIOUSLY excite me.. Like that recent conversation feature
CyanogenMod, AOKP, AOSPA support, along with great kernel devs. The Nexus 5 is essentially guaranteed support for these things, and these are things I like.
darkgoon3r96 said:
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
Click to expand...
Click to collapse
Who said anything about roms or features? Its all about kernels.
But if you look at ROMS like PAC, you'll see what features true roms can offer over xposed
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit