# Simple Mobile Tools to be bought by ZipoApps

**URL:** https://discuss.privacyguides.net/t/simple-mobile-tools-to-be-bought-by-zipoapps/15337
**Category:** General
**Tags:** software
**Created:** 2023-12-02T14:28:18Z
**Posts:** 95
**Showing post:** 36 of 95

## Post 36 by @dngray — 2023-12-05T10:27:01Z

> [@anon73250778](#):
>
> Also PG does not formally endorse them, right?

We’ve never endorsed any of them because they aren’t particularly privacy friendly in any way whatsoever. They’re just some apps, that were open source. There are plenty of apps that are open source out there that we don’t recommend.

There has been threads about them requiring too many permissions (iirc their file manager). I seem to remember being told something about a PDF app too.

I briefly used their SMS app until I found this bug and basically got no follow up on it

> <https://github.com/SimpleMobileTools/Simple-SMS-Messenger/issues/228>
>
> Hi,
> 
> I noticed sending these two images worked, with the `com.android.messagin…g` but not `com.simplemobiletools.smsmessenger`. v5.10.2
> 
> ![c99nu03eeno71](https://user-images.githubusercontent.com/48640805/137448785-3ca00694-ac3d-4cf0-bc89-00bbbfa384f8.jpg)
> ![e_ldttvkaelsi6](https://user-images.githubusercontent.com/48640805/137448797-ecbfd721-5a38-423a-81c9-ef2d3753648c.jpg).
> 
> Here's the logcat from `com.simplemobiletools.smsmessenger`
> 
> ```
> MmsServiceBroker: sendMessage() by com.simplemobiletools.smsmessenger
> MmsService: sendMessage messageId: 0
> MmsService: Current running=0, current subId=-1, pending=0
> MmsService: Add request to running queue for subId 1
> MmsService: [SendRequest@740908 messageId: 0] Executing...
> MmsService: mms config for sub 1: Bundle[{httpSocketTimeout=60000, aliasMinChars=2, smsToMmsTextThreshold=-1, enableSMSDeliveryReports=true, maxMessageTextSize=-1, supportMmsContentDisposition=true, enabledTransID=false, aliasEnabled=false, supportHttpCharsetHeader=false, allowAttachAudio=true, smsToMmsTextLengthThreshold=-1, recipientLimit=2147483647, uaProfTagName=x-wap-profile, aliasMaxChars=48, maxImageHeight=480, enableMMSDeliveryReports=false, userAgent=, mmsCloseConnection=false, config_cellBroadcastAppLinks=true, maxSubjectLength=40, httpParams=, enableGroupMms=true, emailGatewayNumber=, maxMessageSize=307200, naiSuffix=, enableMMSReadReports=false, maxImageWidth=640, uaProfUrl=, enabledMMS=true, enabledNotifyWapMMSC=false, sendMultipartSmsAsSeparateMessages=false, enableMultipartSMS=true}]
> MmsService: PDU read is too large
> MmsService: [SendRequest@740908 messageId: 0] Failed to prepare for request
> MmsService: [SendRequest@740908 messageId: 0] processResult: 5, httpStatusCode: success (0)
> MmsService: [SendRequest@740908 messageId: 0] MMS failed with error: 5 httpStatus:0
> MmsService: Schedule requests pending on SIM
> ```
> 
> Meanwhile with `com.android.messaging` everything seems fine:
> 
> ```
> MmsServiceBroker: sendMessage() by com.android.messaging
> MmsService: sendMessage messageId: 0
> MmsService: Current running=0, current subId=-1, pending=0
> MmsService: Add request to running queue for subId 1
> MessagingAppDataModel: SendMessageAction: Sending MMS message 23 asynchronously; waiting for callback to finish processing
> MmsService: [SendRequest@a6aa00a messageId: 0] Executing...
> MmsService: mms config for sub 1: Bundle[{httpSocketTimeout=60000, aliasMinChars=2, smsToMmsTextThreshold=-1, enableSMSDeliveryReports=true, maxMessageTextSize=-1, supportMmsContentDisposition=true, enabledTransID=false, aliasEnabled=false, supportHttpCharsetHeader=false, allowAttachAudio=true, smsToMmsTextLengthThreshold=-1, recipientLimit=2147483647, uaProfTagName=x-wap-profile, aliasMaxChars=48, maxImageHeight=480, enableMMSDeliveryReports=false, userAgent=, mmsCloseConnection=false, config_cellBroadcastAppLinks=true, maxSubjectLength=40, httpParams=, enableGroupMms=true, emailGatewayNumber=, maxMessageSize=307200, naiSuffix=, enableMMSReadReports=false, maxImageWidth=640, uaProfUrl=, enabledMMS=true, enabledNotifyWapMMSC=false, sendMultipartSmsAsSeparateMessages=false, enableMultipartSMS=true}]
> MmsService: [SendRequest@a6aa00a messageId: 0] MmsNetworkManager: start new network request
> MmsService: [SendRequest@a6aa00a messageId: 0] APN name is MMS
> MmsService: [SendRequest@a6aa00a messageId: 0] Loading APN using name MMS
> MmsService: [SendRequest@a6aa00a messageId: 0] Using APN [type=mms mmsc=http://mmsc.{{ censored }}:8002/ mmsproxy={{ censored }} mmsport=8070 name={{ censored }} MMS apn=MMS bearer_bitmask=0 protocol=IP roaming_protocol=IP authtype=-1]
> MmsService: [SendRequest@a6aa00a messageId: 0] HTTP: POST http://mmsc.{{ censored }}[30], proxy={{ censored }}:8070, PDU size=139420
> MmsService: [SendRequest@a6aa00a messageId: 0] HTTP: User-Agent=g020c
> MmsService: [SendRequest@a6aa00a messageId: 0] HTTP: UaProfUrl=http://www.gstatic.com/android/sms/G020C.xml, UaProfUrlTagName=x-wap-profile
> MmsService: [SendRequest@a6aa00a messageId: 0] HTTP: 200 OK
> MmsService: [SendRequest@a6aa00a messageId: 0] HTTP: response size=67
> MmsService: [SendRequest@a6aa00a messageId: 0] MmsNetworkManager: release, count=0
> MmsService: [SendRequest@a6aa00a messageId: 0] processResult: -1, httpStatusCode: success (0)
> MmsService: Schedule requests pending on SIM
> ConnectivityService: NetReassign [no changes]
> MessagingAppDataModel: ProcessSentMessageAction: Done sending MMS message 23 in conversation 6; status is SUCCEEDED
> MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages
> ```
> 
> I believe that if this is intentional (to provide compatibility with some carriers etc) then the messenger should tell the user the message was not sent.

> [@anon73250778](#):
>
> IIRC, SMT was a Michael Bazell recommendation.

If that’s the case, he probably fell for the marketing.

---

_[View the full topic](https://discuss.privacyguides.net/t/simple-mobile-tools-to-be-bought-by-zipoapps/15337)._