jsolo

Could someone clarify, on an android/cdma device, how do I see what vocoder is in use? On my evo 4g lte, the debug screen does not seem to indicate this (##debug#).

^^Mine is the older 2.0 airave. I made a thread on xda about the fix last night. Someone posted this morning that the 2.5 did indeed fix their handoff issue too. It would be a waste of a perfectly good (airave=pos ) piece of hardware to replace it when the fix is so simple. Another piece of electronics in the landfill. Will push 'em for an updated version when this one fails altogther.

This issue has cropped up yet again. Last time it looks like they shut down the SMR transmissions (or they were just testing them for a short period), and the phone relocked back to the airave when near it. I didn't actually get a chance to try out the instructions in post #10 About 4 or 5 days ago I wasn't hearing the 3 beeps when placing/receiving calls. Called up airave support and as usual they had their heads up their @ss. Had a chance to modify the current 25010 prl as digiblur instructed above. Result, success! http://img268.imageshack.us/img268/9894/prly.png Modified prl: http://db.tt/wk9muM1j When near the airave, phone locks to it. When airrave is powered off, phone relocks to 22439 sid. When airave is back online, phone is back on the airave. This functions now exactly as before the introduction of 22439 sid. I really don't understand why sprint doesn't just include this in the prl themselves. Maybe they're trying to wean people off these things. Either way, using an airave signal should improve battery life. Digi, thanks again for your help!

My method of testing was real simple. Call myself from another phone. Answer on the evo, then continue holding the other phone to my ear. I'd toggle the prox sensor a number of times, hearing a touch tone with each toggle. I then restored an old cm image and repeated the test. No touch tone. Restored the sense backup and repeated. No touch tone. We'll see how long this lasts, but appears to be at least partially connected to sense.

Was the proximity sensor/touch tone issue ever resolved? Just realized I too have this. Now i understand why i've had such difficulty navigating touch tone menus. I have a airrave 2.0 here. My chat with sprint airrave support was not too useful. They are aware of the issue (apparently for some months now), but no resolution yet. The rep suggested speaker phone or BT... Wonderful..

Things have improved marginally. I can now get voice on the airrave, but only 3g if phone is set to cdma/lte. It'll bounce between 4g and 3g depending on signal (4384 sid, sometimes 22439). If I set it to cdma only, i get no data at all (with the airrave or towers). 3G only happens if it's using the erhpd protocol. No 3g on evdo at all. If I cycle airplane mode while on the airrave, i may or may not get data back (3g ehrpd or lte). It makes no sense to make any further tweaks until this issues is worked out and or stabilized.

Digi, thanks for the informative step by step directions! I'll try the above later. Looks like sprint is doing something around here. I can pull up 4g/lte, but not 3g data over the towers or the airave. I do have a question. In the pic I linked, http://imageshack.us/a/img69/5928/prlb.jpg , what is the significance of line 467. It's similar to line 472 in terms of referencing the 4384 sid?

Digiblur, messing with the prl seems to affect the airrave connectivity. If I remove the 22439 (line 465 in prl 25006), then I get the airrave back for voice. However I don't think this is the desired effect. I just don't know how to create a proper record(s) that will give sid/nid 4384/502 priority over 22439 (when near the airrave or it's on). Here's what the stock 25006 looks like - lines 465 and 472. http://imageshack.us/a/img69/5928/prlb.jpg

^^ Thanks Prl 25006 sid 4384 nid = 50 (when connected to tower) sid 4384 nid = 502 (when connected to airrave)

I think this is doable. I already know the sid/nid of the airave from past observations, so all I really need to do is edit the prl. Worth a shot. Will report back. Edit: What's a suitable tool for actually editing the file. I can read/write it to the phone already.

Ecfbsig32, You have a source for this? According to http://www.ifast.org/files/NationalSID.htm, 22439 is pcs 1900?

Yes, everything has been power cycled in various orders several times. Airave has also been hard reset (30s on the reset button in the back). It may very well be the phone, as the SID #'s have changed (see first post). There is a marginally stronger voice signal (-97 to -100 dbm or so). Unfortunately, I have no other sprint phone to test out here. There are several towers serving this area, but I seem to be at the fringe ends of each. Fwiw, lte connectivity is also sporadic, bouncing between the airave's 3g and lte numerous times throughout the day. Signal level close to -120dbm on that typically (-117, -119, etc..)

^^Tried all of the above already. This too is a airave 2.0 (got it about jan/feb of 2011). All solid lights on the device, just no connectivity. I don't know if it's coincidence or not that this started happening the same time lte went live around here.

As of last thursday (10-18), lte has been turned on in my area. Since then, my evo has been unable to connect to the airave for voice function. That, when the phone is on 3g, I can see the mobile light flashing on the airave and data speeds are indicative of being passed through it. However if I place a call, I don't get the usual 3 beeps, and there are no signs of the call being funnel through the airave. I've tried a number of different things including updating profile, prl, rebooting everything multiple times. Interestingly, the SID the phone attaches to now is a 5 digit (22439), where as before it was a 4 digit (sid 4384, nid =50, and when on the airave, nid=502). I find it strange that the phone would even connect in such a manner - data=airave, and voice = tower. I got a ticket in with sprint, but thus far no resolution. Any thoughts/suggestions?