Motorola Harpia XT1607 Issue

/e/OS Devices Motorola
,
1

Hi,

+++ I’ve been using /e/ on my Motorola Harpia XT1607 for about eight months now, and it was working very well until I updated to the ‘Q’ release. I sideloaded the update through adb by the directions on “https://doc.e.foundation/devices/harpia/upgrade”, and I think I followed them correctly. I was able to boot into the upgraded OS with no issues, though after attempting to install an update through the /e/ os settings menu, the phone began to boot loop.

+++ I think that this might have happened because the system updater pushed a cached update, and I inadvertently downgraded. I reinstalled the package that I had originally sideloaded to update to ‘Q’, and although my phone works now, which is good, the cellular internet connection does not. I can make phone calls and send text messages, but cannot access the world wide web through my cellular network.

+++ I have confirmed that the SIM card and network provider is probably not the issue, because I am able to access the internet through this SIM in another device. I am not entirely certain how to fix this. I thought it might have been something related to my modem firmware, but I think that /e/ contains packages for that which it installs when sideloaded. Any ideas?

Kory Mac
(the ‘+’ characters are for indentation = ). )

2

On sideload install/bin/extract_firmware.sh extracts 24 already present modem.*.gz files from /firmware/image/ into /system/vendor/firmware/. Are you on 0.16-q-…-dev-harpia? can you paste the output of

md5sum /system/vendor/firmware/modem.*

If this comes out correct and nothing is missing, I wonder if somehow the IMEI of the sim slots got overwritten, these reside in the modemst1 and modemst2 partitions. Can you check “About Phone” for the two slots IMEI, and if present, if there is any change in behaviour if you switch slots.

3

I’ve only got one sim slot in this phone, but there’s an IMEI listed for two sim slots, and it’s the same number. I will check to see if this is the same IMEI that is listed when I view it from the bootloader. Thank you for your response.

4

Would I be able to fix anything by flashing a stock rom, and then reinstalling /e/?

5

ok, I learned the XT1607 just hasnt’t the second SIM slot populated on the board. I scrambled to find a SIM card frame for the tiny one I have that fits the XT1602, will test tomorrow if I find any issue with mobile data. It’s not my primary device, so I didn’t insert a SIM yet and test with 0.15/0.16, but planned to anyway.

Did you see “Moto G4 Play: no cellular data after upgrade to 17.1” (LineageOS/android#2099)? will read this throughly tomorrow, but skimming it, the problem you describe seems widespread.

6

My own tests were successful, so no fundamental issue. After reading the threads I think there are two categories of problems:

  1. no SIM card detection at all, what is hinting at failed firmware extraction, a known bug. This is fixed since feb/mar '21, one needs to flash a current recovery first before reflashing for the firmware to be properly extracted (los#3129). Not sure if you are affected by this, I think it is unlikely. There can be a deeper error if the /firmware partition is incomplete, by the wrong device or corrupted. But I speculate you would have no mobile service at all then. We can debug this together though.

  2. wrong APN settings. There are a lot of duplicate issues to the extent “no mobile data” and adding/changing apn settings seem to fix issues. Can you disclose your operator? the file relevant is apns-conf.xml (los#2721, los#3343). You can compare and search with a part of your operators name with:

curl https://raw.githubusercontent.com/LineageOS/android_vendor_lineage/lineage-17.1/prebuilt/common/etc/apns-conf.xml -o apns-conf-17.1.xml
curl https://raw.githubusercontent.com/LineageOS/android_vendor_cm/cm-14.1/prebuilt/common/etc/apns-conf.xml -o apns-conf-14.1.xml
diff apns-conf-14.1.xml apns-conf-17.1.xml | grep -i operator

similar procedure between the /e/ nougat or q/pie/oreo branch histories of the file. Download the raw xml and run a diff, looking for your operator. A fix then is to update to a build that includes the proper settings or editing them yourself as root.

7

I would be curious to know your mobile provider to do the comparison myself and see if there is merit to the APN idea.

8

My mobile provider is named ‘PureTalk USA’, and I have tried using some APN settings that they emailed to me, but this did not work. Here are those settings:

"
Settings> Network & Connectivity>Mobile (cellular) Networks>Access Point Names> Select the 3 Vertical dots in the top right and reset to default>Select Add on the top right and enter the information below

( INFORMATION IS CASE SENSITIVE)

Name: PTUSA
click ok

APN (Access Point Name): RESELLER
click ok

MMSC: http://mmsc.mobile.att.net
click ok

MMS Proxy : proxy.mobile.att.net
click ok

MMS port: 80
click ok

Verify that it says MCC: 310

Verify that it says MNC: 410

APN type: default,mms,supl​
click ok

On the upper right hand side, click on the three vertical dots and click Save
Choose PTUSA RESELLER

Power off/on the device
"

This was sent to me when I was trying to resolve the issue I ran into back in April. I began using a different phone, but I now need to replace the screen on that phone after getting it wet accidentally.

9

the APN entry for "Pure Talk USA" is unchanged between lineage 14.1 and 17, but differs to the information they emailed you.

<apn carrier="Pure Talk USA"
     mcc="310"
     mnc="410"
     apn="att.mvno" 
     proxy=""
     port=""
     mmsc="http://mmsc.cingular.com"
     mmsproxy="proxy.mvno.telrite.com"
     mmsport="80"
     type="default,mms,supl" />

In the gitlab (los#2099) issue it says it helps to have the correspnding recovery (not twrp) present on the recovery partition and sideload from there. Did you try this yet?

As initially asked, I’d really like to know the md5 hashes of those modem files to outrule a difference.

(I myself always flashed to 17.1 lineage or /e/-Q from the last official 7.1.1 Android stockrom each and never experienced mobile data issues on 5 different harpias. This being said, they were XT1602 and Vodafone/Telefonica carriers in EU/Germany).