in reply to using perl to get sms messages

More or less standard location for SMS under Android is /data/data/com.android.providers.telephony/databases/mmssms.db. This is SQLite database and one can read it using simple sqlite3 command.

Normally, this path is not accessible by the users. So you can access SMS messages only from inside of Android application, using Android API. Alternatively you may try to root your phone and then you'll get direct access to the file

Replies are listed 'Best First'.
Re^2: using perl to get sms messages
by Aldebaran (Curate) on Oct 30, 2016 at 09:14 UTC

    Thanks all for comments. They all gave me valuable hints, but I'm disappointed that I didn't get farther with my end of it, as I also "upgraded" to windows 10, and now I don't have a driver that will work for media transfer protocol. I realize that this is not the place to discuss why my free operating system, that was worth every penny of it, and my unadulterated piece of crap phone can't communicate. If I can get the driver working, then this thread might be in business.

    If anyone has a success story using perl on their phone, I'd be interested to know the brand and model of telephone, as well as the OS they use to talk to it. Indeed, the whole reason I left the world of apple was that I might use perl on a phone. I do hope to revisit this topic with something more than a strikeout.

[reply]

      I've used perl directly on various Android devices (phones and tablets) without issue with cc tools. I always run cyanogenmod, and have done since the first version of hardware that supported Android. Faster, cleaner, smaller footprint, no bloatware.

      Windows 10 is a train wreck, I'm glad I only have to support close family who run it. You don't mention what you've done and what happens (How do I post a question effectively?), so I can only advise removing the drivers you have, head over to XDA developers, install the adb/fastboot tools package, transfer the files you need to work with via adb, do what you have to on your computer. Failing that get a vendor win 10 driver or at least try the generic google drivers out there. The adb route will be the quickest method of getting the job done, so far as I un derstand it.

      Update: fixed typos, added link.

[reply]

        As a custodial matter, I wanted to report that while I did get drivers correctly installed, I didn't get any closer to the stated goal. What's more, the whole endeavour is *fraught*, and I ended up having to chase malware off of both computer and rooted phone, which I reset back to factory state. Comments and links were very interesting. I wouldn't attempt any of this again on windows 10, with a crummy phone and no software budget.

[reply]

In Section Seekers of Perl Wisdom