I've been using my N6 for 1.5 weeks now, coming over from a Samsung Galaxy S3. I'm on Verizon.
Not sure what the occasion is today, but I just received 2 calls this morning from telemarketers/scammers. On my S3, blocking these callers was as simple as long-pressing the number on the stock phone app and clicking "add to reject list". It was a great feature and didn't require me to get any 3rd party apps. I just tried to do that on my N6, and there doesn't seem any way to do this. Long pressing the numbers doesn't do anything, and I don't see anything in the settings either. Has anyone had any luck with this?
Related
I want my freaking conference call management options back! When will they update this crap? It's sad that an "upgraded" phone has worse features than the old one!
What features.
BACARDILIMON said:
What features.
Click to expand...
Click to collapse
Like, the ability to end a specific call or mute a specific call. The options went away when I "upgraded" from a Galaxy S5 to a Galaxy Note 4.
Grymmstorm said:
Like, the ability to end a specific call or mute a specific call. The options went away when I "upgraded" from a Galaxy S5 to a Galaxy Note 4.
Click to expand...
Click to collapse
I think you need to test a bit more. Those features still in my phone.
BACARDILIMON said:
I think you need to test a bit more. Those features still in my phone.
Click to expand...
Click to collapse
Then you have a different phone...I use the conference call feature on my phone 3-5 times a day. I do not have an option to end a single call or mute a single call. I can add calls, sure, but I cannot MANAGE the conference call. I used to do it with no problems on my old Galaxy S5.
Grymmstorm said:
Then you have a different phone...I use the conference call feature on my phone 3-5 times a day. I do not have an option to end a single call or mute a single call. I can add calls, sure, but I cannot MANAGE the conference call. I used to do it with no problems on my old Galaxy S5.
Click to expand...
Click to collapse
Play around with the phone I was able to more test call while other call heard me. I would post video but don't need my contacts numbers being out their. I use this for work so I know it is all in. Now if ur running a custom rom ask dev if he removed feature
I am running a normal, unrooted, Galaxy Note 4 straight from T-Mobile. I can place a call, then add another call to make it a conference, I can even add at least 4 calls (I haven't needed to try more than that). I cannot choose to end one of the calls or mute one once the conference call has been started. Is the option hidden somewhere? I have tried clicking just about everything during the call, and have gone through EVERY option in the settings and can't find anything about conference calling. There are a few hits on Google that show the steps for conference calls, and one actually shows pictures of managing one. But it looks just like the S5 management looked like, and I don't have the big button on screen that I used to have to manage the conference calls. Believe me, I'm not a newbie to conference calls. I have done 3-5 per day for the last several YEARS. This is my 4th Galaxy product, and it is the first one I've had issues with.
Maybe reach out to samsung.
I can't get any root call blocking apps to work on Marshmallow ROMs. Root call blocker, which I've used for several years and on several different phones was my call blocker app of choice, but it stopped working once I upgraded to Marshmallow (had that problem with both the Nexus 5 and the Nexus 6 I'm currently using). I have noticed that it works flawlessly with Lollipop ROMs, but not Marshmallow. And the RCB developer is no help. Has anyone gotten RCB or any other call blocking app to work on Marshmallow? And if so, how? Also, if there are other call blocking apps out there that will work on Marshmallow, I'd like to know about them. And I want a real call blocker, not one that sends the caller to voicemail (to me, that's not call blocking).
Have you checked out the Marshmallow inbuilt call blocker? Phone/history list/long press on the "bad" caller/"Block number".
I haven't tried it myself yet (no scammers have called me recently) and you have to receive at least the first unwanted call, but after that they should be gone.
dahawthorne said:
Have you checked out the Marshmallow inbuilt call blocker? Phone/history list/long press on the "bad" caller/"Block number".
I haven't tried it myself yet (no scammers have called me recently) and you have to receive at least the first unwanted call, but after that they should be gone.
Click to expand...
Click to collapse
Yeah I've tried it. It doesn't work either.
Sent from my Nexus 6 using Tapatalk
Has anybody figured out a way to get this to answer calls from the Google Voice and/or Hangouts apps? I have the added complication of using it with a tablet that "can't" make voice calls. The "Phone" app is hidden and with everything I've tried (nothing tricky, just the standard options), my Neo tells me something like "your connected Android device is not capable of making calls."
I'm using a rooted AT&T Samsung Galaxy Tab S (SM-T807A), running Android 5.0.2. I'd like to be running basically anything other than TouchWiz but locked bootloader is a pretty big hindrance.
My Neo is running software version R381XXU0BOA2.
I'm able to get notifications from the Hangouts app (even missed call notifications, ironically) so I suspect that if I could somehow trick the Neo into thinking the T807 is (for example) a Galaxy S5, it might let me answer calls. But I have no idea how to do that or if that's even where the problem is.
Google Voice did not ring on incoming calls for my Pixel 5. I tried all the online advice I could find but still failed. After 2 weeks of experimenting, I stumbled on a workaround today! I am still asking this question online so that I can share it with the public.
Many online blogs acknowledge this is a Google bug and the most prevalent workaround is to “use carrier only” for “Making and receiving calls” under Google Voice settings.
"Use carrier only" unfortunately is not much of a solution for those who travel internationally! Google Voice would expect this carrier to be a U.S. company during configuration. Roaming internationally on a U.S. carrier number runs up a HUUUGE phone bill! It begs the question of why even bother with GV if I want to involve my U.S. carrier number when I travel overseas. If I were in the U.S. today, with my unlimited plan, I would see no reasons to use GV either except if I just want to have a separate phone number that is always mine. "use carrier only" is totally brain dead from the cost perspective.
When I was on my Samsung S4, I didn't have this problem. Finally, I decided to upgrade to Pixel 5 and GV stopped ringing for an incoming call.
After I upgraded to Pixel 5, I wiped clean my S4 thinking I would either donate it or give it to a kid as a toy. Out of curiosity, I installed GV again on my S4 today to see if it still works. GV does NOT treat my S4 as a separate device but as the same "Android Device" on my Pixel 5. I guess this is due to both phones are logging into the same account. I then called my GV number and my Pixel started to ring! Curiously, S4 didn't ring. As an experiment, I opened the notification settings of the GV app on my S4 and customized it to the way I wanted it. Now, when I called my GV number, the Pixel didn't ring but the S4 rang! After that, I tried both disabling notifications on the S4 for GV and turning off S4, both methods would enable the Pixel to ring again!
Since the Pixel 5 would ring when the S4 is turned off, what would happen if GV is uninstalled from the S4? Well, the Pixel 5 stops ringing! I re-installed GV on the S4 and called my GV number, the S4 started to ring while the Pixel remained silent. This contrasts the situation after the 1st installation, ie. the Pixel rang instead.
Here is my observation:
*Both phones must have GV installed to work.
*GV would only ring one of the 2 phones, but it's hard to say which phone would ring if both are on and the notifications are enabled on both
*By disabling notifications on the S4 or turning off the phone, the Pixel always rings
*Now I can use GV either over Wi-Fi or my European SIM (traveling in Eu currently) to receive and make calls
For those who are writing these what to do with an old phone blogs, I guess they can add this workaround to their list, ie. to fix a bug for Google! I assume the old one has to be a device that doesn't have this problem to begin with. Haha.
Need help diagnosing and solving a bizarre problem: S10 doesn't receive texts from a specific sender, except after restarting, retroactively receives all texts sent by that sender. Supernatural powers might be involved, given the sender's phone is mine, and the fickle S10 is my wife's.
I'm including a lot of info below, b/c this seems to be a tough problem to diagnose, so I'm erring on the side of completeness.
Specs: My phone is an LG V35, rooted with Magisk, Android 9. Her S10 is not rooted, running Android 9. Her phone is logged in to the same Google account I use on the Play Store, so that she can use any of my paid apps without paying again. (This has never caused any SMS problems in the past, just annoyances like her getting my reminders, which I then turned off on her phone.)
The problem started on 10/26/22 (about three weeks ago). I know this b/c I sent her a long text that day, which her phone received immediately, followed by another text that same day, which she didn't receive until eight days later on 11/3/22. There were several other texts I sent btw 10/26 and 11/2 that she didn't receive until 11/3. However, we did not catch this problem until yesterday (11/17), when she discovered that I had not, in fact, been ghosting her, but that her phone was not getting my texts. We found this out b/c some other app on her phone wasn't behaving normally, so I restarted her phone -- and BAM, all my unreceived texts suddenly arrived on her phone. Since then, I've tried texting her phone, and it receives nothing from me until a restart, and then her phone receives all my texts retroactively.
As far as we can tell, neither of our phones has any problem with SMS communications with anyone else's phone (except some iPhones -- don't get me started). Other people receive my texts normally, and her phone receives other people's texts normally.
I tried texting her from two different Google Voice accounts I have (both different from the Google account our phones share), and her phone received both G-Voice texts immediately.
I tried changing my SMS app (from Pulse to Textra). No effect (her S10 didn't receive texts until restarting). I tried changing her SMS app. No effect. I did a Samsung software update (thru Settings) on her phone. No effect.
I have an old S10e, my last phone before I switched to the LG. As an experiment, I popped her phone's SIM card into my old S10e. I installed an SMS app neither of us has ever used before, Handcent Next, on the S10e. Without doing anything else (i.e. w/o transferring her S10 data or settings to the S10e), I texted her number from my LG. The text arrived immediately in Handcent. I thought, Eureka!
I promptly factory-reset my S10e, and used Samsung's Smart Switch to transfer "Everything" from her S10 to the S10e. After all her data, apps, & settings were transferred to the S10e, I texted her number, and… NOTHING. The S10e did not receive my text, until I restarted it.
So, my question to all Android sleuths out there is: What the hell?
Excellent detail and info.
My initial guess may be because you're sharing the Google account. Yes, I know you said this didn't cause problems before, but now with Google Messages (I know you're not using that, but still) doing lots of RCS and background stuff, I imagine there may be some behind-the-scenes interaction that is causing problems. I'm not saying this is a fault of RCS or anything like that, but I think the sharing may be the issue?
I would suggest trying to create a new Google account, and keeping the phones on separate accounts... it's a free and easy test, I figure... and you seem quite skilled in more difficult things, so this should be easy enough?
Also note, some apps support family sharing, so if you setup a "family" between the two accounts, you may get the purchased apps on both accounts without too much issue. My wife and I do this and it has worked pretty well for our apps. (FWIW, we both have S10+ and use GMessages on separate google accounts, family shared, and don't have any issues with texts, etc.)
schwinn8: I liked your idea & reasoning, and I implemented it -- new personal Gmail account for her, added to my G-family. Restarted her phone, and sent her a text which did not arrive. (I texted her from a Google Voice account, and that SMS arrived instantly.) I then restarted her phone again, and, for the first time, the initial text still did not arrive. That's new, at least.
What setting could possibly delay a text from coming in?
Well, that's not the direction I wanted things to go either!
Not sure what else could delay texts from coming in... not aware of any delay mechanisms in most cases.
Are both on Wifi during this process? Is the LG running a ROM with working VOWIFI? Yes, I am grasping at straws...
Well, recalling my old Windows 3.x experiences, I factory-reset the S10e (my old phone), and installed all of my wife's apps and recreated all her settings on it from scratch -- i.e. no transferring apps or settings from her phone. A labor-intensive solution, to be sure, but it is working so far. The S10e receives my texts normally.