Jump to content

GNEX and airave issues continue


hescominsoon

Recommended Posts

  • 1 month later...
Note 2, S3, and EVO LTE here work fine on the Airave version before the 2.5.

 

Speaking of which. Recently Sprint and Airave Inc passed 2 Airave's thru the FCC. I forgot to start a post on it.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Link to comment
Share on other sites

  • 4 weeks later...

I hope they actually release an airvana that actually works without all the various bugs..airvana 1.0 was texting errors..2.0 was faulty gps..and 2.5 just simply doesn't work right at all..:)  Any timetable for the release of these airaves?

Link to comment
Share on other sites

I hope they actually release an airvana that actually works without all the various bugs..airvana 1.0 was texting errors..2.0 was faulty gps..and 2.5 just simply doesn't work right at all..:) Any timetable for the release of these airaves?

 

Nope. It could be anywhere up to the end of this year of maybe never. Just because it passes the FCC doesn't guarantee release. Sad to, because some people get all excited for something, and then it never gets released.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Link to comment
Share on other sites

I hope they actually release an airvana that actually works without all the various bugs..airvana 1.0 was texting errors..2.0 was faulty gps..and 2.5 just simply doesn't work right at all..:) Any timetable for the release of these airaves?

 

 

Nope. It could be anywhere up to the end of this year of maybe never. Just because it passes the FCC doesn't guarantee release. Sad to, because some people get all excited for something, and then it never gets released.

 

 

 

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Sounds like CES.

 

Sent from my little Note2

 

 

  • Like 1
Link to comment
Share on other sites

After deploying about 10 or so airaves around where I work (half were version 2.5 the other half were 2.0). I can tell you the 2.5's just work and work reliably. The 2.0's will die about once every two weeks requiring a restart. Of course this is a small sample... Anyone seen any differences from my observation?

 

Also, has anyone had any luck getting an airave to Sprint network handoff to work reliably on any phone?

 

Sent from my EVO LTE

 

 

Link to comment
Share on other sites

After deploying about 10 or so airaves around where I work (half were version 2.5 the other half were 2.0). I can tell you the 2.5's just work and work reliably. The 2.0's will die about once every two weeks requiring a restart. Of course this is a small sample... Anyone seen any differences from my observation?

 

Also, has anyone had any luck getting an airave to Sprint network handoff to work reliably on any phone?

 

Sent from my EVO LTE

 

 

On the original first version made by Samsung that I never touched for years since it just did it's own thing I could hand off to the cell network all the time with success.

 

Sent from my little Note2

 

 

  • Like 1
Link to comment
Share on other sites

After deploying about 10 or so airaves around where I work (half were version 2.5 the other half were 2.0). I can tell you the 2.5's just work and work reliably. The 2.0's will die about once every two weeks requiring a restart. Of course this is a small sample... Anyone seen any differences from my observation?

 

Also, has anyone had any luck getting an airave to Sprint network handoff to work reliably on any phone?

 

Sent from my EVO LTE

i'm glad they've worked for you but there is a known and acknowledged bug with LTE devices and the 2.5's..:)

Link to comment
Share on other sites

Almost all the 300 devices I support are not LTE so I could be completely in the dark, however I use my personal evo lte for testing airaves all the time and never notice any significant issues. The only interesting thing that happens on my evo as opposed to the dumb phones is it tends to hang on to whatever network it is connected to for much longer than I think it should.

 

All the phones we have seem to have trouble handing off from an airave to the rest of the Sprint network.

 

Do you have any details of the bug you have seen? I believe you, I am just curious as to where it has been reported.

 

Sent from my EVO LTE

 

Link to comment
Share on other sites

it is only with lte devices..if you don't have any you won't see the bug..as far as handoff to sprint..i can't test that as i don't have sprint service when i leave the house for at least a mile..:)

Link to comment
Share on other sites

I had a 2.5 with my Galaxy Nexus, had tons of problems. Calls dropping within 5 minutes of connecting, double and triple text messages, text messages not sent. Nobody could solve it. Sent it back, and got a version 2 (just by sheer luck I'm guessing, I did not specifically request a 2).

 

It's been running since early January with no problems at all, with all the phones I've owned since then: Galaxy Nexus, BlackBerry Curve 9350, and HTC EVO 4G LTE. The GPS did not lock in the same place the 2.5 did, so I used the external antenna attached to a window and it works great.

 

Now that Sprint is upgrading the towers around me, I'm getting 3 bars of 3G with good LTE in the parking lot of the apartment complex where before I'd do extremely well to get 1 bar of barely usable 3G. Hopefully once the other towers are upgraded I'll be able to send back the Airave.

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

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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