Related
Hey guys,
i was just looking around and saw that meego has a new platform which supports tegra2 aswell. My question is, if anyone had thought about putting or the viability of meego on the optimus 2x? Since it the bootloader is not an issue here (like with the motorola atrix for instance), it shouldnt be that big of a problem or? i have an atrix myself but if we could get meego on the optimus 2x i would most probably exchange it
hers the link to the meego site: https://meego.com/downloads/releases/1.2/meego-v1.2-core-software-platform
what do you think guys?
I would like to know that why meego?.? It's really good and better than Android? I just interest and 3.1 ANDROID.
Sent from my LG-P990 using XDA App
well meegoo is more like full linux, like you would have ubuntu or gentoo, but its tailored for handsets/tablets power, app and functionality wise (so you can use it as a phone), unfortunately the support for it is not really big. On the other hand Android is so to say java on top of a linux kernel, so in order to have some new app you have to do java, you cant use all the available stuff. second to that you could just connect the meego 2x over hdmi to a tv and have a full functioning linux machine so to say (with bt keyboard and mouse), thats why i was wondering, i myself have an atrix 4g, basically same board but its bootloader locked, so meego on it at least for now is out of the question, but we have webtop, which is a bit like real linux on a tv, however its some ultra crippled and old distro of ubuntu and the phone has to run two OSes (android and the ubuntu) and integrate them so that you can still use your phone as a phone, with meego its all one system, so its less resource consumable and easier to use
Me to i love meego because is an full linux os : amazing possibilitie with the hdmi cable.
Please someone could try to port meego on the O2X??
Thanks
Wasn't meego earlier ported to nexus one? That should help a lot
Sent from my Optimus 2X using XDA App
Seeing that the Evo will most likely never get stable USB host support I have abandon future projects on the Evo and am looking at expanding the Atrix/Photon feature set. I'm looking to work with a dev on external touchscreen support for the Atrix/Photon platform as well as other possible USB devices.
Granted, I have a the "CDMA Atrix" a.k.a. Photon but drivers should be easy to port and would benefit both devices. If I can get some devs on board we can nail down hardware specifics and other details later. I won't go into detail here as to what the end results will be but devs feel free to PM me with any questions. Hopefully there will be more dev involvement than the Evo Desktop had.
I am seeking a similar solution, i would like to run my Atrix as a car-pc with a 7 inch touch screen in dash. Please keep us updated!
Lokifish Marz said:
Seeing that the Evo will most likely never get stable USB host support I have abandon future projects on the Evo and am looking at expanding the Atrix/Photon feature set. I'm looking to work with a dev on external touchscreen support for the Atrix/Photon platform as well as other possible USB devices.
Granted, I have a the "CDMA Atrix" a.k.a. Photon but drivers should be easy to port and would benefit both devices. If I can get some devs on board we can nail down hardware specifics and other details later. I won't go into detail here as to what the end results will be but devs feel free to PM me with any questions. Hopefully there will be more dev involvement than the Evo Desktop had.
Click to expand...
Click to collapse
Basically there should be no porting needed. Atrix and Photon kernels are 99.99% the same and just differ in build configuration.
I thought to do this exact same thing as it makes tremendous sense. Everything already on the phone. Could be implemented very easily with the multimedia dock or even the car dock that enters the Photon into navigation mode automagically.
Have you tried the touch screen USB support yet?
Has anyone seen any news on weather or not we will be getting ics for our DROID 3? Not cm9 but the official. I poke around twitter and google but can't find anything new, its all outdated.
Sent from my DROID3 using XDA App
Motorola does not list the Droid 3 on any of their roadmaps...it is like they just forgot about the device.
I would not hold my breath but at this point there is no official response in ether direction.
We are all waiting for Motorola to issue some updates... I think they are going to make the announcements all at the same time, of which phones will and won't make the upgrade.
D3 is in good shape though, it runs almost the same CPU and GPU as Galaxy Nexus, just has half the memory. Let's keep our fingers crossed!
prsterero said:
Has anyone seen any news on weather or not we will be getting ics for our DROID 3? Not cm9 but the official. I poke around twitter and google but can't find anything new, its all outdated.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I remember seeing somewhere that motorola is redoing their software update page on their website, I know they are working on it as we speak. I would hope that it's soon, I remember google saying that the updates should be quicker with ICS but saying and doing are two different things.
prsterero said:
Has anyone seen any news on weather or not we will be getting ics for our DROID 3? Not cm9 but the official. I poke around twitter and google but can't find anything new, its all outdated.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Even if Moto and Verizon don't officially give ICS to the D3, you can bet that shortly after they release it for either the Razr or Bionic that it will be ported in it's "blurred" setup to the D3.
mikedyk43 said:
Even if Moto and Verizon don't officially give ICS to the D3, you can bet that shortly after they release it for either the Razr or Bionic that it will be ported in it's "blurred" setup to the D3.
Click to expand...
Click to collapse
Keep in mind that if they don't release it for the Droid 3, the "ported" version based from those won't get the new kernel that those devices get along with their ICS upgrade...
If they release just one of the phones Hash supports for ICS with a camera, that is all we really need anyway.
MrObvious said:
If they release just one of the phones Hash supports for ICS with a camera, that is all we really need anyway.
Click to expand...
Click to collapse
Not if the app relies on the newer kernel that the upgrade will bring to the other devices...
Sent from my Xoom
Motorola released their "staging plans" for ICS upgrades...
https://forums.motorola.com/pages/00add97d6c
DROID 3
USA
Evaluation & Planning
Further details to follow.
They state that some products may not make it beyond the Evaluation stage....
Categorized in 1 Gig ram devices and 512 Meg Ram devices. Bionic, Razr and Droid4 are also listed as "Evaluation & Planning".
This is good news, but dumb because all those 4 phones should have been evaluated when being made for ics compatibility
Sent from my XT862 using Tapatalk
prsterero said:
Has anyone seen any news on weather or not we will be getting ics for our DROID 3? Not cm9 but the official. I poke around twitter and google but can't find anything new, its all outdated.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
http://bit.ly/MotoSoftUpdate
there is some info (but not confirmed)
same update page but custom url
---------------------------------
i hope D3 and bionic get Official ICS (mb200 in latam didnt get 2.1 so i would not give all my hopes again and then rant a "never more and/again Motorola" quote
Dri94 said:
This is good news, but dumb because all those 4 phones should have been evaluated when being made for ics compatibility
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I wonder if they had to build their new blur before making the actual ICS builds for their phones.
Still I'm happy that they have at least acknowledged that the D3 might get updated to ICS maybe someday possibly a remote chance.
Interesting...the Motorola Razr is in "Development" status but the Droid Razr is still only "Evaluation and Planning" stage....
Verizon must be a big part of the problem....as even the 3G Xoom's are "Evaluation and Planning" while the WiFi Xoom already has it (and non-us WiFi are in Development).
tcrews said:
Interesting...the Motorola Razr is in "Development" status but the Droid Razr is still only "Evaluation and Planning" stage....
Verizon must be a big part of the problem....as even the 3G Xoom's are "Evaluation and Planning" while the WiFi Xoom already has it (and non-us WiFi are in Development).
Click to expand...
Click to collapse
I noticed the same thing... It looks like for the first time Canada might be getting something quicker than the US... (At least in the RAZR ICS upgrade department).
All I care about is that the RAZR upgrade code leaks so that way we can get the cameras working within CM9, then maybe I'll jump ship from stock.
danifunker said:
All I care about is that the RAZR upgrade code leaks so that way we can get the cameras working within CM9, then maybe I'll jump ship from stock.
Click to expand...
Click to collapse
that still really doesn't help as Hashcode has pointed out the dependencies the ICS camera has on the ION driver inside the ICS kernel....which are not present in the Gingerbread kernel that will still be running on the Droid 3 with CM9.
These dependencies won't go away on a Razr ICS camera....as the kernel will be getting updated along with the OS when they push it out.
tcrews said:
Verizon must be a big part of the problem....as even the 3G Xoom's are "Evaluation and Planning" while the WiFi Xoom already has it (and non-us WiFi are in Development).
Click to expand...
Click to collapse
I agree. All Verizon dual-core phones - even the Bionic, Razr series and D4 - are the same status. I think that Verizon's approval process and bloatware install requirements have become too unpredictable to allow for a definitive upgrade period.
It wouldn't surprise me if a working ics blur rom existed at moto and was stable. The hurdle has always been verizon. I can't understand the forced bloat concept considering most users don't use it and will root now to rid themselves of it.
Sent from my DROID3 using xda premium
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
This is a general question from me trying to understand things better. Before the D4 I had a samsung stratosphere. Completely unlocked bootloader with full capability to flash custom ROM/kernel images. Despite this no AOSP ROMs could be build due to lack of driver sources. It was the same situation with the Epic 4G. The Droid 4 on the other hand had the bootloader locked with the key thrown away. Despite this CM9 and other AOSP ROMs are up and nearly fully operational, even with ICS booting on GB kernels. What makes this possible on D4 but not the stratosphere?
My guess is that driver software is available for the D4. This is due to the fact that Motorola uses parts from other OEMs (TI CPU ect) with public drivers. Samsung on the other hand uses their own proprietary parts and keeps the drivers private. Is this an accurate assessment?
It would seem then that the most important thing to making development possible for a phone (apart from popularity) is driver availability, NOT whether or not the bootloader is unlocked. Is that true? Regardless, I will probably steer clear of samsung for future android purchases. HTC still seems best and motorola acceptable. If only HTC still made high end QWERTYs.
Usually devs just pull the proprietary files off the phone and use it in the compile/builds. This has been going on for Motorola phones since the original Droid.
Sounds like no one invested in seeing what proprietary files were needed from the Stratosphere or Epic 4G.
Public AOSP code mixed with copying in private/proprietary files is how most ROMs are made. The higher the user base of a device, the higher the development activity and the larger number of devs finding out what all is needed to be pulled from the stock device to compile a fully functional ROM.
Since some proprietary files are used....you need them for the same version OS you are building, ie...use stock phones ICS drivers for ICS builds or stock phones GB drivers for Gingerbread builds. You can sometimes hack drivers to work but with lots of limitations. Also drivers depend on the kernel so a matching kernel is needed......requiring the device to have the needed kernel level or an unlocked bootloader to be able to replace the stock kernel.
We wont be seeing an unlocked bootloader? Ever?
Sent from my DROID4 using xda premium
twizzles said:
We wont be seeing an unlocked bootloader? Ever?
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
All signs point to no...we will never see an unlocked bootloader on the current Motorola devices.
With Google owning Motorola Mobility and already replacing MM CEO with one of their own from Google........it's possible future devices may be unlock capable.
Current devices....no, not ever.
The first locked bootloader on a Motorola droid was the Droid 2. It still has not been unlocked, hacked, cracked, etc... How long has it been out?
Motorola released a special Razr Dev model with an unlockable bootloader...retail price, zero warranty, nothing you do on it would transfer over to the normal Razr or Razr Maxx.......so why would anyone buy it? Great PR for them to say "see..we released an unlockable device and no one bought it".
Well that just sucks. Thank you for the info
Sent from my DROID4 using xda premium
I have to say, I don't mind not having an unlocked bootloader. I had the Galaxy Nexus and ran multiple different setups on it. The radio still sucked though. With the Droid 4, I don't feel the need to do a lot of hacking. The phone is well built, radio is awesome, it just works.
GermanGuy said:
I have to say, I don't mind not having an unlocked bootloader. I had the Galaxy Nexus and ran multiple different setups on it. The radio still sucked though. With the Droid 4, I don't feel the need to do a lot of hacking. The phone is well built, radio is awesome, it just works.
Click to expand...
Click to collapse
I kind of agree with you for the most, but still I prefer the option and think we should have it as an option. It's one way to keep a device relevant throughout your 2 year contract. For example....the Droid 3. I have one, bought online day of release. In less than a years time it has become a non-supported, forgotten device from Motorola. The locked bootloader prevents devs from picking apart the Droid 4 leaked ICS kernel and compiling one with Droid 3 specs (less RAM, etc..) and bringing a fully functional ICS build to the Droid 3. Unlocked...that would be possible.
JKingDev said:
This is a general question from me trying to understand things better. Before the D4 I had a samsung stratosphere. Completely unlocked bootloader with full capability to flash custom ROM/kernel images. Despite this no AOSP ROMs could be build due to lack of driver sources. It was the same situation with the Epic 4G. The Droid 4 on the other hand had the bootloader locked with the key thrown away. Despite this CM9 and other AOSP ROMs are up and nearly fully operational, even with ICS booting on GB kernels. What makes this possible on D4 but not the stratosphere?
Click to expand...
Click to collapse
I, as well, went from the Stratosphere to the Droid 4. I love my Stratosphere and still have it, but the lack of development on it is just down right aggravating. That is why I took it upon myself to learn how to compile a kernel to provide everyone with root and recovery for it. Otherwise we wouldn't have the ROMs we have for it now. If it wasn't for the Droid Charge using the exact same dev board as the Strat, I doubt we'd even have that much. I had to take the Charge build of CWM and packed it in a Strat kernel and tweaked the scripts, thank god at least that worked.
JKingDev said:
My guess is that driver software is available for the D4. This is due to the fact that Motorola uses parts from other OEMs (TI CPU ect) with public drivers. Samsung on the other hand uses their own proprietary parts and keeps the drivers private. Is this an accurate assessment?
Click to expand...
Click to collapse
I am not sure about the Motorola drivers, but you are right about Samsung. The first time I compiled the kernel, I was missing 11 modules. I couldn't figure out what I did to keep them from being compiled... and then I learned the sneakiness Samsung uses to get around releasing the source, they compile the kernels for the file system and radios and dynamically link them in the init.rc script. Apparently a lot of them do this, actually.
JKingDev said:
It would seem then that the most important thing to making development possible for a phone (apart from popularity) is driver availability, NOT whether or not the bootloader is unlocked. Is that true?
Click to expand...
Click to collapse
Actually both are true to some extent, with a locked bootloader you are stuck with OEM signed boot images and can't recompile the kernel to your own needs, or compiling one with ro.secure = 0 so you get root access in adb (which is how I rooted the Stratosphere). Then you need the drivers to talk to the hardware too. Without them, you'd need to reverse engineer them or use the currently complied ones (also, like we did with the Strat). Finally, you have to have the source for the RIL (Radio Interface Layer) in Android so Android as an OS knows how to talk to the drivers to make calls, send messages, use data, etc. THIS is where we are currently hung up from using AOSP on the Stratosphere. I know work is being done on the RIL for the Charge and since its the same board, we might get lucky and be able to reuse most (if not all) of the same code and bring new life to it. But, I wasn't getting my hopes up and decided to get a D4 anyway.
JKingDev said:
Regardless, I will probably steer clear of samsung for future android purchases. HTC still seems best and motorola acceptable. If only HTC still made high end QWERTYs.
Click to expand...
Click to collapse
You and me both. I was in love with the keyboard on my HTC Touch Pro 2 and wish they'd release something like that running Android on Verizon with newer hardware. Closest they had to a QWERTY on VZ was the Merge, and they botched that up from the gate. I also have the Rezound and am trying to design a way to attach a sliding keyboard to the back battery cover to give me something closer to what i have been wanting in a phone.
I think us QWERTY loves on VZ are at the mercy of Motorola and Motorola alone with the original Droid line of sliders.
KnightCrusader said:
I, as well, went from the Stratosphere to the Droid 4. I love my Stratosphere and still have it, but the lack of development on it is just down right aggravating. That is why I took it upon myself to learn how to compile a kernel to provide everyone with root and recovery for it. Otherwise we wouldn't have the ROMs we have for it now. If it wasn't for the Droid Charge using the exact same dev board as the Strat, I doubt we'd even have that much. I had to take the Charge build of CWM and packed it in a Strat kernel and tweaked the scripts, thank god at least that worked.
I am not sure about the Motorola drivers, but you are right about Samsung. The first time I compiled the kernel, I was missing 11 modules. I couldn't figure out what I did to keep them from being compiled... and then I learned the sneakiness Samsung uses to get around releasing the source, they compile the kernels for the file system and radios and dynamically link them in the init.rc script. Apparently a lot of them do this, actually.
Actually both are true to some extent, with a locked bootloader you are stuck with OEM signed boot images and can't recompile the kernel to your own needs, or compiling one with ro.secure = 0 so you get root access in adb (which is how I rooted the Stratosphere). Then you need the drivers to talk to the hardware too. Without them, you'd need to reverse engineer them or use the currently complied ones (also, like we did with the Strat). Finally, you have to have the source for the RIL (Radio Interface Layer) in Android so Android as an OS knows how to talk to the drivers to make calls, send messages, use data, etc. THIS is where we are currently hung up from using AOSP on the Stratosphere. I know work is being done on the RIL for the Charge and since its the same board, we might get lucky and be able to reuse most (if not all) of the same code and bring new life to it. But, I wasn't getting my hopes up and decided to get a D4 anyway.
You and me both. I was in love with the keyboard on my HTC Touch Pro 2 and wish they'd release something like that running Android on Verizon with newer hardware. Closest they had to a QWERTY on VZ was the Merge, and they botched that up from the gate. I also have the Rezound and am trying to design a way to attach a sliding keyboard to the back battery cover to give me something closer to what i have been wanting in a phone.
I think us QWERTY loves on VZ are at the mercy of Motorola and Motorola alone with the original Droid line of sliders.
Click to expand...
Click to collapse
Thanks for the replies. It is interesting stuff. And KC I definitely appreciated your work on the Strat. So I guess it really was a question of popularity being the problem for stratosphere. I definitely know it wasnt the most popular device but it also seemed like reverse engineering drivers for the Samsung devices was so much harder. The charge was relatively popular and years later the RIL has still not been successfully reverse engineered. All the moto devices get cracked so quickly. Is it only because they are more popular, or are there other reasons that make them easier to hack? Thats what leads me to think maybe it's samsung's use of proprietary hardware that makes things more difficult. Does that have something to do with it?