The droid and palm pre have really similar insides (TI OMAP 3430, PowerVR SGX, CDMA), just wondering if anyone more intelligent than me knows if its a possibility to port the droids android builds over to the pre?
scottysurfs said:
The droid and palm pre have really similar insides (TI OMAP 3430, PowerVR SGX, CDMA), just wondering if anyone more intelligent than me knows if its a possibility to port the droids android builds over to the pre?
Click to expand...
Click to collapse
its possible but no one has tried to make one
edit nvm i lied there has been a project since july but it hasnt been successful
Related
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
This is the development forum. You want the q n a forum.
Sent from my Nexus One
mnv710 said:
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
Click to expand...
Click to collapse
*sigh*
There is a general section, you know...
mnv710 said:
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
Click to expand...
Click to collapse
The HTC magic, the 2nd ever android phone, got official Froyo. If a phone isn't getting it, its not because it's underpowered (with the exception of the G1).
B3astofthe3ast said:
The HTC magic, the 2nd ever android phone, got official Froyo. If a phone isn't getting it, its not because it's underpowered (with the exception of the G1).
Click to expand...
Click to collapse
Huh? The magic is a G1 less the keyboard. Processor is the same. And I think a rooted G1 can have 2.2.
Sent from my Nexus One using XDA App
HTCinToronto said:
Huh? The magic is a G1 less the keyboard. Processor is the same. And I think a rooted G1 can have 2.2.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The G1 is memory starved. A rooted G1 can have froyo with the proper SPL.
We will get every future Android update.
Gingerbread, Honeycomb, IceCream, Jellybean, K..., L..., Mousse, Pie, Q..., ...
I don't think there needs to be a tablet developer platform designated. Screen resolution differences are something that should be simple enough d'or developers to figure out.
The entire point of a developer platform device is to develop the core OS updates on it, so I fully expect at least another year of official updates for the N1. Especially because we haven't actually seen any faster processor released into the market yet.
The secondary point of a designated developer platform would be to support a core of standard hardware under Android. Smarter OEMs should understand that if they want to have less work to port android to their devices, and to get updates on their devices more quickly, they should try to use hardware components either common to ADP or that have Linux support.
Sure, OEMs can deviate, but anything they include that isn't either compatible with ADP hardware, or already supported in Linux will have to be supported by the company making that handset. So it is up to the consumers to say if they want devices more like the Desire, or more like the X10. Laf!
The Nexus One is the official Google Development phone. Until that changes, we shouldn't have to worry about getting the latest versions first
It is one of the advantages to being a N1 owner.
xPatriicK said:
We will get every future Android update.
Gingerbread, Honeycomb, IceCream, Jellybean, K..., L..., Mousse, Pie, Q..., ...
Click to expand...
Click to collapse
Deserts are my N1's favorite meal!
Android mean Google, then there is no point to buy any phone even if it's amazing, i am with Google devices till they close the company N1 TO N100 i am with Google i just want they put some color in this coming build i feel the stock ROM is black and white
I was wondering if anyone thinks it is possible to port the Motorola Webtop application from a phone like the Atrix or Bionic?
Here is a link to a recent thread where they have hacked it to working without a dock and just using a standard HDMI cable like the U9000 uses.
Here is a link to Motorola's site explaining Webtop.
Any thoughts?
dub24 said:
I was wondering if anyone thinks it is possible to port the Motorola Webtop application from a phone like the Atrix or Bionic?
Here is a link to a recent thread where they have hacked it to working without a dock and just using a standard HDMI cable like the U9000 uses.
Here is a link to Motorola's site explaining Webtop.
Any thoughts?
Click to expand...
Click to collapse
really liked ur question seriously if this could be possible then our phone gonna rock out all the developers as i know this phone is available in motorla also withthe name moto triumph i think it could be possible.. jst the basic diff is ... triumph is cdma and our is gsm...
hope webport support could be driven out soon
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
Hello all developers and super flashers, I recently had to depart from my most awesome phone the HTC HD2 when it could not continue ant longer. My loving wife saw that I really enjoyed flashing so she got me this Droid Bionic because the sales pitch to her was Control it and you control everything. Which brings me to this question I have not seen asked or answered. The same way that the HD2 was able to run android and wp7.5 dual boot can anyone say rather if or not this Bionic is capable of a similar task?
No, and why would you want to gimp the Bionic more than it already is?
The Droid Bionic (and every Moto device on the 4 major USA carriers ever since the Droid X) has carried a locked bootloader. This has the side effect of the kernel only being able to be modified by official Motorola updates that contain a heavily encrypted signature.
Nothing except Android can run, and doing anything else is impossible.
The TF701 has a Tegra 4 and DirectStylus is supported on Tegra 4 tablets. I was wondering if it is possible to use the palm rejection technology that it implements as I am looking to upgrade from my TF101, and was hoping to have a integrated keyboard and perhaps stylus support for school related things.
Thanks in advance.
handyguy said:
The TF701 has a Tegra 4 and DirectStylus is supported on Tegra 4 tablets. I was wondering if it is possible to use the palm rejection technology that it implements as I am looking to upgrade from my TF101, and was hoping to have a integrated keyboard and perhaps stylus support for school related things.
Thanks in advance.
Click to expand...
Click to collapse
This is also a mather of technology, and as far as i know the display doesnt support this technology.