[Q] Issue with push notifications - ONE Q&A, Help & Troubleshooting

Recently I've been having a problem on my OnePlus using RedPhone. Whenever I use the normal dialer to try to call someone that also has redphone, the phone tries to launch redphone and it immediately crashes. I don't even get the dialog to ask if I want to do a secure or insecure call. I found this possible thing on redphone's support forum: (I can't submit the link yet because I'm new, but PM me and I'll send the link)
The text from the link: "RedPhone requires Google’s GCM push messaging framework by default. In your RedPhone settings you can change the Signaling Method to “SMS push notifications” and see if this resolves the issue."
I am using privacy guard that came with CM11S, I am using 33R and I have the latest franco.Kernel installed aswell. I have a feeling that there is something in privacy guard that I have disabled related to google services but I can't find the right thing.
I'm thinking it's related to google push services because I also don't get notifications from Tinder, which used to work just fine. The notifications are enabled in the app.
Can anyone point me to which exact app in privacy guard needs which permission enabled so that both of these issues could be fixed? Thanks.

Related

[APP] Root Call Blocker - need some feedback please

Hi guys, Im the dev of Root Call Blocker, a powerful blocking solution. There have been a few reports of people experiencing issues with the data connection on the X, which i dont have.
Could someone please let me know if this is indeed the case?
If you do find an issue please follow this procedure:
- as soon as you spot the radio without a data connection (not after a call) send logs through the "Write to us" item in Settings
- once youve sent the report, try using the Debugging tools found in settings
- if the tools do not help, please send another report - this will still help me track issues
Thanks in advance, PR after the break
****************************************************************************************************************************************
Root Call Blocker - the only truly functional call filter
Feeling paranoid? Need privacy? Discretion? Enter Root Call Blocker, the only true call firewall available on Android.
Unlike all other call blocking apps, Root Call Blocker silently blocks calls at a system level. You need not even know its working.
Supported languages: English, Español, Français, Deutsch, Italiano, Ελληνικά, Português, Magyar, Pyccĸий, Українська.
If you want to help translate, visit http://bit.ly/wCgD4j
Advantages:
- A call will never go through
- Your phone never rings
- Reject calls from anyone, including restricted numbers
- Wildcards block groups of callers
- Keep blocked calls and messages hidden
- Five reject methods, including "Don't answer"
- Per-number logging
Features:
- Multiple profiles
- Groups integration
- Exceptions
- SMS auto-replies
- Toggle widget
- Scheduling
- Logging
- In-app replies
- Persistent and event notifications
- Customizable vibrate notifications
- Export from hidden logs
- Low profile
- And much, much more
Debugging
Please follow the instructions in the app's Settings menu to send us logs of your error. Reproduce the error, then send the log.
Market link:
https://market.android.com/details?id=fahrbot.apps.rootcallblocker.beta&feature=search_result
The Trial allows you to block one ITEM. You can use Groups to block multiple contacts.
Screens:
I've been using it the last few days, no problems here that I can tell. Note receiving telemarketing calls or calls from my congressman, so it must be working.
CleanROM 4.5
I had it on the original One X, if you remember there were some issues with RCB in the early days of that device. I recently have moved over to the One XL and have had no issues at all with RCB.
I'm running CleanROM Dev Beta 4.5
Perhaps the problems people are having has to do with the new AT&T OTA?
nooomoto said:
I had it on the original One X, if you remember there were some issues with RCB in the early days of that device. I recently have moved over to the One XL and have had no issues at all with RCB.
I'm running CleanROM Dev Beta 4.5
Perhaps the problems people are having has to do with the new AT&T OTA?
Click to expand...
Click to collapse
Its possible - unfortunately noone ever writes to us before posting the reviews on the play store, so its hard to fix the rarer problems when i have no logs to look at.
1.8.3.21
Fixed issue that lead to intermittent blocking on JB and CM10
I use it alot! I can test it etc for ya I sent a remote last night then got the update. Just let me know or I'll let ya know if i notice it buging out again thanks! Love this software helps me ignore the people I hate hahaha:good: BTW do you have a unknown caller block in this app?
thcue said:
I use it alot! I can test it etc for ya I sent a remote last night then got the update. Just let me know or I'll let ya know if i notice it buging out again thanks! Love this software helps me ignore the people I hate hahaha:good: BTW do you have a unknown caller block in this app?
Click to expand...
Click to collapse
So wait "again"? You mean you have had trouble?
Yes, look in the add dialog, toward the bottom.
ftgg99 said:
So wait "again"? You mean you have had trouble?
Yes, look in the add dialog, toward the bottom.
Click to expand...
Click to collapse
Last night before the update I did as of now I have no issues I'll report back for sure.
---------- Post added at 05:53 PM ---------- Previous post was at 05:47 PM ----------
thcue said:
Last night before the update I did as of now I have no issues I'll report back for sure.
Click to expand...
Click to collapse
And newp I still cant find the option to block unknown callers think am blind..
thcue said:
Last night before the update I did as of now I have no issues I'll report back for sure.
---------- Post added at 05:53 PM ---------- Previous post was at 05:47 PM ----------
And newp I still cant find the option to block unknown callers think am blind..
Click to expand...
Click to collapse
Go into your list setup. Press "Add". Scroll down and select "Add private and withheld".
The description reads: "Includes anyone calling from unknown, private, restricted and otherwise withheld numbers."
I am having some issues with root call blocker, basically I have it in hidden mode and when I type in the password it loads a black screen with the menu bar and nothing else, the menu bar is unresponsive. Will continue trying to send logs.
Also I am running nocturnal limited edition ROM if that helps.
EDIT: It seems if I clear my data I can get into it for a split second but once it is granted root permissions the screen goes black, I lose service, sim card has to ready itself again, and the same issue as I stated above happens again.
Sent from my HTC One X using xda premium
But aha! So, after doing a recovery install, call blocker wasn't doing its job. So, I restarted the telephony service, super user then asked to grant it access. We'll see if it works. But prior to this it wasn't even in the super user app list.
sindroidx said:
I am having some issues with root call blocker, basically I have it in hidden mode and when I type in the password it loads a black screen with the menu bar and nothing else, the menu bar is unresponsive. Will continue trying to send logs.
Also I am running nocturnal limited edition ROM if that helps.
EDIT: It seems if I clear my data I can get into it for a split second but once it is granted root permissions the screen goes black, I lose service, sim card has to ready itself again, and the same issue as I stated above happens again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I have tried to fix this apparent issue, but on our one x everything works fine. Have you tried another launcher? Or another rom? I only say this because rare issues like this are really hard to track...
XNine said:
But aha! So, after doing a recovery install, call blocker wasn't doing its job. So, I restarted the telephony service, super user then asked to grant it access. We'll see if it works. But prior to this it wasn't even in the super user app list.
Click to expand...
Click to collapse
Sorry what are you saying? That whatever you did in recovery broke root call blocker?
ftgg99 said:
Sorry what are you saying? That whatever you did in recovery broke root call blocker?
Click to expand...
Click to collapse
Something along those lines. I did a Nandroid of my ROM with Root Call Blocker on it. I flashed a few ROMs but decided that CleanROM was the one for me. So I flashed it back through recovery.
Upon doing this, SU never asked to grant permissions for RBC, nor was it on the list of approved apps. RBC then let a few "Unknown" calls through."
I cleared cache, deleted the app, reinstalled it, but nothing. SU was never even triggered. After I went through the Settings and restarted the telephony service in RBC's settings, SU asked to grant it permissions. So, perhaps that's a fix for anyone who's not having their calls blocked?
Never mind haha
How much does it cost after the trial ends?
EDIT: Never mind I see there is a pro version. A little too expensive for me. I probably wouldn't use it much. If it was like $3.49 or around there I could see buying it. Anyway, sounds like a really good app. Keep up the good work.
Sent from my One X using xda app-developers app
I'm not sure that clicking "enable blocking" counts as a fix.
I didn't say anything about enable blocking. I said restart telephony is what I clicked. Enable blocking was checked off and the app wasn't working.
XNine said:
I didn't say anything about enable blocking. I said restart telephony is what I clicked. Enable blocking was checked off and the app wasn't working.
Click to expand...
Click to collapse
What you are saying is that somehow the app never had root. That is not a problem with the app, but rather with the user.
ftgg99 said:
What you are saying is that somehow the app never had root. That is not a problem with the app, but rather with the user.
Click to expand...
Click to collapse
If you say so. But clicking/unclicking Enable Blocking did nothing to trigger a response from SU. Not to mention, prior to the recovery, it worked just fine. Hitting the "reset telephony option" changed that.
But hey, if you don't want people trying to help you with YOUR bad programming (for free no less), that's on you. There's other apps in the market that don't have this issue and do the same thing.
ftgg99 said:
I have tried to fix this apparent issue, but on our one x everything works fine. Have you tried another launcher? Or another rom? I only say this because rare issues like this are really hard to track..
Click to expand...
Click to collapse
I have tried other ROMs and even a stock build. I've cleared cache, etc. but am still unable to get anything to show when I open it. Unfortunately I have tried everything I can think of to get logs but have been unsuccessful. When I first install it there is no problems other than having trouble getting root at first. Not sure if logs from that stage will help since the issue doesn't occur till I set up hidden mode.
Sent from my HTC One X using xda premium

Forward lookup

Hi all. I recently updated the software to 38R and noticed that forward lookup no longer works on the dialer. I've got the setting ticked and the lookup provider is still Google but nothing works.
Is anyone else having this problem?
I have the same issue. I changed the provider but still it won't lookup nearby business phone numbers. Even the reverse lookup is not performing
I hope it gets patched.
Sorry for the bump but has anyone found a way to solve this? It doesn't work with the CM12 Dialer App either and I really miss this functionality from the Stock Google Dialer found on my Nexus 5. I've tried a lot of different ways to get the Google Dialer 2.0 APK working on CM12 including trying to deodex the apk and then building a version of CM12 with odexing enabled and everything just resulted in the dialer force closing, so I'm at a loss here.
EDIT: Well... I did all of that... just to find out my issue with Forward Lookup was that somehow my location services managed to turn itself off. Turned it on and it works now. I feel like a fool but I'll leave this here in case anyone else is having similar troubles.

After Android 6 upgrade, Google Apps are acting odd

This seems to have started after the upgrade to 6... I don't get consistent notification from Gmail, I get no notification from Google rewards, and Google messenger does not send mms. Reinstalled messenger to no avail. Installed textra and it works flawlessly.
All of settings for notifications are on. It's very weird. Anyone else see anything like this? If so anyone figure out a fix, by chance? Thanks.
Sent from my MotoG3 using Tapatalk
I had an issue with my Chromebook not recognizing my phone when attached via USB. The issued was resolved when the Chromebook OS was auto-updated to version 48.
Maybe it's because of Doze. Change the "optimized" setting for applications you'd like to have notifications in real time (especially when screen is off).
The MMS problem is something else though.

Possible to replace the Google Phone (Dialer) App without rooting/flashing?

Hey everybody,
I'm currently in the process of minimizing my phones reliance on Google Apps without installing a custom ROM. Thus, I skipped the account login and disabled all the Google Apps I could and installed alternatives from F-Droid.
Unfortunately I so far haven't been able to get an alternative dialer app (Emerald Dialer, Lineage Dialer) to work, as the ones I've tested so far seem to rely on the Google Phone app being enabled to work. Seemingly, the system apps responsible for managing calls restrict the possible apps that can be used to place calls.
Does anybody know of a solution for this? Thank you! <3
[deleted]
Just in case somebody looking for a solution to the same issue finds this thread:
Turns out my problem was that most alternative dialers don't come with a custom call screen. Calls would still be placed and received, but there was no way to hang up, mute, hold, etc.
The app Should I Answer? does provide its own call screen and can be set as the default phone app. Also I read through their Privacy Policy, and though they use Analytics, like almost every non-FOSS app, at least they don't sell data to third parties or build user profiles like Google does.
Be aware, that you have to activate some blocking option in the app in order to enable the custom call screen.
Hope this helps, have a good one.

Kernel wakelock how to restore functionality

Hi
[no root]
Tell me please how to get / view the program logs? and will it be possible to understand from these logs what the program issue?
The situation is as follows - I installed Wakelock Detector 2.1.0 and the kernel mode worked. then I changed something in the phone settings (but not related to the program), for example samsung push nitification prohibited working in mobile networks. for goole play service removed permishins for microphone, etc. And the kernel mode stopped working. gives the error "Faild perform this time. try later"
Using logs I want to understand what it is missing.
PS: there is another phone nearby where the kernel works in case it helps to quickly understand what it needs.

Categories

Resources