Tired of putting down your Android tablet to check a new SMS on your phone? Me too. Cloud SMS is run on both your phone and tablet to allow you to send and receive SMS messaging from your tablet.
Built for speed and privacy, Cloud SMS works over the Internet, does not require bluetooth, does not share (or transmit) your contacts, and even hashes your account email for added security. Typical messages take about 100ms to transmit.
Cloud SMS is available now in the Google Play Store for only 99 cents!
Super Important & Complex Setup Instructions
Install and run on phone
Install and run on tablet
Done... Ready to go!
Updates
2.3.1
Fixed MMS Receiver for KitKat (Android 4.4) devices.
2.3.0
Fixed SMS History Sync with an empty SMS list on Phone.
Fixed Popup showing in recent tasks
Fixed Attachment selector (KitKat issues resolved!)
Updated UI to improve look and feel, fixed missing Android UX elements (Thanks David!):
Cleaned UI with better spacing, padding
Action Bar now displays Contact name and number to match the stock SMS app.
Updated font sizes on main message list.
Various UI Tweaks and updates.
2.2.2
Fixed a registration bug where Cloud Services were unable to register if Google's service took longer than three seconds to respond.
Changed the Settings description for Force Tablet Mode to better indicate how to use the feature.
2.2.1
Fixed KitKat bug with contact selection when "Show Only Mobile Numbers" was unchecked.
Fixed display of dialog to users when selecting a contact with no mobile categorized numbers.
Fixed other small bugs.
2.2.0
Added support for Android 4.4 KitKat! Please let me know if you experience any problems!
Fixed initial contact detection and photo assignment on SMS History Sync.
Improved compatibility with some cellular tablets.
Fixed other small bugs.
Click Show to see previous update change log.
2.1.18
Fixed long standing bug which prevented sharing images from other apps to Cloud SMS.
Fixed a few minor bugs.
2.1.17
Project extra smooth butter - scrolling should be smoother than ever before with my new image caching
Fixed Mark Read / Mark All Read from notification (really this time, I promise!)
Fixed a few isolated issues when sending new messages from the tablet
Please let me know if you can feel a noticeably smoother scroll, as I only have a few devices to test against and would love to hear some feedback.
2.1.16
Tweaks for Android 4.3
Fixed isolated Notification Mark All Read / Mark Read button where messages were not being properly marked for some devices.
Fixed isolated Message Popup bug.
Misc bug fixes on Tablet.
2.1.15
Added support for Android 4.3!
2.1.14
Fixed issue which prevented Message Popup from firing when messages were received.
Fixed a number of issues which had the potential to cause a crash.
Changed Message Popup behaviour to show popup only when popups are enabled, and when the screen is off, or screen is on but Cloud SMS is not the open app.
A few small bug fixes.
Stay tuned for the next major release!
2.1.13
Added Time Offset setting to fix incorrect incoming message time, for people whose devices refuse to agree on time zones.
Fixed MMS Send from tablet bug where images selected outside of the gallery would cause a crash.
Fixed Mark Read and Mark All Read from the notification. The buttons will now silently do their job rather than briefly flash open and close Cloud SMS.
A few small bug fixes.
2.1.12
Added Image sending from the Tablet! Images are uploaded and sent as a short link using normal SMS due to Android MMS limitations. Give it a try!
Added new network state detection to ensure devices remain sync across mobile/wifi changes
All message timestamps are now based on the Phone's received time
Fixed bug with Phone Call notification running wild, will ring for a max of ten seconds, and ignores any old phone calls when reconnecting to Wifi
Fixed many other small bugs
2.1.11
Added new Mark All Read button on Jellybean notifications. (Thanks Pasquale!)
Fixed MMS receiving for Android 2.x users (Hopefully it really is fixed!)
Fixed many small bugs and potential crashes
2.1.10
Fixed contact list position memory not resetting on new message
Fixed issue for Beta MMS Upload users where selecting an image caused a crash
Fixed MMS receiving for Android 2.x users
Fixed crash report from crashing (crazy, yes?)
Fixed many small bugs and potential crashes
Tested new icons (still working on them!)
2.1.9
Added Setting to use Stock SMS icon on tablet
Fixed Contact Icon skipping on scroll
Fixed Last contact photo showing when viewing unknown contact
Fixed Contact list position memory
Fixed Marking messages read when opened from Dashclock
Fixed Message Popup opening when app is visible
Fixed ^ character being stripped
Fixed Message Times was tablet based
Fixed Phone Ringtone didn't stop on Missed Call
Fixed Receiving messages when app is closed
Fixed Screen flash on dark theme start
Fixed Ringtone selection not updating UI
2.1.8
Added DashClock Extension for Cloud SMS! - To enable Cloud SMS in DashClock, simply add the extension to the widget or lockscreen.
Disabled Slide Animation for Android 4.x consistency, and added a setting to re-enable it if desired.
Updated contact icon to modern unknown contact icon.
Fixed crash on Kindle Message Quick Reply Pop-Up.
Fixed UI flash when started on boot.
Fixed height of Message Reply text field.
Other UI Tweaks and rare crash fixes.
2.1.7
Added New Phone Call Pop-Up with Big Photo
Completely new MMS Handling code for increased compatibility.
Fixed scaling of Message Pop-up for Nexus 10 users.
Fixed a rare wake lock state on Phone Call notification.
Fixed receiving MMS images.
Removed Force Phone Mode from Tablet Settings.
MMS Support is entirely rewritten so please let me know if it suddenly works for you now, I'd love to hear back from you.
2.1.6
Added Quick Contact to Message Thread.
Added handler to automatically re-sync devices when updated from Play Store.
Fixed a Google Play issue where new users were experiencing crashes.
Fixed a rare issue where users upgrading would crash due to DB changes.
Fixed a few more reported bugs.
2.1.5
Fixed a few issues for people upgrading from a few versions back which could cause crashes.
Fixed a few more reported bugs.
2.1.4
Fixed issue where contact photo would be removed when a message is received, but restored when the message was viewed.
Fixed issue where contact name was not displayed, but showed only the phone number in its place.
Fixed issue where the main list did not refresh on new message after being woken up from sleep, or switched from another process.
Added more users to Sending MMS Images from Tablet beta.
2.1.3
More performance caching on the main list! Should be extra buttery now, very close to the stock SMS app.
Fixed problem with MMS receiving, most users should now get MMS images.
Tweaked a few communications items, should fix a couple isolated issues.
2.1.2
Improved Main Conversations list handling of unknown contacts.
Improved Message Conversation performance.
Improved overall performance.
Corrected random contact photo for unknown contacts.
Added on touch colouring to main list.
Added more users to MMS from Tablet Beta.
2.1.0
Project Butter! When you open the app after updating, your main messages list will be cached. Simply scroll through your list to generate a fresh list cache. Go into any message thread, and when you come back, your main list will be buttery smooth. This cache will be automatically updated and stay buttery.
Updated Message character count to indicate number of SMS messages for users who need that detail.
Added more users to MMS from Tablet Beta Testing.
Fixed a few more bugs.
2.0.13
Fixed New Message Crash for Dark Theme users.
Fixed message sending status issue for remaining users.
Added more users to MMS from Tablet Beta Testing.
Fixed a few more bugs.
2.0.12
Fixed MMS Attachment from New Message for Beta Users.
Fixed a few reported bugs.
More UI efficiency updates to improve list scrolling speed.
Please email me with any issues, as I cannot respond to Reviews if you are experiencing any issues!
Also looking for more Send MMS from Tablet Beta Testers!
2.0.11
Added SMS character counter to prevent sending long messages.
Added preliminary support for looking up SMS contact mobile phone from an email address.
Added UI slide transition between Conversations list and the Message Thread View.
Fixed a few reported bugs.
Updated UI efficiency to improve list scrolling speed.
Added more beta users to MMS Send from Tablet.
Updated MMS.
Please email me with any issues, as I cannot respond to Reviews if you are experiencing any issues!
2.0.10
Fixed message sent status updates which was not working for a few users.
Various small bug fixes.
2.0.9
More UI Updates to Message Thread View.
Updated Message Sending to match Stock SMS - When a message is sent, the time field shows as SENDING until the message has been sent, which then shows the time.
Message Delivery Notification is now a setting for users who want that feature and status indicators.
Removed notifications on sent messages, unless message delivery notifications are enabled.
Fixed SMS History Import Ordering - Now imported messages display in the proper order.
2.0.8
Overhauled main conversations list performance.
Updated message status icons to match the stock SMS app.
Added Contact Badge when a contact photo is touched on the main list.
Added arrow indicators over contact photos to match the stock SMS app in the conversation thread view.
Fixed multipart (long) SMS message sending. Long messages are now sent as SMS Multipart rather than cut into pieces.
Keyboard is no longer hidden on message send on the conversation thread view.
2.0.7
Fixed issue where message thread view was refreshing far to often when waiting on message state (sent, delivered, etc).
Fixed multiple notifications on send - Only delivery notification will fire now.
Fixed more MMS issues, should be more reliable and hopefully working for the last 5% of users experiencing MMS reception issues.
Bug Fixes
Feedback Request - MMS Sending, if MMS photos sent from tablet were converted to a link for the recipient, would that be acceptable? *
2.0.6
Improved responsiveness of main contacts view.
Updated time stamps to display only hour within a twenty-four hour period.
Fixed bug where Quick Reply from notification did not open the Quick Reply Pop-Up.
Added Force Phone Mode for a single user who's phone refuses to identify properly
Updated UI with margin changes, many more UI tweaks to come (Thanks Mark)
Bug Fixes
2.0.5
Added full sent message state tracking. Now sent messages turn green when your phone has sent out the message, and turns green with a check mark when the message has been successfully delivered. Failed messages will turn red, which can indicate that your phone was unable to delivery the message.
Updated MMS Receiving - MMS receiving has been overhauled and should now be working for everyone. Many MMS related issues have been resolved.
Bug Fixes
2.0.4
Added Mark Read notification pull-down button (Jellybean 4.2).
Fixed MMS receiver to wait until MMS files have finished downloading from the carrier.
Fixed error with MMS received with no text message.
Fixed a few other stability issues.
2.0.3
Added confirmation prompt to exit to prevent accidental stop of Cloud SMS when users used exit to hide it.
Added create/edit contact for View Contact from an unknown contact.
Fixed displayed name on Delete Conversation from an unknown contact.
Fixed View Contact opening incorrect contact.
Fixed bug which caused phone to show a message from contact "0" with a message about encryption (nothing had every been sent out, it was just wrongly showing on the phone in isolated cases).
2.0.2
Fixed profile photo detection for Android 4.0+. Added new permission: Read Profile to better detect owner profile.
Fixed several database issues to fully resolve locking issues.
Fixed main view displaying last sent message, rather than only the contact's last message.
Phone and Tablet now try to detect if Message Encryption was accidentally set on only one device, and tries to automatically decrypt received encrypted messages.
Improved Message Thread view performance caching.
2.0.1
Updated Quick Reply Pop-Up to be slightly more narrow.
Added second Send button to Quick Reply Pop-up on bottom right to prevent accidental pressing of "Open" when send was intended.
Fixed Quick Reply Pop-up Send button on Dark Theme
Fixed various Dark Theme items in Message View
Updated SMS Sync Description to better indicate that only Tablet messages are deleted on Sync.
Added notification on start of SMS Sync on the Tablet.
Improved contact photo loading performance.
2.0.0
Added Full SMS Sync from Phone (Click the Sync Icon on the Phone, Tablet will notify you when completed!)
Added Incoming Phone Call Notification (Enable in Settings on your phone)
Added Full Message Body Encryption for Android 3.0+ (Enable on both devices, but make sure you are on Android 3.0 through 4.2!)
Added Separate Theme Selection for Quick Reply Pop-Up
Fixed Bug With Quick Reply which stopped the lock screen (Thanks for the report Serge!)
Bonus performance increases!
Added New Permission - Read Phone State - Used to detect incoming phone calls
I am a very active developer and continue to address issues and implement features. Below is a full list of permissions, and what they are used for, along with a note for people using GoSMS and other third party SMS apps.
Required Permissions
Internet - (Needed to connect to the Internet!)
Send SMS / Receive SMS (These are used on the phone side to send/receive messages)
Get Account (This is used to read your gmail address assigned to your device. I never actually send this email, simply make a secure hash of the account to match against the Google Cloud Messaging IDs for your tablet/phone)
Wake Lock (This is required for Google Cloud Messaging)
Receive SMS (This is required to capture SMS messages to send to your tablet)
Vibrate (If your tablet supports it, I can vibrate/light LED, make sound just as your phone does on SMS - This will become a setting)
Read Contacts (This is used on the tablet to show the contact photo / name rather than just the phone number of the recipient/sender. This data is never stored anywhere).
Write SMS (This is used on the phone to add your messages to the stock SMS database to keep conversations properly synced)
Receive Boot Completed (This is used to automatically start on boot if enabled in Settings)
Access Network State (This is used to determine if you've switched to mobile or wifi to ensure you are re-synced)
Access WiFi State (This is used to determine if you've switched to mobile or wifi to ensure you are re-synced)
Read Phone Status (This is used to detect incoming phone calls to tell you that your phone is ringing if Phone Call Notification is enabled)
Read Call Log (This is used to read caller information so that the caller ID and photo can be shown in Phone Call Notification)
Using Go SMS? Do this:
In Go SMS, Under 'Menu -> Settings -> Advanced -> Receive Settings' - Uncheck the box that says 'Disable other message notification'
If still not receiving forwarding messages, reboot.
Using a MIUI Rom? Do this:
In the MIUI messaging app go to "settings" and make sure "System MMS app priority" is unchecked.
Any comments, questions, or feedback?
Working great, thanks.
Sent from my Nexus 7 using xda premium
Purchased and 5 starred. Thanks for your hard work!
RobBull69 said:
Purchased and 5 starred. Thanks for your hard work!
Click to expand...
Click to collapse
Thanks!
Is this great, new app specific to the Nexus 7? I works fine on my N7 with an AOSP custom rom. Might it work on Galaxy Tab 2?
king200 said:
Is this great, new app specific to the Nexus 7? I works fine on my N7 with an AOSP custom rom. Might it work on Galaxy Tab 2?
Click to expand...
Click to collapse
Will work with any 2.2+ tablet and phone. Just noticed the OP said Nexus 7 and changed it.
Seems like when my phone disconnects from Wi-Fi, I have to restart app in order to get messages on my tablet.
N1_Fan said:
Seems like when my phone disconnects from Wi-Fi, I have to restart app in order to get messages on my tablet.
Click to expand...
Click to collapse
I'll give that a look. I may need to detect wifi state changes and request an updated google id. Thanks for the report.
To follow up, if both devices disconnect and reconnect they sync beck up.
N1_Fan said:
To follow up, if both devices disconnect and reconnect they sync beck up.
Click to expand...
Click to collapse
I'm preparing 1.0.2 to address this reported issue. I had to add two permissions, one to get wifi state, and the other for mobile network state.
Now when a network change is detected, the update service will kick off to re-register your device.
Works well on my Nexus 7, Thanks.
Before I go to bed, two new additions for tomorrow:
Sent message status indicator - Yellow = Sent to phone, Green = Received and processed by phone
Automatically update cloud ids on network change
Time for sleep.
Works nice! :laugh:
Could you eliminate the blue background for the navbar icon, so it's just the white cloud? It doesn't jive with my theme lol. Other wise, great app, great development!
Sent from my Nexus 7 using XDA Premium HD app
Hi,
Does it manage mms too? If not will it?
Thank you
Nevermind, was in description..
Maceone said:
Could you eliminate the blue background for the navbar icon, so it's just the white cloud? It doesn't jive with my theme lol. Other wise, great app, great development!
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Would it make sense to use a different icon set for each theme? Which Cloud SMS theme are you using with your device?
onclebob said:
Hi,
Does it manage mms too? If not will it?
Thank you
Nevermind, was in description..
Click to expand...
Click to collapse
I'm currently just working out a way to support MMS and keep with my security design parameters. For MMS to work, I would have to upload the MMS content to my server, and download it on the Tablet side. Likely I'll just assign some random 64 bit name to any uploaded files, and once the tablet has received the file, delete it from the server. 64 Bits of random naming should be enough entropy over the alphabet and numbers to make any attempts to grab a file en route pretty impossible.
This feature will come once I'm sure it follows my design guidelines (and lots of testing)!
Loving this app but the only issue Ive had is that disabling the notification while running does not seem to be working.
airmaxx23 said:
Loving this app but the only issue Ive had is that disabling the notification while running does not seem to be working.
Click to expand...
Click to collapse
The persistent notification feature is working as I intended, but it doesn't seem to be what people wanted. This feature when disabled allows you to dismiss notifications, but they do show up on all events.
I'm testing a change (and rename) for that feature called Always Show Notifications. This will do as you expect, allowing notifications to briefly show on new message, and automatically dismiss themselves (5 second delay) if you leave the setting unchecked. Should this delay be longer?
I'll be testing this through the day before I make an update available to ensure Android doesn't try to close the app down without notifications running.
bechard said:
Would it make sense to use a different icon set for each theme? Which Cloud SMS theme are you using with your device?
Click to expand...
Click to collapse
Icon set would be great. I'm using the dark theme. My navbar is black, and the blue icon stands way out.
Sent from my Nexus 7 using XDA Premium HD app
I'm wondering if you get all notifications on the Gear live or only the apps that had been updated to work with the watch?
I'm specially wondering about 3er party SMSs clients and other like Whatapp and Instagram that I use a lot.
Thanks
All apps. Essentially any app that generates notification on phone.
You can select apps from which you don't want to receive notification on watch thru android wear settings on your phone.
Maturola said:
I'm wondering if you get all notifications on the Gear live or only the apps that had been updated to work with the watch?
I'm specially wondering about 3er party SMSs clients and other like Whatapp and Instagram that I use a lot.
Thanks
Click to expand...
Click to collapse
As stated in google io:
Wear plugs into the 4.3+ notification system. Any notification generated will get converted to a "wear" notification/card
Additionally, any apps that use "notification actions" (not sure what the offical name is) such as; "delete" and "archive" in gmail notifications will get converted to "action buttons" in wear that call the exact same code on the phone, thus producing the same results. This is useful to remember for apps that have notification actions on your phone but haven't updated to support wear.
Additional functionality such as "display extended cards" or "stack multiple notifications" (including the thing that hangouts can do where tapping would bring you a history of the chat on the watch itself) or "reply by voice" types is what would require an "update to the code"...THIS is what people are looking for in apps that "update to support wear".
[**] for instance, whatsapp notification would show up, whatsapp does not have any notifications action buttons on my phone so all I would see is "open in phone" (probably) as a button in my wear device. If they update the app we could tap the wear card to see the full conversation (including the full message rather than just what you would normally see in the notification slide on your phone) slide to the right to get a button to "reply by voice".
It uses the new notification access thingy. All notifications get sent to watch. Can exclude apps
Sent from my GT-I9505 using XDA Premium 4 mobile app
**Updated 5/27/2017**
After installing this profile Google Home will announce your selected incoming notifications by app name and subject line.
Video Demo
Part 1.
1. Download and install Tasker, AutoNotifications BETA, and AutoCast BETA (you will need the Full Paid versions). Also download Notifications.prf.xml
2. Once you have received the AutoNotifications BETA update via the Play Store open the app, grant all permissions, press "Enable Notification Intercept" and grant notification access. Leave all other default settings and exit AutoNotifications.
3. Once you have received the AutoCast BETA update from the play store open the app, grant all permissions, select "Manage Cast Devices," then press + to add your Google Home then exit the app.
Part 2.
1. Place the Notifications.prf.xml file in your device’s Tasker/profiles folder (if these folders do not exist then create them).
2. Open Tasker and long-press “Profiles,” then select “Import” and import the xml file from Part 1.
3. Back-out of Tasker to save the profile. Done!
You can customize your list of apps to announce by pressing the "Notifications" profile in Tasker to expand the profile, then press "AutoNotification Intercept Event...", then the pencil to configure. Press "Apps" to select your apps. Google Home will now announce incoming notifications including the name of the app and subject line (you can disable by placing your phone on silent). Enjoy!
Tip: include the Google App in your selected apps to hear your Google reminders on GH.
**Important**
- GH must be connected to the same wifi network as your phone in order to announce the notification.
- Turn off battery optimization for Tasker, AutoNotifications, AutoCast or your device may disable these apps when idle.
Other Google Home Projects:
- Ask Google Home - Who Called?
- How-To Hear Missed Call and Unread Text Message Reminder on Google Home
- How-To Make Google Home Announce Incoming Calls and Auto-Read New Text Messages
- Google Home - Quick Todoist Update and Recurring Reminder
- Google Home Spotify Alarm
- How-To Reply to Text Message with Google Home
- How-To Have Google Home Read Your Last Text Message
- How-To Send Text Messages via Google Home (Text Any Contact or Ph#)
- How-To Initiate Phone Calls via Google Home
- How-To Create Calendar Events using Google Home
- Start Navigation with Google Home
Instead of Silent to prevent any notification announcements, can I change it to Do Not Disturb instead? Would changing %SILENT ~ off to %DO NOT DISTURB ~ off work?
Ken L said:
Instead of Silent to prevent any notification announcements, can I change it to Do Not Disturb instead? Would changing %SILENT ~ off to %DO NOT DISTURB ~ off work?
Click to expand...
Click to collapse
I haven't tried that but it sounds like it should work.
muniz_ri said:
I haven't tried that but it sounds like it should work.
Click to expand...
Click to collapse
Yes, it does work, but it's not that straight forward. I've attempted many trial and errors and finally discovered one that worked for us (since we have the same phone).
https://photos.app.goo.gl/MbVIj9tRxYOpepIy1
I also removed the reading of the message from the notification and unread text reminder, keeping just a notification of a text received from sender. I didn't feel too comfortable having my text auto-read out loud.
Multiple Google Home's
Thanks for this, it works a treat when casting to one google home.
However i tried to get it to cast to my speaker group which just causes the app to crash. Do you know of any work arounds or is it just not capable of doing this yet ?
Unfortunately the app can currently only cast to one device at a time.
Cool things here! A Question Please, - When I import the tasker.xml, are then all my other tasker-tasks still there?
Thanks!
roselanguste said:
Cool things here! A Question Please, - When I import the tasker.xml, are then all my other tasker-tasks still there?
Thanks!
Click to expand...
Click to collapse
Yes
muniz_ri said:
Yes
Click to expand...
Click to collapse
Thanks, I have already running Three of this Wonderful Profiles, and it is awesome!
Thank You very much!
italione said:
Thanks for this, it works a treat when casting to one google home.
However i tried to get it to cast to my speaker group which just causes the app to crash. Do you know of any work arounds or is it just not capable of doing this yet ?
Click to expand...
Click to collapse
I know Your Question is a time ago, but I wanted to let You know, that it is Possible to cast to more than one Google-Home! - You must only go in the Tasker-Profile, tab on the profile to expand it, tab on the right side in the expanded profile (tasks of the profile), and setup the last task a second time the same but now choose a further Google-Home-Device, done! So the Google-Home's speaking out the information one after another, how it set in the Tasker-Profile! It's really Great!
---------- Post added at 01:57 AM ---------- Previous post was at 01:43 AM ----------
muniz_ri said:
Yes
Click to expand...
Click to collapse
I have seen Your awesome Profiles, and in the moment I'm addicted to it! I wanted to let You know, because I have seen that in the past Someone have asked about to cast to more than one Google-Home, and You answered that yet is not possible! - Probably You know this anyway, but in case not, I have found a Workaround in the way that I have set up the last task in the profile (Autocast) a second time, and choosed a second Google-Home, and now the Google-Home's speaking out the informations one after another, in the sequence it is setup in the Tasker-Profile! So it is possible to setup many Google-Home's as Wish with this Wonderful Profiles!
Thanks for Your Awesome Work and Time!:good:
Hello Guys,
I've always used a simple automation to read from whom my whatsapp messages are while I was with my headphones and walking on the streets or the subway. It's useful for me to know if I might have to stop to read any of those or if I could just leave for later.
The events are:
Notification - Whatsapp
Headset plugged - Any
The action is:
Say %NTITLE
But recently, due to a whatsapp or Android 6 upgrade, this not always read the last notification title, but the first unread notification I got in whatsapp. For example, if I get a message from person A and then 3 messagens from person B, it would say 4 times message from person A.
I've tried the %evtprm2 variable as well. Does any one know of a way to fix this issue?
Thanks!
Hi,
Maybe you can look into AutoNotification: https://play.google.com/store/apps/details?id=com.joaomgcd.autonotification
It gives you a lot more info on notifications, but I'm not sure if it can solve your problem. Make sure you open AutoNotification, and click 'Enable Notification Intercept'. Then create a new Event profile in Tasker: Plugin --> AutoNotification --> Intercept.
Hope this helps!
I'm using a third party app to read notifications by voice. There are many apps available on play store for this purpose.
Sent from my Phone
I'm working on an app that send SMS remaninder by SMS once a day.
Basically I set an intent at the specified time, that trigger a receiver where It send the SMS, and show a notification that the job is done.
I tested it on some devices: old moto with oreo and also newer devices like some samsung with android 13.
When I tried it on this Huauei P30 Pro I faced 2 problem:
-the receiver not work, so I change energy save setting and it seem to work.
-SMS are not sent, but notification is showed, so I know that code is executed, but do nothing. (of course I asked the permission to access SMS when installing the app).
I did not know very well huawei devices so my question : is there any security setting that not allow me to send SMS?
any advice?