Related
Thought this was insane!
"sprint Android update! Upgrades to 2.1 for Hero/Moment now expected early 2Q10. Currently working through options for upgrades w/ HTC and Samsung. "
Sorry for another thread, but the others are so long...
So we are looking at April or May.. nice althought most probably by that time we'll be sick of having it for a couple of months already.
I read that. Meh, What they are saying is, "HTC, Samsung : DO we have all of the bugs patched" and HTC and Samsung going...****....did we patch asroot2? Haha.
They can patch whatever they want, Ill be waiting for the DEVs here to make custom ROMs based on that update.
Kcarpenter said:
Thought this was insane!
"sprint Android update! Upgrades to 2.1 for Hero/Moment now expected early 2Q10. Currently working through options for upgrades w/ HTC and Samsung. "
Sorry for another thread, but the others are so long...
Click to expand...
Click to collapse
This may be obvious, but what is Sprints Official Twitter username? I would like to follow them.
Darkshneider said:
They can patch whatever they want, Ill be waiting for the DEVs here to make custom ROMs based on that update.
Click to expand...
Click to collapse
+1 Same here
rockcrawler said:
This may be obvious, but what is Sprints Official Twitter username? I would like to follow them.
Click to expand...
Click to collapse
@Sprint
Kcarpenter got schooled by @Sprint!
Originally Posted by twitter.com/sprint
@Kcarpenter5407 Have always said 1H2010, now we're saying early Q2.
Click to expand...
Click to collapse
1H2010 is business-speak for 2Q2010, but with false optimism for 1Q2010. Coming from Sprint's mouth, 1H2010 probably means 3Q2010. They're not known for making their release deadlines.
cmccracken said:
Kcarpenter got schooled by @Sprint!
1H2010 is business-speak for 2Q2010, but with false optimism for 1Q2010. Coming from Sprint's mouth, 1H2010 probably means 3Q2010. They're not known for making their release deadlines.
Click to expand...
Click to collapse
ROFL i hadn't checked back! That is true, they did say 1H.
EDIT:
Who knew they actually read that crap.
cmccracken said:
@Sprint
Click to expand...
Click to collapse
I knew I was going to feel special, but I asked anyway LOL
I wonder if they are going to be updating due to the fact that the Legend and Desire are both going to be release early next quarter? Hence, a new version of Sense will be on the market and they won't be able to use the 'it's not ready' yet excuse anymore.
if i were sprint, i would be PISSED after looking at forums like this. Not because people are modding the devices but because ppl who are doing this on their free time for next to nothing with none of the resources that the htc/sprint guys have are almost finished making this completely ready and stable, meanwhile the people they are PAYING to do this still arent done, with all the resources and source code in the world to work with
Street_Knowledge said:
if i were sprint, i would be PISSED after looking at forums like this. Not because people are modding the devices but because ppl who are doing this on their free time for next to nothing with none of the resources that the htc/sprint guys have are almost finished making this completely ready and stable, meanwhile the people they are PAYING to do this still arent done, with all the resources and source code in the world to work with
Click to expand...
Click to collapse
No offense to the devs here, but what they do is really not in any way similar or comparable to what the HTC devs are doing.
Really? I thought the only difference was that guys at HTC have official kernels and the closed source part of the phone...
The "closed source part of the phone" is the vast majority of the code running on it, including most bundled apps and Sense UI. The bundled Google apps are also closed-source and non-distributable (and the new versions rock).
Exactly, DEVs over here still tinker with what they have and make amazing things with so little.
I'd imagine there's an UNGODLY big difference from editing code till it works or looks differently, icons, colors, bitmaps... and creating your own functioning code from scratch. This is what sprint is paying htc for.
I've been able to hack together programs to work a certain way I wanted, but if you told me... i want a program to do a new function... I would absolutely give the deer in the headlights look.
I'd imagine the majority of the DEV's here are able to fill the first type very nicely, only a select few are able to fill the second type, or are willing to code from scratch for free in their free time.
johnsongrantr said:
I'd imagine there's an UNGODLY big difference from editing code till it works or looks differently, icons, colors, bitmaps... and creating your own functioning code from scratch. This is what sprint is paying htc for.
I've been able to hack together programs to work a certain way I wanted, but if you told me... i want a program to do a new function... I would absolutely give the deer in the headlights look.
I'd imagine the majority of the DEV's here are able to fill the first type very nicely, only a select few are able to fill the second type, or are willing to code from scratch for free in their free time.
Click to expand...
Click to collapse
Sometimes writing from scratch is much easier that editing/fixing someone else's F*^ed code.
[rant]I worked as a Team lead and the company basically replaced most of my team with offshore (H1B's). I got stuck trying to support poorly written code. In my experience one good developer that writes well-documented code and properly tests his code is worth about 15-20 Offshore developers when you start factoring in bug fixing, code management, and support. The company saved $30,000 for each developer they replaced, but then had to hire 3 times the amount of personnel for support.
[/rant]
Can anyone contest to the quality of htc's kernel source? is it poorly commented and hacky? My guess it would be pretty professional looking, could and probally am wrong, seeing how it's taking some time to twist the kernel into a fully functioning 2.1.
I haven't dove into htc's code just look around yet, I did with the palm pre a bit and saw some of their almost comical comments they made on some of their internal apps, very neatly commented just some of the stuff they said was kinda comical (talking bout sections of their code being rubish but working.. noting to clean it up later)... I liked the general mood the palm dev's had at the time of their first release (rushed but focused it seemed)
johnsongrantr said:
Can anyone contest to the quality of htc's kernel source? is it poorly commented and hacky? My guess it would be pretty professional looking, could and probally am wrong, seeing how it's taking some time to twist the kernel into a fully functioning 2.1.
Click to expand...
Click to collapse
see thats the thing, they have already shown off several phones running sense and 2.1
whats the holdup here?
hey all, i found this little guy floating around cyberspace and though maybe we should sign, who knows we can try right?
http://www.petitiononline.com/honey30/
Why? It will be released when it's ready.
This is dumb. Why would they release it before its done?
People are angry because the xoom has honeycomb, and honeycomb hasnt been released.
The xoom has an unfinished build of honeycomb. The SD card slot doesn't even work yet.
Also, when you say things like "found this floating around", when in reality you actually created it yourself... That doesn't help you gain any support.
Yea because google is somehow required to release honeycomb to the public, grow up
Okay, I know that everyone is infuriated by this petition. But there are still many devs that would enjoy making the source better by working on it now. Not to mention larger companies would like to have the source like barnes and noble and notion ink. It would just be nice if google posted the source with a disclaimker kf its problems
Sent from my PG06100 using XDA App
Lakers16 said:
This is dumb. Why would they release it before its done?
People are angry because the xoom has honeycomb, and honeycomb hasnt been released.
The xoom has an unfinished build of honeycomb. The SD card slot doesn't even work yet.
Also, when you say things like "found this floating around", when in reality you actually created it yourself... That doesn't help you gain any support.
Click to expand...
Click to collapse
Totally agree with you...
Google have some very good reasons for not releasing the source code. Mainly it's because of a key change in their strategy AGAINST the open source nature you love.
They are worried about issues like fragmentation and want to ensure anyone picking up an android device will feel its a 'high quality' device. By releasing the source code anyone can do what they like with it and some devices will fail badly. This makes android look bad. By keeping the source code in house Google can control who develops it and who can use it in their devices. This is all an attempt to maintain a 'high quality' feel to devices running android.
I know this goes against the open source nature everyone says Google has but at the end of the day they REALLY want to dominate the mobile OS war. I dont think a little online petition will send them running to think about their actions and then return to hand over the source code.
Agreed its unfinished. Why would you release code on an unfinished product? This is not about open source or fragmentation, blah blah blah. Its the fact they shoehorned Android on a tablet to compete with the iPad. When the code is finished they'll release it. For now we have gingerbread
Sent from my Eris ADR6200 using XDA App
edcoppen said:
Google have some very good reasons for not releasing the source code. Mainly it's because of a key change in their strategy AGAINST the open source nature you love.
They are worried about issues like fragmentation and want to ensure anyone picking up an android device will feel its a 'high quality' device. By releasing the source code anyone can do what they like with it and some devices will fail badly. This makes android look bad. By keeping the source code in house Google can control who develops it and who can use it in their devices. This is all an attempt to maintain a 'high quality' feel to devices running android.
I know this goes against the open source nature everyone says Google has but at the end of the day they REALLY want to dominate the mobile OS war. I dont think a little online petition will send them running to think about their actions and then return to hand over the source code.
Click to expand...
Click to collapse
What? You are completely wrong.
Honeycomb ISNT FINISHED. It has nothing to do with fragmentation. Google's new stance wont even effect the end user or even rom devs much, its simply to stop big companies from slapping their own terrible UI over the top.
The honeycomb source will be released when its good and ready. I'm pretty sure Google are required by law to release it anywany so just be patient.
Sent from my Nexus One using XDA Premium App
Meltus said:
its simply to stop big companies from slapping their own terrible UI over the top.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Galaxy Tab 8.9 and the new 10.1 have TouchJizz 4.0 all over them.
Meltus said:
its simply to stop big companies from slapping their own terrible UI over the top.
Click to expand...
Click to collapse
Its actually to discourage them from doing it.
Meltus said:
What? You are completely wrong.
Honeycomb ISNT FINISHED. It has nothing to do with fragmentation. Google's new stance wont even effect the end user or even rom devs much, its simply to stop big companies from slapping their own terrible UI over the top.
The honeycomb source will be released when its good and ready. I'm pretty sure Google are required by law to release it anywany so just be patient.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Completely wrong! The chief editor of engadget agrees that there is huge pressure for Google to change their strategy. Have a look at this article he wrote...
http://www.engadget.com/2011/04/09/editorial-androids-problem-isnt-fragmentation-its-contamina/
He says exactly the same as me, except I took it one step further by suggesting this is the reason Honeycomb hasn't been released yet. I agree with you that honeycomb still has improvements to be made before its source is released. I just don't believe that's all there is to it. There are other considerations too!
Also note this was released today, after my my comment was made
DanWilson said:
Galaxy Tab 8.9 and the new 10.1 have TouchJizz 4.0 all over them.
Click to expand...
Click to collapse
The touchwiz ux on the tabs looks real nice. Much easier to tell what some things do. Just my opinion.
Sent from my always stock, EC05 Epic 4G
Cyanogen himself said Honeycomb was probably a pile of hacks. Google needs to clean it up a little before we get a bunch of half assed horrible android tablets. I just wish they would put a hardware requirement and requires companies to update their devices at least once (like 2.2 -> 2.3) in a timely manner (like 2-3 months after the code is pushed to AOSP)
So have been thinking. As we did a pretty good #NeverAgain campaign way back to get Froyo to our Vibrants we could try a new approach.
We may be waiting for Samsung and T-mobile to come out with Gingerbread for the our Vibrants. I don't know what the chances for this is. But if they are planning on retiring the Vibrant (or already have) than there shouldn't be anything that keeps Samsung from releasing the sourcecode for the Vibrant. The good press that Samsung would get by releasing the source code (and I'm talking about the kernel) for the Vibrant, can be tremendous. If they are not planning on using it, than great if they release the source. If they do plan on releasing it, but also hand it over to the developers like the CM team, how much more grateful will we be as their power user group.
Keeping on the developers good side should be important for Samsung and the other manufacturers, as that also leads to a very happy power user group. Which in turn refers their products to their friends and families.
So just checking to see what the interest would be for us people that are left with the Vibrant would be involved in making a campaign like this to succeed?
#bashingsamsungandtmobileoverandoverisntgoingtogetusanythingandsinceyounameditspecificallyforthevibranttherewontevenbethatmuchsupportevenontheneveragainthepeoplefromfascinatecaptivateetccameoverandhelpedout
xriderx66 said:
#bashingsamsungandtmobileoverandoverisntgoingtogetusanythingandsinceyounameditspecificallyforthevibranttherewontevenbethatmuchsupportevenontheneveragainthepeoplefromfascinatecaptivateetccameoverandhelpedout
Click to expand...
Click to collapse
You made some spelling mistakes
But yes its pointless to do that, once something is used with success it won't touch the crowd the same/losses its meaning
Sent from my SGH-T959 using Tapatalk
iwillkillyou said:
You made some spelling mistakes
But yes its pointless to do that, once something is used with success it won't touch the crowd the same/losses its meaning
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
I agree. The first campaign worked because it was something new and half way legitimate. If they are working on GB for us, a year after release, I don't think we have much ground to complain. Not that you can't, feel free, but now people are starting to hit the down hill slope of looking forward to their next upgrade.
Just my opinion.
Edit: I am 'tarded
The Vibrant is powerful enough to maintain a long lifespan. There really are only about 2 phones I'd consider a strong enough upgrade to even consider jumping ship.
Ice Cream Sandwich isn't far away. Since it's meant to work on all devices (phones, tablets, pc's, etc)... I really hope drivers aren't the reason I can't use this phone for long time to come..
Well, that and AT&T. BOO.
As much as we love this phone it won't live forever. We can't beg for every update
Sent from Moto Atrix
joshyy_rey said:
As much as we love this phone it won't live forever. We can't beg for every update
Sent from Moto Atrix
Click to expand...
Click to collapse
I know we can't ask for the update. Don't really care. But we know they are sitting on the code and if they are not planning on giving us GB at least they could give us the code. Especially the kernel so that CM can get a perfectly working CM7 for the Vibrant.
swehes said:
I know we can't ask for the update. Don't really care. But we know they are sitting on the code and if they are not planning on giving us GB at least they could give us the code. Especially the kernel so that CM can get a perfectly working CM7 for the Vibrant.
Click to expand...
Click to collapse
The problem is that if it's not finished (which is very likely) and we use the code a lot of misinformed people will complain about how we were given buggy code. Then the conspiracy theorists will assume that Samsung sabotaged the code just to get people to hate their phones and want to buy a new one.
All of this will go back to Samsung and they will be labeled as bad for not knowing how to program, or hurting development, or being evil, or ...
Perfect world they could just make all their code transparent for us all to see as soon as it happens, but they would rather be like every other company and hold out on giving out source until they feel it is ready than risk being hurt by trying to help out.
If the code was finished they would be pushing for an update. I doubt they have anything complete for the vibrant.
I just started #lovemesomelesbianasianfootfetish.
LET'S CHANGE THE WORLD!!!!!111!one!!!1!eleventy
TheSneakerWhore said:
I just started #lovemesomelesbianasianfootfetish.
LET'S CHANGE THE WORLD!!!!!111!one!!!1!eleventy
Click to expand...
Click to collapse
Lol, this made me laugh. Thank you. I hit the button but I hit my cap
Sent from my GT-I9000 using XDA Premium App
Why need it be so hard to support the developers working on Samsung phones....releasing code that is impossible to work with....as on the sgs2 for example.....there are ways to work with and support those working on porting phones...Sony Ericsson has made that effort to support the community....so should Samsung....they make great phones wich could be even greater.....if only they embraced the community and made an effort to work with, and not against......
Sent from my GT-I9100 using Tapatalk
maybe you should research before you post pointless threads that have nothing to back up your points.
Samsung have arguably been the most developer friendly company.
If you're talking about releasing proprietary drivers then what the fk can SAMSUNG do about it? It isn't theirs, they can't give something that doesn't belong to them.
$1 gets you a reply
So then there is no way to make it easier to get things working without releasing proprietary drivers .......then i give up on believing there is a way to get a working port to the sgs2.....but as i refuse to accept that reality , i still believe there are things possible to be change.
To make it easier without releasing proprietary drivers ......
Well people could make their own drivers, but I believe they'd need the full architecture map and the details outlining. Moreover testing and refining would take an immense amount of time.
It's slightly more complicated that this in the software world.
1 - as soon as samsung release anything they become responsible for it, i.e. they also need to release manuals, maybe maintain, support etc.
2 - samsung have how many different active handsets ? And each of them needs to be supported. It's one HELL of a job. I wouldn't be surprised if they just don't have time or don't want to spend money to support community.
Either you have no idea or your just impatient,Think about Samsung,there one of the world largest electronics company's in the world,while your sat at home drinking coffee or tea,there bashing out a new product and ideas to try and make electronic lives that more easier,from TVs,Phones,Fridges,Microwaves,laptops,sound systems,mp3s,hardware for other manufacturers,every second of the every day there working on something,its amazing they have anytime to actually release stuff like this but they do it,they try and support our device as much as they can despite having a patent war with apple at the same time.There about 10 different variants of this device,each one is slightly different,each one has there own different hardware,each one needs there own drivers,each one also needs supported,S2 is also not the one they need to support,Theres S,Nexus S,Galaxy Nexus,ACE,W,R,all need supporting so when they release the code when they do,you have a think of what else there doing and be more grateful they do it compared with say htc,who only manufacture mobiles but are tight arses,Samsung even sent several Galaxy s2 to CyanogenMod to he could bring his software onto the device,they didnt have to but they did.If they didnt care,they wouldnt do any of this,There not perfect but trust me they do try
http://codeworkx.de/wordpress/
And i agree with you about all they are manufacturing and that they have a lot to do....and need not support all of the products if so needed....
Sent from my GT-I9100 using Tapatalk
NickoPulver said:
Why need it be so hard to support the developers working on Samsung phones....releasing code that is impossible to work with....as on the sgs2 for example.....there are ways to work with and support those working on porting phones...Sony Ericsson has made that effort to support the community....so should Samsung....they make great phones wich could be even greater.....if only they embraced the community and made an effort to work with, and not against......
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
wtf are you talking about? Please state how Samsung's released code for the I9100 is impossible to work with. Yes, apparently the original source release had some stability bugs (see Ninphetamine kernel thread), but Samsung fixed that MONTHS ago with update1...
Samsung is, in my opinion, the most developer-friendly manufacturer out there. Download mode (Odin) makes it almost impossible to hardbrick, and they're now the only major manufacturer that is not locking their bootloaders. They also usually release kernel source BEFORE a product even officially launches.
Entropy512 said:
Samsung is, in my opinion, the most developer-friendly manufacturer out there.
Click to expand...
Click to collapse
LOL.
ROFL.
ithehappy said:
LOL.
ROFL.
Click to expand...
Click to collapse
duno why your laughing, they are, not only did they even hire the founder of cyanogen, but they also sent the cyanogen devs a bunch of SGS2's when they first come out so that they would support the SGS2.
I don't understand why Samsung sent team Hacksung free SGS IIs only to hold them up by not giving them what they need to develop on them.
d3ck4rd said:
I don't understand why Samsung sent team Hacksung free SGS IIs only to hold them up by not giving them what they need to develop on them.
Click to expand...
Click to collapse
Good point there my friend.
ithehappy said:
LOL.
ROFL.
Click to expand...
Click to collapse
Name a manufacturer who has done a better job.
HTC? Locked bootloaders, kernel sources withheld for extremely long times.
Motorola? Locked bootloaders
LG? Don't really know - at least in the US, their devices tend to be such bugridden **** (such as the battery-hogging Thrill) that you'd spend months just getting to the point of a stock Samsung firmware.
Samsung donated devices to the Cyanogenmod team and gave them nearly everything they needed to port the device - the only thing that isn't working very well in CM7 is Bluetooth, and you can blame Broadcom for that. Broadcom are ****ing douchebags when it comes to open source, they are one of the LEAST developer-friendly companies on the planet. Unfortunately it seems like these days, your only choices for Wifi/Bluetooth implementations are either the BCM4330, TI's WLAN solution (which is tightly coupled to OMAP), or some wacky niche player (Samsung tried to do that with the Infuse and the STE CG2900 - that epicfailed for them.)
If you're referring to ICS - for ****s' sake, Samsung hasn't even released their own ICS firmware yet. The sense of entitlement on these forums is getting to be utterly ****ing ridiculous. It's almost unheard of for an AOSP bringup to be successful to an Android version higher than the latest manufacturer release.
Entropy512 said:
Name a manufacturer who has done a better job.
Click to expand...
Click to collapse
Sony Ericsson has actually helped with development for CM7, I think they take the cake .
Samsung is pretty cool too for donating phones to devs. Maybe they'll even help them develop in the future. One step at a time
NickoPulver said:
Why need it be so hard to support the developers working on Samsung phones....releasing code that is impossible to work with....as on the sgs2 for example.....there are ways to work with and support those working on porting phones...Sony Ericsson has made that effort to support the community....so should Samsung....they make great phones wich could be even greater.....if only they embraced the community and made an effort to work with, and not against......
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
So what would you like us to do? Petition them?
What outcome would you like?
If the code is "impossible to work with" then why are there so many kernels out there based on their code?
Also, your ENTER key says "hi", and your period key says "ouch".
Sammy might have lots of smartphones and lots of stuf to worry about and its all that story about proprietary drivers, software and all that crap, but the truth is if they wanted, it wasnt that dificult to help the team.
If you do a little search in the forum u will see devices sucessfully running AOSP cm9 alpha on Android 4.01 which is higher than the latest manufacturer release, since only nexus have ics lolol
d3ck4rd said:
I don't understand why Samsung sent team Hacksung free SGS IIs only to hold them up by not giving them what they need to develop on them.
Click to expand...
Click to collapse
That was just very very cheap advertising
Sent from my HTC Desire HD using xda premium
Why would Samsung even release ICS drivers for SGS2 when they are working on their own ICS release for it? You don't give out the plans to something that you are about to bring out to the market before you launch it. Think about that.
I have to agree. The sense of entitlement is a bit crazy.
Hello you all
mods, feel free to move our delete my post if you feel it's in the wrong section
I am planning to buy the find 5, but I want to be sure this is the right buy for me. I know the performance is awesome and the screen is one of the best or there, so +1 for those, but now for development support. I see there it's a fresh new cm10.1 so that seems ok but are you developers going to keep this phone for a long time? The price tag is pretty hefty for me and I want to keep the phone for a few years. Any change for long term development here? With android 5, and up support? Fast kernels?
Thank you so much
Sent from my HTC Desire C
Phenziox said:
Hello you all
mods, feel free to move our delete my post if you feel it's in the wrong section
I am planning to buy the find 5, but I want to be sure this is the right buy for me. I know the performance is awesome and the screen is one of the best or there, so +1 for those, but now for development support. I see there it's a fresh new cm10.1 so that seems ok but are you developers going to keep this phone for a long time? The price tag is pretty hefty for me and I want to keep the phone for a few years. Any change for long term development here? With android 5, and up support? Fast kernels?
Thank you so much
Sent from my HTC Desire C
Click to expand...
Click to collapse
ask Oppo, but they might not guarantee it, or go back on their word
eg: motorola promises android update, then reneges on it
developers do porting on their free time, if you want to guarantee something (like having Android version x), do it yourself........ bootloader is unlocked - you can install anything you want on it
paperWastage said:
ask Oppo, but they might not guarantee it, or go back on their word
eg: motorola promises android update, then reneges on it
developers do porting on their free time, if you want to guarantee something (like having Android version x), do it yourself........ bootloader is unlocked - you can install anything you want on it
Click to expand...
Click to collapse
Yeah I wasn't really talking about oppo itself, more of xda support
Sent from my HTC Desire C
Phenziox said:
Yeah I wasn't really talking about oppo itself, more of xda support
Sent from my HTC Desire C
Click to expand...
Click to collapse
as I said, devs work on this on their free time
no dev will tell you: "I will work on this forever and not sell it.. if it breaks, i'll get a new one to continue support"...
if you want android 5.x, learn how to port
paperWastage said:
as I said, devs work on this on their free time
no dev will tell you: "I will work on this forever and not sell it.. if it breaks, i'll get a new one to continue support"...
if you want android 5.x, learn how to port
Click to expand...
Click to collapse
Yup. So far, I see myself as far less likely to wind up in the "OMFG I HATE THIS DEVICE AND I AM SICK OF DEALING WITH IT" category like all of the Exynos4 CM maintainers did.
That said, if I get spread too thin, the device might receive less attention in the future.
A lot depends more on Qualcomm than on Oppo.
Entropy512 said:
Yup. So far, I see myself as far less likely to wind up in the "OMFG I HATE THIS DEVICE AND I AM SICK OF DEALING WITH IT" category like all of the Exynos4 CM maintainers did.
That said, if I get spread too thin, the device might receive less attention in the future.
A lot depends more on Qualcomm than on Oppo.
Click to expand...
Click to collapse
Well, you got that right
The exact reason why I was planning to skip on the s3
And to be clear, I wasnt trying to demand support, just asking whether it was there or not
And I saw the full source code was available so this seems like a good source to learn development xD
Thank you
Sent from my HTC Desire C
Security setting FC
Security setting FC
Oppo has been great about getting the find it developers hand. They have given out almost ten free devices. So there will be Roms, not as much as a nexus but a few. Again in the long term support won't be as good as a nexus but it uses a qualcom chip so support is easy, not nexus easy but second best. I say it will be supported as long as the nexus four dependent on binary issues.
Sent from my PG86100 using Tapatalk 2