No update on G290 since februari

/e/OS Devices Gigaset
,
1

I’m using /e/ on a GS290. It is running version 1.10-20230406280390 and I never get an update proposed though I think I’ve read a GS290 user had received an update in october.
I’ve had this phone since februari 2021 and didn’t have issues updating the system after I got a notification that an update was available. But since february I got no update notification.
When I manually trigger a check for a newer version I get the message “You are running the lastest version”… What’s going on?

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

2

Hi @rbauduin the GS290 has been upgraded to Android 12 /e/OS S. We support only one OS version per device.

image
image1342×1055 229 KB

2 Likes
3

Are you running dev or stable? Here’s how to check … [HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc.
(Your info suggests dev according to the download pages, but please make sure for clarity.)

If dev, upgrades to new major Android versions would have to be done by you manually …

https://doc.e.foundation/devices/GS290

If stable, an upgrade should be on offer via the updater to get from Android 10 to Android 11, and the question would be why it isn’t …

… and the upgrade from Android 11 to Android 12 would be under testing …

4

Thanks @AnotherElk and @Manoj .
I’m indeed running a dev build. I’d rather switch to a stable build to have all future OTA updates proposed automatically.
However I have an error raised with the easy-installer installed as a snap on Ubuntu 22.04:

$ easy-installer 
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
X Error:  BadAlloc
  Request Major code 149 ()
  Request Minor code 2
  Error Serial #39
  Current Serial #40

Any idea what that might be?

5

You do not say at what stage you see this but I guess your locale is different from en_US.UTF-8 … changing locale probably requires root.

You might check these links and see what workaround might fit your situation.

Part of your error also fits with a bug seen in Snap [1]

[1] Cannot get the easy installer to work on Ubuntu latest version - #9 by nige

6

For clarity’s sake: On dev you get the usual regular updates via the updater while staying on the same major Android version … until the update support moves on to the next major Android version, which happened on your device (twice since the /e/OS version you are running). As @Manoj pointed out already …

On stable, the developers may additionally prepare upgrades via the updater (“OTA” - over the air) from one major Android version to the next for select devices and select Android version jumps (it’s complicated and takes considerable effort), so this possibility is what you would gain with stable. But there’s no guarantee your device will get any further Android version upgrades offered by the updater after the ones already there or in testing currently.
You can follow proceedings here … https://community.e.foundation/tag/development-updates … section “OS OTA upgrades” in the posts respectively.

7

I’ve looked further and I have an AMD CPU which seems to be an usual culprit with snaps as linked by @aibd. Seems the snap published uses the snap Core18, and an advice somewhere was to go to Core20. So to avoid this it seems the easy-installer snap would need to be updated.

I finally built it from source, but I also encountered an error already reported on the forum. Maybe the instruction on https://doc.e.foundation/easy-installer-contribute#how-to-build should be updated to use the command JAVA_HOME=buildSrc/linux/jdk-11.0.2 ./gradlew dist.

With the right command, it was trivial to build. But I still hope this appimage merge request [1] can be merged soon :slight_smile:

Now, going to look for a way to backup my phone to restore it after the upgrade, as using easy-installer erases everything.

[1] https://gitlab.e.foundation/e/devices/easy-installer/-/merge_requests/217