Jump to content

Sprint Galaxy Nexus jelly bean port

pyroscott

By pyroscott
in Samsung

 Share

Recommended Posts

pyroscott Member Level: LTE Advanced

pyroscott

Posted
Posted

The ACS forums have a jelly bean port for Sprint's version of the Galaxy Nexus. The developer claims that it is fully working, but always backup before flashing.

 

http://forums.acsyndicate.net/showthread.php?5535-ACS-ROM-4-1-JRN84D-Galaxy-Nexus-Jellin-RC_1&fb_action_ids=253224554793555&fb_action_types=og.likes&fb_source=aggregation&fb_aggregation_id=288381481237582

 

Sent from my Jelly Bean Toro using Forum Runner

  • Like 2
Link to comment
Share on other sites
pii100 Member Level: 3G EVDO

pii100

Posted
Posted

You sure about that, it looks like they are saying it includes the stock JB kernel and gapps. But I'll defer to you since it looks like you're already up and running. Got a rooted kernel you recommend?

Link to comment
Share on other sites
pyroscott Member Level: LTE Advanced

pyroscott

Posted
  • Author
Posted
You sure about that' date=' it looks like they are saying it includes the stock JB kernel and gapps. But I'll defer to you since it looks like you're already up and running. Got a rooted kernel you recommend?[/quote']

 

Well, I'm not actually using that ROM. I'm using the Verizon version that the Sprint ROM is based on.

 

I am using faux 19 kernel. I am out of it today, I re read the post and it includes franco kernel on vzw oops

the Sprint version seems to have stock as you said...

 

Sent from my Jelly Bean Toro using Forum Runner

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.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • dkyeager
      FCC Auctions

      By dkyeager · Posted

      https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Trip
      SignalCheck Beta Crew Forum

      By Trip · Posted

      Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • RAvirani
      Network Vision/LTE - New York City Market

      By RAvirani · Posted

      Forgot to follow up on this. The service was once again abysmal .
    • Grabber5.0
      Official Tmobile-Sprint merger discussion thread

      By Grabber5.0 · Posted

      Paying employees would have been nice 

  • Recently Browsing

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