Related
It seems that a lot of companies are really taking advantage of twitter to communicate with customers at large. Some examples are Verizon and HTC announcing the Eris OS update, Sprint has announced items via twitter. Lot's of people follow these companies and I am sure that these companies search twitter for references to there name.
So I propose that we use the power of twitter to send a clear message to Sprint that we would like an Android 2.0.1 update and that we would like some sort of news confirming it. We don't need exact deadlines but just knowing that it's coming would be great news for the community. It would also benefit Sprint in the long run because potential and current customers would have a little bit more faith in buying a Hero at 179.99 knowing that it will be getting an update.
I am going to post this to a few other Sprint/Hero related forums. Everyone can start twitting now or we can try to get some clear defined message written out that we can all retweet. Please post any thoughts, inputs or messages that you have twitted @Sprint.
My twitter ID is kennyidaho.
You do know that HTC announced we would be getting 2.x on Twitter about a month ago, right?
http://twitter.com/htc/statuses/5243593307
Flipz beat me to it.
I was googling for the article where HTC Confirmed it. They wouldn't bother with the update for CDMA Hero if Sprint wasn't going to give it to us. It costs them too much money to build an OS/Rom for a phone just in case Sprint ever asks for it.
Yes but nobody knows for sure if this applies to CDMA Hero's (we do know that it applies to GSM Hero's because of the leaked ROM - is there any proof a CDMA rom has been created?). HTC control's the update process on GMS Hero's, however Sprint has to request and push an update to Sprint Hero's. HTC is primarily a GSM manufacture and will cater to those devices first.
Assuming that HTC's announcement regarding Android 2.0 applies to carrier branded devices is as naive as assuming that the successor to the Hero (to be announced in February) applies to Sprints Hero.
Trust me I would like to hope it's true. Having Sprint and HTC devices in the past I know that just because HTC updates it's GSM equivalent it does not always indicate CDMA devices will receive the update (or will be updated in a timely manner).
Well if its been confirmed well what's the harm of twittering Sprint
No harm...
Just seems like a waste, one way or another we will have a 2.1 update.
Kcarpenter said:
No harm...
Just seems like a waste, one way or another we will have a 2.1 update.
Click to expand...
Click to collapse
Myself and I am sure many others grow tired of the waiting game with these devices. In the end the main goal really is to see sprint open up a little bit.
If Sprint has ordered the update, if it's in testing and is slated to be released sometime first quarter 2010 then what's the harm in telling us? Verizon can notify it's customers that their Droid Eris, which is basically the same phone as the Hero, is getting updated - Sprint can take that risk too!
Right now Verizon is blitzing the media with Droid this Droid that, update this update that. What's sprint doing? A 5 second mention on a commercial also advertising the Pre and Tour?
Kcarpenter said:
No harm...
Just seems like a waste, one way or another we will have a 2.1 update.
Click to expand...
Click to collapse
just saying, in the time it took you to type that out and post it here, you could just as easily have tweeted something to sprint about getting the update.
how are you so absolutely positive that we'll get it? do you know something the rest of us don't?
all i'm saying is that it's not a waste to tell them what you want, whether or not you already know you're going to get it.
I agree totaly. We make huge investments in these devices, especially those of us who don't get them by signing a new contract. Personally I have to have the coolest gadget on the market, its my kryptonite. To that note also, Sprint does have the best service converage and price in my area. So I can't afford necessarrily to go else where. Damned if you do Damned if you don't. We are at the mercy of the phone company and until we get the portablity openness in the U.S. that our European counterparts have, we are stuck with what we get.
That being said, the Devs on this forum and else where make the phone what its worth, not Sprint. Luckily in our case, "There is always someone smarter than you". Meaning Sprint can hold out all they want, we will get ours eventually. I am sure we can yell and scream and cause a fuss, but I don't see the merit behind it. Kind of like getting upset with the Customer Serivce reps at sprint when we call to ask the status of the update, you can yell at them all day long and nothing will get accomplished other than making them pissed and ruining their day.
Just Twitter don't be upset just ask nicely, what id they respond back with next week. Then the debate can hold off on thief build and relax
Gah, I even went out and made a twitter account for you guys. Now knowing I have a twitter account gives me the chills... I feel like a 'myspace' person now.
@sprint and @htc right???
@kcarpenter5407
Kcarpenter said:
Gah, I even went out and made a twitter account for you guys. Now knowing I have a twitter account gives me the chills... I feel like a 'myspace' person now.
@sprint and @htc right???
@kcarpenter5407
Click to expand...
Click to collapse
Hey Twitter is nothing like having a MySpace account, granted most people mis use by updating about nothing. I follow cnn, some journalist that I like and some online stores and ESPN plus a couple sports teams. Which has Me do less surfing cause all the info comes straight to me
If u decide to give Twitter a try may I suggest if you find someone intresting follow them and check out who they are following
I don't see any harm in this... I'm going to twitter Sprint here in a few
I was being slightly facetious.
Well HTC posted a response nothing from sprint
Noob here.
I'm having to make a financial decision and when my contract ends with Verizon in April, I'm going to switch to Straight Talk. I would love to afford the biggest and best, but I cant, so I'm having to go with something a bit less. My question is, has anyone been able to flash or convert their standard Verizon phone to work with Straight Talk? I'm wondering whether it be a regular phone, windows mobile/smartphone, or android, if anyone has been able to pull this off, and if so, how? I enjoy getting my phone and other devices to do more than allowed at original purchase and think this would be fun to do when I make the switch. Please let me know if anyone has done this and how. Thanks!
anyone with any info on this subject?
An issue like this requires a bit more than rooting, or 'unlocking' the phone. What your looking at doing is essentially jailbreaking the phone. This CAN be a complicated process.
I don't know for sure that whether or not there is an area in XDA committed to doing this. My suggestion at this point would be to google jailbreak (your phones name).
depending on the phone, this isnt always possible. On top of this, there are potentially features that your phone has that will not be supported once jailbroken.
Good luck.
EDIT: I should mention that, depending on the phone, you may not be able to do this. Certain phones REQUIRE that you have not only a talk plan, but a data plan as well. These are usually newer smart phones.
StraightTalk Now Had Android Phone
With straight talk now offering an android phone, will this help in converting my OG Droid to straight talk?
HELP i did succeed in flashing phone,everything works great. but the problem is i started gettin text messages from 31778 and 55330, and it only gives a series of numbers. can you help me with this issue? thanks
Mind sharing or pm'ing me on how you got it to work? I got a donor st phone and 2 fascinates from verizon. I successfully got the esn changed, *22890 to work. I can browse the net and receive texts. sending text says fail but still go through. The calls won't go out, get a autho error. If I am outside my market it will send/receive calls fine but soon as I cross back into it quits working. Occasionally it will even recieve a call and work but then it goes back to autho failure. Any idea where I went wrong?
Verizion or sprint android phone to straight talk on verizon towers
Still looking for anyone who is working on this project. I have found several people selling this service. Anyone have more information to share.
Thanks
Do you guys not search? this thread was orig posted back in Dec asking about flashing VZW to ST, but this guide had been posted already for months, was posted back in August... pretty much has everything you need to do for VZW to ST flashing:
http://forum.xda-developers.com/showthread.php?t=1210240&highlight=+straight+talk+
justan00b said:
Do you guys not search? this thread was orig posted back in Dec asking about flashing VZW to ST, but this guide had been posted already for months, was posted back in August... pretty much has everything you need to do for VZW to ST flashing:
http://forum.xda-developers.com/showthread.php?t=1210240&highlight=+straight+talk+
Click to expand...
Click to collapse
ha thats the same thing i was going to post so i can do that method on DROID 1?
But that thread is more specifically aimed at the Fascinate, and it's ilk, than the X or X2's. If anyone has more detailed procedures pertaining to the MB870 please don't hesitate to PM me.
Thread lightly cleaned of ESN discussion. Keep that out of here... Time to reset and get on topic. Final warning.
^^ .... So like I was saying... I'd Just your contract run out, give em a call and tell em that if they want to keep your business switch your phone over to Straight talk. They want your money no matter what but until you push them they won't do squat for you...
Hi everyone,
I maintain a firmware archive for all Nexus and "Google Experience" devices from the OG Droid up through present day. Now that I'm a GS4 owner, I've decided to start archiving Galaxy S4 firmware for US variants on my site as well. As I'm not as familiar with Samsung naming conventions and terminology as I am with Google ROMs, I was hoping some of you Samsung software junkies out there could take a look at my pages to make sure I'm using all my terminology correctly.
Here is a sample Nexus firmware page: http://www.randomphantasmagoria.com/firmware/nexus-7.
Here is my new Galaxy S4 page: http://www.randomphantasmagoria.com/firmware/galaxy-s4.
Make sure to click through to the detail pages.
My rule for the firmware archives are that I do not deal with unofficial stuff whatsoever. I don't do leaked ROMs or anything of the like. I only archive whatever was officially released to the general public, both shipping on new devices and OTA updates. The idea is to be able to follow the strict official release chain from launch to end-of-life. Also, all firmware is indexed on the site by the official firmware name in build.prop.
As you can see, right now I only have a page up for the AT&T I337 variant (the one I own). Right now, I'm displaying the Android version, build, PDA, CSC, links to the ODIN packages and links to the OTA updates if available. Are there any other pieces of info you think I should show on those detail pages? Also, I'm showing the OTA updates as "<new> from <old>" which is how Google names its OTA files. I know that Samsung sometimes does "<old> to <new>" (especially in the yakju(xx) OTA files for the Galaxy Nexus). Which one do you guys think I should go with?
Any feedback you guys could provide would be greatly appreciated. Once I've settled on a final layout, I'll create pages for Sprint, Verizon, T-Mobile, and US Cellular. I'll also add pages for Cricket and C Spire when those devices actually launch. Why am I only doing US devices? Because there are a lot of international device variants and each one of them can have a ton of different firmware variants depending on the country in which it was purchased. It's way too much for one man to manage. Managing 7 US variants will be enough work as it is. haha
So anyway, click around and please provide feedback.
Thank you!
Hi everyone,
I maintain a firmware archive for all Nexus and "Google Experience" devices from the OG Droid up through present day. Now that I'm a GS4 owner, I've decided to start archiving Galaxy S4 firmware for US variants on my site as well. As I'm not as familiar with Samsung naming conventions and terminology as I am with Google ROMs, I was hoping some of you Samsung software junkies out there could take a look at my pages to make sure I'm using all my terminology correctly.
Here is a sample Nexus firmware page: http://www.randomphantasmagoria.com/firmware/nexus-7.
Here is my new Galaxy S4 page: http://www.randomphantasmagoria.com/firmware/galaxy-s4.
Make sure to click through to the detail pages.
My rule for the firmware archives are that I do not deal with unofficial stuff whatsoever. I don't do leaked ROMs or anything of the like. I only archive whatever was officially released to the general public, both shipping on new devices and OTA updates. The idea is to be able to follow the strict official release chain from launch to end-of-life. Also, all firmware is indexed on the site by the official firmware name in build.prop.
As you can see, right now I only have a page up for the AT&T I337 variant (the one I own). Right now, I'm displaying the Android version, build, PDA, CSC, links to the ODIN packages and links to the OTA updates if available. Are there any other pieces of info you think I should show on those detail pages? Also, I'm showing the OTA updates as "<new> from <old>" which is how Google names its OTA files. I know that Samsung sometimes does "<old> to <new>" (especially in the yakju(xx) OTA files for the Galaxy Nexus). Which one do you guys think I should go with?
Any feedback you guys could provide would be greatly appreciated. Once I've settled on a final layout, I'll create pages for Sprint, Verizon, T-Mobile, and US Cellular. I'll also add pages for Cricket and C Spire when those devices actually launch. Why am I only doing US devices? Because there are a lot of international device variants and each one of them can have a ton of different firmware variants depending on the country in which it was purchased. It's way too much for one man to manage. Managing 7 US variants will be enough work as it is. haha
So anyway, click around and please provide feedback.
Thank you!
Looking for help obtaining a galaxy s8 plus for development purposes, Specifically the SM-G955F variant. Please donate, like share and help me get this a success! Not your average story. I've gotten a few roms to work on the s7 active as no ones ever done it or taken an interest at least. Was also the first to confirm different carrier roms to work on the G920P like tmo and Verizon roms. Would love to get my hands on this beauty to get root, dev some roms and make some awesome tweaks. any donations would be great! https://www.gofundme.com/3o4u02w
Don't be "that guy"
It's a hard sell when you are asking us to buy you a phone to possibly dev for and yet you don't even have recognized dev beside your name. No offense but I just can't see this being taken seriously.