I need some help, and I'm trying to figure out if I caused my own problem or not. I've got a rooted Evo3D, 1.4 Eng HBoot, stock ROM. I noticed while at another location and latching on to an Airave that my audio was extremely garbled. In fact, all audio while making a phone call is completely garbled. I chalked it up to maybe just issues in that Airave's setup.
Now, I have one of my own. My Wife's Epic works on it perfectly. When latched on to my Airave, I get that same garbled audio. When I'm not on the Airave, everything is fine. I've tried 2 different ROM's with the same result. I went back to the .530 radio, same result. I reflashed the stock kernel while on the stock build, same result. I'm currently on Android Revolution HD which if I remember correctly has a different kernel built into it. Same thing.
Am I missing anything else here? Is there anything that I may have done while rooting the phone originally that might have caused my problem? Any ideas on how to fix it? I believe the Airave its perfectly fine, as my Wife's phone works with no issue, and a friend has come over with her Evo 4G and it works just fine as well.
Thanks for any help you guys can offer!
EDIT: Figured it out. The one thing I forgot I had done. I had enabled EVRC-B and that apparently doesn't play nice with the Airave. Changed those settings back to stock and all is well.
LiquidFusion01 said:
I need some help, and I'm trying to figure out if I caused my own problem or not. I've got a rooted Evo3D, 1.4 Eng HBoot, stock ROM. I noticed while at another location and latching on to an Airave that my audio was extremely garbled. In fact, all audio while making a phone call is completely garbled. I chalked it up to maybe just issues in that Airave's setup.
Now, I have one of my own. My Wife's Epic works on it perfectly. When latched on to my Airave, I get that same garbled audio. When I'm not on the Airave, everything is fine. I've tried 2 different ROM's with the same result. I went back to the .530 radio, same result. I reflashed the stock kernel while on the stock build, same result. I'm currently on Android Revolution HD which if I remember correctly has a different kernel built into it. Same thing.
Am I missing anything else here? Is there anything that I may have done while rooting the phone originally that might have caused my problem? Any ideas on how to fix it? I believe the Airave its perfectly fine, as my Wife's phone works with no issue, and a friend has come over with her Evo 4G and it works just fine as well.
Thanks for any help you guys can offer!
EDIT: Figured it out. The one thing I forgot I had done. I had enabled EVRC-B and that apparently doesn't play nice with the Airave. Changed those settings back to stock and all is well.
Click to expand...
Click to collapse
Wish I would have seen this earlier I could have saved you the troubleshooting. I had the same problem a couple months ago and yep evcr-b doesn't play nice with the airraves. Glad you got it fixed though.
3VO Sent
Related
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
Ok, so for some reason today i havent received alot of texts or calls from anyone, and this kinda just randomally started happening, im a huge texter sometimes upwards of 2-300 a day so this came as a shock to me since im running bamf and have had no problems/issues ever with this..
now i was told that bamf has their own kernal so i never installed a new one on the phone..
and i did use a newer radio, but could the kernal or radio have anything to do with what happened today, is their a better kernal or radio that i could flash onto my phone and this problem will never happen again?
Thanks in advance!
Willis_G said:
Ok, so for some reason today i havent received alot of texts or calls from anyone, and this kinda just randomally started happening, im a huge texter sometimes upwards of 2-300 a day so this came as a shock to me since im running bamf and have had no problems/issues ever with this..
now i was told that bamf has their own kernal so i never installed a new one on the phone..
and i did use a newer radio, but could the kernal or radio have anything to do with what happened today, is their a better kernal or radio that i could flash onto my phone and this problem will never happen again?
Thanks in advance!
Click to expand...
Click to collapse
Was your line suspended due to non payment? Lol
Sent from my Synergized Thunderbolt via XDA Premium App
lol the bill is paid.. maybe the network was screwed up where im at yesterday or something, maybe today will be better.
if you can make calls and text yourself, then I don't think its the radio
Sent from my SHIFTAO5P using XDA App
I did some work on my brother-in-law's Thunderbolt. When we used the 802 radio set (CDMA+LTE), he couldn't send sms/mms, we didn't test receiving, but once we backed down to the 627 radio set everything was fine.
bigdwg71 said:
I did some work on my brother-in-law's Thunderbolt. When we used the 802 radio set (CDMA+LTE), he couldn't send sms/mms, we didn't test receiving, but once we backed down to the 627 radio set everything was fine.
Click to expand...
Click to collapse
Can you elaborate please? is that just different versions? or is one more more compatible then another?
So far it seems to be ok texting again, however (and i know this sounds stupid) but one of my friends i cant text.. literally i can recieve everything he says but if i try to send anything to his phone it wont recieve, he is a tmobile carrier and i have never had issues.. even put the phones side by side and he still gets nothing.
Hello Folks,
I just replaced my old Droid Eris (that I took swimming) with a Samsung Fascinate that I bought from a guy on Craigslist.
The phone is in pretty great shape, and it is wonderfully faster than my old Eris was (especially after it went swimming).
The stock rom was disgustingly hogged by VZW and M$, as I'm sure you all know. I am currently running PowerWashedGB on it, and it is fabulous.
I am having a problem however with audio dropping out during streaming, and am trying to decipher whether it is software or hardware related.
Does anyone else have problems with audio dropping when streaming? Works great when read off a disk. I went back to the VZW stock rom to see if it had to do with PWGB, but the problem persisted.
Does anyone know a way I can pick this problem apart, and if there is a different radio/modem I could try flashing? Everything else on the phone works great, even data for the most part, just not stable enough to hold a steady stream (drops every 30 seconds or so for about 5-10 seconds).
Thanks guys.
ignurant said:
Hello Folks,
I just replaced my old Droid Eris (that I took swimming) with a Samsung Fascinate that I bought from a guy on Craigslist.
The phone is in pretty great shape, and it is wonderfully faster than my old Eris was (especially after it went swimming).
The stock rom was disgustingly hogged by VZW and M$, as I'm sure you all know. I am currently running PowerWashedGB on it, and it is fabulous.
I am having a problem however with audio dropping out during streaming, and am trying to decipher whether it is software or hardware related.
Does anyone else have problems with audio dropping when streaming? Works great when read off a disk. I went back to the VZW stock rom to see if it had to do with PWGB, but the problem persisted.
Does anyone know a way I can pick this problem apart, and if there is a different radio/modem I could try flashing? Everything else on the phone works great, even data for the most part, just not stable enough to hold a steady stream (drops every 30 seconds or so for about 5-10 seconds).
Thanks guys.
Click to expand...
Click to collapse
228
Do a *228 options 1 and 2 and let the phone reset. If the problem persists: does it happen with only one streaming app or with all of them. If it's all of them try streaming with the charger plugged in to check if it's a voltage issue with the screen off. Lastly, does it happen with the screen off or on or both ?
sent from my SCH-I500 PWGB 2. 0b3
The amount of awesome that happens in this forum is simply pure awesome.
Do a *228 options 1 and 2 and let the phone reset.
Click to expand...
Click to collapse
Thank you for your quick reply. Setting the phone to reprogram seems to have fixed the issue, I've been streaming about a half hour now with no problems, which is far more than was working previously.
I sold my 3D to someone and have been trying to put a new rom on it for em. Everytime I flash a 2.3.4 rom everything works EXCEPT during a call you can hear the person talking but they cant hear you. And I know the speaker works because voice commands work fine but during it call it doesn't work, period.
Sounds Like a personal phone issue..I've been on 2.3.4 with multiple roms and never had this issue.
Sent from a little place called ETERNITY in the 3rd Dimension.
I never had that problem running 2.3.4 ROMs either.
I honestly don't get it. Every 2.3.4 rom I tried to put on the phone would have the issue with not being able to be heard during a call. I tried 4 different roms and had the same issue everytime. Put a 2.3.3. rom on it and I could be heard during calls fine. I dunno but I got tired of fooling with it.
I did notice one thing though... when wiping in recovery I got an error that said
E:can't give path "/sdcard/.android_secure" to format_volume
Think that might have something to do with it?
OP, did you do the EVRC-B mod? If so, undo it.
Compusmurf said:
OP, did you do the EVRC-B mod? If so, undo it.
Click to expand...
Click to collapse
I don't even know what that is lol. This is basically the scenario. I can flash ANY 2.3.3 rom or lower than that and everything works perfectly fine. But as soon as I flash any rom with a 2.3.4. base everything works except for callers being able to hear me. It's crazy... I even tried the stock 2.3.4. deodexed update and it was the same thing. Flash a 2.3.3. rom and boom, they can hear me again.
brownhornet said:
I don't even know what that is lol. This is basically the scenario. I can flash ANY 2.3.3 rom or lower than that and everything works perfectly fine. But as soon as I flash any rom with a 2.3.4. base everything works except for callers being able to hear me. It's crazy... I even tried the stock 2.3.4. deodexed update and it was the same thing. Flash a 2.3.3. rom and boom, they can hear me again.
Click to expand...
Click to collapse
The EVRC-B mod enhances voice, the same settings found on Verizon phones but in some cases it might not be supported by the tower. Its accessed in the EPST edit menu, via your MSL code.
But if you're flashing the ROMs with voice performance changing, I'm not sure whats going on. As I seriously doubt the EPST settings get changed by the ROM.
I could be wrong.
I don't know either... im clueless. First time i've ever had a hangup like this when flashing. I put it on the phone for her and everything was all good until she got a call and realized they couldn't hear what she was saying. I thought maybe it was a bad flash but hell i've tried every rom in the development forum almost.
none
Give the guy his money back, put it under your car tire, then smoke the tires, that phone sounds retarded.
Try revolution by Mike and see if that shows the same issue.
If it does then either your doing something wired while flashing, have some app messing crap up, or its hardware problem somehow.
Likely its user error somehow though. I dunno any roms that flip evrb on for voice by default for the mere fact that its not supported everywhere.
Sent from my PG86100 using XDA App
But how would it be user error only for the 2.3.4. roms lol. Im sayin... i'm not doing anything different. Just download, transfer from pc to sd and flash through recovery like I always have. If it was user error it seems like id have problems with the 2.3.3. roms too. I gave up on it though.. technically it's not even my phone anymore lol
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Same exact issue !
cauger24 said:
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Click to expand...
Click to collapse
My evo lte has been doing this for as long as i can remember also. I've been through dozens of roms and full wipes and still no bluetooth at all, not even recognizable.
Try deleting everything that is paired or was paired and then reboot. You may have Bluetooth defects if that still doesnt work. I have used on many sense roms, cm10, 10.1 varients with no problems. Hope that helps.
Sent from my EVO using xda app-developers app
Im having the same issue
I have updated my radios and noticed that i lost my Bluetooth connectivity. I was originally running meanrom ics until JB came around. Then updated my radios and moved to JB MeanBean. I did an Ruu and got it back to stock. No dice, stock rom Bluetooth still cannot find or be found. I tried my laptop ipad macbook car audio everything and nothing works. I ve never had any issues with my phone and it seems after Jelly Bean Bluetooth is non existent.
Currently I am running
Twrp 2.3.1
Arc Reactor Kernel
MeanBean3.09
Is there a way to see if the actual Bluetooth is borked or if its working properly, "if its sending a signal"?
Is it possible that something happened when upgrading that the BlueTooth became corrupted? or can it just plain old stop working, died?
At that point if it's Borked on several roms
Then it's time to take it into sprint. That's a manufacturer defect / issue and they should swap it out. Assuming you bought legit from them
Sent from my EVO using Tapatalk 2
Yes I bought it legit when it came out. I also have the insurance plan with Sprint. The only thing I'm worried about is the new hboot and unlocking/rooting the new phone .
But I guess if it means a new phone then I guess its best... To get a fresh new evo
Sent from my EVO using xda app-developers app