[GH-ISSUE #389] Android KitKat (hangouts) support #326

Closed
opened 2026-02-26 00:36:51 +03:00 by kerem · 43 comments
Owner

Originally created by @abrown1982 on GitHub (Nov 5, 2013).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/389

As the new version of android has no SMS app but its all merged into a single Hangouts app, are there plans to support restoring to this?

Originally created by @abrown1982 on GitHub (Nov 5, 2013). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/389 As the new version of android has no SMS app but its all merged into a single Hangouts app, are there plans to support restoring to this?
kerem 2026-02-26 00:36:51 +03:00
Author
Owner

@jamgregory commented on GitHub (Nov 5, 2013):

@abrown1982 - as far as I can tell, SMS Backup+ works with Hangouts SMS "out of the box". I've got 1.5.5 on my Nexus 5, and it's been backing up my SMSes without needing any other config than the usual one :)

<!-- gh-comment-id:27763809 --> @jamgregory commented on GitHub (Nov 5, 2013): @abrown1982 - as far as I can tell, SMS Backup+ works with Hangouts SMS "out of the box". I've got 1.5.5 on my Nexus 5, and it's been backing up my SMSes without needing any other config than the usual one :)
Author
Owner

@abrown1982 commented on GitHub (Nov 5, 2013):

The backing up seems to be working fine, but I ran a restore which says it succeeded but none of the restored messages seem to be showing in the Hangouts, so I assumed it wasn't compatible.

<!-- gh-comment-id:27764320 --> @abrown1982 commented on GitHub (Nov 5, 2013): The backing up seems to be working fine, but I ran a restore which says it succeeded but none of the restored messages seem to be showing in the Hangouts, so I assumed it wasn't compatible.
Author
Owner

@abrown1982 commented on GitHub (Nov 5, 2013):

Ran a few tests, backup seems fine, restore says it works but nothing shows in the Hangouts app.

<!-- gh-comment-id:27764552 --> @abrown1982 commented on GitHub (Nov 5, 2013): Ran a few tests, backup seems fine, restore says it works but nothing shows in the Hangouts app.
Author
Owner

@jamgregory commented on GitHub (Nov 5, 2013):

Ah, sorry @abrown1982 - I hadn't realised you were talking about restoring specifically.

<!-- gh-comment-id:27764796 --> @jamgregory commented on GitHub (Nov 5, 2013): Ah, sorry @abrown1982 - I hadn't realised you were talking about restoring specifically.
Author
Owner

@jberkel commented on GitHub (Nov 5, 2013):

restoring is being worked on as part of #388

<!-- gh-comment-id:27764838 --> @jberkel commented on GitHub (Nov 5, 2013): restoring is being worked on as part of #388
Author
Owner

@viper31 commented on GitHub (Nov 5, 2013):

Same issue here : restore problem due to Android KitKat SMS API change

<!-- gh-comment-id:27779804 --> @viper31 commented on GitHub (Nov 5, 2013): Same issue here : restore problem due to Android KitKat SMS API change
Author
Owner

@maaxxxx commented on GitHub (Nov 8, 2013):

Same issue here.

<!-- gh-comment-id:28019491 --> @maaxxxx commented on GitHub (Nov 8, 2013): Same issue here.
Author
Owner

@wheelerruss commented on GitHub (Nov 10, 2013):

Same issue. Do we have any rough eta on the release? It looks like @beverloo has done the work?

Thanks

<!-- gh-comment-id:28152315 --> @wheelerruss commented on GitHub (Nov 10, 2013): Same issue. Do we have any rough eta on the release? It looks like @beverloo has done the work? Thanks
Author
Owner

@jberkel commented on GitHub (Nov 14, 2013):

@wheelerruss there are few things left to do - i'm hoping to be able to release a new version some point next week.

<!-- gh-comment-id:28469797 --> @jberkel commented on GitHub (Nov 14, 2013): @wheelerruss there are few things left to do - i'm hoping to be able to release a new version some point next week.
Author
Owner

@wheelerruss commented on GitHub (Nov 14, 2013):

@jberkel Brilliant. I'm holding off really using my Nexus 5 at the moment until I get all my texts etc on there...I don't know why I am, I just am! haha....

<!-- gh-comment-id:28494586 --> @wheelerruss commented on GitHub (Nov 14, 2013): @jberkel Brilliant. I'm holding off really using my Nexus 5 at the moment until I get all my texts etc on there...I don't know why I am, I just am! haha....
Author
Owner

@IGBmart commented on GitHub (Nov 17, 2013):

It's the same for me. But now after I read this post I will use it :)
I am a big fan oft this App, and I am glad to see, that the problems and questions does not get ignored.

<!-- gh-comment-id:28659075 --> @IGBmart commented on GitHub (Nov 17, 2013): It's the same for me. But now after I read this post I will use it :) I am a big fan oft this App, and I am glad to see, that the problems and questions does not get ignored.
Author
Owner

@jberkel commented on GitHub (Nov 24, 2013):

i also pushed out a new beta (version code 1536) with kitkat fixes, please help to test this.

how to get the beta:

https://github.com/jberkel/sms-backup-plus#beta

after installing the beta make sure it mentions kitkat in the "about" section.

<!-- gh-comment-id:29170171 --> @jberkel commented on GitHub (Nov 24, 2013): i also pushed out a new beta (version code 1536) with kitkat fixes, please help to test this. how to get the beta: https://github.com/jberkel/sms-backup-plus#beta after installing the beta make sure it mentions kitkat in the "about" section.
Author
Owner

@TobberH commented on GitHub (Nov 26, 2013):

Seems like the beta version does a full restore but you still get no old SMS texts in the Hangout app. If there is anything I can do to help test a new version please tell me! I really want to get my SMS history back! :)

<!-- gh-comment-id:29315593 --> @TobberH commented on GitHub (Nov 26, 2013): Seems like the beta version does a full restore but you still get no old SMS texts in the Hangout app. If there is anything I can do to help test a new version please tell me! I really want to get my SMS history back! :)
Author
Owner

@TobberH commented on GitHub (Nov 26, 2013):

OK, small update.. I've tried to install another SMS app (GO SMS Pro) and that actually shows me all my old SMS messages, so it's the Hangouts app that is not working/updating properly I guess!

<!-- gh-comment-id:29315961 --> @TobberH commented on GitHub (Nov 26, 2013): OK, small update.. I've tried to install another SMS app (GO SMS Pro) and that actually shows me all my old SMS messages, so it's the Hangouts app that is not working/updating properly I guess!
Author
Owner

@jberkel commented on GitHub (Nov 26, 2013):

ok, interesting. any idea @beverloo ?

<!-- gh-comment-id:29316147 --> @jberkel commented on GitHub (Nov 26, 2013): ok, interesting. any idea @beverloo ?
Author
Owner

@jberkel commented on GitHub (Nov 26, 2013):

i guess hangout uses separate storage, or has some extra flags. not sure if this is documented anywhere

<!-- gh-comment-id:29316256 --> @jberkel commented on GitHub (Nov 26, 2013): i guess hangout uses separate storage, or has some extra flags. not sure if this is documented anywhere
Author
Owner

@TobberH commented on GitHub (Nov 26, 2013):

Update! Setting the other app as Default SMS and the opening Hangouts again and letting it take over SMS again actually made it update, so now I have all my SMS in Hangouts! YAY!

<!-- gh-comment-id:29316420 --> @TobberH commented on GitHub (Nov 26, 2013): Update! Setting the other app as Default SMS and the opening Hangouts again and letting it take over SMS again actually made it update, so now I have all my SMS in Hangouts! YAY!
Author
Owner

@TobberH commented on GitHub (Nov 26, 2013):

I guess it could be because SMS Backup Plus sets the Hangouts app as default instead of letting it figure it out by itself? Anyway it's something that should be possible to fix somehow...

<!-- gh-comment-id:29316867 --> @TobberH commented on GitHub (Nov 26, 2013): I guess it could be because SMS Backup Plus sets the Hangouts app as default instead of letting it figure it out by itself? Anyway it's something that should be possible to fix somehow...
Author
Owner

@RoadXY commented on GitHub (Nov 26, 2013):

Indeed, was having the same problem. Checked by using the work around suggested above.
Setting messaging app as default, all my messages appeared (which have been restored several weeks ago). Setting Hangouts as default after that and now all my messages appear in Hangouts without intervention of SMS Backup+.

Thanks for the great app anyway!

<!-- gh-comment-id:29322524 --> @RoadXY commented on GitHub (Nov 26, 2013): Indeed, was having the same problem. Checked by using the work around suggested above. Setting messaging app as default, all my messages appeared (which have been restored several weeks ago). Setting Hangouts as default after that and now all my messages appear in Hangouts without intervention of SMS Backup+. Thanks for the great app anyway!
Author
Owner

@Gappa commented on GitHub (Nov 28, 2013):

Yup, had the same problem. The solution that TobberH/RoadXY mention helped me to get the restored messages to show in Hangouts.

<!-- gh-comment-id:29445526 --> @Gappa commented on GitHub (Nov 28, 2013): Yup, had the same problem. The solution that TobberH/RoadXY mention helped me to get the restored messages to show in Hangouts.
Author
Owner

@stefanhoth commented on GitHub (Dec 7, 2013):

I just found this info. I guess it's the better solution for restoring sms on KitKat onwards http://www.androidpolice.com/2013/12/06/non-default-sms-apps-in-kitkat-can-still-write-to-the-sms-database-using-a-switch-in-app-ops-no-root-required/

<!-- gh-comment-id:30053114 --> @stefanhoth commented on GitHub (Dec 7, 2013): I just found this info. I guess it's the better solution for restoring sms on KitKat onwards http://www.androidpolice.com/2013/12/06/non-default-sms-apps-in-kitkat-can-still-write-to-the-sms-database-using-a-switch-in-app-ops-no-root-required/
Author
Owner

@jberkel commented on GitHub (Dec 7, 2013):

@stefanhoth thanks for the info, will have a look

<!-- gh-comment-id:30054885 --> @jberkel commented on GitHub (Dec 7, 2013): @stefanhoth thanks for the info, will have a look
Author
Owner

@jberkel commented on GitHub (Dec 8, 2013):

i have implemented @stefanhoth's suggestion: github.com/jberkel/sms-backup-plus@037756fdbf

i also pushed a new beta with this code, let me know if it works for you.

<!-- gh-comment-id:30088311 --> @jberkel commented on GitHub (Dec 8, 2013): i have implemented @stefanhoth's suggestion: https://github.com/jberkel/sms-backup-plus/commit/037756fdbf56fd7d2871a0204af73c1ddd1cd5e5 i also pushed a new beta with this code, let me know if it works for you.
Author
Owner

@stefanhoth commented on GitHub (Dec 8, 2013):

I'm currently running a restore on my old N4 (with KitKat) and it seems to run fine. But it will take a while and I will only update the ticket again if I run into problems (which I don't expect).

One suggestion for the process: It's a rather technical text and it might help to show the steps in 3 Screenshots with a Next - button rather than just a text. For me personally it was OK but then again I knew what I was looking for. ;-)

Thank you for implementing it so fast!

<!-- gh-comment-id:30096851 --> @stefanhoth commented on GitHub (Dec 8, 2013): I'm currently running a restore on my old N4 (with KitKat) and it seems to run fine. But it will take a while and I will only update the ticket again if I run into problems (which I don't expect). One suggestion for the process: It's a rather technical text and it might help to show the steps in 3 Screenshots with a Next - button rather than just a text. For me personally it was OK but then again I knew what I was looking for. ;-) Thank you for implementing it so fast!
Author
Owner

@mathbouq commented on GitHub (Dec 13, 2013):

As reported on the Google+ page, with the withdrawal of App ops in Android 4.4.2, restore fails on that version of Android. Even the first workaround posted on this thread (set another default sms app, restore, then switch back to hangout) fails: upon restoration, it looks like sms are restored but empty, which finally ends up in no conversation displayed in the sms app (tried with GO SMS Pro and with ChompSMS).
All of this was done on Android 4.4.2 (Nexus 5) with SMS Backup Plus 1.5.6-beta

<!-- gh-comment-id:30551952 --> @mathbouq commented on GitHub (Dec 13, 2013): As reported on the Google+ page, with the withdrawal of App ops in Android 4.4.2, restore fails on that version of Android. Even the first workaround posted on this thread (set another default sms app, restore, then switch back to hangout) fails: upon restoration, it looks like sms are restored but empty, which finally ends up in no conversation displayed in the sms app (tried with GO SMS Pro and with ChompSMS). All of this was done on Android 4.4.2 (Nexus 5) with SMS Backup Plus 1.5.6-beta
Author
Owner

@ptepper commented on GitHub (Dec 14, 2013):

Hi. I'm on the beta, just installed on KitKat, Nexus 5. When I try to restore I get "SMS write permission required", I click OK and the app crashes. It says "Unfortunately settings has stopped" and gives the option to send a report to Google.

<!-- gh-comment-id:30560144 --> @ptepper commented on GitHub (Dec 14, 2013): Hi. I'm on the beta, just installed on KitKat, Nexus 5. When I try to restore I get "SMS write permission required", I click OK and the app crashes. It says "Unfortunately settings has stopped" and gives the option to send a report to Google.
Author
Owner

@jberkel commented on GitHub (Dec 14, 2013):

great, google pulled App ops shortly after i implemented this :/ . i hope they'll bring it back at some point, since i don't really like the other solution (changing the default app).

<!-- gh-comment-id:30570645 --> @jberkel commented on GitHub (Dec 14, 2013): great, google pulled App ops shortly after i implemented this :/ . i hope they'll bring it back at some point, since i don't really like the other solution (changing the default app).
Author
Owner

@RoadXY commented on GitHub (Dec 14, 2013):

Changing the default app is the suggested way though:
http://android-developers.blogspot.nl/2013/10/getting-your-sms-apps-ready-for-kitkat.html?m=1

Quote:
Advice for SMS backup & restore apps
Because the ability to write to the SMS Provider is restricted to the app the user selects as the default SMS app, any existing app designed purely to backup and restore SMS messages will currently be unable to restore SMS messages on Android 4.4. An app that backs up and restores SMS messages must also be set as the default SMS app so that it can write messages in the SMS Provider. However, if the app does not also send and receive SMS messages, then it should not remain set as the default SMS app. So, you can provide a functional user experience with the following design when the user opens your app to initiate a one-time restore operation:

Query the current default SMS app's package name and save it.
String defaultSmsApp = Telephony.Sms.getDefaultSmsPackage(context);
Request the user change the default SMS app to your app in order to restore SMS messages (you must be the default SMS app in order to write to the SMS Provider).
Intent intent = new Intent(context, Sms.Intents.ACTION_CHANGE_DEFAULT);
intent.putExtra(Sms.Intents.EXTRA_PACKAGE_NAME, context.getPackageName());
startActivity(intent);
When you finish restoring all SMS messages, request the user to change the default SMS app back to the previously selected app (saved during step 1).
Intent intent = new Intent(context, Sms.Intents.ACTION_CHANGE_DEFAULT);
intent.putExtra(Sms.Intents.EXTRA_PACKAGE_NAME, defaultSmsApp);
startActivity(intent);

<!-- gh-comment-id:30584873 --> @RoadXY commented on GitHub (Dec 14, 2013): Changing the default app is the suggested way though: http://android-developers.blogspot.nl/2013/10/getting-your-sms-apps-ready-for-kitkat.html?m=1 Quote: Advice for SMS backup & restore apps Because the ability to write to the SMS Provider is restricted to the app the user selects as the default SMS app, any existing app designed purely to backup and restore SMS messages will currently be unable to restore SMS messages on Android 4.4. An app that backs up and restores SMS messages must also be set as the default SMS app so that it can write messages in the SMS Provider. However, if the app does not also send and receive SMS messages, then it should not remain set as the default SMS app. So, you can provide a functional user experience with the following design when the user opens your app to initiate a one-time restore operation: Query the current default SMS app's package name and save it. String defaultSmsApp = Telephony.Sms.getDefaultSmsPackage(context); Request the user change the default SMS app to your app in order to restore SMS messages (you must be the default SMS app in order to write to the SMS Provider). Intent intent = new Intent(context, Sms.Intents.ACTION_CHANGE_DEFAULT); intent.putExtra(Sms.Intents.EXTRA_PACKAGE_NAME, context.getPackageName()); startActivity(intent); When you finish restoring all SMS messages, request the user to change the default SMS app back to the previously selected app (saved during step 1). Intent intent = new Intent(context, Sms.Intents.ACTION_CHANGE_DEFAULT); intent.putExtra(Sms.Intents.EXTRA_PACKAGE_NAME, defaultSmsApp); startActivity(intent);
Author
Owner

@jberkel commented on GitHub (Dec 15, 2013):

yes, i guess i have to revert back to the previous fix. very inelegant solution though.

<!-- gh-comment-id:30608105 --> @jberkel commented on GitHub (Dec 15, 2013): yes, i guess i have to revert back to the previous fix. very inelegant solution though.
Author
Owner

@artgon commented on GitHub (Dec 16, 2013):

+1 looking forward to this fix

<!-- gh-comment-id:30636131 --> @artgon commented on GitHub (Dec 16, 2013): +1 looking forward to this fix
Author
Owner

@smarek commented on GitHub (Dec 23, 2013):

@stefanhoth your solution stopped working with 4.4.2 update, stacktrace below:

D/AndroidRuntime( 8208): Shutting down VM
W/dalvikvm( 8208): threadid=1: thread exiting with uncaught exception (group=0x41614ba8)
E/AndroidRuntime( 8208): FATAL EXCEPTION: main
E/AndroidRuntime( 8208): Process: com.android.settings, PID: 8208
E/AndroidRuntime( 8208): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings}: java.lang.IllegalArgumentException: Invalid fragment for this activity: com.android.settings.applications.AppOpsSummary
E/AndroidRuntime( 8208):    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2195)
E/AndroidRuntime( 8208):    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245)
E/AndroidRuntime( 8208):    at android.app.ActivityThread.access$800(ActivityThread.java:135)
E/AndroidRuntime( 8208):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
E/AndroidRuntime( 8208):    at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 8208):    at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 8208):    at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime( 8208):    at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8208):    at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 8208):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 8208):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime( 8208):    at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8208): Caused by: java.lang.IllegalArgumentException: Invalid fragment for this activity: com.android.settings.applications.AppOpsSummary
E/AndroidRuntime( 8208):    at android.preference.PreferenceActivity.switchToHeaderInner(PreferenceActivity.java:1180)
E/AndroidRuntime( 8208):    at android.preference.PreferenceActivity.switchToHeader(PreferenceActivity.java:1199)
E/AndroidRuntime( 8208):    at android.preference.PreferenceActivity.onCreate(PreferenceActivity.java:545)
E/AndroidRuntime( 8208):    at com.android.settings.Settings.onCreate(Settings.java:207)
E/AndroidRuntime( 8208):    at android.app.Activity.performCreate(Activity.java:5231)
E/AndroidRuntime( 8208):    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime( 8208):    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2159)
E/AndroidRuntime( 8208):    ... 11 more
W/ActivityManager(  764):   Force finishing activity com.android.settings/.Settings
D/dalvikvm(  764): GC_FOR_ALLOC freed 1854K, 26% free 33560K/45160K, paused 53ms, total 54ms
W/ActivityManager(  764):   Force finishing activity com.zegoggles.smssync/.activity.MainActivity
<!-- gh-comment-id:31121684 --> @smarek commented on GitHub (Dec 23, 2013): @stefanhoth your solution stopped working with 4.4.2 update, stacktrace below: ``` D/AndroidRuntime( 8208): Shutting down VM W/dalvikvm( 8208): threadid=1: thread exiting with uncaught exception (group=0x41614ba8) E/AndroidRuntime( 8208): FATAL EXCEPTION: main E/AndroidRuntime( 8208): Process: com.android.settings, PID: 8208 E/AndroidRuntime( 8208): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings}: java.lang.IllegalArgumentException: Invalid fragment for this activity: com.android.settings.applications.AppOpsSummary E/AndroidRuntime( 8208): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2195) E/AndroidRuntime( 8208): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245) E/AndroidRuntime( 8208): at android.app.ActivityThread.access$800(ActivityThread.java:135) E/AndroidRuntime( 8208): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196) E/AndroidRuntime( 8208): at android.os.Handler.dispatchMessage(Handler.java:102) E/AndroidRuntime( 8208): at android.os.Looper.loop(Looper.java:136) E/AndroidRuntime( 8208): at android.app.ActivityThread.main(ActivityThread.java:5017) E/AndroidRuntime( 8208): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime( 8208): at java.lang.reflect.Method.invoke(Method.java:515) E/AndroidRuntime( 8208): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) E/AndroidRuntime( 8208): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) E/AndroidRuntime( 8208): at dalvik.system.NativeStart.main(Native Method) E/AndroidRuntime( 8208): Caused by: java.lang.IllegalArgumentException: Invalid fragment for this activity: com.android.settings.applications.AppOpsSummary E/AndroidRuntime( 8208): at android.preference.PreferenceActivity.switchToHeaderInner(PreferenceActivity.java:1180) E/AndroidRuntime( 8208): at android.preference.PreferenceActivity.switchToHeader(PreferenceActivity.java:1199) E/AndroidRuntime( 8208): at android.preference.PreferenceActivity.onCreate(PreferenceActivity.java:545) E/AndroidRuntime( 8208): at com.android.settings.Settings.onCreate(Settings.java:207) E/AndroidRuntime( 8208): at android.app.Activity.performCreate(Activity.java:5231) E/AndroidRuntime( 8208): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087) E/AndroidRuntime( 8208): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2159) E/AndroidRuntime( 8208): ... 11 more W/ActivityManager( 764): Force finishing activity com.android.settings/.Settings D/dalvikvm( 764): GC_FOR_ALLOC freed 1854K, 26% free 33560K/45160K, paused 53ms, total 54ms W/ActivityManager( 764): Force finishing activity com.zegoggles.smssync/.activity.MainActivity ```
Author
Owner

@RoadXY commented on GitHub (Dec 23, 2013):

App Opps is indeed removed and tucked away more.

<!-- gh-comment-id:31144653 --> @RoadXY commented on GitHub (Dec 23, 2013): App Opps is indeed removed and tucked away more.
Author
Owner

@Tuinslak commented on GitHub (Jan 7, 2014):

Any update on this ? Looks like it's still not working ?

<!-- gh-comment-id:31721648 --> @Tuinslak commented on GitHub (Jan 7, 2014): Any update on this ? Looks like it's still not working ?
Author
Owner

@unsound commented on GitHub (Jan 11, 2014):

We desperately need an update to the beta, reverting to the dirty way of setting SMS Backup + as default SMS app... it's non-functional on Android 4.4.2 since App Ops is gone.

<!-- gh-comment-id:32086785 --> @unsound commented on GitHub (Jan 11, 2014): We desperately need an update to the beta, reverting to the dirty way of setting SMS Backup + as default SMS app... it's non-functional on Android 4.4.2 since App Ops is gone.
Author
Owner

@martimlobao commented on GitHub (Jan 17, 2014):

@jberkel what's the status on KitKat compatibility? Is it just a case of reverting to the previous version? If so, would it be possible for the update to get pushed to the beta channel (even pushing it to the stable version seems fine, imo)?

It's clear that Google doesn't want apps to rely on App Ops to implement standard functionality, especially since it is little more than a hack at this point. It's probably preferable to use the documented and recommended method of switching the default SMS app.

<!-- gh-comment-id:32617460 --> @martimlobao commented on GitHub (Jan 17, 2014): @jberkel what's the status on KitKat compatibility? Is it just a case of reverting to the previous version? If so, would it be possible for the update to get pushed to the beta channel (even pushing it to the stable version seems fine, imo)? It's clear that Google doesn't want apps to rely on App Ops to implement standard functionality, especially since it is little more than a hack at this point. It's probably preferable to use the documented and recommended method of switching the default SMS app.
Author
Owner

@jberkel commented on GitHub (Jan 17, 2014):

@martimlobao yes. i think i'll have to bring the old way of switching SMS apps back.

<!-- gh-comment-id:32628038 --> @jberkel commented on GitHub (Jan 17, 2014): @martimlobao yes. i think i'll have to bring the old way of switching SMS apps back.
Author
Owner

@nk222 commented on GitHub (Feb 5, 2014):

Any chance for an updated beta with the previously working solution anytime soon? My wife really wants her text messages back :)

<!-- gh-comment-id:34222542 --> @nk222 commented on GitHub (Feb 5, 2014): Any chance for an updated beta with the previously working solution anytime soon? My wife really wants her text messages back :)
Author
Owner

@mloraditch commented on GitHub (Feb 10, 2014):

+1. Just got my KitKat Update for the 1 and I keep all my old SMS.

<!-- gh-comment-id:34691328 --> @mloraditch commented on GitHub (Feb 10, 2014): +1. Just got my KitKat Update for the 1 and I keep all my old SMS.
Author
Owner

@rah-phi commented on GitHub (Feb 13, 2014):

for the temporary fix, app ops for 4.4.2 is back as an xposed module:
https://github.com/jclehner/AppOpsXposed

<!-- gh-comment-id:34985456 --> @rah-phi commented on GitHub (Feb 13, 2014): for the temporary fix, app ops for 4.4.2 is back as an xposed module: https://github.com/jclehner/AppOpsXposed
Author
Owner

@jberkel commented on GitHub (Nov 21, 2014):

dup of #475

<!-- gh-comment-id:63966464 --> @jberkel commented on GitHub (Nov 21, 2014): dup of #475
Author
Owner

@smarek commented on GitHub (Nov 21, 2014):

@jberkel shouldn't newer issues be closed as duplicates of older ones?

<!-- gh-comment-id:63966597 --> @smarek commented on GitHub (Nov 21, 2014): @jberkel shouldn't newer issues be closed as duplicates of older ones?
Author
Owner

@jberkel commented on GitHub (Nov 21, 2014):

in theory yes, in practice the open issues in this project are getting out of control. sorry!

<!-- gh-comment-id:63966816 --> @jberkel commented on GitHub (Nov 21, 2014): in theory yes, in practice the open issues in this project are getting out of control. sorry!
Author
Owner

@smarek commented on GitHub (Nov 21, 2014):

@jberkel it's ok, i'm just curious, thanks for your service

<!-- gh-comment-id:63966890 --> @smarek commented on GitHub (Nov 21, 2014): @jberkel it's ok, i'm just curious, thanks for your service
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sms-backup-plus-jberkel#326
No description provided.