Jump to content

Nexus S 4G regains AOSP status


nels0300

Recommended Posts

This is cool, maybe the Sprint Galaxy Nexus is next? I got rid of my EVO for this phone so I had something to hold me over until LTE comes to Minneapolis. This phone could turn out to be the only "4G" phone on Sprint (for most people) with Jelly Bean.

 

http://www.engadget.com/2012/07/03/nexus-s-4g-regains-aosp-status/

  • Like 1
Link to comment
Share on other sites

Certainly good news for nexus s owners. Hopefully they are just being coy about the galaxy nexus. I was under the impression that the WiMax support or CDMA radio support were the largest hurdles. NFC? Are they kidding?

 

Sent from my Jelly Bean Toro using Forum Runner

Link to comment
Share on other sites

I recently bought a good esn Nexus S with a broken screen off ebay for $20. Bought a replacement screen for $40 that will be here Friday. Looking forward to checking out some AOSP goodness.

 

Sent from my LTEless Evo LTE using Tapatalk 2

Link to comment
Share on other sites

I almost caved yesterday and got an S3, but something came up and I couldn't make it to the sprint store. After I heard this news, I think I'll hold onto the nexus S 4G. I was thinking about it, and you could make a case for the nexus S 4G being the best phone on the sprint network right now. It is the only Nexus phone with AOSP status with access to the more mature 4G network. Obviously this will change in a year or so, but RIGHT NOW, the Nexus S 4G is sitting pretty, and will be even prettier when Jelly Bean rolls out.

Link to comment
Share on other sites

I almost caved yesterday and got an S3' date=' but something came up and I couldn't make it to the sprint store. After I heard this news, I think I'll hold onto the nexus S 4G. I was thinking about it, and you could make a case for the nexus S 4G being the best phone on the sprint network right now. It is the only Nexus phone with AOSP status with access to the more mature 4G network. Obviously this will change in a year or so, but RIGHT NOW, the Nexus S 4G is sitting pretty, and will be even prettier when Jelly Bean rolls out.[/quote']

 

Unless you classify HSPA+ as 4G (I don't) the Nexus S 4G is the only 4G phone with AOSP support. Disclaimer: I don't consider WiMax 4G either.

 

Sent from my Jelly Bean Toro using Forum Runner

Link to comment
Share on other sites

Unless you classify HSPA+ as 4G (I don't) the Nexus S 4G is the only 4G phone with AOSP support. Disclaimer: I don't consider WiMax 4G either.

 

I have a strong minded, engineering based perspective on the definition of 4G. It may be best we keep that Pandora's box closed.

 

AJ

  • Like 2
Link to comment
Share on other sites

I have a strong minded, engineering based perspective on the definition of 4G. It may be best we keep that Pandora's box closed.

 

AJ

 

Marketing... but what happens when they FINALLY achieve 4G speeds? Are they going to try to call it 5G?

Link to comment
Share on other sites

Unless you classify HSPA+ as 4G (I don't) the Nexus S 4G is the only 4G phone with AOSP support. Disclaimer: I don't consider WiMax 4G either.

 

Sent from my Jelly Bean Toro using Forum Runner

 

Whether or not the Nexus S 4G is on a true "4G" network, it's on a faster network than they guy or gal next to me with the brand new EVO or Galaxy S3 here in Minneapolis and many other cities and now it'll have the newest operating system from google (not a cobbled together rom) before them too. Kinda cool for a two year old phone.

  • Like 1
Link to comment
Share on other sites

 

 

Have you had bad experiences with custom ROMs?..

I've never used a custom from for a few reasons, #1 the possibility of wrecking your phone, #2 voiding your warranty, and #3 it seems there is always something that doesn't work, no 4G, camera doesn't work, messaging doesn't work,etc.
Link to comment
Share on other sites

I've never used a custom from for a few reasons, #1 the possibility of wrecking your phone, #2 voiding your warranty, and #3 it seems there is always something that doesn't work, no 4G, camera doesn't work, messaging doesn't work,etc.

 

I understand where you are coming from, but dismissing every single custom ROM for every single device as something "cobbled together" is what is dramatically limiting your choice of phones.

Link to comment
Share on other sites

 

 

I understand where you are coming from, but dismissing every single custom ROM for every single device as something "cobbled together" is what is dramatically limiting your choice of phones.

. I know. I read up on it when I had my og evo because it ran so poorly after its last gingerbread update not playing nice with sense. I realized I didn't know what I was doing and I am too lazy to figure out which from would work 100%. Now that I have a nexus, I prefer stock android. The nexus s 4G has essentially the same specs as my og evo, but it runs so much better (although I miss the evo radio). I might still get a phone with a custom skin, but I'd prefer not to.
Link to comment
Share on other sites

I've never used a custom from for a few reasons' date=' #1 the possibility of wrecking your phone, #2 voiding your warranty, and #3 it seems there is always something that doesn't work, no 4G, camera doesn't work, messaging doesn't work,etc.[/quote']

 

The jelly bean rom I am running on my gnex is perfect. Not one thing that doesn't work. I can understand why some people choose not to root/unlock/run custom rom but:

 

It is really rare to hard brick your phone unless you are trying to do crazy experimentation or don't follow developer instructions.

 

It is nearly impossible for the service center to prove that you rooted/rommed the phone and declare your warranty void.

 

Most ROMs with non-working items are in the pre-beta/beta stage. CM9 for example, is in the release candidate stage for most devices. Most bugs are gone at that point and all functions should be working. Manufacturers go through all these stages too and have to fix functions that aren't working. I will concede that there are some amateur devs out there that never get their rom out of beta stage because they either lack the time or knowledge to reverse engineer non-open source components like wimax.

 

Like I said though, I can completely understand people not wanting to mess with their OS. That said, I believe it is a great disservice to developers who spend countless hours working on ROMs with no incentive other than the small amount of donations and the thanks of the people who use the ROM to say that they are mostly junk. The development community keeps devices relevant long after the manufacturers have abandoned them.

 

I see the development community much like the S4GRU website. Any donations go back into the costs of running the website, and there are a lot of man hours being poured into the various things that the site provides (maps being the largest one) because Robert feels that sprint fans deserve to know about the latest news that sprints LTE rollout. Some information may be off, but you wouldn't dismiss the whole site because of a couple pieces of bad info. Right?

 

Again, this is not meant to be an attack of any kind, but just a PSA of sorts.

Link to comment
Share on other sites

. I know. I read up on it when I had my og evo because it ran so poorly after its last gingerbread update not playing nice with sense. I realized I didn't know what I was doing and I am too lazy to figure out which from would work 100%. Now that I have a nexus, I prefer stock android. The nexus s 4G has essentially the same specs as my og evo, but it runs so much better (although I miss the evo radio). I might still get a phone with a custom skin, but I'd prefer not to.

 

After my experience with gaining S-OFF and flashing Sense ROMs on both Evo 3D and Evo 4G LTE, I would say an afternoon of reading XDA would be sufficient to brush up on all the terminology and best practices. Permabricking is extremely rare when following directions. Warranty is usually not an issue since you can always re-lock and flash a stock RUU. Most mature ROMs are actually at least as stable as stock while having better battery life and / or performance and much more customization.

Link to comment
Share on other sites

The jelly bean rom I am running on my gnex is perfect. Not one thing that doesn't work. I can understand why some people choose not to root/unlock/run custom rom but:

 

It is really rare to hard brick your phone unless you are trying to do crazy experimentation or don't follow developer instructions.

 

It is nearly impossible for the service center to prove that you rooted/rommed the phone and declare your warranty void.

 

Most ROMs with non-working items are in the pre-beta/beta stage. CM9 for example, is in the release candidate stage for most devices. Most bugs are gone at that point and all functions should be working. Manufacturers go through all these stages too and have to fix functions that aren't working. I will concede that there are some amateur devs out there that never get their rom out of beta stage because they either lack the time or knowledge to reverse engineer non-open source components like wimax.

 

Like I said though, I can completely understand people not wanting to mess with their OS. That said, I believe it is a great disservice to developers who spend countless hours working on ROMs with no incentive other than the small amount of donations and the thanks of the people who use the ROM to say that they are mostly junk. The development community keeps devices relevant long after the manufacturers have abandoned them.

 

I see the development community much like the S4GRU website. Any donations go back into the costs of running the website, and there are a lot of man hours being poured into the various things that the site provides (maps being the largest one) because Robert feels that sprint fans deserve to know about the latest news that sprints LTE rollout. Some information may be off, but you wouldn't dismiss the whole site because of a couple pieces of bad info. Right?

 

Again, this is not meant to be an attack of any kind, but just a PSA of sorts.

 

Didn't mean to rip any developers. I guess what I mean is I'm not ROM savvy enough to be messing around with an expensive piece of equipment and I'm too lazy to learn. If it was as simple as plugging it in to my computer and dropping a few files in some folders, I could handle it, but from what I've read, there's more to it than that.....and there are always warnings about doing it at your own risk.

 

I'd love it if I could get a new S3 with completely stock ICS.

Link to comment
Share on other sites

 

Didn't mean to rip any developers. I guess what I mean is I'm not ROM savvy enough to be messing around with an expensive piece of equipment and I'm too lazy to learn. If it was as simple as plugging it in to my computer and dropping a few files in some folders' date=' I could handle it, but from what I've read, there's more to it than that.....and there are always warnings about doing it at your own risk.

 

I'd love it if I could get a new S3 with completely stock ICS.[/quote']

 

Oh, yeah, I didn't mean that you were ripping developers. I just have a lot of respect for the service they provide.

 

Sent from my Jelly Bean Toro using Forum Runner

  • Like 1
Link to comment
Share on other sites

Didn't mean to rip any developers. I guess what I mean is I'm not ROM savvy enough to be messing around with an expensive piece of equipment and I'm too lazy to learn. If it was as simple as plugging it in to my computer and dropping a few files in some folders, I could handle it, but from what I've read, there's more to it than that.....and there are always warnings about doing it at your own risk.

 

I'd love it if I could get a new S3 with completely stock ICS.

 

They always have to put that disclaimer, however, once you get a custom recovery on your device, flashing roms is simple and a fun way to see different things your device can do.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...