Unable to log in with App Lounge

Hello,

I am using a Samsung S20 with /e/os 3.0-a15-20250612-UNOFFICIAL-r8q and App Lounge 2.13.8.

For the past few days, I have been unable to log in with App Lounge — neither anonymously nor with my Google account.
I cleared the cache and deleted App Lounge’s data. I also waited 12 hours. Logging in is still impossible.

Thanks in advance for any ideas.

That is rather an old build, it contains this date 20250612 :slightly_smiling_face:

Your App Lounge version will almost certainly be “too old”.

This is the current build list. (Android 16 shows by default, tap on Android 15 to show.)

If your System Updater does not show available updates it would be worth clearing storage of System Updater in case this is the reason you have not received updates for so long.

Should a long list of updates appear just load latest, they are full ROM not incremental.

Thanks a lot.

You are right: System updates aren’t working. You mention a “system updater.” Are you referring to the “Dynamic System Updates” app?

Ah, it is Mises ä jour du systême aka Gestionnaire de mise ä jour aka org.lineageos.updater.

Ok, thanks.

So you mean that I should “Vider l’espace de stockage”/of this app “Gestionnaire de mises à jour”?

Hello @Arnaud35 you just need to go to Settings → System Updater.
In french : Paramètres → Mises à jour du système.
This is the first item when you open “parameters”


Then you have 3 dots on top right corner. It opens the menu with Local update (Mise à jour locale), then just select the file you downloaded and it will update. That’s all !

Ah, @AurelienS you probably do not recogise that e-3.0 was a withdrawn build.

It might be a good idea to find out whether the regular way works. If not I will leave it to you.

Yes.

However you saw what I missed that this is an unofficial build.

Merci Aurélien

However that setting doesn’t work!

You will always have this message “la vérification de nouvelles mises à jour à échoué” on unofficial builds, because the updates are not pushed on a server. This is why you need to do it manually.

First download a more recent build for your device, from the link provided above by @aibd then use the 3 dots and select “local update”, and choose the downloaded .zip file on your phone : it should read the zip and update the system.

And if you download from the link above, your /e/OS will be a COMMUNITY build, so you should get the next updates

1 Like

Thanks a lot @AurelienS ! Thats clearer for me.

Two questions from a beginner like me:

  1. Where can I find which build is OK for my device (Samsung S20) ?
  2. Should I prefer Android 15 or Android 16?

Thanks

According to this post, I see that this device S20 seem to have 2 different hardware versions : r8s and r8q

You are currently using the e-3.0-a15-20250612-UNOFFICIAL-r8q, so just make sure you download a r8q build (not for another device), but the link provided bu @aibd is the right one for your device, so no problem.

e-3.7 is pretty new : they are currently collecting feedback about it and it seems there is some compatibility problems with some devices. You can read to make sure if someone else has tested e-3.7 on Galaxy S20 and there is no problem. Otherwise you can just download the e-3.6.

About Android version I don’t know if there was a major update between A15 and A16 (in data format for instance) that could break your device. I don’t think so but I’m not an expert so I prefer not to recommend you something potentially harmfull for your device.

What I would do if it was my phone :

Then, you will be able to get the updates directly in update manager, so it will make it easier for the next updates

1 Like

Merci beaucoup, @AurelienS !
Everything is much clearer now.
I’ll follow your advice and stay on A15.
I’ll perform the recommended backups and plan this migration in a few weeks.

Hello

Before this topic will close…

I have downloaded 3.7 because 3.6 seems no more available : https://images.ecloud.global/community/r8q/e-3.7.1-a15-20260416609262-community-r8q.zip

And I will try the OS update ad soon as possible…

Today I have tried to import the local zip.

But I get the error message : “impossible d’importer la mise à jour locale” (impossible to import local update) :frowning:

The Local update method maybe cannot manage the change of Unofficial → Community. The method is “fail safe” but does not usually give a reason for fail.

You could attempt a different build

with latest a15.

Thanks @aibd

But failed with latest a15, first a16 and latest a16 :slightly_frowning_face:

Any idea ?

I think you will have to go to Install /e/OS on a Samsung Galaxy S20 FE (Snapdragon) - “r8q”.

Starting from the heading

Installing a custom recovery using Odin

What you will aim to do is to replace the e-Recovery; then be sure to use the matching main ROM.

Please decide if you want to change two things at once.

  1. Unofficial → Community
  2. a15 → a16

You want to be sure of your backup but you will aim to do the install but omit Format data.

If you make two changes you may be forced to Format data. Even if you do the job in two steps you might have to format data at the second step. :slight_smile:

Overall I think you have better than 50% chance to avoid data loss.

Thanks a lot @aibd

You are right: I have to come back into the community version.

Hum, installing e/os from scratch seems too complicated for me. I will consider the option of buying an other telephone, with e/os community version, and reinit this one (Samsung S20) with Google Android. And sell it.

It was my first experience with e/os,m and I am really convinced!

Thanks all

I understand the page is intimidating. Do you have the PC which did the original install?

This time it is really only 2 jobs, the Recovery then adb sideload the main ROM.

No, I haven’t the PC!

1 Like