Database Info

Issues completing call with slash character in contact phone number

Treo 650, WM 6.1, ActiveSync with Exchange 2003.
Contacts pulled/queried from Exchange global address list contain a slash separating the area code and the rest of the phone number (e.g. 404/123-4444). When I attempt to call a number with a slash, the dialing sequence halts at the slash, but still tries to make the call (e.g. the phone dials 404 and activates "send").
Before someone states the obvious like try to import as many contacts as possible to my personal contacts and replace the slash, let me say this is not practical. Also, my company predominantly uses Blackberry for its handheld needs and this does not cause issues for those devices, so I cannot ask that the company go in and change the phone number formatting for 50K+ entries. Lastly, I have tried searching xda and the rest of the interweb to no avail - feel free to search-slap me with a valid search link (one that is properly formated url including search string) if you know of one that has relevance to my plight.
I've tried changing regional settings hoping another country setting would "interpret" the slash to no avail so far. Tried other contact software, hoping there would be a setting for controlling "special characters", but nothing yet.
xda-developers, you are my only hope
Thanks in advance!

[APP][1.6+] Balance update / USSD blocker

Hi Folks,
Some carriers send a USSD balance update message after each call, and sometimes after each data session on prepaid plans. This is very annoying, and SMS blockers won't stop these USSD messages.
I wrote an app to block USSD messages by keywords or regex. Works well for me in blocking my carrier's balance update messages.
My first android app, so please let me know if I can do something better.
Credits to commandus.com/blog/?p=58 for showing how to intercept these messages using the undocumented hook.
App is "com.melkote.quietbalance" on Google App Store. The v1.0 of the app is also attached to this post.
https://play.google.com/store/apps/details?id=com.melkote.quietbalance

talkative said:
Hi Folks,
Some carriers send a USSD balance update message after each call, and sometimes after each data session on prepaid plans. This is very annoying, and SMS blockers won't stop these USSD messages.
I wrote an app to block USSD messages by keywords or regex. Works well for me in blocking my carrier's balance update messages.
My first android app, so please let me know if I can do something better.
Credits to commandus.com/blog/?p=58 for showing how to intercept these messages using the undocumented hook.
App is "com.melkote.quietbalance" on Google App Store. The v1.0 of the app is also attached to this post.
Click to expand...
Click to collapse
isn't working
Using galaxy s2 (AOKP 1CS ) If that matters.
I selected keyword and its not blocking ....
Edit: working, my bad didn't restart.thanks it's what i was looking for

Works perfectly (Galaxy S2 with CM9)
I've been looking for something like this for a long time but I just wasn't sure how to do it. I was told that these messages are not exactly USSD because USSD requires a code to be sent.
Also, thanks for the link to the blog with the sample code. I was looking for a way to make a widget that updates automatically using the intercepted message.

a big thanks
Thanks a lot, just what i need,i have requested for this in numerous forums, the only reply i got was it's operator based, contact your operator btwn you should reboot after seeting the matching words,
In my case the matching words are,last,call,
U can set this according to your ussd, n once you set you are ready to go,if some one wishes to be know their balance their can try prepay widget , n since it's not free i would like this feature to be incorporated in this app,
s2 running ics remix,

Hi Folks,
Thanks for all the feedback, here and elsewhere.
I've updated the app to ver 1.1 - this version adds a screen to show the last 25 messages and action taken (block or allow) and fixes a bug with blocking frequency.
You must reboot your phone if you update from 1.0 to 1.1 (or install either version).
As I'm a new XDA user, I can't edit the original post (due to presence of URL). So I've attached the APK to this post. If any moderators can move the APK file to the first post, it'll be great!
Thanks!
Talkative

how to block idea data usage msg. ths app not banning class 0 message i.e. data usage

I'm on airtel n it's working for my data messages, so it should work on idea also
Just place the words that appear in your data balance ussd, like mb,last,charge,etcn you should be fine, you should reboot to get it started
from raj's s2

do an tutorial please

I'm on Airtel in India, and worked a charm - thank you very much!
I managed to use it on several messages that come through with different wording using the Keyword List.
Thanks again!
Now, what would be *really* useful is a widget that takes the info from the messages and displays the latest balance info - although there are other aps that do that

aldredd said:
Now, what would be *really* useful is a widget that takes the info from the messages and displays the latest balance info
Click to expand...
Click to collapse
+1

The messages have stopped, which by itself is a great relief......earlier by the time i had waded through the layers of OK i was missing calls! Thanks talkative.
But the beeping still continues. Is there any way to turn that off too or have i missed something in the settings?

Not able to block the message bal pop ups
Hi I installed this app but itz not able to block the msgs.
When I tried to send the bulk sms from my sms application, I still recieve the balance messages from service provider.
How to block the messages? What to write the message matching string for that?

Multiple options to match strings would've been nice.

s
Bydefault for the past few days my balance messages stopped. is there any way to activate it.

Works perfectly with Airtel. Just use keyword blocking list and add words like balance, validity, usage to it to block all messages. Thanks!

Hi, I just installed it today and was just amazed by it. Currently I am using Keyword blocking to block messages.
I would like someone to explain blocking messages using sub string and / or regular expression with example.
Thanks in advance.

rmittal said:
Hi, I just installed it today and was just amazed by it. Currently I am using Keyword blocking to block messages.
I would like someone to explain blocking messages using sub string and / or regular expression with example.
Thanks in advance.
Click to expand...
Click to collapse
+1 Does it work on Jelly Bean too ?

It blocks the Message but Bip and Vibration is still there
Dear Developer,
Many congratulations for making such a wonderful app.
I found two problems with it.
1. It blocks the message but vibration and bip sound comes after every net session
(this has been solved by reinstalling) <s>2. When I send any code from my mobile to check balance e.g. *111#, it stop them too. I mean it keep showing "sending" on screen so message is not going out. </s>
I will appreciate if you look and check for above problems
Thanks
Raship

Source Code?!
Great work.
If it's not too much bother, is the source code available? I'm trying to implement a USSD interceptor and I was wandering if I can use your code as a starting point.
If it's not open-sourced but you are OK with sharing it please send it to me @
[email protected]
Click to expand...
Click to collapse
If it's not feasible, sorry for bothering you.

Hi mSobhy90,
I'll clean it up and put it on GitHub in a few days, I love open source!
In the interim, everything you need is here:
commandus.com/blog/?p=58
(You can translate it quite well with Google Translate)
I want to link to that post so the original finder of the hook point gets credit.
Bye,
Talkative

[Q] SMS time sent vs. received

I give up. I have searched here and elsewhere for a solution that works for me but nothing does. I am running a custom TW ROM (Dandroid 3.9 for JB 4.1.2) on Verizon firmware VRBMF1, so the fix for JPX/JPY firmware won't work for me. Other mods I have seen are for different firmwares also, and Wanam Xposed only works from JB 4.2+. I have also tried 3rd party apps that supposedly fix this, but SMS Sent Time Fix does not work, and SMS Sent Time does not actually fix the timestamp on the message; it only appends the actual sent time to the end of the body of the message which I don't prefer.
I did find a modded SecMms.apk with a fix baked in which does successfully add the actual sent time to the 'date_sent' field in the mmssms.db database; however this still does not accomplish the task of substituting the time sent in the timestamp that appears above each message. Also knowing that the SMS Sent Time app can locate the actual date/time sent gives me the belief that there has to be a way to get the timestamp in my conversations to use this value. Technically it wouldn't be the time I received it, but in cases where I'm in airplane mode for hours - as happens frequently - seeing that I received a text while my phone was off and knowing the time it was sent is more important that using a true time of receipt.
If I thought it was a limitation with JB 4.1.2 I would bite the bullet and update either to 4.3 or even to KitKat, but I like to think that it's possible yet the developers that do all this amazing work haven't found that Verizon SCH-i535 phone running TouchWiz Jellybean 4.1.2 to test on.
So does anyone have any ideas as to what I can try next?

Hi!
I'm the developer of "SMS Sent Time". I haven't been active here on xda for some time now but I got noticed about your thread via Google Alerts and I thought I will use this occasion to bring some light into the overall situation:
Sorry, the post got much longer than intended, but there was so much to explain...
How SMS receiving works in general:
Your mobile network sends you a PDU (protocol data unit) packet containing a SMS message. This PDU format also contains a timestamp field which is filled by the SMSC server of the SMS sender. In most of the times this timestamp == sent time (the time when the SMSC of the sender's mobile network received the message by the sender's phone). However some obscure mobile network providers around the world seem to insert a wrong time into this field (mostly because of wrong set timezone settings, UTC time vs. local time, applying wrong timezone values, etc., you can imagine.. ).
How SMS are received/stored in Android
In Android there exists a system wide database where the received SMS messages get stored into. When a SMS arrives, a system service parses the raw PDU packet it received from the modem part of your phone and stores the SMS data into the system database. The user then can use any SMS application he likes (the default one, GoSMS, HandcentSMS, etc..) to display the messages from this global system SMS database. All SMS apps access the same underlying Android system SMS database.
The problem:
When implementing this SMS database and the receiving service Google made 2 decisions:
they decided that the timestamp from the provider might not be reliable and
they initially only included ONE "date" field in the system database (you can see the structure of this database table in old Android 2.2 here: Android 2.2 SMS database structure).
As a result we ended up having only one time field for a SMS and the SMS receiver service filled this time field with the current time when it receives the SMS (because it doesn't trust the SMSC timestamp).
What SMS Sent Time does:
Given this situation (and not liking it) I realized a few years ago that it is possible for any application in Android (of course only with the according permissions) to register for incoming SMS Intents (simply register a rceiver for "android.provider.Telephony.SMS_RECEIVED" in the app). When doing this the Android system informs the app on any incoming SMS and also lets it access the data from the raw PDU packet received from the network provider (more or less).
So in this moment (when receiving the SMS) the information about the SMSC timestamp is still available!! This was all I needed to build the SMS Sent Time application. But first I had some troubles when modifying the SMS database, mostly because of the fact, that my app first needs to wait until the system service has stored the SMS into the database and then my app has to reliably find the very same sms in the database. But when the message is found the app can modify it (prior to Android 4.4). So the app also could easily change the date field (instead appending it to the text). I was thinking about doing this, but then I got unsure that this might mess up the sort order in some SMS apps when I receive some SMS with a really completly wrong timestamp. So - just to be on the safe side - I decided to append it to the text (which didn't bother me personally).
I also have to say that at this point in time I had no intentions to make this application ever public. This was just meant as a quick hack for myself. Only some time later when I realized that a lot of more people are facing the same problem I decided to publish it. But it still was and is a quick hack for myself. I have not the resources (mostly time) to invest more work. I develop on Android only in my free time and never made a single cent with this app (no donations, no ads) but spent over the years hundreds of hours (including answering a lot of users' mails). So I was glad when people started asking me for the source code (it's public on GitHub: SMS Sent Time on Github) hoping different/improved solutions might arise...
What Google learned about this:
There existed a loooong time bug-report on exact this issue (sorry cannot find the link at the moment) where a lot of users where complaining about exactly this problem (sent time != received time). So Google finally listened to its users and changed the format of the SMS system database beginning Android 4 (AFAIK). You can see it here, if we look at the same database code as above in Version 4.0.3: Android 4.0.3 SMS database structure you will notice that now there is an additional field "date_sent" in the database table! Hooray! :victory: Finally!
Unfortunately the Android world is very fragmented and every phone manufacturer seems to go its own ways. So not all phones with Android >4.0 did implement this change or even if they did inherit this part of the Android core system they often did not update their SMS applications!
The same applies for 3rd party SMS apps. For example: I have a Nexus 4 running a cyanogen-based 4.4.1 and I can confirm that in my system database both date fields are filled correctly. So the sent time is definitely there! But neither "Go SMS Pro" nor "Handcent SMS" seem to display this second field (please correct me if I am wrong, I just made a quick test, I normally don't use these apps). Only the original AOSP SMS app and Google Hangout (when used as SMS app) seem to display both times (sent and received) in message details.
New limitations with Android KitKat (4.4):
Additionally another change came along the road when Google introduced Android 4.4 (KitKat). Suddenly a lot of users reported that SMS Sent Time stopped working for them. The background: Starting with Android 4.4 Google introduced the concept of a "default SMS app". The user has to choose, which app should be the default application for handling incoming SMS on the phone. While other SMS apps (for example like my SMS Sent Time) still are able to receive incoming SMS (and read the sent time) they are no longer allowed to modify the content of the system's SMS database (even with the correct permissions in place). The database update silently fails. Sad enough this is a fact and there is nothing I can do in my app to change this. It's a security feature of Android which I cannot change. (And the reason why I am writing a lot of feedback mails to users lately.)
Workaround:
But at least there is a known "workaround" to overcome this new KitKat limitation (altough it seems that Google decided to remove this possibility with the update from 4.4.1 to 4.4.2). In Android 4.4 there exists a hidden settings screen ("AppOps") which allows you to grant or deny specific permissions to applications. You cannot open this settings screen directly from the system settings, but there are some apps in the Play Store which do nothing else, than just opening this (already existing but hidden) settings screen. For example, I used the app App Ops Starter. This simple app needs no permissions and does nothing else then opening Android's hidden "app ops" settings screen. Once opened, on the tab "Messaging", you see a list with all your installed apps which have sms-permissions. If you open the settings page for one specific app you can grant the permission "Write SMS/MMS" again and the system will behave again like it did before Android 4.4.
So, long story short:
It's been a long time with this problem in the Android world. Hopefully workarounds like my app should not be needed in future (when all SMS apps make use of the "date_sent" field in the SMS database).
Until then it would be possible to modify the SMS Sent Time app to overwrite the datestamp field in the database (instead appending the time to the message text). Any develper should feel free to take the source code and modify it accordingly.
[edit]
corrected spelling
[/edit]

Now THAT is a response! Thanks so much for taking the time to explain in vivid detail (and I actually understands more than half of it!). I do recall the Google thread that dates back to 2009 and kept running across it in my searches. I also saw references to "App Ops" along the way and the suggestion that even that workaround fails starting with 4.4.2. So yeah there's a lot to digest here but I suppose the 3 takeaways for me are:
1) It is possible for 3rd party messaging apps like Handcent and Go SMS to implement the sent time either in message details or in the timestamp above the message.
2) That hope vanishes with KK 4.4.2
2) That hope could be restored if Android again revises its SMS database structure or the message handling process to capture and display the time the SMS was actually sent
Still the issue of different time zones can muddy the waters so it may be that a perfect solution does not exist, at least without a lot of extra effort to identify sender location, compare to receiver's location, look up a time zone offset value somewhere, etc. etc.
But at least your explanation clears up a LOT of confusion for me so now I know the sordid history behind it all. And I will say that though I don't prefer to see a timestamp at the end of my messages, it is better than not being able to get the real sent time at all.
Thanks again for making your "quick hack" available to us and for all the other support you've given the user community on this nagging issue!
androcheck said:
Hi!
I'm the developer of "SMS Sent Time". I haven't been active here on xda for some time now but I got noticed about your thread via Google Alerts and I thought I will use this occasion to bring some light into the overall situation:
Sorry, the post got much longer than intended, but there was so much to explain...
How SMS receiving works in general:
Your mobile network sends you a PDU (protocol data unit) packet containing a SMS message. This PDU format also contains a timestamp field which is filled by the SMSC server of the SMS sender. In most of the times this timestamp == sent time (the time when the SMSC of the sender's mobile network received the message by the sender's phone). However some obscure mobile network providers around the world seem to insert a wrong time into this field (mostly because of wrong set timezone settings, UTC time vs. local time, applying wrong timezone values, etc., you can imagine.. ).
How SMS are received/stored in Android
In Android there exists a system wide database where the received SMS messages get stored into. When a SMS arrives, a system service parses the raw PDU packet it received from the modem part of your phone and stores the SMS data into the system database. The user then can use any SMS application he likes (the default one, GoSMS, HandcentSMS, etc..) to display the messages from this global system SMS database. All SMS apps access the same underlying Android system SMS database.
The problem:
When implementing this SMS database and the receiving service Google made 2 decisions:
they decided that the timestamp from the provider might not be reliable and
they initially only included ONE "date" field in the system database (you can see the structure of this database table in old Android 2.2 here: Android 2.2 SMS database structure).
As a result we ended up having only one time field for a SMS and the SMS receiver service filled this time field with the current time when it receives the SMS (because it doesn't trust the SMSC timestamp).
What SMS Sent Time does:
Given this situation (and not liking it) I realized a few years ago that it is possible for any application in Android (of course only with the according permissions) to register for incoming SMS Intents (simply register a rceiver for "android.provider.Telephony.SMS_RECEIVED" in the app). When doing this the Android system informs the app on any incoming SMS and also lets it access the data from the raw PDU packet received from the network provider (more or less).
So in this moment (when receiving the SMS) the information about the SMSC timestamp is still available!! This was all I needed to build the SMS Sent Time application. But first I had some troubles when modifying the SMS database, mostly because of the fact, that my app first needs to wait until the system service has stored the SMS into the database and then my app has to reliably find the very same sms in the database. But when the message is found the app can modify it (prior to Android 4.4). So the app also could easily change the date field (instead appending it to the text). I was thinking about doing this, but then I got unsure that this might mess up the sort order in some SMS apps when I receive some SMS with a really completly wrong timestamp. So - just to be on the safe side - I decided to append it to the text (which didn't bother me).
I also have to say that at this point in time I had no intentions to make this application ever public. This was just meant as a quick hack for myself. Only some time later when I realized that a lot of more people are facing the same problem I decided to publish it. But it still was and is a quick hack for myself. I have not the resources (mostly time) to invest more work. I develop on Android only in my free time and never made a single cent with this app (no donations, no ads) but spent over the years hundreds of hours (including answering a lot of users' mails). So I was glad when people started asking me for the source code (it's public on GitHub: SMS Sent Time on Github) hoping different/improved solutions might arise...
What Google learned about this:
There existed a loooong time bug-report on exact this issue (sorry cannot find the link at the moment) where a lot of users where complaining about exactly this problem (sent time != received time). So Google finally listened to its users and changed the format of the SMS system database beginning Android 4 (AFAIK). You can see it here, if we look at the same database code as above in Version 4.0.3: Android 4.0.3 SMS database structure you will notice that now there is an additional field "date_sent" in the database table! Hooray! :victory: Finally!
Unfortunately the Android world is very fragmented and every phone manufacturer seems to go its own ways. So not all phones with Android >4.0 did implement this change or even if they did inherit this part of the Android core system they often did not update their SMS applications!
The same applies for 3rd party SMS apps. For example: I have a Nexus 4 running a cyanogen-based 4.4.1 and I can confirm that in my system database both date fields are filled correctly. So the sent time is definitely there! But neither "Go SMS Pro" nor "Handcent SMS" seem to display this second field (please correct me if I am wrong, I just made a quick test, I normally don't use these apps). Only the original AOSP SMS app and Google Hangout (when used as SMS app) seem to display both times (sent and received) in message details.
New limitations with Android KitKat (4.4):
Additionally another change came along the road when Google introduced Android 4.4 (KitKat). Suddenly a lot of users reported that SMS Sent Time stopped working for them. The background: Starting with Android 4.4 Google introduced the concept of a "default SMS app". The user has to choose, which app should be the default application for handling incoming SMS on the phone. While other SMS apps (for example like my SMS Sent Time) still are able to receive incoming SMS (and read the sent time) they are no longer allowed to modify the content of the system's SMS database (even with the correct permissions in place). The database update silently fails. Sad enough this is a fact and there is nothing I can do in my app to change this. It's a security feature of Android which I cannot change. (And the reason why I am writing a lot of feedback mails to users lately.)
Workaround:
But at least there is a known "workaround" to overcome this new KitKat limitation (altough it seems that Google decided to remove this possibility with the update from 4.4.1 to 4.4.2). In Android 4.4 there exists a hidden settings screen ("AppOps") which allows you to grant or deny specific permissions to applications. You cannot open this settings screen directly from the system settings, but there are some apps in the Play Store which do nothing else, than just opening this (already existing but hidden) settings screen. For example, I used the app App Ops Starter. This simple app needs no permissions and does nothing else then opening Android's hidden "app ops" settings screen. Once opened, on the tab "Messaging", you see a list with all your installed apps which have sms-permissions. If you open the settings page for one specific app you can grant the permission "Write SMS/MMS" again and the system will behave again like it did before Android 4.4.
So, long story short:
It's been a long time with this problem in the Android world. Hopefully workarounds like my app should not be needed in future (when all SMS apps make use of the "date_sent" field in the SMS database).
Until then it would be possible to modify the SMS Sent Time app to overwrite the datestamp field in the database (instead appending the time to the message text). Any develper should feel free to take the source code and modify it accordingly.
[edit]
corrected spelling
[/edit]
Click to expand...
Click to collapse

Hi!
Sorry for the delayed answer and thanks for your appreciation.
Just wanted to comment on your 3 points:
Brianakin said:
1) It is possible for 3rd party messaging apps like Handcent and Go SMS to implement the sent time either in message details or in the timestamp above the message.
Click to expand...
Click to collapse
Yes! Indeed! On every ROM which inherited the new SMS database layout from Google's original open source Android version 4.0.3 it should already today be possible for SMS apps to display both times: the sent time AND the received time!
So if your Android system database has this additional sent_time field, you just need a SMS app which shows it to you. So go ahead and send mails to your favorite SMS app developers and ask them about it (you may provide the link to the updated SMS database layout since Android 4.0 including the new "date_sent" field)
2) That hope vanishes with KK 4.4.2
Click to expand...
Click to collapse
No, this hope does not vanish! Only my app may not work any longer on 4.4.2 but if have already the sent_time in your normal SMS app you won't need my app anymore. (I'm probably the first developer being happy about decreasing user numbers. )
3) That hope could be restored if Android again revises its SMS database structure or the message handling process to capture and display the time the SMS was actually sent
Click to expand...
Click to collapse
No, that has nothing to do with it. As noted above, Google has already improved the database structure beginning with Android 4.0.3. Now just all phone manufacturers need to inherit this improvement (which I hope they already did - but I have no concrete infos here).
And we need all the SMS app developers (3rd party apps like Handcent and Go SMS but also the "default" messaging apps from Samsung, HTC, etc..) to display the sent_time (which hopefully is already there on every phone running Android 4.0.3 or higher).
So in general we are on the right way!
P.S.: When I use Google Hangout as SMS app I can see in the message details sent time AND received time. Can you try this just to verify if in principle it also works on your phone?

Principle confirmed. Hangouts does display both times in msg details. On to my favorite SMS app developer to request this option in a future update!

SMS Sent time Issue, but which new phone?
Yes, many thanks Androcheck for the SMS Sent Time app. The issue is immensely irritating and I don't mind at all that the time sent is appended to the message itself. However, it's now time for a new phone (for a number of reasons) and I would welcome advice on whether it would be easier to:
1. Stick with Android and ensure the new phone has up to 4.4.1 only and not 4.4.2?
2. get a 4.4.2 and wait fo the developers to catch up and all start using the sent time field
3. get an iphone - no, have already ruled this out for various reasons
4. Consider a windows phone - do these have the same issue?
Advice anyone?
Thank you for reading my post

Lollipop
Hi. Any chance to have this one run on Lollipop? This is a big help on my Acer and Xperia phone previously running ICS. Please help. Thank you.

Lollipop & S4
I just want to confirm that if you turn on the SMS/MMS write permission for SMS Sent Time in App Ops, then this fine application is still working also in Lollipop 5.0.1 (at least on my S4 i9505 it is!). Unfortunately, App Ops need root! I had rooted mine before, but it's definitely a very fine reason for rooting the phone.
This is really one of the most useful apps for me on my android phone. I don't understand why this feature has always slipped through with the manufacturers. Just as an example: yesterday my boss sent me a text. Due to slow network and bad coverage, I received his text at 12:30 AM, asking to call him when I have network. Yeah...well...luckily he was not sleeping yet Had I known that it was sent hours before, I would have known that he had already reached one of my colleagues and a callback (at this time) was totally unnecessary.
So, I am very happy to find that it is working again! Of course, a timestamp field in the messaging app would be better, but for most people to confusing. So to append the sent time to the message seems like the 2nd best to me.

I see this is an old thread now but, since I've been redirected here from "SMS Sent Time" google play page, I'll use it anyway.
I've recently update to android 7.1.1 and the app doesn't seem to work anymore.

Korean (S) foibles

Received this one this week and have rooted, flashed new rom (which was identical to stock anyway) but there are a few minor annoyances I was wondering if anyone else has any clues to remedy.
First off is the weather DB for TW weather. It is from Korea so has very limited information for other countries. Seems to be no way to add to the DB in UI.
Then there is the SMS app. Each time a new text is received it just says 'New Message' you have received a new message. No details about sender or a preview of the message at all.

Fatila said:
Received this one this week and have rooted, flashed new rom (which was identical to stock anyway) but there are a few minor annoyances I was wondering if anyone else has any clues to remedy.
First off is the weather DB for TW weather. It is from Korea so has very limited information for other countries. Seems to be no way to add to the DB in UI.
Then there is the SMS app. Each time a new text is received it just says 'New Message' you have received a new message. No details about sender or a preview of the message at all.
Click to expand...
Click to collapse
Don't know the answer to your first question but the second one, probably yes.
If you mean message details showing up on edge screen? Try this:
Go to Settings > Application Settings > Message > Notification > Edge Screen. Here tick that option. Now if you get texts it will show preview of messages.

Thats great thanks, now get message preview and a popup. Strange that is disabled by default.

Ok noticed some other problems now.
One is S Planner, it likes to crash when I am trying to alter any time. Also is there any calender app that lets you duplicates events likethe web one? Pretty annoying missing functionality.
Another weird thing is the edge notification bar. It nearly always says no nitrifications even when an SMS or e-mail is in notification bar!
Weird that Korean has no S Health app as well, or voice recorder,

S health and voice recorder needs to be downloaded from the Samsung app store.
My notifications works fine and also the s planner.

Thanks for that tip. I had searched the galaxy store with no luck but it seems you have to drill down to the essentials list to find it. I downloaded S Health and it crashes before launching. There must be some disabled service (Greenify?) or configuration that is causing issues with some Samsung apps.

Fatila said:
Thanks for that tip. I had searched the galaxy store with no luck but it seems you have to drill down to the essentials list to find it. I downloaded S Health and it crashes before launching. There must be some disabled service (Greenify?) or configuration that is causing issues with some Samsung apps.
Click to expand...
Click to collapse
I have not had any such issues with S Health or S Planner apps.
A few days ago I noticed that the notifications weren't showing up but resetting the phone it returned to normal.

SMS app to combine conversations from the same contact in the same chat window

Hy there,
I hope I posted where I should and if I didn't please tell me the correct section where I should do this. Also, I am not a developer, I do not have root on my phone. I do not want solutions that require changing XML files or anything. I am just asking about an app that I could find in the Play Store, or, maybe, and apk to download (this being the second option)
I have a problem with the messaging app since I left my HTC One S for the Nexus 5X in June 2016 and I did not find an app to replace that, not even on my current Oneplus 5T.
So, I have a contact in my phonebook saved with multiple numbers - work / mobile / home etc. and she texts SMS from either of the numbers (doesn't really matter because they are included in the carrier plan as unlimited). But my messaging app is sorting those SMS as different entries by phone number, and not by contact. So if we start a conversation in a chat window based on the home number, the answer may end up in a different chat windows (she has a dual sim phone so it depends on the settings on which is right now, and because the SMSs are "free", she tends to not look at which carrier is using, because, why would you if they are all free?), but this actually disrupts the logical flow of the conversation.
I know that a such app exists because I used it on HTC One S in 2012 and I was able to send SMS to which number I wanted to select (home / mobile / work of the same contact from the phonebook) and I had all the conversation in only one place, but after I changed on Nexus 5X and now on OnePlus 5T I can not find this feature in the installed app messenger (Google's or Oneplus's), neither on Google searches or specialized websites. I have tested some of the SMS apps, looked for settings, but all of them seem to show the SMSs based on the phone number, and not based on the contact entries.
Can someone suggest an app that could do that? Maybe I didn't search good enough.
P.S. The MMS option to send grouped messages is not an option because this means I will send the same SMS to multiple numbers, but those numbers are of the same person so there is no need to do that ...
Thank you very much for Your answer.