I am seeking help/advice with an echo issue on a recent install of /e/OS onto a new Pixel 7 using Web Installer.
So far everything’s working great except there is a pronounced echo on the other end of my calls. Using the e/OS Dialer and an AT&T SIM (not using VOIP or WiFi calling). It behaves much the same as other echo issues discussed here including the VOIP echos I had on my first /e/OS Samsung S7…
I hear no echo on the Pixel but the person on the other end hears a distinct word for word repeat of what they say, with about a 1-sec delay. No echo issues using speaker phone mode or Bluetooth device.<
What I’ve tried so far with no chnage…
multiple troubleshooting calls with AT&T to rule out possible problems with weak signals, tower switching, WiFi calling, 4G-5G switching. They concluded it is a “problem with the phone”.
tested with other Dialers installed from App Lounge
updated to latest eOS 3.1.1 official build (Android 13)
tested with and without the phone in the case
adjusted Call Volume
Some other observations…
When trying to turn off 5G to stop it toggling to 4G, the Network & internet > SIMs Settings page did not offer me a “Preferred Network Type” option.
When trying to turnoff off 5G with custom dialer code (##4636##) via the Phone app there was no LTE option - all choices began with “NR”.
When booting, the yellow warning “your device is loading a different operating system” comes up first, followed by a Google splash screen, and then the Murena splash screen
I installed /e/OS on it straight out the box. Seller represented it as new. It looked new but there is some possibility it was a return with an old account on it.
@TKR If you installed with the web installer then you should have gotten the official build with which is possible to lock the bootloader, looks like you didn’t do that step properly with the installer.If you would to it now, after locking the bootloader the yellow message would be gone. A locked lootloader helps you mostly have good compatibility with banking apps or similar ones. If you lock the bootloader all your data will be gone. You need a backup of it.
No idea if it will help with your problem. Since you will lose all data you can also think about going a15 with community build.
As a sidenote, I lost faith in that one. My first try went ok, but not sure anymore if it worked literally from beginng to end. I feel like the old installer was less buggy…
Losing data or reinstalling the apps I’m testing are not a concern at this stage so I will try Community build.
Given the state the phone is in now (Official build, bootloader already unlocked, echo issue), is there anything I should do before stepping through the Command Line install procedure?
You can just use the Pixel repair tool but be cautious not to update to Android 16 as it has a no rollback feature. The instruction is correct you need to be at A15 on the Pixel 7.
I then started manual install of Community for Pixel 7 and came to impass at Flashing Additional Partitions when the fastboot flash boot command could not find .img files.
Command Prompt Log: C:\Users\admin>adb devices List of devices attached 28131FDH2004L5 device
What I like to do in either Linux or Windows is go to the downloaded *.img file and right click and hit rename, then copy the file name, now click in the white space to not rename the file, then paste the first part of the file name in a text editor. Do the same to the command on the instruction page and paste into the same text editor.
Now paste the file name in front of .img and you have the full command, use cursor to check there are no unwanted spaces or tabs. This way you have a clean command to paste in the terminal windows.
I actually prepare my command lines in advance in the text editor, all of them.
