yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] badboytw:
What I did is backup app+data but reinstalled from PlayStore and opened up app to where it asked you to login and then goto TiB and restored Data and it worked for me!

I wish best to luck to everyone!
[Android Q&A, Help & Troubleshooting] Noiz:
Also having the same issue but I've restored so many apps that I don't know which ones, other than the obvious messengers and the like, use GCM and might have it broken. I did at least figure out that deleting the app data (or uninstalling/reinstalling from the Play Store in my case) fixes the problem on an app by app basis.

A thought occurred to me but I haven't tried it myself... Has anyone tried restoring an app while using SuperSU? I seem to recall Titanium prompting that normal SU isn't very good and should be changed for optimal results but I've always ignored it. Maybe it's affecting that part of the restore.

---------- Post added at 02:00 PM ---------- Previous post was at 01:26 PM ----------

Tested my own theory with Voxer and it didn't help.
[Android Q&A, Help & Troubleshooting] Hirishiolo:
for me "Push Notifications Fixer" didn't resolve the problem with Whatsapp and UppTalk. To re-enable notifications and not lose data I do this:

1) delete AppData

2) open the App

3) login

4) restore AppData

like badboytw suggested above...
[Android Q&A, Help & Troubleshooting] L.iam:
A clue as to which apps break?

If you run Xposed w/greenify does Titanium only break the apps with the GCM cloud? I'm just curious as it will make clearing data on those apps much easier than clearing all data.

I'm shocked that there still hasn't been a one-stop fix for this other than clear and log back in.
[Android Q&A, Help & Troubleshooting] nldxda:
Add me to the list of people needing a fix for the broken push notifications problem..

I've suffered this problem for years now across different devices and now the whole reinstalling broken apps from the play store after a restore has gotten outta hand.. Too many apps to have to keep track of that need manual restore..

For once, I just tried the "app backup & restore" app to restore my apps and then restore those apps' data from TB backup (data only).. The push notifications problem is still there!

Is it something in the data restore process (not app restore) from TB that causes this maybe? Had to manually reinstall my email apps.. I imagine a bunch of other apps are "broken" atm..

I even tried installing the pnf app and hitting the reset default heartbeats, which didn't fix anything..

I even sent an email to TB support days ago, but no reply.. Can't believe this hasn't been addressed by TB in all this time..
[Android Q&A, Help & Troubleshooting] ccelis:
I've the the same problem up until today. I almost reflashed my rom because I'm not getting notifications from Facebook, messenger and most importantly I can't use pushbullet. I made the same mistake of restoring app+data of those apps and clearing data or reinstalling did not work.

What I did was removed my Google account, clear data of play store, Google play services and Google services framework. Reboot to recovery and wipe dalvik and cache. After booting to system, I added my Google account again and all of a sudden my Facebook messenger notification was working again. I was also able to successfully register my device to pushbullet.

Hope this helps

Sent from my LG-F320L
[Android Q&A, Help & Troubleshooting] gieffe22:
by 1 week i have the same fu**** problem! ...i tried everything but nothing!...now i try your way and let other know if this works!

in my case is not titanium problem...i have this problem even with full wipe, i think it's a play services v5 problem!... tried 3 rom for my phone, stock samsung, cyano, and another one...nothing...

EDIT

still not working sync...incredible, i'm so pissed!!!! never had this problem on 4 years of android!
[Android Q&A, Help & Troubleshooting] ccelis:
Have you tried if it's working on a different phone?

Sent from my LG-F320L
[Android Q&A, Help & Troubleshooting] gieffe22:
on my gs2 is perfetcly working sync...it's only one my s3 the problem...and pretty much with wifi... with data it seems to working good...wifi router in my case is ever the same since 4 years, and never had any problem
[Android Q&A, Help & Troubleshooting] maids:
Factory reset

My titanium backup is on my computer.

How do I put one app back with data.

Also cant backup on sd card any more app cant find it
[Android Q&A, Help & Troubleshooting] harryspar:
FIX: Defrost Talk / Hangouts

In my case, defrosting Talk/Hangouts and Network Location fixed it for me instantly.

I believe in some versions of Google Services Framework, the registration for pushes is managed by a service built into the GTalk service and somehow connected to the Network Location service.

BTW a good app to test if Push is working for you is the free Push Notification Test: https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester&hl=en
[Android Q&A, Help & Troubleshooting] jaymino:
none of these "fixes" work
[Android Q&A, Help & Troubleshooting] zmalach:
I have the same problem with TiBu, notifications are random!! Also in some app, TiBu hang on restoring app+data forever and I have to restart my phone or kill the process, any idea??
[Android Q&A, Help & Troubleshooting] jlechner:
Add me to this list. I've noticed that when the app updates on the play store (or manually if I'm "acquiring" the apk) then the notifications start working again. Hopefully that will give someone a clue on how to fix this.
[Android Q&A, Help & Troubleshooting] 43matthew:
gcm is just broken on restore

tl;dr push notifications just won't work across restore for some apps.

This is years late, but might be useful for anyone who finds this thread after the fact, like myself.

App developers using push notifications usually end up storing a device-specific token in the app's data directory (in a shared preferences file).

Because titanium backup (and others) basically do the equivalent of "adb backup" and "adb restore" this results in this device-specific token getting backed up and restored.

Now on the new device that has just been restored, the app starts up and checks its shared preferences file - it determines that there's already this token present so it doesn't bother to ask for a new one. This is what breaks - the token is associated with the original device, so any push notifications that are sent by the app's server to the app will actually be routed to the original device. Effectively the newly restored app never registered for push notifications so can never receive push notifications - but it doesn't know this b/c it uses the old token's existence as proof that in fact is has already registered.

Now some apps will work - for e.g. those apps that correctly store this token in a folder that "adb backup" knows to ignore, or those apps that never bothered storing it in the first place (instead they just query the api for the token each time the app starts).
[Android Q&A, Help & Troubleshooting] seanpr123:
Nice response and info there Matt, thanks for registering just to give a bit of insight.
[Android Q&A, Help & Troubleshooting] Mysterion1:
The problem still exists in 2k16.......
[Android Q&A, Help & Troubleshooting] 1651321:
Yep, problem also exists here on Android 6.0.1 after restore using Titanium Backup. Titanium should really think about something to deal with that problem :mad:
[Android Q&A, Help & Troubleshooting] Mysterion1:
On androidpit a guy told me the solution is backing up the Android ID before changing the custom rom. Without the ID matching to the apps data, notifications won't work at all. I actually don't know where to backup the ID in TB but maybe this helps you.
[Android Q&A, Help & Troubleshooting] 1651321:
Thanks for the advice! But I think Titanium Backup is already doing this. When you start Titanium the first time after changing to a different ROM, there appears a popup which lets you restore the Android ID. However, the problem with the not-working notifications is still there after doing this.
[Android Q&A, Help & Troubleshooting] thoros1179:
Exactly. I have the same problem and I always restore the Android Id of the previous Rom with TB. Before changing Roms I extract WhatsApp and Threema apks, backup my data from within the apps and after flashing new Rom I reinstall the apps from my extracted apks manually and restore data. This is a very annoying procedure and I'm also hoping this is addressed by TB team. Since the issue is years old until how I doubt it will be fixed.
[Android Q&A, Help & Troubleshooting] InfX:
I am probably way too late with this, but i wonder if sending an "android.intent.action.MY_PACKAGE_REPLACED" intent to the offending app would make it re-register for the GCM. The reason i think this would work is because the GCM token invalidates at application update. And that's the intent an app is supposed to use in order to detect it, it really should re-subscribe so the GCM doesn't break on update. I can't really try it right now (already wiped the data for offending apps), but whoever stumbles upon this thread and have some app ready to try, go ahead and report it.

Using an am command from the shell should do the trick, something like the one below, just replace the "com.example.application" with an offending app package name. Feel free to try and broadcast it to all apps as well, but be theoretically ready for another restore if you do.

am broadcast -a "android.intent.action.MY_PACKAGE_REPLACED" -d "com.example.application"

Edit: The -d switch I've mentioned above is wrong, it doesn't target a specific app, I've copied it from some unknown web page without actually checking. Using the command above will send the intent to ALL installed apps, even if you do specify the right package name with -d. Although, i did try it on my device without knowing, and it didn't cause any visible damage. And it did fix GCM for at least one app (that i'd rather keep broken - McDonalds). Note that in order to send this intent to just one app with "am" one should seemingly use the -n switch, which requires one to explicitly specify the broadcast receiver name, something you don't know without extracting the manifest from the app. Anyway, if you have GCM issues and don't mind risking another restore, try it...

am broadcast -a "android.intent.action.MY_PACKAGE_REPLACED"
[Android Q&A, Help & Troubleshooting] tefole:
Any further processes on this issue? I have exactly the same issues with non-properly-working push notifications with whatsapp.

The known workaround is a reinstall and avoiding TB.

Threema isnt a big deal, hence there is well export/import of settings and messages.

But whatsapp is renewing the encryption keys on every fresh install. So, if you are reinstalling whatsapp on every test of a CFW, all your chat contacts and groups will be informed. I

I did four times in the last two weeks. Thats annoying, indiscrete, consufing and it is looking quite incompetent.
[Android Q&A, Help & Troubleshooting] italia0101:
2017 , this is still a problem, i'm guessing its just a no go at this point, i'll have to rely on google backup and uninstall t-backup me thinks.
[Android Q&A, Help & Troubleshooting] patrickdrd:
I don't think it's a titanium problem (ok, titanium could help if it was backing up the token),

but an android one,

I even rooted my 2nd phone this weekend (I didn't have to restore anything, I didn't use titanium) and

notifications broke
[Android Q&A, Help & Troubleshooting] rionline:
Nice, thanks... It seems to work for me...

1 Installing older version via apk than in playstore

2 Restoring data with TB

3 Updating app in playstore
[Android Q&A, Help & Troubleshooting] gumikjuggler:
I wonder if it can be somehow automated in TB. And if you don't have older version, then maybe forcing upade with the same version would be enough too. However, I'm not sure if there is any possibility to "update" with the same version. Maybe some hacking of version number would do the job and make Play Store think you have older version. Then it should allow to update.
[Android Q&A, Help & Troubleshooting] zelendel:
Well the fact that you are restoring system data very well could be causing the issue. It is never advised to do this as the code in that partition changes all the time. Also restoring the Android id has never worked for me personally. It has always caused issues.
[Android Q&A, Help & Troubleshooting] Agent.:
Still would love a fix for this.
[Android Q&A, Help & Troubleshooting] mko000:
Has anyone tried deleting the

com.google.android.gms.appid.xml

files in the apps data folders?

E.g.

/data/data/com.whatsapp/shared_prefs/com.google.android.gms.appid.xml
[Android Q&A, Help & Troubleshooting] adinechin:
I'm also affected with this regularly, it's a lead, I'll try this soon. If it works, perhaps we can suggest a new functionnality in TiBu to do so for all apps ?!
[Android Q&A, Help & Troubleshooting] patrickdrd:
I contacted their support:

http://www.titaniumtrack.com/support.html

about this problem and possible workaround/solution,

I'll post again if/whenever they respond back
[Android Q&A, Help & Troubleshooting] adinechin:
I tried this for the Slack app : it seems to work :)

I'll try this for more apps but it sounds good !
[Android Q&A, Help & Troubleshooting] adinechin:
After some time, I realise that with Slack I don't have all notifs (not from all threads). I will try further with other apps...
[Android Q&A, Help & Troubleshooting] adinechin:
One thought : is there a possibility in TiBu to save just the name of the app, and make TiBu download it from Play Store, or do something similar to renew the gcm token ?

Or if I backup an old APK, a way to backup and restore separately only the data (and then update it via Play Store)
[Android Q&A, Help & Troubleshooting] zelendel:
With the first thought. At that point you might as well use Google back up setup. Not the greatest option but I hear it works for many.
[Android Q&A, Help & Troubleshooting] adinechin:
The only working solution I found to have notifications, is to backup n-1 version.

When I restore, I have to update the apps and thus renew the GCM token. I hope it'll help.
[Android Q&A, Help & Troubleshooting] ram4ufriends:
Wow almost 4 years (issue was even before) but no solution..have there been any workarounds atleast except clearing data of the apps?

Also is there any use in restoring Android Id?
[Android Q&A, Help & Troubleshooting] ram4ufriends:
May try this.fix, did it fix notifications for all your apps?
[Android Q&A, Help & Troubleshooting] adinechin:
I did not try this, but if it works perhaps you should post it on a Titanium Backup specific thread to include this in the app...
[Android Q&A, Help & Troubleshooting] ram4ufriends:
Have been trying to get this to work...but I either get bad component name or java.lang.SecurityException: Permission Denial: not allowed to send broadcast android.intent.action.MY_PACKAGE_REPLACED. Looks like this command can only be executed before Kitkat, after Kitkat this command can only be issued by System. Tried both the below commands..If somebody can build a quick app, we can try...

adb shell am broadcast -a android.intent.action.MY_PACKAGE_REPLACED -n com.google.android.talk

adb shell am broadcast -a android.intent.action.MY_PACKAGE_REPLACED -d com.google.android.talk
[Android Q&A, Help & Troubleshooting] InfX:
If you do just

am broadcast -a "android.intent.action.MY_PACKAGE_REPLACED"

without any package names, the broadcast should be sent to ALL apps on the device, but do try it on your own risk. Mind it, this thread and my posts on it are OLD! Lollipop was still new. And yea, try actually entering adb shell, gaining root (sending su) and then sending the am command,
[Android Q&A, Help & Troubleshooting] ram4ufriends:
Should I not append adb wheel at the beginning?
[Android Q&A, Help & Troubleshooting] InfX:
1. adb shell

(you should get a $ pormpt)

2. su

(you should get a # prompt)

3. am broadcast -a "android.intent.action.MY_PACKAGE_REPLACED"

(broadcast should happen, you should go back to # prompt)

4. exit and see if it helps anything or breaks everything

Good luck.
[Android Q&A, Help & Troubleshooting] ram4ufriends:
I did this and I could see app ( I tried with Hangouts) sending notifications and it got me excited. But after restart, app is not sending notifications anymore :(
[Android Q&A, Help & Troubleshooting] ram4ufriends:
I used oandbackup and many of the applications are sending notifications though there are some which doesn't
[Android Q&A, Help & Troubleshooting] adinechin:
Is it a mistake or is it the name of an existing backup/restore app ?
[Android Q&A, Help & Troubleshooting] ram4ufriends:
Its name of an open source app
[Android Q&A, Help & Troubleshooting] adinechin:
I just found it on FDroid, I'll give it a try ;)
[Android Q&A, Help & Troubleshooting] adinechin:
I just tried it, it seems ok but some features are missing, do you know where I can suggest improvements ?

Especially :

- being able to differentiate an old version backup from an update

- being able to have the app's APK copied on Sdcard (I have a permission error)
[Android Q&A, Help & Troubleshooting] ram4ufriends:
You can find the GitHub link on F-Droid page..or you can click on Help, changelog inside the app and provide your feedback on Issues tab in Github
[Android Q&A, Help & Troubleshooting] sToRm//:
Maybe a fix

It's 2k17 and these problems still exist. I did a full wipe of my device, flashed a firmware and restored my apps+data with Titanium Backup Pro. But a few apps didn't get push notifications after that. Same problem as described in this thread. I had an idea and tried something, that fixed the problems for me. Here is my workaround:

+++ You need a ROOTED device! +++

#1. Clean the cache of your app (Settings -> Apps -> YOUR_APP -> Storage)

#2. Use a file manager (like ES File Explorer, ...) and navigate to the folder: /data/app/

There you have to search for the folder of your app, which doesn't get push notifications.

For example: /data/app/me.pou.app-1/

#3. Then open the folder and install the base.apk of your app, which is in there.

After that, the folder is empty or removed, because there is a new one /data/app/me.pou.app-

2

/

Start your app, close your app and voila... get push notifications again. :highfive:

If that doesn't work, then try to clean the cache AND the app data in settings and do #2 & #3 again.
[Android Q&A, Help & Troubleshooting] ram4ufriends:
Do you have to setup your app when you install the base.apk again? When you clean data of your app you definitely have to...
[Android Q&A, Help & Troubleshooting] sToRm//:
No, i only have to clean the cache, reinstall with base.apk and it's ready to go. :) For me that did the trick.
[Android Q&A, Help & Troubleshooting] ram4ufriends:
Restarted phone and you still getting notifications?
[Android Q&A, Help & Troubleshooting] sToRm//:
Yepp :cowboy:
[Android Q&A, Help & Troubleshooting] adinechin:
It still seems tedious to me... I prefer having a backup of a previous version and downloading an update afterwards.

I just miss some filter to select the right apps to backup (the ones with notifications).
[Android Q&A, Help & Troubleshooting] ram4ufriends:
Hmm..tried the same for Hangouts but didn't work...
[Android Q&A, Help & Troubleshooting] sToRm//:
Okay, hmmm... Perhaps it depends also on the respective version or the manufacturer. For example, Huawei has its own system to manage notifications and other settings. For me it works on my Xperia XZ Premium @ 7.1.1
[Android Q&A, Help & Troubleshooting] fox793:
I think the solution may depend on the specific app that is having the problem, but in my case, the suggestion above worked. Specifically for me, the Grindr app notifications broke after being restored from another device. After reading 43matthew's post, it dawned on me that opening and logging in to the app before restoring might create a newer token than the one in the backup, and perhaps that newer token would survive after the restore because the app goes with the newer token. Whether my theory is right or not, it did in fact work for this app. Here are the specific steps I took:

before TiB restore:

clear app data (or uninstall/reinstall)

open app and log in to account - let it load up

force stop app (may be optional, since TiB does it anyway)

then restore the app (data only) on TiB

Again, not sure if this works for every app, but it did work for this one, and I wanted to share it, since I've been searching around for a solution for a few hours now :eek:
[Android Q&A, Help & Troubleshooting] patrickdrd:
seems that there's a new release that fixes this problem:

Titanium Backup ★root v8.0.2-test

WHAT’S NEW

Fixed the problem described here. www.xda-developers.com/broken-push-notifications-fix/

anyone who wants can test it
[Android Q&A, Help & Troubleshooting] ram4ufriends:
This seems to have resolved the issues for me..tried with hangouts and whatsapp and both are sending notifications after restoring....this would be a life savior...
[Android Q&A, Help & Troubleshooting] mko000:
Cool, I hope it really is fixed. That would be awesome!

I wonder how they did it?
[Android Q&A, Help & Troubleshooting] comediiian:
official update via PlayStore?
[Android Q&A, Help & Troubleshooting] patrickdrd:
not yet I guess..
[Android Q&A, Help & Troubleshooting] sToRm//:
Here is an untouched version (free):

https://mega.nz/#!QnAgFYTT!Qq8wRo_cRliI4XmrPcwblb3s_ZZnPHAkPQYNpIkN7BY
[Android Q&A, Help & Troubleshooting] patrickdrd:
the question is would we need to backup again all our apps?
[Android Q&A, Help & Troubleshooting] adinechin:
You can also get it on Aptoide ;)
[Android Q&A, Help & Troubleshooting] mko000:
Or apkmirror...
[Android Q&A, Help & Troubleshooting] arshu16:
The app opens and crashes.
[Android Q&A, Help & Troubleshooting] sToRm//:
Really? No problems here. :confused: I can do a reup or you use aptoide.
[Android Q&A, Help & Troubleshooting] arshu16:
I am on 7.1.1 oxygen os on oneplus 3. Which android version are you on?

I downloaded the apk from apkmirror also but of no use.
[Android Q&A, Help & Troubleshooting] sToRm//:
I'm on 7.1.1 too. Sony Xperia XZ Premium. No problems with this version.
[Android Q&A, Help & Troubleshooting] zelendel:
Reminder not to mention aptoid it's banned as a Warez market.
[Android Q&A, Help & Troubleshooting] sToRm//:
Thank you. I didn't knew that, sorry.
[Android Q&A, Help & Troubleshooting] adinechin:
Just tested it on stock S034 (yes I know, no comments here please ;)), and notifications seem to work too :o
[Android Q&A, Help & Troubleshooting] mko000:
I just got an update to Titanium Backup 8.1.0. Does anyone know if the fix is still included? I can't see it in the changelog: https://www.titaniumtrack.com/changelog/titanium-backup-changelog
[Android Q&A, Help & Troubleshooting] xdaninja:
thank you, in this entire thread this is the only thing that worked to get my slack notifications working
[Android Q&A, Help & Troubleshooting] Bewildered Wolf:
It got fixed. Last time I restored apps 3 days ago, bht notifications were broken.

Will try it. Thanks.
[Android Q&A, Help & Troubleshooting] adinechin:
On my side I got back to my old technique : I don't backup last versions of apps with notifications.

That way, when I restore, I have to update only some apps, and notifications are good ;)
[Android Q&A, Help & Troubleshooting] kaihansen2001:
I still can't get if this is fixed in the lastest version of TB 8.1.0, can anyone clarify please? thanks
[Android Q&A, Help & Troubleshooting] Bewildered Wolf:
The post above you.
[Android Q&A, Help & Troubleshooting] kaihansen2001:
If you mean your own post you said that notification were broken 3 days before, but I do not know if you were using the lastest version or not.

---------- Post added at 06:07 PM ---------- Previous post was at 05:17 PM ----------

@Bewildered Wolf possible to clarify for me if youo don't mind? thanks
[Android Q&A, Help & Troubleshooting] Bewildered Wolf:
This post.
[Android Q&A, Help & Troubleshooting] kaihansen2001:
Ok, so I guess it does not work. Thanks.