Related
Hello, im the developer of Root Call Blocker, an advanced call and SMS blocking app for rooted phones.
The app is currently in open beta here at XDA:
http://forum.xda-developers.com/showthread.php?t=1051274
I dont have the inspire and need testers! Please let me know if you are interested in some hard-core testing and logging...
Your in the wrong place, the inspire isn't a CDMA phone.
That was just a copy paste issue - we still need testers of all sorts, so dont be shy!
I actually stumbled upon this in the market about 2 days ago and downloaded. It actually blocked all of my calls, incoming and outgoing. Since i couldnt call out i promptly uninstalled it. I'll be honest, i didnt spend a whole lot of time with it and at that moment didnt have time to really test it out much.
Theres no way it could be blocking outgoing calls. We have tested it extensively and this is the first time I hear mention of the issue...
After I installed it, if I manually typed in a number and hit the call button then the keypad would just disappear and return to my call history, after I uninstalled I was able to place calls again..
I didn't try a number from my contact list though, so I don't know if that had anything to do with it.. I would have tested further but my kids were with a baby sitter and I needed my phone to work.. I love the concept though
Sent from my Desire HD using XDA Premium App
I've been running it now for I guess 2 weeks. I have my ex and her boyfriends number in my blacklist. Been working great
Good to know... be sure to donate!
Been running it for awhile now and its great for blocking the annoying unknown numbers. Keep up the good work.
Thank you! Prey tell, does it block it block SMS as well?
I don't really get any.unknown SMS so I don't know
Hi, you could always use Skype to call/text yourself. I often calls from unknown and private numbers...
I had the same problem if not being able to make calls. Had to turn the app off to fix. Any idea why it would be doing that?
It should not be doing that. In fact, you are the first person to have this issue.
It is probably your rom, but if you want us to fix it, please, send some logs (use the "send debug data" menu item).
Here's the logcat
http://db.tt/WYZ5JaJ
Hi, that is not what we need - the app has its own logging mechanism. Please use the "Send debug data" menu item in Settings. Be sure to include a brief description of your error at the top of the page!
Hello guys, please get me some feedbeack on the latest build. Are sms blocking issues with ";block and save" still present?
Guys, whats the story - many agreed to test but im getting no logs from people with inspires!
ftgg99 said:
Guys, whats the story - many agreed to test but im getting no logs from people with inspires!
Click to expand...
Click to collapse
I havent re-installed this yet... but just so you know, the MODEL of the inspire actually shows up as Desire HD.. so if you are looking for MODEL=Inspire in the debug logs, then you wont ever see any, unless someone changes the build.prop
i havent sent a log because i havent had a problem. Today i got a call that was supposed to be blocked, and when i opened the app it said that that version had expired. i uninstalled and reinstalled and all is good again.
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
Hi all,
I've done some searching on this and found some "general" instances of this happening in the official Sprint Community forums, but nothing of value and certainly nothing with particular application to the Shift.
I recently rooted and installed CM7.2RC2 on a family member's phone (not 7.2 final due to bluetooth bug). Although I'm no expert, I've rooted a number of phones and had no issue with the awesome directions provided on these forums.
Randomly, when making a call, the Shift dialer does not ring once "send" is pressed, but rather one only hears an "echo" of anything being said into the phone. On the other end, the call seems to connect normally; however, the recipient only hears an echo of their own voice as well. As such, the two parties cannot communicate, despite the fact that for all appearances the call is connected.
This occurs in the opposite situation as well. Seemingly randomly, if a call is placed into the Shift, the user of the Shift can accept the call no problem. However, once the call is accepted, the person using the Shift only hears an echo of their own voice. On the dialing end, the call appears to be connected, but that caller only hears an echo of their own voice as well.
The issue tends to occur in "blocks", like a few calls won't work, but then it'll work normally again all of a sudden. The phone might be fine for a few hours, then randomly it'll happen again.
I've attempted to downgrade to CM7.1, upgrade to the latest nightly, and use just about everything in between with no luck. I updated the radios to the current version again (also did this during the rooting process, updating the profile/prl/pri as well, before flashing CM). Last night I downloaded newSENSE in the hopes of flashing that tonight and using the Sense interface to update the Profile on the phone. However, I'm not sure that will do any good if I nan back to CM7.2RC2.
Just wanted to shoot this out to the rest of the group to see if anyone else might have had this same or a similar issue with their Shift. I've used CM/AOKP on my OG Evo since I brought it home and never experienced anything similar.
Thanks for any thoughts/input!
--DC
This happens to me on cm9.
I can still hear the other person, but I always hear a slight echo (not enough to make the conversation impossible)
Its annoying, but its not too bad.
As far as I know, the other person doesn't experience any echo.
Sounds similar...but the only difference is, with my issue, neither party can hear the other. All each party hears is a slight time-delayed echo of their own voice; not the other person.
When the issue occurs during a dial-out on the Shift, the caller on the Shift doesn't even hear the "ringing" of the phone on the other end to confirm that the call is being routed (although it is, and the person on the other end can pick up)...all the Shift user hears from the point where they press the dial key is an echo of what is on their end of the line.
It's very weird.
Also, if it helps, the phone has Google Voice integration enabled on Sprint. I'm seeing some posts saying that this may be the issue, although I'm not convinced since this problem never presented itself prior to rooting/flashing.
Thanks!
--DC
DamienChaos said:
Sounds similar...but the only difference is, with my issue, neither party can hear the other. All each party hears is a slight time-delayed echo of their own voice; not the other person.
When the issue occurs during a dial-out on the Shift, the caller on the Shift doesn't even hear the "ringing" of the phone on the other end to confirm that the call is being routed (although it is, and the person on the other end can pick up)...all the Shift user hears from the point where they press the dial key is an echo of what is on their end of the line.
It's very weird.
Also, if it helps, the phone has Google Voice integration enabled on Sprint. I'm seeing some posts saying that this may be the issue, although I'm not convinced since this problem never presented itself prior to rooting/flashing.
Thanks!
--DC
Click to expand...
Click to collapse
Yeah, it hasn't been as bad as your situation.
This ROM has google voice installed on it, but I disabled it (i dont like it lol)
I honestly don't know what could be causing the echo.
I haven't tried flashing other roms to see if the echoing persists because it's not too much of a nuisance for me.
I don't know the cause of your issue, so not much help. But I can say I have had Voice integration setup for a while now, across all different types of ROMS and never experienced this problem. Everything from the new ICS/CM9 Roms, chinese ports and etc.. to me just having to unroot back to stock today, the integration has worked for me without a problem on everything.
I'm running NewSense and get an echo call once a day or so. Isn't continous and if I hang up and dial again it always goes through normally. I was running CM7 and UKE ROM and can't remember if I had the same issue so I just deal with it and assume it's a Sprint service glitch. As it's not terrible, I don't feel like reflashing just to see if that would fix it.
As a quick update: This morning I deactivated Google Voice integration on the line and the user has had not experienced the problem since I took that action (approx 14hrs of normal use sending/receiving numerous calls).
I'm going to reintegrate Google Voice on the line tomorrow, giving it 24hrs to be sure that was the issue, and will report back whether the problem returns.
In the interim, thanks again to all for your input!
--DC
After reintegration of Google Voice on Sprint, the issue reappeared immediately. As a result, I've just decided to forego Google Voice integration and instead set up conditional call forwarding. Not really a big deal; but still a very odd bug! Odds are I'll re-try the integration again at some point in the future, but for now call forwarding should be fine.
Oh well, hope this might help out someone else in the future!
same issue on Evo 4G LTE
I am experiencing exactly the same issue on my Evo 4G LTE. I have Google voice integration as well. I was told at a Sprint store that it is a known network issue (even happening on iphones) and that I should call Sprint and tell them where it was happening, but I'm pretty sure they have no idea it has anything to do with Google Voice, and I know the low level customer support rep that I get when I call *2 is not going to be helpful at all, nor will they accept the evidence that it is a GV issue. I really don't want to disable GV integration, but if that is what I have to do, I will.
Oh, and this is happening on a stock rom both with S-OFF and S-ON
Same thing on ET4G (S2), At first I thought it was a hardware problem so I took it to Sprint and they gave me a new phone. The problem persisted. Then I suspected it was Google Voice. I use GV's features all the time so disconnecting it from Sprint is not a preferable option. Has anyone made any progress on this?
If you read the other posts, he said that the only way to fix it that he found was to disable google voice. If you mean to ask if there is any workaround, I would not think so, but if you absolutely needed to use Google Voice, you could RUU back to stock (only if rooted) and then take it to Sprint to have them replace it
It might also help if you exaggerated your problems a bit, thats what I did and they gave me a new phone for no charge
Sent from my PG06100 using xda premium
EDIT: Sorry ignore my post, I didn't read your post completely.
---------- Post added at 02:13 PM ---------- Previous post was at 02:07 PM ----------
As an alternative to Google Voice, you could always use something like Skyvie from the Play Store
Sent from my PG06100 using xda premium
Just thought I'd update for posterity. The user of the Evo Shift 4g has been using a Photon Q since release with Google Voice integration. This week it started developing this same issues with calls in/out echoing with at least one party not being able to hear the other. Although the user of that handset loves GV, I think I might just turn off integration permanently and relegate GV to a voicemail service rather than an all-encompassing messaging client. Too bad, really. The integration was a great idea.
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Roy2208 said:
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Click to expand...
Click to collapse
Unfortunately this is a known issue that hundreds, if not thousands of people have been experiencing and reporting ever since the phone was released a year ago. So yes ever since 4.4, before even 4.4.2. Even more unfortunately it is a known issue that neither Google nor any carriers admit to own up to. Anyways to my knowledge no one knows if it is a software or hardware issue, but it is most likely not a carrier issue since it is reproduced on multiple different carriers. Anyways I will link you to the Google Forums thread that started on this issue a year ago and has hundreds of people posting and reporting it in that thread. You can find that post if you click right here.
The only solution is a work around, not a permanent solution. If you find out that someone called you, and the phone did not ring, restart the phone. It seems to have resolved the issue temporarily. I always restart mine every 2 to 3 days anyways to try to prevent it as little as possible, so that is what I would suggest. Also maybe state on your voice mail if you did not pick up to leave you a voice mail or send you a text so you know they called, because you been having issues with calls on your phone. That way you know someone called, because you will still get the text message or voice mail notification.
I had the problem mentioned in the second post (which may not be what OP was describing) and I solved it by trying out different radios. Latest one with Lollipop is fine, but the two before that weren't good.
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Flash something else more stable that better suits your needs for now. This rom is still a work in progress. There will be a few hiccups from time to time. Wait for the next update
Sent from my SAMSUNG-SM-G890A
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
spacebar208 said:
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
Click to expand...
Click to collapse
I'm on 20151222 right now until the problem be solve
Sent from my SGH-I727 using Tapatalk
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Cyanogen Mod is dead
dimapoter said:
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Click to expand...
Click to collapse
I don't think anything will really work in cm now because it's now discontinued and function will not work Cyanogen Account, etc. I also think it's modems stopped working... see here:Click Here