Jump to content

GNEX and airave issues continue


hescominsoon
 Share

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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Update just showed up for both of my phones. So far I don't notice any difference, LTE TA is still reporting as 0, I was hoping the new routine might fix that. I sent a diag report from both phones in case you need any of that info. I'll let you know in a day or so if its crashing as frequently or not. 
    • A new SignalCheck Pro beta release is rolling out now, and should become available on Google Play shortly! Some notable changes: New "swipe to refresh" -- flick down on the main screen, and the data will "refresh" -- I put this in quotes because it will *not* force the modem to be polled (that's unfortunately not possible), but it will 'wake up' the app and display the latest information if for some reason your screen did not automatically update. I am still working on improving this. New cell identification methods for Android 12+ devices -- new routines are available in Android 12 and this is my first attempt at implementing them. I have not seen any changes positive or negative on my Pixel 6, but hopefully someone sees improvements. I will continue exploring these methods and adding new features as I get them working. Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing. Missing/invalid TAC values included in web uploads -- this will need some testing, because I can't replicate it myself. The option to log cells with missing TAC must be enabled for this to have an impact. Feedback welcome as always!
    • Another converted keep site: Sprint eNB 9436 -> T-Mobile eNB 895067 (40.60777246698788,-74.16199692361377) Looks like they're using the FFVV-65A-R2-V1 here, as well!   Edit: Also, I know this technically isn't NYC, but here's a Jersey City conversion. Not 100% sure on either eNB. Sprint eNB 105863 -> T-Mobile eNB 876452 (40.72265196811989,-74.08804945021805)
    • More confirmations incoming! T-Mobile eNB 880561 (40.74176835140717, -73.88364207139453)   Sprint eNB 6191 / T-Mobile eNB 880065 (40.71339007010928, -73.85695387371624) Confirmed this site but was unable to get a photo because the antennas are set back from the edge of the building. I could see them from super far away but there wasn't a good area for me to pull over and snap a pic.   Sprint eNB 6189 / T-Mobile eNB 877995 (40.71183894845567, -73.83529788316665)   Sprint eNB 253741 / T-Mobile eNB 875537/875538 (40.70170960850086,-73.83302208208359)   Sprint eNB 79912 / T-Mobile eNB 875989 (40.86349197342981, -73.923456682535) — — — — — T-Mobile eNB 880536 in the Bronx isn't a Sprint conversion but rather, T-Mobile changed the eNB when they upgraded the site. The nearest Sprint site at 40.8150405321864, -73.93010756429787 still has all of its antennas up and is literally within spitting distance of two other T-Mobile sites in an area that's very industrial as opposed to residential or commercial so a keep site isn't particularly necessary. You can see on Cellmapper that the old eNB stopped broadcasting about two days after the new eNB went live.  — — — — — Also wanted to add that I spotted AT&T C-band antennas quite a bit in both Queens and the Bronx. I would expect a summer C-band launch announcement from them because they're moving FAST. At least in my area, it seem like they're upgrading at a faster pace than Verizon is. Some more pics: AT&T eNB 116408 / T-Mobile eNB 42887 in Woodhaven. This one is interesting because T-Mobile upgraded this site but in the process didn't put any Ericsson n41 antennas. There are just two of the RFS antennas that we normally get.   AT&T eNB 112047, bad pic but the arrows on the billboard are pointing right at the C-band antenna lol   — — — — — Last edit I promise: I noticed T-Mobile submit a permit to convert the keep site I found in Staten Island (Sprint eNB 75141). I 100% guessed it's location since I connected to it literally 4.5 miles across the water while inside a building. Glad to see I was right!
    • Support for the -1 TAC is good to go now, so I'm ready whenever you are!
  • Recently Browsing

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