• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Offical Moment Update

I'll be picking up my phone shortly.

The tech I spoke to said that the issues he had were related to getting the right drivers installed on the workstation that they use for updates. Once he got the driver issue worked out, the update stopped hanging in the middle and only took a few minutes.

-SF
 
Well I got mine back and my phones all sorts of jacked up. Contacts are dupped, market wont download anything, wifi wont connect. Im 2 days into quitting smoking so the timing couldnt be worse for my blood pressure.
 
I work at a Sprint Repair Center. I will be going in tomorrow to try the update on my phone, and yes ICSS is tied to a USB hub. I don't think he was trying to do the update though, there's another program used for that.
 
Hey, all! I've been lurking for a while now and just registered to let you know that my Moment was successfully updated to CL14 today. The techs at the Sprint store in the Town Center Plaza in Overland Park, KS, know what they're doing. So far I'm noticing that it's faster, but that might just be because all my apps were wiped out. Now I'm busy reinstalling everything. Fun times!

cool .. i tried the Olathe, KS and they gave me a 2 hr window that I couldnt make .. the TCP store is the closest to Sprint HQ .. maybe Hesse employs the best techs near his office ... and I couldnt believe there are 12 repair centers in a 5 mile radius here ... I guess one benefit of living next door to Sprint campus ...
 
Just to chime in, I live in Socal-- Just called 2 service stores that I know get heavier traffic; the first one said that OTA updates were going to be available at some point today (but I don't think he really knew). The second store said they were having problems and weren't doing the updates there at all, to try back later. Anyone with a success story yet?
 
Just to chime in, I live in Socal ... Anyone with a success story yet?
I'm here in SoCal, too- and am lately in both North SD County and LA/OC. I was going to head to the Poway repair center today but decided to check here first, and after the reports here I think I'll wait 'till I get home tomorrow and try the Irvine Culver store (they seem to have their isht together there, but not exactly sure if they're a repair center).

Which stores did you try?

It's amazing this is going so badly- I never had this issue with updating my Treos.
 
I'm here in SoCal, ..... I think I'll wait 'till I get home tomorrow and try the Irvine Culver store (they seem to have their isht together there, but not exactly sure if they're a repair center).

Which stores did you try?

Ha. The first one I tried was the Irvine store (the ones who told me the OTA was available.. but not). The second one I called was the Harbor Blvd store in Costa Mesa.
 
Ok....

I'm a newbie, and maybe I need to have more time under my belt before a rant like this....

But WTF?!!!

Seriously, half of Sprint doesn't know about this, there's a quarter that know about it and don't know how to get it on the phone...

And they don't tell us moment users.

Then their update messes up some phones.

You guys provide more tech support than those guys...

Thank you!!!

As for the update, I don't feel like it's worth the risk. I would rather have outdated software that functions, than updated software that didn't and couldn't be fixed because sprint locked up the way it was fixed.

Plus I don't understand what's the big deal with keeping the software all hush hush, can't share.
Is sprint afraid of losing trade secrets or income on OPEN SOURCE software that also runs on several different networks?
And it's supposed to be updated again soon.... so what's the point?

It's our phone, we bought it, let us do with it as we please!
 
Crap- by the Daphne's? That was gonna be my backup plan. :)

Hm, maybe I did call that one. I thought I was calling the sprint store on Harbor right by Merimac, a few doors down from the 7-11.

Hope that was helpful to everyone else here in the forum. :D
 
cool .. i tried the Olathe, KS and they gave me a 2 hr window that I couldnt make .. the TCP store is the closest to Sprint HQ .. maybe Hesse employs the best techs near his office ... and I couldnt believe there are 12 repair centers in a 5 mile radius here ... I guess one benefit of living next door to Sprint campus ...

is that the one in the middle target, chicago's, and AMC 30

Oh... and I know MORE about sprints phones and release dates and stuff better than BOTH my parents the work for sprint
 
Ok....

I'm a newbie, and maybe I need to have more time under my belt before a rant like this....

But WTF?!!!

Seriously, half of Sprint doesn't know about this, there's a quarter that know about it and don't know how to get it on the phone...

And they don't tell us moment users.

Then their update messes up some phones.

You guys provide more tech support than those guys...

Thank you!!!

As for the update, I don't feel like it's worth the risk. I would rather have outdated software that functions, than updated software that didn't and couldn't be fixed because sprint locked up the way it was fixed.

Plus I don't understand what's the big deal with keeping the software all hush hush, can't share.
Is sprint afraid of losing trade secrets or income on OPEN SOURCE software that also runs on several different networks?
And it's supposed to be updated again soon.... so what's the point?

It's our phone, we bought it, let us do with it as we please!

They have released the notice via twitter, their community help, their announcement and other avenues... just because it hasn't hit "mainstream" yet doesn't mean they havent announced it... obviously you know about it so they must have done some notification
 
Is sprint afraid of losing trade secrets or income on OPEN SOURCE software that also runs on several different networks?
Unfortunately, yes. ... and this is one of the biggest misconceptions about an "Open Source" handset that people don't understand.

The only part about the phone that's actually "Open Source" is the core Android software- things like the Launcher screen, or the notification pulldown, etc. But at the same time, there's literally hundreds of parts that are proprietary and/or trade-secret to the various companies that make up the SW that goes into a typical handset- from things like Google's closed-source "Android Market", to Sprint's closed-source Navigation, to Samsung's proprietary kernel-drivers for things like the audio (and in the case of a typical example for another Android phone, Qualcomm's kernel drivers and spec sheets for the MSM7201 CPU, and HTC's proprietary bootloader(s) on the G1/ADP/Nexus1/Hero/...).

These companies, for whatever reasons, have decided to keep these parts closed to protect their intellectual property. But these parts are necessary to make a phone that's worth having (case in point- the "radio" for each phone is heavily chipset-dependent, and ain't no way the manufacturer's going to give that huge bulk of software away). Also, there's a lot of work that goes into making these parts work with the core Android software, too- and that's an investment they might feel they'd want to keep to themselves.

This is why when you get folks like that one guy who said "Just download the SDK" we know he's full of isht, or why it takes talented people like Zefie and those guys at XDA so long to eke out custom roms (that in many cases are lacking in certain functionality).

(Even when you're an insider they don't give you everything you need- I'm a contract software developer working with a couple of large handset and chipset manufacturers and I've spent plenty of hours just trying to get from them what I need to do the job those same companies are paying me to do!)
 
Social Engineering. Say "Oh, that is a shame, I already have a copy, I got it from the hacking community, and it worked. I just wanted to see if it was the same thing. Can I at least see the screen?" (or if on the phone, ask for the name of the software) With any luck he will at least show you the screen or tell you the name, and we can go from there :)

Good Job Zelphie!

My bet is that they stole your code. Come on, Samsung releases it and it bricks phones. Do you really think that these guys came up with this on their own--I don't!!!

Had any job offers yet??? I'd think Sprint would fly you to KC and offer you a job by now--they are idiots if they don't..

Keep up the good work!!!
 
Just have to chime in...

Took my phone in, updated and working as expected based on what I know of the dev community reports. Didn't take long, like 30 minutes or so.

Location services working as they should. Phone does not seem faster or slower. Battery meter undetermined at this point. GPS locks as fast as it did before (about 20-30 seconds)
 
Unfortunately, yes. ... and this is one of the biggest misconceptions about an "Open Source" handset that people don't understand.

The only part about the phone that's actually "Open Source" is the core Android software- things like the Launcher screen, or the notification pulldown, etc. But at the same time, there's literally hundreds of parts that are proprietary and/or trade-secret to the various companies that make up the SW that goes into a typical handset- from things like Google's closed-source "Android Market", to Sprint's closed-source Navigation, to Samsung's proprietary kernel-drivers for things like the audio (and in the case of a typical example for another Android phone, Qualcomm's kernel drivers and spec sheets for the MSM7201 CPU, and HTC's proprietary bootloader(s) on the G1/ADP/Nexus1/Hero/...).

These companies, for whatever reasons, have decided to keep these parts closed to protect their intellectual property. But these parts are necessary to make a phone that's worth having (case in point- the "radio" for each phone is heavily chipset-dependent, and ain't no way the manufacturer's going to give that huge bulk of software away). Also, there's a lot of work that goes into making these parts work with the core Android software, too- and that's an investment they might feel they'd want to keep to themselves.

This is why when you get folks like that one guy who said "Just download the SDK" we know he's full of isht, or why it takes talented people like Zefie and those guys at XDA so long to eke out custom roms (that in many cases are lacking in certain functionality).

(Even when you're an insider they don't give you everything you need- I'm a contract software developer working with a couple of large handset and chipset manufacturers and I've spent plenty of hours just trying to get from them what I need to do the job those same companies are paying me to do!)
Pretty sure the most important part of the phone (the kernel) is covered under the GNU GPL... as in.. the linux kernel that runs the entire phone..
This is what we need bad in cl14 to see what they attempted to change

Amazingly enough the GNU GPL does not protect proprietary parts of the kernel.. infact it specially says these are required to be open source no matter what if they utilize GNU
 
Back
Top Bottom