Database Users

"Sprint expects to launch Android 2.2 in the near future" (except Hero and Moment)

"Sprint expects to launch Android 2.2 in the near future" (except Hero and Moment)
A bit misleading... Link goes to Sprint's BAW forum where the excitement quickly turned to anger about Sprint abandoning currently shipping phones and users stuck in contracts. Despite the headline, only the Evo will be getting the 2.2 upgrade from Sprint.
Originally Posted by twitter.com/sprint:
Sprint expects to launch Android 2.2 in the near future - http://bit.ly/d0HRgj
Click to expand...
Click to collapse
From Sprint link...
SprintEmployee JGatSprint says:
... 2.2 will not be available for HTC Hero or Samsung Moment
Click to expand...
Click to collapse

I thought that when 2.2 was announced at the big Google press event, HTC's CEO was quoted as saying that all currently shipping HTC phones would be getting the upgrade...? I'll see if I can dig up that quote.
Ah, nevermind. I found the quote and it was regarding 2.1.

I just saw the tweet, and I don't think it includes the hero, but I did hear something on that about them getting 2.2..
Sent from my HERO200 using XDA App

cool! good job for sprint!

radxcoresteven said:
I just saw the tweet, and I don't think it includes the hero, but I did hear something on that about them getting 2.2..
Click to expand...
Click to collapse
No, you heard that all currently available Android phones would be getting the 2.1 update. That was when all us Hero owners were clamoring for the 2.0 upgrade.

Oh, and the good news is that we don't need HTC or Sprint to do this for us. We're fortunate enough to have a community of developers that are working hard to put out a Froyo update compatible with the Hero. Remember to tip them well, kiddos, because Sprint just left you behind. Oh, and tell your Sprint rep that this is why you rooted your phone.

They're melting down over at the official sprint forums.

gunnyman said:
They're melting down over at the official sprint forums.
Click to expand...
Click to collapse
Drop a bomb that size, you better expect nuclear fallout. If darchstar, damageless and TrevE can get Froyo on the Hero, Sprint and HTC could as well. They just want people to keep upgrading. Good business sense; poor customer support.

All you need to do is have enough of publicity about this and they'll have to do something about it.
Imagine top tech headlines;
"Sprint drops support for currently shipping phones... refuses to update firmware", "Would you trust Sprint again...", "Angry Sprint Android owners demand a refund"
...and the last one "Sprint agrees to update older android phones’ software after many complaints from customers"

obsanity said:
All you need to do is have enough of publicity about this and they'll have to do something about it.
Imagine top tech headlines;
"Sprint drops support for currently shipping phones... refuses to update firmware", "Would you trust Sprint again...", "Angry Sprint Android owners demand a refund"
...and the last one "Sprint agrees to update older android phones’ software after many complaints from customers"
Click to expand...
Click to collapse
Good luck with that. I'm not sure they care. It's business. Besides, like I said, just tell them these types of decisions are why *ahem* some dude you know *cough* rooted his phone and he knows some guys that are working on putting 2.2 on the Hero right now.

subcypher said:
Oh, and the good news is that we don't need HTC or Sprint to do this for us. We're fortunate enough to have a community of developers that are working hard to put out a Froyo update compatible with the Hero.
Click to expand...
Click to collapse
Posts like this are a pet peeve of mine. Not to discredit the great work that the community dev's do, but community generated ROMs that are cobbled together from other devices are NOT the same as vendor-genuine ROMs from HTC/Sprint. While in MANY ways the community ROMs are far superior, they lack the hardware-specific code (kernel drivers, etc...) that only the OEM can provide. Consistently, the most stable and fully-functional community ROMs are those based off of hardware-accurate vendor ROMs (like Fresh, based off of the shipping RUU). The ROMs derived from other devices are far more likely to have caveats such as "fully-functional except for the camera, sensors, martini shaker, ..." (I don't know what part of the term "FULLY-functional" is unclear to some devs).
While it is inevitable that the community devs WILL create a 2.2 ROM, it will not be of the same caliber that would be possible with a genuine vendor ROM to use as a starting point.

i guess you havent run. darchdroid heh
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

cmccracken said:
Posts like this are a pet peeve of mine. Not to discredit the great work that the community dev's do, but community generated ROMs that are cobbled together from other devices are NOT the same as vendor-genuine ROMs from HTC/Sprint. While in MANY ways the community ROMs are far superior, they lack the hardware-specific code (kernel drivers, etc...) that only the OEM can provide. Consistently, the most stable and fully-functional community ROMs are those based off of hardware-accurate vendor ROMs (like Fresh, based off of the shipping RUU). The ROMs derived from other devices are far more likely to have caveats such as "fully-functional except for the camera, sensors, martini shaker, ..." (I don't know what part of the term "FULLY-functional" is unclear to some devs).
Click to expand...
Click to collapse
Darch Droid is fully functional now. Took some time to get things figured out but now that he knows how to get it working. It shouldn't be any issue on future releases...once we get kernel code.
Not to mention that, our drivers are there in these roms, just quirky.

cmccracken said:
Posts like this are a pet peeve of mine. Not to discredit the great work that the community dev's do, but community generated ROMs that are cobbled together from other devices are NOT the same as vendor-genuine ROMs from HTC/Sprint. While in MANY ways the community ROMs are far superior, they lack the hardware-specific code (kernel drivers, etc...) that only the OEM can provide. Consistently, the most stable and fully-functional community ROMs are those based off of hardware-accurate vendor ROMs (like Fresh, based off of the shipping RUU). The ROMs derived from other devices are far more likely to have caveats such as "fully-functional except for the camera, sensors, martini shaker, ..." (I don't know what part of the term "FULLY-functional" is unclear to some devs).
While it is inevitable that the community devs WILL create a 2.2 ROM, it will not be of the same caliber that would be possible with a genuine vendor ROM to use as a starting point.
Click to expand...
Click to collapse
Doth mine ears deceive me? Are you saying that just because an Android developer works for HTC and Sprint that he's better than the hobbyists that hang out here? I think you missed the whole point of open source.
And, yes, fully-functional may take some time, but it usually happens. Kernel and drivers always come out and are adjusted as needed. As gunnyman said, Darchdroid 2.7 is fully functional. My point is that they're doing what they're doing and doing it well. Sprint/HTC could do it, but they're choosing not to, forcing users to upgrade. Again, one of the benefits of open source.
So, why the pet peeve? I'm just curious. I'm not sure if you're serious or trolling. You're on these forums, so either you're into custom ROMs or you're some kind of troll. If you're into ROMs, why are you bashing devs, because whether you meant to or not, that's what you're doing with this post. You're basically saying, "Cool painting, Picasso, but you'll never be Monet." WTF?

subcypher said:
Good luck with that. I'm not sure they care. It's business. Besides, like I said, just tell them these types of decisions are why *ahem* some dude you know *cough* rooted his phone and he knows some guys that are working on putting 2.2 on the Hero right now.
Click to expand...
Click to collapse
I gotta keep this phone until next March so I'm kinda stuck unless I wanna shell out 500 for another phone with this one is 2.5 months old. Well, I don't want to and I can't afford to play this game. So, when we get a 2.2 for the Hero that works like it's supposed to I can hopefully stick with Flipz FreshROM and i'm donating at least 50 to that guy. Between him, Damage and all the other guys with the time and skill to do this they've earned 100x that.

subcypher said:
And, yes, fully-functional may take some time, but it usually happens. Kernel and drivers always come out and are adjusted as needed. As gunnyman said, Darchdroid 2.7 is fully functional. My point is that they're doing what they're doing and doing it well. Sprint/HTC could do it, but they're choosing not to, forcing users to upgrade. Again, one of the benefits of open source.
Click to expand...
Click to collapse
cmcraken has a point though, Darchdroid is only fully functional because it is based on the 2.1 RUU made specifically for the hero. Until that RUU hit the streets, every previous 2.1 ROM was handicapped in some form or other. If Sprint/HTC doesn't develop a 2.2 RUU specifically for the Hero, the best the devs will be able to do is get us as close as possible, but never spot on.

subcypher said:
Doth mine ears deceive me? Are you saying that just because an Android developer works for HTC and Sprint that he's better than the hobbyists that hang out here? I think you missed the whole point of open source.
Click to expand...
Click to collapse
I'm saying that the community developers will never have access to the resources that the vendor devs do. They will never have access to the low-level engineering data that the vendors keep behind locked doors, nor the source code for things like SenseUI. Reverse engineering can only get you so far.
I understand full well what the point of open-source is. the problem is that these phones as a whole are definitively NOT open-source. Only a small portion of the total package is open-source, and even a major portion of that (the Linux kernel source code) is a colossal PITA to get our hands on. Despite the open-source sales pitch on Android phones, they aren't very open-source in implementation.

cmccracken said:
I'm saying that the community developers will never have access to the resources that the vendor devs do. They will never have access to the low-level engineering data that the vendors keep behind locked doors, nor the source code for things like SenseUI. Reverse engineering can only get you so far.
I understand full well what the point of open-source is. the problem is that these phones as a whole are definitively NOT open-source. Only a small portion of the total package is open-source, and even a major portion of that (the Linux kernel source code) is a colossal PITA to get our hands on. Despite the open-source sales pitch on Android phones, they aren't very open-source in implementation.
Click to expand...
Click to collapse
I see your point and concede to you on this. Well played, sir. I think, though, that given the status of what has come before, that we can expect great things from reverse engineering. Hopefully, with the things I've been reading about Google and Android specifically, that things will change with Froyo. I've heard rumblings about making Android one package, the things HTC wants to do another package and the things Sprint wants to do a third package, that way Android updates can continue and the other guys have to keep up if they want us using their stuff.
Longshot? Yes. The way it should be? Yes.

subcypher said:
Longshot? Yes. The way it should be? Yes.
Click to expand...
Click to collapse
Ditto. The vendor support (or lack thereof) and OS fragmentation is absolutely killing Android. 1.5 million iPhone 4's sold so far despite it being inferior to the Evo on all fronts. The reason? Apple. They fix bugs for their devices and provide added functionality via regular software updates. iOS 4 is provided as an upgrade to the iPhone 3G, released July 2008. Sprint can't even provide updates for a phone that's less than a year old. These Android vendors have got to get on the same page and start playing by Apple's rules if they want to compete with Apple.

subcypher said:
Drop a bomb that size, you better expect nuclear fallout. If darchstar, damageless and TrevE can get Froyo on the Hero, Sprint and HTC could as well. They just want people to keep upgrading. Good business sense; poor customer support.
Click to expand...
Click to collapse
100% agree

Possible reason for the update delays

Dunno if you guys have seen this. I didn't notice because I usually only hang around here but it just got posted to reddit so I saw it.
http://forum.xda-developers.com/showthread.php?t=913045
If true, it would definitely explain a lot of things. It does make me dislike Samsung, but hopefully the carriers can strong-arm Samsung into doing what everyone else is doing.
Personally, I bought this phone because it was either this or the Droid X, and the difference was that while the DX might have Froyo now, the odds of Motorola putting Gingerbread on it are less than 100%, and the odds of it getting anything after that are even lower, and with the locked bootloader you can't do anything about it. With the Fascinate, at least we can look forward to community built ROMs for some time into the future, definitely past what Samsung is willing to do (I figure they're never going to even consider putting Gingerbread on the Fascinate what with the LTE phones coming out soon, and SAMOLED+ and all that). People should probably avoid Samsung unless they specifically want the nice hardware and easy hacking, in which case it seems like Samsung is the most lax with security so they're the best choice for hacking.

Hmm, very enlightening, of it's true of course. Sounds entirely plausible though. Oh well, I really don't care anymore, not with kaos and friends on the job.
Sent from my SCH-I500 using XDA App

This is what we all expected.
But the question is... Why was it released with Eclair when Froyo was released before this phone was released.

wasn't the reason it was released with eclair because of the 1.6 ril or whatever? from what i read, the ril would barely work with eclair and no way for it to work with froyo.
my understanding is that a large part of the magic that kaos is doing was to build a functional ril.

They arent building a new ril. They are hacking android around the current crap ril Samsung gave us.

Don't buy it.
Sent from my SCH-I500 using XDA App

upsidedownaaron said:
wasn't the reason it was released with eclair because of the 1.6 ril or whatever? from what i read, the ril would barely work with eclair and no way for it to work with froyo.
my understanding is that a large part of the magic that kaos is doing was to build a functional ril.
Click to expand...
Click to collapse
That's what jt's been doing, and he ended up just hacking the current Samsung RIL to work. And if you follow his twitter, he said that the RIL from Eclair, Froyo, and Gingerbread on the Android side didn't change much which is why they're jumping straight to Gingerbread instead of wasting time with Eclair.

upsidedownaaron said:
wasn't the reason it was released with eclair because of the 1.6 ril or whatever? from what i read, the ril would barely work with eclair and no way for it to work with froyo.
my understanding is that a large part of the magic that kaos is doing was to build a functional ril.
Click to expand...
Click to collapse
Um, wow, what have you been reading? First off, our phone came with 2.1, not 1.6, so I'm not sure where you got that number from.
Secondly, the reason that we (not Samsung) could not build a ROM not based on the stock OEM ROM was because the source code for the RIL that Samsung provided for the Fascinate was bad code, which made it extremely difficult to create a working RIL what will work with a custom OS. However, jt1134 and punk.kaos were able to reverse engineer the bad code into working code, in order to proceed with ROM building.
This has nothing to do with Samsung themselves though. Samsung built the RIL to begin with, so they most certainly can (and have) created RIL code that works with Froyo, quite a long time ago in fact. They released the Galaxy S line with Eclair because that was likely the newest version available when they began developing the OS for those phones. In order to convert the OS to Froyo to launch it on the phone, they would have had to significantly delay the launch, which was not an option. This is likely why so many phones are released with outdated versions of Android. And I would like to point out that if they just put Google's code on there and didn't insist in polluting it with their own proprietary junk, it wouldn't take so long to release in the first place, and wouldn't be so difficult to upgrade later.
Getting back on topic, I figured that the problem with getting these updates really all comes down to money. People have always had to pay for OS upgrades for PCs, but due to Android and iOS, have now come to expect to receive these updates for free. The problem is, somebody has to develop an upgrade process, and test the heck out of it, and those developers have to get paid. So the OEM pays them, and then naturally tries to pass the cost along to the carrier, because they don't want to work for free. The carrier also doesn't want to pay for the upgrade, but also knows they can't get away with charging their customers for it without significant backlash, so they basically just sit there and hope the problem eventually goes away, or that the OEM will finally back down and release the update for free, which is what's been described as our current situation.
If this is really such a big problem, they could be taking steps to not end up in this situation, such as figuring the cost of these upgrades into the price of the phones and/or rate plans. However, the carriers also have added incentive to not push for the upgrades, because that effectively extends the life of the handset, and they want you to keep buying new hardware all the time, since they make money from selling hardware, and lose money on the free upgrades.
In the end, it's all about money. Thankfully we have such a great community of developers here on XDA that are willing to go the extra mile to not only get us our upgrades, but also add cool features and boost the performance way beyond what the manufacturer gave us. Thanks to that, our hardware's lifetime is determined not by when a carrier or OEM pulls support, but rather by when the devices physically die or break, or the hardware becomes too outdated for the tasks we wish to perform. And this way, through donations, we can pay our developers for good upgrades, not our carrier for crappy, bloated ones.

Im not saying its true but the most legitimate explanation for all this bull**** I have actually heard in a while. So for what its worth Im not going to shoot that down. Possibly true at this point.
Sent from my fascination station using XDA App

ivorycruncher said:
Um, wow, what have you been reading? First off, our phone came with 2.1, not 1.6, so I'm not sure where you got that number from.
Click to expand...
Click to collapse
Mrbirdman said it himself, actually. (1.5, but close enough).
http://twitter.com/#!/_mrbirdman_/status/3002051533479936
Anyway, I don't know whether to believe this but it explains why no US carriers have Froyo yet. It's kind of frustrating that Verizon is the only carrier that hasn't even had a leaked Froyo build it seems. Damn ingrates spoiling leaks for the rest of us.

Ah, I see. Thanks for the link. I admit that tweet came before I followed him on twitter, so I hadn't seen that. I can see how that would complicate matters though.

This is the last farkin' time I ever buy a Samsung phone. Shame on me for believing their lies when they said they'd support it.

If that user is really violating an NDA, he's already fired, and the XDA admins would be hearing from lawyers demanding they remove the thread.
Sounds like it's just more trumped up bull**** designed to stir up the masses. Who knows really, but all I know is I wasn't stupid enough to purchase a phone based on future "promises."

Jake_Mongoose said:
This is the last farkin' time I ever buy a Samsung phone. Shame on me for believing their lies when they said they'd support it.
Click to expand...
Click to collapse
You might wanna rethink that. Why, you ask? Because Samsung puts out some of the best hardware available, especially the screens, and we always have devs that can hack up the code to make it better than it ever would have been with a stock ROM. HTC isn't too bad, though the issue with rooting the G2 is certainly raising some eyebrows, but if you were thinking about Motorola, have fun with your locked bootloader and other fun tricks that attempt to squash community development. Aside from lousy source code, Samsung phones are the easiest to root and customize due to the unlocked bootloader. You can basically just flash anything you want with ODIN, no problem.

It is not necessarily the case in the future because Tab reportedly has locked boot loader. This said people already found workaround, but who knows?..

That is true. Nobody knows what the future holds. In any case, if you have no problem loading custom software from XDA devs on your phone, then OEM software support should not even be on the list of requirements when buying a phone. I now make my phone purchasing decisions purely based on hardware specs and quality. If it's a quality piece of hardware with the features I want, on my carrier of choice (Verizon), I will buy it, regardless of manufacturer or UI. Warranties and insurance work the same no matter who makes it, and software updates come from XDA, so nothing else really matters. But then again, that's just my opinion.

ivorycruncher said:
That is true. Nobody knows what the future holds. In any case, if you have no problem loading custom software from XDA devs on your phone, then OEM software support should not even be on the list of requirements when buying a phone. I now make my phone purchasing decisions purely based on hardware specs and quality. If it's a quality piece of hardware with the features I want, on my carrier of choice (Verizon), I will buy it, regardless of manufacturer or UI. Warranties and insurance work the same no matter who makes it, and software updates come from XDA, so nothing else really matters. But then again, that's just my opinion.
Click to expand...
Click to collapse
Yup, this is how I've decided to make phone decisions from now on as well. As long as the phone's software can be replaced by XDA, I don't care too much about the manufacturer's updates.

J Shed said:
If that user is really violating an NDA, he's already fired, and the XDA admins would be hearing from lawyers demanding they remove the thread.
Click to expand...
Click to collapse
It is easier to hide posting on a forum than it is sending a tip into an online news outlet, at least in general. Also, by posting it in a forum, it is entirely likely that it will be up for longer than it would be if posted at say, Engadget, because it takes longer for news to show up in major outlets if posted in a forum first as opposed to a news site. If it were posted at Engadget or another tech blog, they are likely watched over very closely for potential NDA breaches, etc. I doubt Samsung looks are random forums/subforums/threads nearly as close.

IF it were $$ couldn't we as users pay like $20 for Froyo...
x 3 million phones = more than enough to pay for DEV

I don't buy it.
Why?
Because these companies work off of contracts. Verizon would know exactly what they were getting into before signing. If Samsung decides to breach said contract, fine, let Verizon sue the hell out of them. Lastly, Verizon would not have sold or marketed docks that rely on 2.2, if they had no intention of releasing it.
Actually one more thing. If US Carriers were refusing, Samsung would halt development. We are seeing new leaks for the other US models all the time, and Verizon is still being worked on (but not leaked).
This is a case of where 2+2=5=false.

We gotta laugh it off, right?

http://www.gottabemobile.com/2011/03/24/samsung-mesmerize-android-2-2-update-now-available/
I check back here and poke through Google News 'Samsung Fascinate' searches pretty much daily and at this point, I'm pretty sure we're one of, if not THE last Galaxy S phone, to be on 2.1. At this point, we just have to laugh about it, right? Then I read articles like this and it makes me remember the angry "WTF " feeling... but what's the point in being pissed off. It'll get here when it gets here, right?

We don't need Verizon anymore. The Mesmerize's code is compatible enough with the Fasicnate that we don't need an official release... plus, their source is already out. Hell, we've been using their leaked kernels for a while now (EB16 and EC10 are both mez kernels).

Us Continuum users are still on 2.1
Sent from my SCH-I400 using XDA Premium App

trailblazer101 said:
Us Continuum users are still on 2.1
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
Adryn said he will work on Continuum, but not sure when.

Well, not to lessen the Continuum state, but you guys do have that funky Ticker thing with all of it's own settings I can actually understand something like that holding up the Verizon/Samsung ability to push out an update. But the Fascinate?
It's just mind-blowing that two multi-billion dollar companies are such a miserable failure in this department. The Froyo SDK came out over 10 months ago. Some team, some where, should've lost their jobs ages ago and been replaced with competent individuals.
Ok, back to laughing

True.. its gotten to the point of being so ridiculous that I really do almost laugh out loud at the whole thing these days. Still though I do feel extremely frustrated at the fact that the two big companies involved just seem to refuse to give a straight answer regarding an update - if an update is coming out for sure.. ETA.. status.. etc.. That part of it just drives me crazy.

Very true. I am waiting and hoping for ASOP or MIUI to be fully functional now.

So why the hell did Samsung drop this phone, essentially, and all the other phones are fine? This is a great phone.
Samsung Fascinate, Verizon
EB01 Superclean 2.4
Kenesis' TransMyst GBKB (EPIIIIIC)
Mob87's Honeycomb Theme
Stock Kernel

If you didn't notice the froyo versions that leaked have all had their own issues and caveats. Knowing Verizon, they would never allow a release of flawed software so I refuse to be angry about the lack of an official release. Those of us knowledgeable enough and willing to tolerate have been using it for months and with Kaos, Adryn, JT and our other AMAZING Fascinate devs we will have GB, MIUI and AOSP as well as all the wicked kernels we could possibly want ahead of anything we would ever get from sammy. I always put my faith in these ambitious and innovative people over some billion dollar team that never faces us.
Sent from my SCH-I500 using XDA Premium App

I gotta say I released a bit of a chuckle when I saw on Twitter that Samsung released Froyo for the Mesmerize the other day. I was like, "The MESMERIZE? REALLY?"
But oh well.

Hatespawn said:
Knowing Verizon, they would never allow a release of flawed software so I refuse to be angry about the lack of an official release.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I'm not one to correct, but wasn't the next to last official VZW release the one with the 911 puzzle lock bug? VZW has always been a pain in the butt for updates, but never, NEVER, this nad. IMO, this all falls on Samsung and their incompetence. I get done what I need done just fine from my SC 2.9.2 and stopped waiting for anything official a long time ago. All owning the fascinatehad done is solidify the fact that Sammy won't get another dime of mine. What actually makes me laugh is the BS that Samsung PR puts on here to attempt to make users happy.

From what I understand, Samsung has already released the update to Verizon, but it didn't have Bing integrated...so then Verizon's one guy in some back room closet has to integrate Bing before they can release it. Of course, any dev on here could do that in a day....

I wouldn't go stock if they did release it. I am digging Launcher Pro on SC 2.9.2 Voodoo. I have my wifi hotspot and google and NO VZW crap. Everything on my phone is working better than before and I have no lag, waits or FC. I honestly don't mind the UI of touchwiz but the implementation is piss poor in the quality department and I don't expect that to change with the next rev. I'm a happy man going to save a few duckets for Adryn he is a deserving soul.

Yep I'm with Joey - at this point even if they do come out with an official release, I dont think I could go back to a stock 'bloat rom' after trying out a rooted phone with a fast cool SC-Voodoo setup developed here by the dev community. AWESOME!

running DR v3 voodoo
EC10v
launcher pro plus
loaded the apk's that i like
battery life is good / to GREAT
Samsung / Verizon = i will be voting with my money when it comes time to upgrading my phone & service
because of leaks i am currently happy with my Fascinate

Imo I would say this definetly falls on samsung and verizon not giving the ok on an update that would have its own issues. Ive never been a fan of samsungs touch wiz interface, but I think this is a really good example of phone makers tweaks on android really effecting users getting to experience there devices as they should. Sammy has always been little slow on updates to there phones. Love there displays and there TVs are the best. I just wish they would pay as much attention to devices already launched as they do pushing out new devices. Seeing that droid x is on the verge of getting gingerbread it makes me sick thinking that fascinate is still on froyo. I keep.secretly hoping that thsy will surprise us all and just skip froyo with the vzw update and push out gingerbread for it. If they do.end up putting a froyo update out for the fascinate I guess a gingerbread update would be out of the question because who knows how lonh that would take

Samsung , has a bunch of bs programers, and poor project management. If our devs out code theirs, why haven't they been hired? Because, they'd have to eat humble pie. My guess, is that if you paid close enough attention, you find that samsung borrowed quite a bit of code from our devs. Why else would they "leak" code? They are having problems solving their own, self made hacks of miss placed code and purpose built convolutedness, so why not get someone else to fix it for free.
Just my 2¢
Sent from my SCH-I500 using XDA App

http://www.gottabemobile.com/2011/0...ung-intercept-froyo-update-coming-april-11th/
And now the Intercept. Against, I don't know if it's Verizon or Samsung, but at this rate I'm leaning towards Verizon being the weak link here.
Must... maintain... laughing...

At this stage, it really doesn't much matter who's to blame. We'll never know whole truth and nothing but the truth. All I can say is TY to XDA and their team!!

dfa7 said:
At this stage, it really doesn't much matter who's to blame. We'll never know whole truth and nothing but the truth. All I can say is TY to XDA and their team!!
Click to expand...
Click to collapse
Far as I've seen, it's looking like they're being held back by Verizon and Bing stupidity as much as Samsung amd Verizon.
Sent from my MIUI SCH-i500

The truth about the bootloader

http://www.vampii.com/dcom/componen...-x-bootloader-already.html/blogger/czerdrill/

Indeed I saw a presentation from a guy who worked for a major phone hardware company recently about recent advances in 'locking down' hardware. They are getting better and closing more loopholes with every generation. 2048-bit encryption, complete trust chains, burying sensitive traces, chip-swapping detection and on and on. Even digging right into the hardware it is getting harder and harder to find weaknesses if the manufacturer is determined to lock something down.
If you look at older phones like Droid X and Milestone that still haven't cracked there is almost no chance the Atrix has a weakness unless someone majorly goofed or there is a leak.

Well there is one 4th option that I think that what devs are trying to do and, IMO, is the real meaning of cracking: Finding a security hole and exploit it.
But as haloimplant already mentioned that's highly unlike to happen...

Unfortunately nothing said was news to me. I gave up a long time ago when my Milestone never got cracked.
Mods still make the phone fun, but it's night and day different of what you can do with say a Galaxy S...

Until applications stop supporting Froyo/Gingerbread/ICS/whatever the final update Motorola pushes is, I dont see the need for a custom kernel. Stuff like 2init that allow everything but the kernel to change would be enough for almost everything you'd want to do. As long as Motorola pushes semi-recent kernels, we should be ok.

From what I've read, in the bootloader bounty topic, we have something close to release.
Bootloader might not ever get cracked completely, but there are certainly ways around it. Look at the iPhone, they can modify it with various levels of exploits. (iBoot, ramdisk, userland) and they don't have it cracked completely.
Also, number 3 on that list could be pure speculation, or it could be complete truth. There could be hundreds of people that know it, or just 1.

PixoNova said:
From what I've read, in the bootloader bounty topic, we have something close to release.
Bootloader might not ever get cracked completely, but there are certainly ways around it. Look at the iPhone, they can modify it with various levels of exploits. (iBoot, ramdisk, userland) and they don't have it cracked completely.
Also, number 3 on that list could be pure speculation, or it could be complete truth. There could be hundreds of people that know it, or just 1.
Click to expand...
Click to collapse
+1. Us Atrix users obviously don't have the userbase that iDevices have, but we have the *new* nVidia chipset, there are bound to be holes. Some talented dev needs to find it. But we have like 1/20 the users that iDevices have. And like 1/1000 of those are devs. But coming as a jailbreak dev on the iPhone. Im gonna take a plunge and see myself.
Sent from my screaming Atrix *4G* using the XDA App

Jotokun said:
Until applications stop supporting Froyo/Gingerbread/ICS/whatever the final update Motorola pushes is, I dont see the need for a custom kernel. Stuff like 2init that allow everything but the kernel to change would be enough for almost everything you'd want to do. As long as Motorola pushes semi-recent kernels, we should be ok.
Click to expand...
Click to collapse
Motorola will have an "Official Gingerbread" out this year. Will they have an "Official ICS"? Highly doubtful
There will be partial ICS available through mods, but why play the waiting game when the update is available and easy to flash? Most of the waiting is for sales/marketing purposes anyway.
^ Look at the HTC Desire, Froyo was available to be installed early last summer. One major carrier didn't release it till Halloween. Guess what, the "Official version" was the exact same as the leaked version (I used both to compare). Then there's the T-mobile Galaxy S "Froyo incident" (which everyone knows that story by now). Verizon Fascinate, (the list goes on and on).
The average Joe will sit around and wait for an OTA, but the average XDA user knows better.
That's why any exploits found on the Bootloader will still better than nothing...

PixoNova said:
From what I've read, in the bootloader bounty topic, we have something close to release.
Click to expand...
Click to collapse
Seriously? Will it allow us to finally get rid of blur via another Rom?

Want to start a #PleaseShareYourSourceCode for the #Vibrant #Samsung

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