Anyone the least bit upset about the cdma xoom losing developer supported device status?
Sent from my SPH-D710 using xda premium
Huh?
Theres a whole slew of developers supporting this device, who'd you rub the wrong way? Are you talking about Moto discontinuing the device or ???
Do some more reading. Unless you are building AOSP for a non-rooted device, none of that CDMA garbage applies. Nothing to see here. Move on.
Sent from my Nexus S using Tapatalk
Related
http://www.engadget.com/2011/01/21/motorola-ready-to-make-sweet-love-to-rom-devs-and-rooters/
Looks like future Motorola devices might be better off than the DroidX/2/Milestone.
If you are too lazy to read, Moto stated:
"We are working closely with our partners to offer a bootloader solution that will enable developers to use our devices as a development platform while still protecting our users' interests. More detailed information will follow as we get closer to availability."
Not sure how nobody has posted this yet...
EDIT: Looks like this was mentioned in this thread already. Anyway we'll see what happens.
They have posted it all over the internetz and the general consensus is that Moto will just keep locking the bootloaders.
We can always hope though...
Mortalys77 said:
They have posted it all over the internetz and the general consensus is that Moto will just keep locking the bootloaders.
We can always hope though...
Click to expand...
Click to collapse
Moto did not have to come out and say this.
What is your reasoning that they will just continue to keep it locked if they outright say they aren't?
and in their statement, who would their "partners" be? The carriers?
Hmmmm interesting
Sent from my DROIDX using XDA App
Yes you are right I know it has been posted many places. I was curious to hear the thoughts of people in this forum in particular some devs. I trust XDA forum opinion above others .
Sent from my DROIDX using XDA App
sciulli999 said:
What is your reasoning that they will just continue to keep it locked if they outright say they aren't?
Click to expand...
Click to collapse
Because they won't unlock it now, and this was just of a damage control thing.
They won't unlock the bootloader forbthis phone likely ever, but it is starting to look like they are going to work for their phones being development friendly judging by their recent response on facebook or twitter. I can't find it now, but they did state that they would like their phones to be more dev friendly
Sent from my DROIDX using XDA App
Actually, the link is in the first post(OP). that is at least promising
Sent from my DROIDX using XDA App
sciulli999 said:
Moto did not have to come out and say this.
What is your reasoning that they will just continue to keep it locked if they outright say they aren't?
and in their statement, who would their "partners" be? The carriers?
Click to expand...
Click to collapse
They definitely had a reason to come out and say this. It was a direct response to: http://www.droid-life.com/2011/01/1...er-to-buy-elsewhere-if-they-want-custom-roms/
I don't get the feeling that their willing to unlock any of their current phones. Someone would've said something by now if they were really working with devs.
What's most likely is they will phones through google unlocked but not discounted by the cell companies.
Sent from my DROIDX using Tapatalk
Protecting users? That line makes it sound like you would have to go out of your way to unlock the bootloaders. Either by giving up warranty rights beforehand, or buying a "development model", at unsubsidized pricing. Either way is reasonable, but as an average joe, I like warranties and cheap/er phones lol
Sent from my DROIDX using XDA App
Well rumor mill is there will be an optional ota that will unlock bootloader. Your warrenty will be void BC it shows on your esn number.
Sent from my DROIDX using XDA App
papi92 said:
Well rumor mill is there will be an optional ota that will unlock bootloader. Your warrenty will be void BC it shows on your esn number.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Wow, this would be very cool, where are you seeing rumors like this?
If it comes out as an OTA then I'll just wait for the devs to get it and break it apart so we can finally have an unlocked bootloader without having to SBF to get the OTA.
Sent from my DROIDX using Tapatalk
Just a friend. Its an idea there tossing around you wont need to sbf as its optional and only unlocking bootloader which will show on your esn and void your warranty
Sent from my DROIDX using XDA App
honestly I would take the loss of my manufacturer warranty as long as I still have assurian for lost or damaged I'm cool just give me an unlock option and I would stay with motorola
Im not sure if it voids your whole warrenty. I will have to get back on that as it seems this isn't the set plan yet.
Sent from my DROIDX using XDA App
papi92 said:
Im not sure if it voids your whole warrenty. I will have to get back on that as it seems this isn't the set plan yet.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Where are you getting your information?
My neighbor is on the team that develops for moto
Sent from my DROIDX using XDA App
Alot of you guys have a good point. However. Papi92 is a liar. Show some proof and ill give u the benefit of the doubt. Till then you are just gonna be a liar in my book
Sent from my DROIDX using XDA App
ksizzle9 said:
Alot of you guys have a good point. However. Papi92 is a liar. Show some proof and ill give u the benefit of the doubt. Till then you are just gonna be a liar in my book
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Do not listen to this man! Look at his post count! "Posts: 666"
http://mobile.slashdot.org/story/12/02/05/0422238/google-pulls-support-for-cdma-devices
Holy crap. This seems really bad. At least for those of us on sprint and looking forward to future development. Unless I'm just an idiot and missing something lol.
Sent from my PC36100 using xda premium
scottspa74 said:
Holy crap. This seems really bad. At least for those of us on sprint and looking forward to future development. Unless I'm just an idiot and missing something lol.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Yea, that's bad. Basically it boils down to this scenario:
Google: Sure you can have ICS on ____ device
CDMA carrier Sprint/Verizon: Well, we'd like over our skin on ICS
Google: We'd like to keep it stock Google
Carriers: We want the skin...
Google: No [and cue that article]
Says its based on the software to make it 'fully functional' Because CDMA device needs carrier binaries to make them work.
There is no way in hell US carriers will open up their binary drivers. This just hurts users on Verizon/Sprint. Does this mean the next Nexus will be GSM only?
man sprint always f##kin up
Sent from my PC36100 using xda premium
sobaked2921 said:
man sprint always f##kin up
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Who said it was Sprint only? It ranges to all CDMA made phones not one specific CDMA carrier.
My understanding is that this is Google only.
It has to do with the trying to keep Android compliant with the GPL, and the companies making the CDMA radios are making it difficult so Google pulled out. It doesn't mean no more Android phones on Sprint or Verizon (that would be a bit silly) but it does mean no more Nexus phones on CDMA. It could also mean Motorola will be pulling out of the CDMA market as well.
Then again, this could all be a plan by Google to force the companies to release the drivers. It wouldn't be the first time Google has played hardball with companies. If Google and Motorola both leave, this puts pressure on Sprint and Verizon to push the manufacturers to release the drivers as it leaves them at a severe disadvantage compared to GSM carriers. It's good in a way, but could have some bad consequences down the road if it backfires.
It's nothing to really worry about guys if i can find the article I'll post it but Google came back and clarified why they did it exactly and it was to do with how CDMA phones have certain files stored for them and it caused an issue with compiling from AOSP and all. They still are pushing straight updates to cdma nexus phones as usual too.
Edit: here's one part for the mean time...
https://groups.google.com/forum/?fromgroups#%21topic/android-contrib/phz3S5ZdveU
Sent from my PG86100 using XDA App
Found this on Google Groups
sgt. slaughter said:
It's nothing to really worry about guys if i can find the article I'll post it but Google came back and clarified why they did it exactly and it was to do with how CDMA phones have certain files stored for them and it caused an issue with compiling from AOSP and all. They still are pushing straight updates to cdma nexus phones as usual too.
Edit: here's one part for the mean time...
https://groups.google.com/forum/?fromgroups#!topic/android-contrib/phz3S5ZdveU.com
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I only quoted this to add .com to the end lol (makes it easier from mobile). Can't get damn page to load.
Sent from my PC36100 using xda premium
tropicalbrit said:
Found this on Google Groups
Click to expand...
Click to collapse
wow! I just got lost in the rabbit hole for 2hrs on that one lol. Thanks for the find, though.
Sent from my PC36100 using xda premium
My understanding is that it's only a signing issue. It should be resolved
http://www.androidcentral.com/nexus-s-4g-officially-aosp-device-once-again
This relates to the porting of the crespo drivers for our Epics to be able to access 4G, etc. Now that it's officially official (again) maybe this will aid all of our devs (especially Team Epic) in their continued quest of perfection!
If considered non-news or just not that interesting, please feel free to close this thread Kenny.
I don't get it was the nexus s 4g not also at one point?
Sent from my SPH-D710 using xda premium
Edit: lmao cause of too much xda I associated aosp with roms instead of open source
Correct. The Nexus S 4G on Sprint was part of and then was shunned by AOSP because of the proprietary drivers needed for CDMA and WiMax. The gist of the article is that they've all somehow come together and worked things out to where Nexus S 4G will now see updates about the same time as GSM Nexus S. This pertains to us Epic users as well, at least those of us on ICS, since Team Epic devs are currently using several drivers from Nexus S 4G to make our phones work. This should also help them port Jelly Bean to our phone, once official source code drops.
Sent from my SPH-D700 using xda premium
Sounds Promising ...:fingers-crossed:
I'm planning to buy a nexus 7 for flashing purposes. Does both Wi-Fi and 3g versions flashes same kernel and roms?
Sent from my One V using xda app-developers app
Yes and no. They are different devices and, as such, the roms are going to be slightly different between grouper and tilapia. As for kernels, I can't speak as to what's compatible with tilapia or not. Your overall best best is going to be reading up in the dev forum for the 3G to get an idea of what's available.
Sent from my Nexus 7 using Tapatalk HD
Suggest which version to buy with reasons. I'll die if I don't get developer support later
Sent from my One V using xda app-developers app
If you simply took a look in the dev threads yourself you would see how many options they each have. Its a good idea to look at the 1st post in the threads as some of the WiFi ones also say they support 3g.
Sent from my Galaxy Nexus using xda premium
harsh.ea said:
Suggest which version to buy with reasons. I'll die if I don't get developer support later
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Okay.
You should buy whichever version that YOU feel, after careful evaluation, will fit your individual needs and circumstances better. I would strongly advise, if dev support is your key requirement, to peruse the dev subforums to get an idea of what the individual dev scenes for both devices look like. In the end, it is you that will be the one using it, not any of us. Each person has their own reasons for picking one poor the other. The bottom line I'd that it's a decision that only you can make for yourself.
That being said, the one and only reason I'd recommend Tilapia over Grouper is if you require 3G connectivity. Its not as if the dev scene for either device is lacking. They are Nexus devices, after all.
Sent from my Nexus 7 using Tapatalk HD
So Wi-Fi over 3g in terms of development?
Sent from my One V using xda app-developers app
I am eagerly anticipating the release of sprints lg g2. I am wondering what devs are coming to develop for the sprint lg g2. Would like to get a idea of the family that I will be with. I am sure that the device will gain popularity as time goes by, but wondering if you are a dev or a theme creator or person who does kernels etc and coming over. Would love to check out some of your work on other devices. Just haven't heard anyone ask and really am interested in this device provided the devs are on board with it, I am locking in to a agreement for 2 years so want to weigh my options carefully .
Sent from my SPH-L710 using xda app-developers app
pintopunk said:
I am eagerly anticipating the release of sprints lg g2. I am wondering what devs are coming to develop for the sprint lg g2. Would like to get a idea of the family that I will be with. I am sure that the device will gain popularity as time goes by, but wondering if you are a dev or a theme creator or person who does kernels etc and coming over. Would love to check out some of your work on other devices. Just haven't heard anyone ask and really am interested in this device provided the devs are on board with it, I am locking in to a agreement for 2 years so want to weigh my options carefully .
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I am curious about this too.
Anyone heard of any devs?
Sent from my SPH-L710 using xda app-developers app
I'm sure there will be many developers once the phone actually comes out and they know what they are working with.