[Q] Hyperdrive romRLS16 phone issues ! PLEASE HELP ! - General Questions and Answers

I have an at&t samsung galaxy s3 and i flashed hyperdrive rom (RLS16) one week ago and i just realized that when people are calling me, sometimes I can answer them, and sometimes i'm not receiving calls. When i receive calls, the vibrator and the ringtone are not working... also, I tried to go to my voicemail several times by holding 1 button or *81 and it's not working.. I love this rom but i need my phone to work ! What can i do ? thanks a lot !

Related

[Q] Mic not working on gt-i9000 {ICS}

Hi, recently I flashed Onecosmic's ICS 4.0.3 RC3 on my galaxy s....now the problem is that whenever I receive a call the MIC DOES NOT WORK !!
While when i make a call it works perfectly.....its pissing me off....as i dont want to leave ICS because of this silly problem.....nyone with a solution????
(P.S: I have tried reflashing other ics roms...like that of teamhacksung...but the problem exists...its only solved when i get down to gingerbread.)
Androlover said:
Hi, recently I flashed Onecosmic's ICS 4.0.3 RC3 on my galaxy s....now the problem is that whenever I receive a call the MIC DOES NOT WORK !!
While when i make a call it works perfectly.....its pissing me off....as i dont want to leave ICS because of this silly problem.....nyone with a solution????
(P.S: I have tried reflashing other ics roms...like that of teamhacksung...but the problem exists...its only solved when i get down to gingerbread.)
Click to expand...
Click to collapse
I also have this annoying problem that stops the basic function of the mobile phone. I also searched the net but did not find any fix for it also tried several ICS builds/version available on internet but all are having this problem of poort MIC audio while incoming call, perfectly working when doing outgoing call.
I discovered that just after receiving the call if you taggle the mute/unmute button then it works perfectly no matter how long your call can go - i check this on more than 30 min call.
Hope developer should rectify this issue as soon as possible.
dk147in said:
I also have this annoying problem that stops the basic function of the mobile phone. I also searched the net but did not find any fix for it also tried several ICS builds/version available on internet but all are having this problem of poort MIC audio while incoming call, perfectly working when doing outgoing call.
I discovered that just after receiving the call if you taggle the mute/unmute button then it works perfectly no matter how long your call can go - i check this on more than 30 min call.
Hope developer should rectify this issue as soon as possible.
Click to expand...
Click to collapse
need this sorting asap paranoid is the best rom i have used so far with this bug the onjly thing making this just short of awsome

[Q] Internet Calls (Issue) with CM10 !! Galaxy S2 Skyrocket !!

I have a Samsung Galaxy S2 Skyrocket running CM10.
Every time I try to make a video call or voice call thru Skype, tango, text plus, etc.. this annoying sound turns on (BEEPPPPPPPPP) and it doesn't shut off till I reboot the device. Therefore I can't make video calls without this annoying sound turning on and it consistently plays until I shut off the device. Even if you put the volume to 0 it still plays and it's really loud too.
Has anyone else experienced this same problem ?
Is there anyway I can fix this ? Do I need to install something ?
Please Help !!

[Q] Galaxy S4 very weird problem with tone

Hi,
Please help me, I don't know what to do any more.
I have a Galaxy S4 GT-I9505 and since an update to kitkat 4.4.2 I have a very weird problem with the tone.
Randomly without any reason it stops. No notifiaction tone, no ringtone, no lockscreen tone, no more tones at all. After rebooting the device everything functions well again. I have tried to test the receiver and speaker with *#0*# and it works fine. As soon as the tones stop and I try the test again it doesn't.
I have tried several factory resets, I have flashed original samsung firmware, I have flashed different roms (my device is rooted and I use philz recovery).
I have tried to search the web, but after weeks of trying I still didn't find any answers.
PLEASE, PLEASE, PLEASE if anybody could help me!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Please anybody?

Call Waiting Problem in CM12 or any Lollipop based ROM!!

I have been facing this issue from the time I installed CM12 or any CM12 based ROM. Pretty surprised that there are two or three mentions of this problem in some of the threads but non has replied. Don't know whether its a bug or some intermittent issue. Problem is When I am on a call and a new call comes in(call waiting), my call goes on HOLD automatically and if I reject the new call, my already active call didn't work. I have to disconnect the call and call the person again. This problem is very annoying.
Can anyone please help.
mannu_in said:
I have been facing this issue from the time I installed CM12 or any CM12 based ROM. Pretty surprised that there are two or three mentions of this problem in some of the threads but non has replied. Don't know whether its a bug or some intermittent issue. Problem is When I am on a call and a new call comes in(call waiting), my call goes on HOLD automatically and if I reject the new call, my already active call didn't work. I have to disconnect the call and call the person again. This problem is very annoying.
Can anyone please help.
Click to expand...
Click to collapse
I'm having the exact same problem and have been searching for a solution but no luck. Because of this reason I've been having to go back to KitKat. Does anyone have a solution for this? I have the lollipop one plus modem that I flash every time I flash any lollipop rom
That's what happens when you volunteer to test alpha firmware.
An easy workaround is disable call waiting bc it sucks anyway. Nobody likes to be put on hold. You can have interruption-free calling and extra incoming callers get an old-fashioned busy tone.
Did anyone filed bug for this..
tollboy said:
Did anyone filed bug for this..
Click to expand...
Click to collapse
No I just went back to kit kat.
same problem. its really problematic.even the people are ia m in call with are getting irritated as they are being pushed to hold. some one from cyanogen should address this
mannu_in said:
I have been facing this issue from the time I installed CM12 or any CM12 based ROM. Pretty surprised that there are two or three mentions of this problem in some of the threads but non has replied. Don't know whether its a bug or some intermittent issue. Problem is When I am on a call and a new call comes in(call waiting), my call goes on HOLD automatically and if I reject the new call, my already active call didn't work. I have to disconnect the call and call the person again. This problem is very annoying.
Can anyone please help.
Click to expand...
Click to collapse
Hello...I am yureka plus user....I have installed Cm12 manually.....I have resolved many issue.....but still facing is conference call....as it shows"can't switch calls" and goes back to current call......neither it hold the call.....shows same error...please help.....big fan of cyanogen.....as able to use full features of my device...

[BUG] No incoming calls received on any CM12 Radio when screen locked for 5 mins

After so many tests, i can finally confirm this problem.
Basically, in the last week or so, i have been missing almost all incoming calls because of this problem.
I found, even with the newest nightly 02072015,
all CM12 Modem update will cause my OnePlus to not responding to incoming calls after screen lock for more than 5-10 minutes.
My area does not have the best reception, normally 1-2 bars, but i rarely missed a call because of it.
all test are done with clean installation after revert to stock. put in lock for about 5-10 mins.
My test result:
CM11S + 44S Radio, 3 test calls, received all. Caller side ring twice until phone respond.
CM11S + 38R Radio, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
CM11S + CM12 Radio, 3 test calls, received one call. 2 not received, Caller side ring twice then went into voicemail.
CM12 + CM12 Radio, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom2.0 + Bacon_firmware_update, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom1.8 + 44S, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
This problem will not occur if the phone is "freshly" locked.
I have had this issue for some time as well, I know your frustration. It has even made me to the point of switching to a different phone
icedmayhem said:
I have had this issue for some time as well, I know your frustration. It has even made me to the point of switching to a different phone
Click to expand...
Click to collapse
Right now , i am sticking with 44S + BlissPop but it pop error process from time to time =( . i just wish they fix the radio soon.
I got a roommate using CM11S works with no problem. so I might just switch back to KitKat for now.
Gh05tShie1d said:
After so many tests, i can finally confirm this problem.
Basically, in the last week or so, i have been missing almost all incoming calls because of this problem.
I found, even with the newest nightly 02072015,
all CM12 Modem update will cause my OnePlus to not responding to incoming calls after screen lock for more than 5-10 minutes.
My area does not have the best reception, normally 1-2 bars, but i rarely missed a call because of it.
all test are done with clean installation after revert to stock. put in lock for about 5-10 mins.
My test result:
CM11S + 44S Radio, 3 test calls, received all. Caller side ring twice until phone respond.
CM11S + 38R Radio, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
CM11S + CM12 Radio, 3 test calls, received one call. 2 not received, Caller side ring twice then went into voicemail.
CM12 + CM12 Radio, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom2.0 + Bacon_firmware_update, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom1.8 + 44S, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
This problem will not occur if the phone is "freshly" locked.
Click to expand...
Click to collapse
Sent from my XT1023 using XDA Free mobile app
does any one have possible fix ?
I had luck flashing a different modem. From the website below the Full-CM12-23.01.15-modem-flashable.zip did the same thing but I had good results with the Full-CM12-12.01.15-modem-flashable.zip
since I am a new user it wont let me post the link so you guys will have to take out the spaces
http : / / boeffla . df - kunde . de / bacon / modems /
---------- Post added at 06:06 PM ---------- Previous post was at 05:45 PM ----------
Merlin696 said:
I had luck flashing a different modem. From the website below the Full-CM12-23.01.15-modem-flashable.zip did the same thing but I had good results with the Full-CM12-12.01.15-modem-flashable.zip
since I am a new user it wont let me post the link so you guys will have to take out the spaces
http : / / boeffla . df - kunde . de / bacon / modems /
Click to expand...
Click to collapse
Never Mind, that didnt work either.
Tried that before, no luck but thank u regardless
Ok I got it working and have been using it for a quite a while now without issue.
First this is for CM12
Download this modem
cm-28112014-modem-flashable.zip
http : // forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734/post57129886#post57129886
Next you will need to do a firmware flash/update as well otherwise the proximity sensor wont work
bacon_firmware_update_2015_01_29.zip
http : //downloads.katinatez.com/addon/
I know I probably dont have to say it but just to make sure, these should be flashed from recovery
again you will need to take out the the spaces in the http since I have not posted enough to post links
So the fixed worked all day until I turned on my WiFi and then I failed to receive my test call. I turned the WiFi off and it worked fine again. Not sure yet what the correlation is but I think its more than just a modem issue.
I give up, i'm going back to KitKat
---------- Post added at 11:52 AM ---------- Previous post was at 11:37 AM ----------
looks like maybe just maybe the devs have finally started having the issue too
http : //t.co/h0361GBRZl
well its not a fix, but if you leave your radio on 2G calls come through just fine.
I have searched high and low and still cant find anywhere someone has a fix for this issue yet.
Having the same problem on the latest nightly. I really don't want to revert to kitkat.
Problem still persists!
I am on cm-12-20150329-NIGHTLY-bacon.zip nightly and I still have the issue! I really really dont want to go back on KitKat so temporarily I am back on my old phone.
I, too, am experiencing this strange problem. No calls or texts when set to LTE, but they do come through when set to 2G.
I am currently on the 4/5 Exodus rom with the new firmware and modem from Oxygen OS. The issue still happened after flashing the newest CM nightly so I took a chance the new firmware and modem would fix it..... No luck.
Sent from my A0001 using XDA Premium HD app
same problem as well with OxygenOS and recent CM12 nightly. I wish that someone could help find a resolution. This is nuts.
I experience the same problem when I was on Blisspop, gave up and reinstall KK.
Recently tried CM12.1 and have the same problem with that rom too, a little better perhaps.
Hope someone found a solution.
Well back to KiteKat again.
All this time and this thread is buried WAY down in the Q&A section.
Are we the only ones having this problem?
Sent from my OnePlus One
Man I so glad I'm still on kk and I will not update to "L" IMO I think it's the biggest flop from Google just like when M$ released Windows ME....guys stay away....
JohnM109R said:
Man I so glad I'm still on kk and I will not update to "L" IMO I think it's the biggest flop from Google just like when M$ released Windows ME....guys stay away....
Click to expand...
Click to collapse
I don't think it is a total flop by Google at all. It's probably some errant coding for the radio on our particular phone. I would love to try to figure out why but I have no idea how or where to even start.
Sent from my OnePlus One
OK, it isn't me then. Had a missed call on my screen yesterday when the phone was next to me all the time.
Did you all get a missed call or nothing?

Categories

Resources