Does Purism Respond to RMAs?

[FranklyFlawless]

Support staff vacancy

This might explain why my two week old support case is still waiting for a response

@JCS

[Sharon]

@FranklyFlawless

at the expense of their time as well.

OPINION:
Well. I don’t mind waiting if there is light at the end of tunnel, and it’s not a train like it has been for almost 2 years now.
All I see are the backs of support. No lights.

To not bother them by taking up their time asking ‘how’s it going’ is not your style. I’m disappointed.

Extremely poor support. Actually, so far Zero support. They have the phone, and based on ‘Purism support’ history they can do as they please, or not do as the case seems, when or if ever they feel like it.

I trusted the suggestions that I send it to Purism. Never again.

Any company building communication products should learn how to communicate with their customers.

I can only conclude, by support’s silence that they no longer have the time, staff, or know-how to fix the phone. Those resources are being used to push for a foreseeable profit through more sales at the expense of existing customers. Ponzi?

Customers should never suffer because of very poor business management.

It’s not a customers place to have to track down and ask if they are working on the 'ware. It is Purism’s job to communicate. I bet if I ordered a L5 that I would receive a immediate email from ‘no-reply’ that I now own a L5 with a note that ‘shipping is TBA’.

[ASwyD2]

Extremely poor support.

@JCS

[FranklyFlawless]

@Sharon

I can only conclude, by support’s silence that they no longer have the time, staff, or know-how to fix the phone.

@JCS

there is a significant (1-2 week) support ticket backlog that Purism is actively addressing while onboarding new support staff, composing new documentation to answer FAQs, and dedicating existing staff to manage during this transition. No one is being ignored - we’re just trying to catch up.

Feel free to continue sharing your opinion, although I will mention it may be unnecessary to declare/preface them within your posts.

[Sharon]

@FranklyFlawless

Feel free to continue sharing your opinion, although I will mention it may be unnecessary to declare/preface them within your posts.

Not sure what you mean by that but:

@amarok @irvinewade @FranklyFlawless
ANNOUNCEMENT:
I have emails from @support with a detailed analysis of what they have tested and results.
It’s not looking good.
On the flip side, I would have always wondered if I just packed the phone up and buried it my drawer and didn’t try the last resort (@support).
I surmised from their results that it is no longer going to work with our carriers in Canada that support L5 text with pics. Remember, it did send text with pics - then suddenly it went crazy.

As soon as I mention the L5 to a carrier, their assimilated brains attached to the collective, cannot compute and go for the path of least resistance and ‘‘We’re sorry - we do not support’’ xyz. They only support the leashes by the duopolies.

According to my carrier Koodo, the manufacturer (Purism?) has to update to comply with new settings. Yet they offer settings and You (reader) and others here have worked with me to get the settings the way Koodo displays them, to no avail.

One kiosk agent said they would give me a account for 48 hours to test it.

Off to answer the @support questions.

~s

[FranklyFlawless]

Okay, that leaves you with a few options left:

1. According to TELUS/Koodo, wait until Purism updates the Modem Manager profile.
2. Migrate to a different telecommunications carrier.

[Sharon]

Just a UPDATE:
To answer my own question, ‘Yes Purism does respond to RMA’s’ … for me anyway.

I have had some good rapport from Purism @support.

The last email said they are testing the modem as it is possible it needs a new one.
‘Adam’ has done a great job of keeping me updated on the progress of the L5 testing.

Even though I despise what digital devices like phones are designed to do, I miss receiving texts with pics (grand kids).

~s

[FranklyFlawless]

Great, mark your post as a solution.

[Sharon]

We’re not done yet.

[Sharon]

Just to keep ya’ll in the loop.
Just received confirmation that the L5 is shipping home via (unfortunately) DHL .
Getting antsy and started out never wanting a cell phone AKA leash. Now I can’t wait.
Apparent cure was a “Modem firmware updated”.
The test will be if I can send/receive text w/ pics. And doesn’t hang when disconnecting from charger and, and …

If it doesn’t do the text/pic thingy, I have a fellow at a kiosk for phones, and he said he could set me up on temp access to carrier as a test for 48 hours, and another if that fails. He said “Don’t worry, I’ll get ya set up one way or the other.”

I only worry about “don’t worry”, and “set up”

[Sharon]

Another update.

I received my L5 back from @support about a hour ago.
Though DHL sent 2 notices that I could opt out of signing for it by clicking a link. I didn’t opt out and still, they silently dropped it off outside the door. No knock, tap - nadda. No signature. I could say it was never delivered. I know, they take a pic. But that means they could jut take it back and use it.
Some people don’t follow rules I guess.

Any way, it’s here. “Modem firmware updated”.
Now I’ll look up about when battery goes in verses when Sims go in order, and see what happens.

[Sharon]

Result of all of this grief - L5 cannot send/receive texts with pics.
Sends/receives text OK, but not with pic attached.
So, it might be L5 doesn’t have a place for the settings the carrier requires.

The 4 fields L5 doesn't seem to have are:

Field	Entry	Details
MMS Port	8799	Same as above
MCC	302	Mobile Country Code: Unique identifier for the mobile phone operator/carrier.
MNC	220	Mobile Network Code: Another unique identifier.
APN Type	default,supl,mms	Note: Do not leave any spaces when entering “default,supl,mms” for services used on APN. When an application accesses the network, it provides an APN type when it requests access for data. If “default,supl,mms” is not an option, choose “internet&MMS;” option from list.

I’d appreciate it if someone knows a way to wedge the last 4 (Port/MMS/MCC Port//MNC 220/APN Type) pieces of data the carrier seems to require.

Είναι όλα ελληνικά για μένα.
~μικρό

[amarok]

First:

1 With the SIM card inserted (and if it’s not yet inserted, make sure you power down before inserting it, then power back on), what does Settings > Mobile > Access Point Names show, after you then click on the “gear wheel” to see more settings? (Expected: “Koodo” and whatever their APN is.)

2 In Chatty, under Preferences > SMS and MMS Settings > MMS Carrier Settings, is anything prepopulated based on the inserted SIM? (Expected: yes, but if not, fill in Phone, MMSC, and APN values provided by Koodo.)

3 In Terminal, run the command mmcli --modem=any, scroll down toward the bottom and look for “operator ID.” The 6 digit value corresponds to MCC and MNC. Yours should show “302220” if the SIM card caused it to be set for you already.

4 For APN Type, I suspect that that’s pretty standard, so it is probably set somewhere in the internals automatically based on the SIM. (Just a guess.)

5 For the MMS port number, that might be standard, too, or set automatically, but I’m not sure. I guess you’ll find out if MMS is still inop after checking/setting the above.

It may be possible to set the port number specifically some other way, but I don’t know for sure.

And after checking/setting the above, you might also want to restart.

FYI, there is a file called mms inside /home/purism/.mms/modemmanager, but I’m not sure if it’s possible (or effective) to add additional entries there. I would avoid that for now.

[FranklyFlawless]

@amarok

It may be possible to set the port number specifically some other way, but I don’t know for sure.

Two methods:

1. Chatty:

@FranklyFlawless

4. Open Chats, tap the hamburger menu on the top right corner, then tap Preferences:

5. Under Protocol Settings, tap SMS and MMS Settings:

6. Under MMS Carrier Settings, input these three values separately into the three text fields labeled MMSC, APN, and Proxy, then tap the Apply button on the top right corner:

• http://aliasredirect.net/proxy/koodo/mmsc
• sp.koodo.com
• mmscproxy.mobility.ca:8799

7. Send an MMS to someone.

2. ~/.mms/modemmanager/mms:

@FranklyFlawless

The mms file has this boilerplate template:

[Modem Manager]
CarrierMMSC=
MMS_APN=
CarrierMMSProxy=
DefaultModemNumber=
AutoProcessOnConnection=
AutoProcessSMSWAP=
IMSI=

[Settings]
UseDeliveryReports=
TotalMaxAttachmentSize=
MaxAttachments=
AutoCreateSMIL=
ForceCAres=

The value of CarrierMMSProxy for @Sharon should be mmscproxy.mobility.ca:8799.

[amarok]

Very nice. Koodo’s customer service should be given these instructions, in case they get other Librem 5 users.

[Sharon]

Yeah - about Koodo. I doubt you’ll be able to reach a real human that can add the suggested settings. But a Forum member can post it there along with a batch of keywords embedded to lure any L5’er to those settings.
~s

[Sharon]

!! SUCCESS !!

Now we’re sending/receiving text and text with picture. Video didn’t work though.

By process of elimination, and kudos to @FranklyFlawless for the added code, here are the lines from which I think did the trick. The highlight is mine showing the code that made it work

@FranklyFlawless

• http://aliasredirect.net/proxy/koodo/mmsc
• sp.koodo.com
• mmscproxy.mobility.ca :8799

A lot of folk helped to arrive at the codes that work for me now.
Thank you everyone for the help as it has added tips & tricks for anyone using the search tool here.

The end…
~s
EDIT: a typo.

[michel_souris]

In short and for the record, I got a response on my RMA request and it got handled fine.

In long : shipped my dead phone and 3 batteries to Purism. The device was unable to charge while turned off (internal power switch failing). Repairs were done and all shipped back, total cost for me was 30 euros. Took about 3 weeks including shipping from and to Europe. I’m happy.