Feedback for v1.7

/e/OS Smartphone Operating System Build Feedback
85

Thank you for point me there. If I understand, it seems we have to wait 1.8 release for PicoTTS (instead a restoration of eSpeak).

86

I had the stable version update for S9+ on January 24th. And everything is ok :+1:

87

At least there are related merge requests for 1.8. We will have to wait and see if it’s not moved to 1.9 or… Move back to PicoTTS (#5728) · Issues · e / Backlog · GitLab

88
  • Vendor Name: Fairphone
  • Device name: FP3
  • Device CodeName: ?
  • Version of /e/OS or Stock which existed previously: 1.6-r-stable
  • Is the device Rooted / Not rooted: Not rooted

I manually updated to 1.6 last week as OTA update was unavailable from 1.4. Update to 1.7 appeared in the updater this evening after tapping “refresh” about 5 times.
I updated from 1.5 to 1.6 last week by doing a fresh install via adb and bootloader, not sideloading. Today’s update to 1.7 was OTA.

I’ve encountered a few minor issues since upgrading to 1.6 that continue into 1.7:

  • Camera tile in pull-down menu used to circumvent the lock screen and activate the camera with my phone locked. This is no longer the case. Now have to unlock my phone to take a photo, which defeats the point.
  • Main SIM card shows “unknown number” in Settings > About Phone (FP3) but connects with inactive airplane mode without a problem.
  • Prompt to select default file browser app not popping up. Native Files app automatically opens when (e.g.) choosing a password vault to open in KeePassDX, but installing a second file browser app doesn’t make it ask me which app I want to use. Second file browser app may lack permissions granted to native app, such as viewing the /Android/data/ folder.
  • Night Light (in Settings > Display) does not change automatically at sunrise/sunset. Setting a schedule for it is the same as leaving it constantly on or off.

It’s completely possible I missed something when manually updating last week – e.g. I didn’t reinstall the stock Fairphone ROM before installing 1.7…

Otherwise I’ve noticed no major issues; working well so far. I have yet to try out the Bluetooth, make or receive phone calls or SMSs; the audio jack seems to be working OK too (known issue with FP3 in previous versions).
Like others have said, I would appreciate newer security updates than October.

89

It arrived yesterday on my FP4, in France

90

i know i have too :wink:

91

I’ve a FP4 and the OTA shows up this morning. Just to be sure before doing the update : should I make a backup of my data (pictures and texts messages) ?

92

Vendor Name: Samsung
Device name: Samsung S7 SM-G930F
Device CodeName: herolte
Version of /e/OS or Stock which existed previously: 1.6
Version installed now : 1.7-q-20230110250405-stable-herolte
Is the device Rooted / Not rooted: Not rooted

  • Echo in normal calls, worse in loud speaker.
  • Some app (Izly) disappeared since 1.4
  • BUG in alarm display. When I set the alarm it says : “next alarm scheduled in and .”. It misses the number of hour and min.
93

94

For Teracube users, anyone notice the UX seems to be getting better with each update?
The device is quite laggy so I always toggle on the Disable HW Overlays in Developer Options.
In the past two or three updates it’s been better. With 1.7 its feeling much smoother. No need for the setting just yet.

95

My phone is a Motorola 5G Ace, model xt2113-2, codename Kiev.

Briar, a secure, P2P messaging app is detecting a screen overlay as I use the program. I have gone through the apps, even system apps and have turned off overlay permissions for just about everything except, of course, the system interface which cannot be touched. I can’t determine what’s doing the screen overlay.

This only began happening after the latest update. I fear that I may have to regress to the earlier build to resolve this issue which means using Motorola software to put the standard OS back on the phone, then reinstalling the earlier build and restoring my phone apps and data - a long and not always successful process.

96

Interesting, as a similar issue was mentioned earlier in this thread whereas previous build had no such problem. :thinking:

97

Motorola G7+
Revvlry+

After upgrade to 1.7, Bliss crashes every few seconds.

I’ve installed a different launcher so i can use the phone.

Screenshot_20230126-094522_Updater
Screenshot_20230126-094522_Updater1080×2270 75.3 KB

98

Yeah, I saw that. I am curious about what changed to cause that. I’m also interested in the fix as I have no desire to revert and rebuild.

99

Oups.

Here it is : 1.7-q-20230110250405-stable-herolte

1 Like
100

Smooth OTA upgrade from 1.6-s to 1.7-s on FP4 - many thanks to all developers.

101

OnePlus Nord “avicii”
Android 11
/e/ OS version 1.7-20230110250404

When visiting websites which want to use the camera and microphone (e.g. jitsi meet) I allow the permission but then a message appears which says “This site can’t ask for your permission. Close any bubbles or overlays from other apps then try again.” It gives the option to try again or cancel. Selecting either option sends me back to the request and rounds in circles we go.

102

It just started working on the supplied browser. I don’t know what changed. Brave browser still not working.

103

herolte and SM-G930F is S7 rather than S8

1 Like
104

Samsung S7 SM-G930F
purchased in /e/-shop
not rooted
just updated from 1.6-q-20221129238948-stable-herolte
to
1.7-q-20230110250405-stable-herolte

works fine from what I can tell so far, haven’t tested everything yet :slight_smile:

Thank You!