Dead - Motorola Droid 3

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.

Related

Should I Get a Droid?

Hi guys(and girls), in 2011, should I get an original Droid? If I bought one it would be my first android phone, i've flashed a custom rom on a windows phone before but i don't know how to root yet, but would it be good for me to get a Droid now? With the newer phones that are out?
Honestly just get a newer and better phone for free. There are many free phones out there that are better hardware and software wise like the inspire 4g(which I have)
I'll pass on a contract.
Juanito216 said:
Hi guys(and girls), in 2011, should I get an original Droid? If I bought one it would be my first android phone, i've flashed a custom rom on a windows phone before but i don't know how to root yet, but would it be good for me to get a Droid now? With the newer phones that are out?
Click to expand...
Click to collapse
yes! I have one aswell and I can show you or message you on how to
and how to flash roms just like i did
no.
i think a nexus is way better supportet.
google is developing right on the nexus phones. i would by one of these. and not a doird again.
Thanks for the replies, I might wait to get something more advanced. Good things come to those who wait.
GodT2 said:
no.
i think a nexus is way better supportet.
google is developing right on the nexus phones. i would by one of these. and not a doird again.
Click to expand...
Click to collapse
That thing is freaking expensive
Sent from my Droid using XDA Premium App
If I was buying my first Android right now (I bought the Milestone in September of '10) I might look at the Nexus one. I think Amazon has it for around $280, new. The screen size is the same but I think it's a little faster and is obviously better supported.
Consider buying a device with more RAM than droid.
Also you should answer a question, whether you are confortable with touchscreen virtual keyboard or not - I'm not, so I took Milestone
I would consider a keyboardless device ie EVO/HD2/Thunderbolt(big screens), my sister had a Cliq XT at one time and i tried texting on that, my thumbs were kind of big for the buttons?
Well guys, I got a Droid X today.
I've had my Droid for 2 years now and it's been a great device. The development community has been great and there are still a lot of good ROM a currently being developed and supported for it.
While it might not have the most memory, most apps can be pushed to SD. The processor overclocks to 1g (and usually even higher), so it can still match the quadrant scores of many newer phones.
If the price is right, and you want to experiment with rooting and flashing ROMs, not many other phones have as much community support and it's next to impossible to brick a Droid.
I have my Droid (Milestone, actually) for more than a year now and can't say anything bad about the device itself. When it comes down to Motorola, we're talking about a different sport
Motorola's update policy had me waiting for FroYo for months and when it came out, it was a beta-versions, months old that gave a lot of people WLAN-problems. Also the use of the bootloader is a real pain.
If you're willing to install a custom ROM, you're fine, there are good ones out there (I'm using FroyoMOD), but due to the company's update (and bootloader) policy, my next device won't be a Motorola.

Android 4.0 Source

Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
I was wondering the same thing. if this is possible I might not even update it to GB cause it wouldnt make sense. Hopefully its possible.
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
thank your for you input on this matter. Can you please tell me which Galaxy S II is better i777 or the i727 because I am thinking of returning my LG Thrill 4G for the Skyrocket?
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
kleeman7 said:
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
That's the only difference in data speed. That's also the only area the i727 is better. In EVERY other way the i777 is better.
They have the same screen resolution, but because the 727 screen is bigger, so the pixel density is lower, most people won't notice, but its worth mentioning.
The processor in the 727 is a qualcomm chip oc'd to 1.5 GHz, vs a Exynos chip at 1.2 GHz. People say the qualcomm chip is inferior, and choppy. Most people won't notice it, but it is there. The exynos can be oc'd higher than the qualcomm chip. The qualcomm chip is the reason it won't get i777 or i9100 ROM ports. With the i777 and i9100 running the same chip you can port any i9100 ROM really easy.
I don't know specifics on GPU, but its widely accepted the i777 has better graphics and 3D processing.
The 777 is thinner and lighter.
They both have disabled nfc on board. Att to possibly unlock at a later time, maybe at ICS rollout.
If you have LTE coverage you need to think about the choice, if you don't have LTE, there is absolutely no reason to get the 727. I talked a little about other differences in your other thread.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
Did you check the TI site and read the 4460 documentation? The processors are almost identical. The 4460 is just a little more capable. Its still in the OMAP4 family with the exact same architecture. We'll have the LG gingerbread drivers shortly as well as the galaxy nexus ICS drivers which will get us started there. Kernel shouldn't be too big of an issue as again, same architecture on CPU, same exact gpu. Yea its gonna take a lot of time to get everything working but we don't need LG to do it. GB was more of a shot in the dark for this phone than ICS will be. Zero omap4 devices released with GB but it still got ported to a couple Motorola devices. ICS released for two devices, both omap4.
Sent from my LG-P925 using Tapatalk
I said this about GB too. I hope I'm wrong for all of your sake's. When people were saying GB was around the corner (in September), and I said December, people said I was being too cynical. Well ... here we are, December is right around the corner, and the GB port is not flashable in CWM, nor is it complete. I over-cynicized a little, but not much.
I think it's all great on paper, just like building a AOSP GB build for the phone looked simple, did that ever actually get off the ground?
As I look in the past, I use that to forecast the future. My guess is that there is no where near a functional daily use ROM for the Thrill until a ICS build comes from LG (I would guess no sooner than July). If the the Nexus S and Captivate running the exact same hardware (CPU/GPU plus lots of others) both made from the same company, cannot share ROMs with lots of dev support, I just find it hard to believe that a phone with a similar chip, packaged with other chips (WiFi, BT, USB, Power, comination unknown) by another OEM is not going to provide useful drivers for the small dev community here. Again, I would love to be wrong, but ...
To be honest I think the Thrill is more Thrilling (rim-shot) because it's an underdog, and it feels like a start-up, ground-floor opportunity to build and jury rig everything and frankenstein it together. I think it would be fun, and I would have loved to have been involved had I stayed. But, I moved on, as many others have. I can't wait for months for something like this when I will only have that phone for a year. I don't hang on to old tech, I sold my Captivate and it paid for my Galaxy S II, talk about the circle of life.
The Thrill is definately an underrated phone, but it's also not the highest end phone. As I said before, as it stands it's definately the best AT&T phone for less than $100, it's the king of the mid-range offerings. Unless you can get the i777 for $50 or less, like many places have advertised for Black Friday.
I wish everyone the best of luck with the Thrill, but the reality train is leaving the station, and I feel my welcome may just be wearing thin here.
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Demonface said:
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Click to expand...
Click to collapse
it'll be about 3-8 months before other devices will recieve ics. samsung has the same problem. they still haven't updated the charge, fascinate, captivate and infuse.
tampaboy1984 said:
Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Trekfan422991 said:
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Click to expand...
Click to collapse
This is after all the reason why I got this phone cuz of the chipset and the fact that ICS is designed for it
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Thats very good news , Hopefully it gets released soon. Instead of using GB I would go straight to ICS when its released. Does anyone have the link to the video because I cant seem to find it.
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
seriously i know your trying to help us keep a grip on our excitement.. but its starting to get annoying seeing your comments pop up here all the time after you switched weeks ago.. and they are all how the thrill has potential but im so happy with my choice... like we cant even get our hopes up because your too afraid of our dreams getting dashed to pieces... we should all follow your example. i know thats not what you mean but it feels that way...
like many others i choose this phone based off the hardware specs... so i will be sticking it out for a few months at least if not for a few years.
we know the decision you made to switch and that you have support for the thrill and knew it to be a good device.. there is no rule about posting in forums for phones you dont have.. but please... please ease back a bit on clarifying all the realities for us...
there is nothing wrong in wishing.. we had no development for ages, it feels like, and now we have some things to look forward too, thats all!
so give us our hopes please... *tears up* its all we have!
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Wait wait wait...
You mean AT&T doesn't give super fast firmware updates to their phones?!
Here's what I will say about this phone so far...
I like it. It's treated me better than any Samsung phone I've had. It does everything I need it to.
I can't really remember ever saying "I wish this phone could..." that I wouldn't say about any other phone.
I hear people talk about how fast this phone is and that phone is and how fast the GSII compared to the Thrill. But how much faster is faster? The web browser pops up a second faster? A file is downloaded 10 seconds faster? I don't really think a lot of that is that big of a deal. It almost reminds me of the Crackberry forums when they were talking about not going to Android because the email isn't push (which isn't true) and so you got your emails a whole 30 seconds later. I mean, c'mon, how many of us are in a position where if we don't get that email 30 seconds faster our entire corporation loses billions?
I think it'd be cool to get 2.3 or above right now because there are a couple of games I'd like to play that are on 2.3 or above. But considering I have 25 games already installed and over 1/2 of those I ahven't touched, it's okay.
I've had a few Samsung phones and everyone of them I had had a lot of issues. I went through 8 Captivates. Now I did have to return one Thrill and exchange it but every Samsung phone I've had, I've had to get replaced at least twice. I keep saying I want a Note but then think about how bad I've had it with Samsung phones.
Phone technology is crazy. The thrill came, then the GSII, then the GSII skyrocket and the HTC Vivid, then there are three new Galaxy devices coming to AT&T in the next 2-3 months, and whatever awesome quad core devices, and then pretty soon we'll have the hologram phones in which you tell the phone to contact someone and they pop out of the phone like in Star Wars.
Honestly, I think I need a couple more pairs of shoes more than I need a newer phone.
CallMeAria said:
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I won't get drawn into a pissing contest regarding dev support of the Optimus 3D vs the Galaxy S II (i9100).
But, I will respond.
I'm sorry I over estimated and called that port half functional, you are right: its not a half functional port.
The build status of CM9 for the phone that half the Cyanogen team was given months ago is unknown to me. I made no claims on timelines, just forecasts based on the past and opinion.
There is indeed a very similar ICS ROM built for the i9100 (and by extension the i777) from the source that just dropped, but I cannot comment as to whether or not it was put together by a "legit cm dev."
I am not a developer, no. I am just an observer, an observer that tends to be realistic with expectations, and generally accurate.
I don't accuse the community here of being ignorant or naive. I can see that some people here do have realistic expectations.
I too was once an Aria, Captivate and Thrill fanboy. Today I am a GS II fanboy. I picked my team, as you have too. I don't think there is anyone on xda that isn't passionate about their phone.
I will not dignify further condescending comments from you with a response. This is the last time you will see me on the Thrill forums. Do not take my future lack of response as an admission of your perceived superiority. And do not take my comments to imply I believe I am better than you. I know you built a ROM, and were the first to share how to port O3D ROMs. Just because I never used your contributions I will not be so arrogant to say they don't exist.
And with that, I will be on my way. Again, best of luck to every one with a Thrill.
Sent from my Galaxy S II (i777)
Just checked out the optimus 3d thread about ICS and it seems that Ricardo is getting a lot of progress done and it seems like its getting done quickly. So hopefully it gets released before Christmas
. BTW I know that's still a long wait still but it would all be worth it.

And sorry Droid1 owners, we’re dropping support for you.

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

What are the expectations of an official ICS update for the Bionic?

What should we expect to see? Will there be a motoblur intergration or will it be straight up ICS?
My preference would be a non molested ICS but I'm sure we'll end up with another locked steaming turd.
Sent from my DROID BIONIC using xda premium
Keep in mind that Google now owns Motorola Mobility... if we're lucky, that will mean a more pure version of AOSP on our devices.
I'm really hoping for an AOSP build of ICS for the bionic, I love the way AOSP looks for Android 4.0
Starting to have my doubts that we get ICS from moto.... Have a feeling our developers are gonna make it work 100% for our Bionic before moto hands it to us. If moto even does hand it to us.. For the Razr Maxx to be coming out pretty soon and not even have ICS kindof makes you wonder wth moto is even doing in motoworld.
The Xoom- a Google Experience device with reference firmware- JUST today got Android 4.0. The Nexus 2 still doesn't have it officially. These things take time. It'll be April or May before we start seeing phones that are actually being released with ICS.
MillionManMosh said:
It'll be April or May before we start seeing phones that are actually being released with ICS.
Click to expand...
Click to collapse
Or about a month ago when the Galaxy Nexus was released...
It will take a little time for us to see it, I think. Hopefully not too long. I'm pretty sure they have officially stated that they will be releasing it for the Bionic, so I would hope they don't go back on a public announcement like that.
But, it looks like we've got devs that might get a working option for us before we get something official.
The Bionic will definitely get ICS. The phone just came out in September. Moto is pretty good with updates (usually). The Google purchase has NOT gone through yet. Will not go through til Feb supposedly.
My predictions:
-We will get it in March
-It will look pretty similar to blur as it looks now
-We will not notice much difference
-On paper second core of processor is suppose to be more optimized.
--
we are lucky that the galaxy nexus as well as the newer moto phones (Razr, Razr MAXX) all use similar hardware so getting the drivers and radios up shouldnt be to difficult.
that being said its moto's skin that'll take time so we'll see. It would only be fair that they would upgrade the Bionic "fist" but who knows what will happen. I just pray ever day for an unlocked bootloader.
I wish they would throw their skin on in a similar fashion as using go launcher with beautiful Widgets so the process would be much faster. It just seems like they're making it more difficult on themselves.
Sent from my DROID BIONIC using XDA App
easting said:
My preference would be a non molested ICS but I'm sure we'll end up with another locked steaming turd.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Then get a different, unlocked phone. No one wants to hear whining and not everyone cares about flashing a million roms or kernels every week.
Back on topic, I fully expect the update will include most of Moto's current modifications with maybe a few less changes from stock ICS. I'm hoping they will include the same kernel as the Razr's so we can easily overclock to 1.2 GHz like they did with the 2.2 update on the original Droid.
I ditched the Bionic for a Rezound but the Bionic definitely felt like a quick phone. I just got an ICS rom for my Rezound, it was smoking fast on GB and is much smoother with ICS. The Bionic should be very fast with ICS. Maybe they can help the camera out with ICS aswell.
I ditched as well. Sorry, the point of android is openness and MOTO bit the big one after they lied.
davwman said:
I ditched as well. Sorry, the point of android is openness and MOTO bit the big one after they lied.
Click to expand...
Click to collapse
While that is the point of android, the cell providers lost the memo. It will never be as open as it should be with their greedy little paws on it (illegal tethering, come on, we've been tethering since before they even offered their crap hotspot service) .
Sent from my DROID BIONIC using XDA App
nrage23 said:
I ditched the Bionic for a Rezound but the Bionic definitely felt like a quick phone. I just got an ICS rom for my Rezound, it was smoking fast on GB and is much smoother with ICS. The Bionic should be very fast with ICS. Maybe they can help the camera out with ICS aswell.
Click to expand...
Click to collapse
I actually no longer have camera problems with the liberty rom. I know the issue that you refer to as I once had it. Click the button to take a picture then wait several seconds before it actually took the picture. So inconvenient that problem was.
I'm not exactly sure what any of these newer phones can do that the bionic can't do because app developers still have to develop for the older phones because developing for the newer phones limits your user base. If your going to develop an app, you're going to develop it for as many devices as possible. By the time we start getting apps that maximize the capabilities of our phones, there will be something much better out.
Sent from my DROID BIONIC using XDA App
smokedkill said:
I actually no longer have camera problems with the liberty rom. I know the issue that you refer to as I once had it. Click the button to take a picture then wait several seconds before it actually took the picture. So inconvenient that problem was.
I'm not exactly sure what any of these newer phones can do that the bionic can't do because app developers still have to develop for the older phones because developing for the newer phones limits your user base. If your going to develop an app, you're going to develop it for as many devices as possible. By the time we start getting apps that maximize the capabilities of our phones, there will be something much better out.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
The camera app problem on the bionic is totally Motorola's fault. They built the phone you would think they could write code for the hardware they chose. Again I think ICS will do wonders for the bionic. It felt like they rushed it out so they could finish the razr. Given that razr and the bionic are so similar, ICS should come much sooner for you guys.
sent from my Galaxy Tab 7 Plus
nrage23 said:
The camera app problem on the bionic is totally Motorola's fault. They built the phone you would think they could write code for the hardware they chose. Again I think ICS will do wonders for the bionic. It felt like they rushed it out so they could finish the razr. Given that razr and the bionic are so similar, ICS should come much sooner for you guys.
sent from my Galaxy Tab 7 Plus
Click to expand...
Click to collapse
I agree that Motorola screwed this phone up. I no longer have the camera issue with the liberty rom.
Even with all the screw ups Motorola made, I was still able to get my bionic running top notch, even without the .901 radio.
The biggest problem this phone had was after it got delayed by so much, and the hype it had, it shouldn't have had some of its initial problems. Its not like we didn't all know about this phone for 8 months before being released. Don't hype up a phone so much then fail to deliver. Even with their screw ups, I feel I have mine running as good as you can expect an android to run. I've had the thunderbolt and revolution and the bionic is far better than they were.
Sent from my DROID BIONIC using XDA App
smokedkill said:
I agree that Motorola screwed this phone up. I no longer have the camera issue with the liberty rom.
Even with all the screw ups Motorola made, I was still able to get my bionic running top notch, even without the .901 radio.
The biggest problem this phone had was after it got delayed by so much, and the hype it had, it shouldn't have had some of its initial problems. Its not like we didn't all know about this phone for 8 months before being released. Don't hype up a phone so much then fail to deliver. Even with their screw ups, I feel I have mine running as good as you can expect an android to run. I've had the thunderbolt and revolution and the bionic is far better than they were.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I hear you. The Tbolt was a dog. I am very glad I got rid of the bionic but it was much better than the Tbolt.
sent from my Galaxy Tab 7 Plus
There's nothing out there that I feel that is worth getting rid of the bionic for. The nexus has plenty compatibility issues with running some apps (majority of Samsung phones do though) and the razr is too skinney for my taste plus I feel the marginal increase in it's specs aren't worth it. I also don't like the 3 button setup on the nexus. I'm too used to having 4 and using the 4 for so long to change my way.
We have quad core coming between now and summer that will blow everything away that's out now. Dont see any sense in replacing my phone for something that is only marginally better. Every Android has its problems and the ones I have with the bionic are manageable for me.
The only thing I could see me trading my bionic is if there is a significant increase in the app development world where more processing power is necessary. But with the fragmentation of android, an app developer would be dumb to do that because as an app developer, you want your app to be compatible with as many devices as possible. I can see some games coming out that may need more processing power though. Its only a matter of time before we start seeing PlayStation 2 emulators popping up.
Sent from my DROID BIONIC using XDA App

NO ICS For Us :(

Just checked the updated Motorola page... looks like this device is stuck at android 2.3 forever.
That really sucks, it's gotta be the 512mb memory that's in the device. I knew that would possibly be an issue when I first got the phone. Maybe we can put more pressure on moto to unlock our bootloader so we can get a fully functional ICS (even if it's hacked) on our devices.
Check the link:
http://forums.motorola.com/pages/00add97d6c
PFFFFFFFFFFFFF
I just saw this as well, very disappointing. I wish they would open up development to the community on devices they no longer plan on upgrading/supporting. I know it will never happen...but I can dream
Droid4 and Bionic get the ICS
maybe Hashcode or some one try to do what he can, and pull out from this phones something for us and for CM9 on D3
niko99 said:
Droid4 and Bionic get the ICS
maybe Hashcode or some one try to do what he can, and pull out from this phones something for us and for CM9 on D3
Click to expand...
Click to collapse
Just got a response back from hash regarding this on twitter:
" @danifunker @dhacker29 I have 1 more trick up my sleeve for the D3. And if that doesnt work, then ill drop back to cm7.2 or something. "
Let's hope the tweak works out... but either way I think I could live with CM 7.2, although I would REALLY love running ICS on this phone.
What ever happened to Kexec for the D3? I'll sacrifice a core for a new kernel that could even OC that one to 1.2.
I started to believe that motorola doesn't want anyone to buy motorola products.
calash said:
I just saw this as well, very disappointing. I wish they would open up development to the community on devices they no longer plan on upgrading/supporting. I know it will never happen...but I can dream
Click to expand...
Click to collapse
Sure would be nice if they would just open up phones when they started considering them legacy devices. Other than 4G which I don't particularly need anyway, the D3 is a great phone that could keep going for a long, long time just like my D1 did (I skipped the D2 and went directly from 1 to 3).
Part of the reason the D1 lasted me so long was that I could keep getting updates for it from Cyanogen. In fact I still have it. Though its no longer on the Vzw network I can test various things on it like security software, remote wipes etc over WiFi.
Verizon is probably against unlocking the D3 because they don't want to have the support issues and that's probably why we will never see it. How many people on these forums do you hear about that are constantly returning/exchanging phones that they have managed to kill through tweaking? Then its those same people who complain the loudest when the Motorola and the carriers won't unlock the phones. So, while I wish it was not so, we will probably never see them unlocked unless someone finds a way to hack them. Motorola isn't going to help and particularly VZW is not going to help.
danifunker said:
Just checked the updated Motorola page... looks like this device is stuck at android 2.3 forever.
That really sucks, it's gotta be the 512mb memory that's in the device. I knew that would possibly be an issue when I first got the phone. Maybe we can put more pressure on moto to unlock our bootloader so we can get a fully functional ICS (even if it's hacked) on our devices.
Check the link:
http://forums.motorola.com/pages/00add97d6c
Click to expand...
Click to collapse
HTC just released the HTC Desire C with a 600Mhz processor and 512MB ram. It runs Android 4.0
If they can do it with that, surely Motorola can too
ChristianPreachr said:
HTC just released the HTC Desire C with a 600Mhz processor and 512MB ram. It runs Android 4.0
If they can do it with that, surely Motorola can too
Click to expand...
Click to collapse
It's possible that the HVGA screen on that device needs far less memory - HVGA is 480x320 which is 70% less pixels to push than the qHD on the Droid 3. Also, Moto is pretty terrible at software, Blur runs a lot slower and chews up a lot more memory than a lot of its competitors.
What Moto should do is release a plain vanilla, non-blur ICS as an optional upgrade. I have to think that would take a minimal amount of time to port vanilla ICS to the Droid 3 if there is no need to get it working with Blur - just need the drivers which should be substantially similar to Droid 4.
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
ratman6161 said:
Sure would be nice if they would just open up phones when they started considering them legacy devices. Other than 4G which I don't particularly need anyway, the D3 is a great phone that could keep going for a long, long time just like my D1 did (I skipped the D2 and went directly from 1 to 3).
Part of the reason the D1 lasted me so long was that I could keep getting updates for it from Cyanogen. In fact I still have it. Though its no longer on the Vzw network I can test various things on it like security software, remote wipes etc over WiFi.
Verizon is probably against unlocking the D3 because they don't want to have the support issues and that's probably why we will never see it. How many people on these forums do you hear about that are constantly returning/exchanging phones that they have managed to kill through tweaking? Then its those same people who complain the loudest when the Motorola and the carriers won't unlock the phones. So, while I wish it was not so, we will probably never see them unlocked unless someone finds a way to hack them. Motorola isn't going to help and particularly VZW is not going to help.
Click to expand...
Click to collapse
Couldn't they just do what HTC did - online based bootloader unlock tool, which builds a list of unlocked IMEIs which are then voided of their warranty, and people calling for support will be checked against this list. Of course, the most enterprising guys with bricked phones will try to change their IMEI sticker, but that wouldn't match their Verizon account records.
This is so sad... Cant believe that Dual Core Processor phone is not eligable to receive Ice Cream Sandwich... Media shall be contacted, so they could make fun from Motorola... I'm never going to buy Motorola products again.. Ever.
Rlin5741 said:
What Moto should do is release a plain vanilla, non-blur ICS as an optional upgrade. I have to think that would take a minimal amount of time to port vanilla ICS to the Droid 3 if there is no need to get it working with Blur - just need the drivers which should be substantially similar to Droid 4.
Click to expand...
Click to collapse
Im pretty sure all we need is a compatible kernel and hashcode will take care of the rest. If Motorola could do that, it can extend the life of our phones.
Sent from my XT860 running ICS
Time to do some more Facebook trolling, I may even make an account over on the Motorola forums and do some spamming/trolling.
In July 2011 when I bought my phone there were 2 new Motorola smartphones out there the Droid 3 and Droid X2. Both had dual core processors and felt mid-high end at the time. But somehow an Android OS upgrade that was released less than 6 months after the Droid 3 was released is skipped by Motorola.
This was my first Android phone and I bought it because I wanted a keyboard and really liked the feel of a friends OG Droid. The OG was probably built better but I have still been mostly satisfied with the Droid 3 hardware wise. But I just can't see myself buying another Motorola device. I will have to see what is out there in 2013 when I upgrade, hopefully some nice QWERTY non Motorola devices.
Damn it Verizon
This is the Fourth phone that I've had from Verizon that has been abandoned before the end of it's life cycle. Although I am sure this is Motorola's fault I will curse Verizon for all time and remember to get the latest and greatest for top dollar right off the bat to ensure that I will get updates when dealing with a cell phone company or maybe get a landline and tell jerks like Verizon to stick it where the sun don't shine. The real pisser is that I am finding this out the day after I spent the money that could have been used to buy out my contract. Color me angry and frustrated.
I'm going to start reading up about custom roms for this phone I might as well since support is all but gone from this model.
Return the phone and tell them you want out. Can be done.
Sent from my DROID3 using xda premium
spunker88 said:
Time to do some more Facebook trolling, I may even make an account over on the Motorola forums and do some spamming/trolling.
In July 2011 when I bought my phone there were 2 new Motorola smartphones out there the Droid 3 and Droid X2. Both had dual core processors and felt mid-high end at the time. But somehow an Android OS upgrade that was released less than 6 months after the Droid 3 was released is skipped by Motorola.
This was my first Android phone and I bought it because I wanted a keyboard and really liked the feel of a friends OG Droid. The OG was probably built better but I have still been mostly satisfied with the Droid 3 hardware wise. But I just can't see myself buying another Motorola device. I will have to see what is out there in 2013 when I upgrade, hopefully some nice QWERTY non Motorola devices.
Click to expand...
Click to collapse
Please don't troll that forum. The mods there aren't actualy affiliated with moto like you think.
I did some of this back in the day about the d2 and learned the hard way.
Sent from my DROID3 using xda premium

Categories

Resources