Related
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.
I have I think a kind of strange problem. I've had my V or a few months now and all of a sudden it doesn't get move than 2 bars on the reception scale where as before it used to get 3-5 sitting in my rec room. Don't know what changed other than adding and removing some apps that I wanted to try out. Don't know which are still there that weren't before but wouldn't think that apps would cause the reception to be poorer.
Thought about an antenna booster/adapter/extension but thought I'd ask others first.
Also, anyone added any antennas to theirs? I noticed there isn't an external connection for one and everything I've read so far talks about add one with the external connection.
Any help would be appreciated.
Try updating your PRL
http://forum.xda-developers.com/showthread.php?t=991668
My optimus had problems like that too, but after upgrading my by rom, baseband stuff is quite better.
Which one are you using ?
bloodclot said:
Try updating your PRL
http://forum.xda-developers.com/showthread.php?t=991668
Click to expand...
Click to collapse
Agreed, Updating the PRL is highly recommended.
Sent from my VM670
Have you really noticed a difference by upgrading your PRL?
Don't know what PRL is
In reading all the responses I was afraid since I don't know what the PRL is. Several places warned against changing things in the PRL if you don't know what the PRL is.
I have rooted my phone and have changed the rom a couple times including bricking it a couple times but had a backup so I recovered but don't know what the PRL is so didn't try that avenue.
Jim
I flashed my PRL today and could only get data to work. SMS and Phone stopped working so I flashed back to my original PRL. I think it was trying to connect to the tower closests to where I was, but told me to call customer service If I wanted to use it.
ROM issue on signal reception
JimReid said:
I have I think a kind of strange problem. I've had my V or a few months now and all of a sudden it doesn't get move than 2 bars on the reception scale where as before it used to get 3-5 sitting in my rec room. Don't know what changed other than adding and removing some apps that I wanted to try out. Don't know which are still there that weren't before but wouldn't think that apps would cause the reception to be poorer.
Thought about an antenna booster/adapter/extension but thought I'd ask others first.
Also, anyone added any antennas to theirs? I noticed there isn't an external connection for one and everything I've read so far talks about add one with the external connection.
Any help would be appreciated.
Click to expand...
Click to collapse
Recently I upgrade my ROM to cyagenmod 10.1. It shows the signal is very poor, but I did not face the issues on call receiving/making. This is the known issue ( fail to refresh the signal strength in status).
Also faced some other issues ( phone hang while call is coming in 'phone locked' condition'.
Finally changed the OS to Android 4.2.1 & PAC-MAN 19.9.0. Except the battery drain issue, no more issues now.
Hey all,
I'm using mhx's stock debloated ICS rom flashed through CWM coming from SKYICE GB.
So far all my incoming calls are showing up as unknown since I flashed this rom. I haven't tried any of the other ICS roms as of yet. I'm with Rogers.
Is there a fix for this?
as a prev rogers rep i must ask the stupid but obv question
do you have call display or a valuepack?
I am running the smooth ics and no issues so far.
steeven01 said:
Hey all,
I'm using mhx's stock debloated ICS rom flashed through CWM coming from SKYICE GB.
So far all my incoming calls are showing up as unknown since I flashed this rom. I haven't tried any of the other ICS roms as of yet. I'm with Rogers.
Is there a fix for this?
Click to expand...
Click to collapse
Reflash the modem? Maybe it will work...
Sent from my SAMSUNG-SGH-T989 using Tapatalk
uhhdoug said:
as a prev rogers rep i must ask the stupid but obv question
do you have call display or a valuepack?
I am running the smooth ics and no issues so far.
Click to expand...
Click to collapse
Sent From my Two Tin Cans & String Device on The Wookie Network
steeven01 said:
Hey all,
I'm using mhx's stock debloated ICS rom flashed through CWM coming from SKYICE GB.
So far all my incoming calls are showing up as unknown since I flashed this rom. I haven't tried any of the other ICS roms as of yet. I'm with Rogers.
Is there a fix for this?
Click to expand...
Click to collapse
I'm having the same issue, any solutions/suggestions? I'm using the ICS rom from: http://forum.xda-developers.com/showthread.php?t=1567817
uhhdoug said:
as a prev rogers rep i must ask the stupid but obv question
do you have call display or a valuepack?
I am running the smooth ics and no issues so far.
Click to expand...
Click to collapse
I'm on a government plan which includes caller ID name display.
I'll try reflashing though.
Sent from my SAMSUNG-SGH-I727 using XDA
steeven01 said:
I'm on a government plan which includes caller ID name display.
I'll try reflashing though.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Does the government know what you're up to
Sent From my Two Tin Cans & String Device on The Wookie Network
I think it's something to do with ICS and not the modem because when I reflash skyice GB I didn't change the modem back and my caller ID started working again.
Sent from my SAMSUNG-SGH-I727 using XDA
i have the same problem as you, my id display doesnt work any fix ?
I've been doing some searching and have found that rogers and fido are the only carriers that have caller id with name and number display. Other carriers just have caller id with number display. Problems android users may experience are name/number coming up as unknown, pay phone, or has the number but says unknown name. Other android users have been fixing this problem by calling rogers and disabling name display leaving you with basic caller id which only shows the number if the person is not in your contacts list. If they are in your contacts list it will show their name aswell. I haven't tried this for myself though.
Common words that came up when I was searching this is RIL and CNAP (Call Name Presentation)
Another fix I was reading is that it has to be built into the rom to understand caller id with name display. On the Galaxy Nexus board they talking about something called CNAP. http://forum.xda-developers.com/showthread.php?t=1419175
I was thinking maybe pulling whatever it is that is needed from the rogers gingerbread rom and putting it into the ics rom to make it but work if that's even possible I have no idea.
I remember having this problem on my old LG EVE and the temporary fix was to call rogers and disable name display but I just waited for a fix instead.
LeeC's ICSradio.zip
I was having the same problem earlier after I flashed mhx's ICS-Superlite-4.2 with the radio included in that OP. The baseband came up but caller IDs didn't work. So I tried fixing it by flashing the Stock Bell Note radio I717MUGLA2, still nothing. And this time the baseband said unknown as well. But keep in mind both flashes had no problem with dialing and receiving calls. Just the caller IDs weren't coming up.
Finally I flashed LeeC's ICSradio.zip (http://forum.xda-developers.com/showpost.php?p=24140728&postcount=5), and accidentally clicked on fix permission in recovery, and now caller ID's working just fabulously. I'm not sure what exactly fixed it (LeeC's radio? Flashing ICSradio after the Bell one? Or randomly fixing permission?). Either way, something to try for my fellow Rogers people.
whatlobster said:
I was having the same problem earlier after I flashed mhx's ICS-Superlite-4.2 with the radio included in that OP. The baseband came up but caller IDs didn't work. So I tried fixing it by flashing the Stock Bell Note radio I717MUGLA2, still nothing. And this time the baseband said unknown as well. But keep in mind both flashes had no problem with dialing and receiving calls. Just the caller IDs weren't coming up.
Finally I flashed LeeC's ICSradio.zip (http://forum.xda-developers.com/showpost.php?p=24140728&postcount=5), and accidentally clicked on fix permission in recovery, and now caller ID's working just fabulously. I'm not sure what exactly fixed it (LeeC's radio? Flashing ICSradio after the Bell one? Or randomly fixing permission?). Either way, something to try for my fellow Rogers people.
Click to expand...
Click to collapse
So was it the radio or the permission that fixed it? It only happens to me when people call from landlines.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
kr3w1337 said:
So was it the radio or the permission that fixed it?
Click to expand...
Click to collapse
Can't tell ya. I flashed the radio and as I was navigating out of the touch recovery I accidentally clicked on fix permission. Not sure if it's the combination of both or one of them worked. I just tried calling my phone with landline and caller ID comes up fine now.
This is a good topic. Been having the same issue. This should've neen brought up in the ICS-Superlite thread though for better answers and results. I stumblled across this one by mistake
Sent from my SAMSUNG-SGH-I727 using XDA
I'm having the same issue on Rogers. I flashed NexusMod ICS on it last night (my second xda rom) and both have the same issue. I get about 30% of my callers showing up correctly, all the rest are "unknown".
Would love to know about a fix if anyone finds one. I will try that fix permissions fix in touch recovery.
update: The fix permissions did nothing
As steven said its a cross between that name display feature and something with the leak. if the radio/fix permissions fix doesn't work the other fix is to call rogers and tell them to disable name display. I had to do that with my atrix as it was a bell device.
AlonB. said:
This is a good topic. Been having the same issue. This should've neen brought up in the ICS-Superlite thread though for better answers and results. I stumblled across this one by mistake
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Except it's not just an ICS-Superlite issue.
Thanks All!
I had posted about this in a different forum but wasn't getting any replies.
I can Verify that if you call Rogers and ask to have the name portion excluded from the caller ID this problem is fixed. Just called and while I got a few questions as to why they were able to do it and now numbers show up!
YEAH!!! Thanks so much steeven01
whatlobster said:
Can't tell ya. I flashed the radio and as I was navigating out of the touch recovery I accidentally clicked on fix permission. Not sure if it's the combination of both or one of them worked. I just tried calling my phone with landline and caller ID comes up fine now.
Click to expand...
Click to collapse
It works fine for landlines with me too but calls from other cell phones always come up unknown.
I've tried what you said you did and no luck I've tried with the Note I717MUGLA2 modem and it gets no signal and is unknown baseband, I've tried with the new Note UCLC5 ICS modem no luck with caller id but everything else worked fine, I tried the original rogers modem but it gets no signal and is unknown baseband. I've tried fixing permissions after each modem and no luck. Are you sure your caller id is working for you when you receive calls from cell phones?
I think I'm just going to get rid of the damn name display.
Also no problem JoeSmoo I'm glad I finally helped someone on these forums.
uhhdoug said:
as a prev rogers rep i must ask the stupid but obv question
do you have call display or a valuepack?
I am running the smooth ics and no issues so far.
Click to expand...
Click to collapse
Just curious, why would that make a difference? Don't hate me if that is a stupid question, just wondering...
I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Well the 4.0.4 thazz build should be pretty stable as its essentially stock. That being said my wife (who is INCREDIBLY picky on how her phone functions... I've yet to get her to try something not TW-based) has been using Tweaked since before it was even posted and uses her phone as a phone constantly (... lot's of out-of-state sisters that she's always yapping with) and has yet to report an issue. I am unclear why you would be having these issues with the particular specificity you are experiencing... especially if kernels are remaining consistent across TW-based builds anyway. Without me being able to recreate it on my end or a logcat taken during the premature disconnect on your end I'm at a loss. If nothing else, at least you found something that works for you, so I suppose it a could be worse.
Sorry for the troubles.
Not all stock apps or play store apps work with 4.1, I had the same problem when I let my battery app manage my data. It would wait to connect sometimes up to 20-30 secs later after waking to make a call. Check all your apps your using for compatibility, and when you wake your phone give it a sec before calling out. If your in a bad area the alternating of edge/3g/HSDPA+ doesn't help either. I stopped allowing my battery app data control and that solved 90% of my issues, sometimes it still does it but only when I'm in the boonies.
techclan said:
I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Click to expand...
Click to collapse
LOL I am using T-Mobile service with this device, so if that's the case for you I would expect a few drops from time to time
On a serious note, drops can happen with full bars for a variety of reasons. Tower is overloaded (signal shows strong but can't connect/gets dropped), person you have called drops you (calling someone in NY that has AT&T? ), bad/faulty sim card (free to get checked and replaced), etc. No cell phone/ROM is drop call immune, even stock (and yes even those people using Verizon). FWIW, I haven't dropped a single call in over a month using Thomas' PA and Tweaked. That's pretty good considering that's including the holidays and I didn't go home this year.
Thanks for the replies guys. What drives me crazy is that I have absolutely no dropped calls when using the stock ICS ROM, but as soon as I load any of the ICS ROMs mentioned the voice call gets disconnected periodically. Same Location, Same Apps, Same Calling Number, nothing changes except the ROM.
I'm fairly technical and good at troubleshooting but not an expert in reading the Android Logcat and don't know what to look for in the log. I have loaded the UVLH5 radio after flashing the the custom ROMs to see if that might be the cause but same thing.... I wondering if I need to try an older Radio...
Like I said all is running great with Android ICS 4.0.4 UVLH5 (by tthaz777) + merwin's scorched-kernel-t769-ics v1.0.29 OC to 1728 but not knowing what's causing the drops is just driving me crazy....
To test I just load the ROM and then call one of the free news numbers (ABC News etc 650-293-9114) and put the phone on speakerphone, and yes I have tried varies other numbers... JUST WEIRD
Try finding an app of the app store to make logging easier like logcat or something. Then run the app and make a call. If it doesnt disconnect, restart the log. When it does disconnect, end the log and copy+paste it here. That is the only real way to find out whats up.
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
techclan said:
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
Click to expand...
Click to collapse
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
anactoraaron said:
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
Click to expand...
Click to collapse
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
techclan said:
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
Click to expand...
Click to collapse
Ordering a new sim doesn't mean getting a compatible sim. Have you taken the phone to a Tmo store and had someone check it out? They could've sent you another partially compatible sim for it. If I knew more about reading the logs I would love to help you out....
Dear All.
My samsung galaxy s2 skyrocket had been working with ParanoidAndorid (v 2.55) for 2 months without problems, but since a week ago I couldn't place regular calls. I can dial the numbers and receive calls, but in neither case I can hear any sound. The rest of the functions work just fine (youtube, chrome, etc). After checking for sound configurations, such as noise reduction, the problem persisted. I have to say that the problem goes away after rebooting the system, but is happens again at random times. I've change to Cyanogenmod 10, but the situation holds.
I noted that two apps seems to be producing this problem: Viber and Line. Immediately after I receive a Viber/Line call the problem arises. This is strange as I've been using Viber from the beginning, but the problem has been happening only from last week.
I would appreciate any suggestions. Thanks in advance
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
hechoen said:
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
Click to expand...
Click to collapse
I'll try using the phone without Viber/Line for a couples of days just to be sure that is a app-driven problem. Given the popularity of these apps, I would be surprised if this is only happening to me.
Did the app update recently? I'd unistall it then clear caches and reboot. If the problem goes away it's the app.
Hi @MarceloR -
I am a rep. of Viber here on XDA.
Thanks for sharing the details of the problem.
First, please note that Viber does not officially support your device, s2 skyrocket (here is the full list of fully compatible devices: http://bit.ly/Hm5k9p). Furthermore, we (Viber) don't claim to fully support devices with Custom ROMs, since it is impossible for us to adapt our app with all of the Custom ROMs out there.
Both these issues may be the sorurce of the problem you're experiencing. Have you tested this issue on Stock ROM on your device? (though it's not fully supported).
Having said that, the problem still sounds odd - Viber should not affect your ability to use your phone for regular calls.
Same problem, different software
I'm having the same issue - no mic, no sound on phone calls. I do not have either of the above-mentioned apps installed. I'm running CM10.1, though (Rogers). Tried installing the CLI3 modem, and the stock Rogers modems to see if that might help.
I did notice that the ear speaker was getting quite hot when I tried to use the phone, and the phone app itself is performing tremendously slow.
If anyone has thoughts / suggestions about how to fix this, I'd really appreciate it.
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Update: pulled SIM card, battery. Reboot, shut down, insert SIM card. Everything works again. Using the same 3/3 nightly. No other changes.
lingowistico said:
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Click to expand...
Click to collapse
Common for whom I don't have these issues. I swear how do you guys have all of these crazy problems.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
http://forum.xda-developers.com/showthread.php?p=39678817
@lingowistico -
Thank you for sharing this valuable information, that will help us aide our users as well.
If you have any news in this matter, please do let us know
lingowistico said:
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
Click to expand...
Click to collapse
I circumvented this problem by installing an old version of viber (one from Dec 2012). I found the old version here: http://www.androiddrawer.com/
So far, no problems. Everything seems to be back to normal.