A new up-to-date Q-build for the Samsung S5neo.
Tested on my own device and running smoothly.
1 Like
t I found this site helpful when deciding to buy the Samsung Galaxy S5 Neo to try /e/. I have the SM-G903W model, to be specific.
https://www.frequencycheck.com/
For example, here is the reports on the compatibility of the SM-G903W on AT&T: https://www.frequencycheck.com/carrier-compatibility/yjNqFN/samsung-sm-g903w-galaxy-s5-neo-lte-a-samsung-pacific/at-t-united-states
I looked at the lists of devices compatible with /e/ (including the Unofficial build list) and then would look various devices up on FrequencyCheck and look on eBay for prices.
I am not an expert on this subject, and I’m not sure if FrequencyCheck is the most up-to-date and/or reliable source, but it has been accurate and helpful for me insofar as my SM-G903W is working so far on AT&T in the USA.
1 Like
Thank you for continuing to update these builds! It is running well on my SM-G903W.
I have a newbie question: when I want to upgrade, e.g., from e-0.12q-20201102 to e-0.13-1-20201127, do I have to wipe everything again using TWRP to prepare for the sideload, or is there a way to perform the sideload but also preserve my settings, data, installed apps, etc.?
(I understand that the Unofficial builds do not have OTA update capabilities.)
That’s right, no OTAavailable.
1 Like
You can dirty flash this build. Boot into TWRP.
click on “Wipe” then “Advanced Wipe”
Select the following items to delete : * Dalvik / ART Cache and System* Not Data and
Internal Storage.
In the TWRP main menu, click on “Install”.
Select the .zip file
slide the “Swipe to confirm Flash” arrow from left to right
Click on “Wipe cache/dalvik” at the bottom left, confirm if necessary.
Click on “Reboot System”.
Ready
1 Like
I’ve told about /e/ OS to my friend who has Samsung Galaxy S5 Neo SM-G903F, will this build for for that model? If it will, I’ve promised to flash /e/ for my friend.
Yes, this Build is supported
1 Like
Thanks! Finally got that phone to my hands today, flashed and phone is going back today. Hope this experience will effect the way that my friend wants other phones in the house also run /e/ OS 
1 Like
Fine, my Samsung Galaxy S5 Neo SM-G903F is on /e/ now. Many thanks!
What am i missing is a radio app. the S5 neo does have an integrated radio.
Would be nice to hear radio without internet. Are you using the integrated radio?
A new update on eOS-Q for the s5neolte with security string 2021-01-05
Hello,
I installed/upgraded today to the 20210118 & 20210129 Roms. Now I get a strange message at start/login as well as with non-encrypted and with encrypted device (but then twice) when to key in the PIN:
Android System
There’s an internal problem with your
device. Contact your manufacturer
for details.
Otherwise, on first glance everything until now seems to be OK.
Kind regards
Reiner Schmidt
I had the same message on my device and I really don’t know where this comes from. Apart from that, it’s running smoothly.
1 Like
It comes shortly before entering the PiN on encrypted devices to start at all and again after the system is booted and the PIN is asked again. On non-encypted/before encrypted ones its after the system booted and the Pin is asked for. This happens with/since the 20210118 version, not before.
I made a totally new unofficial r-build (lineage-18.1) for the s5neolte.
I tested it and its running fine…
Enjoy
I just installed the new release on my encrypted S5 via TWRP.
The problem when to enter the key for encryption is gone.
But since then just the jumping “e” logo stays obviously forever.
I will give it another hour to see if it comes back.
I now wiped the S5 completely and reinstalled it. No problems yet.
Now trying to encrypt again.
regards
Reiner Schmidt
Hmm, the dialog on startup for the encryption key stays in english, and I also found that Configuration of the home key for longer pressures as well as for the Task-key donot work.
It can be partially overcome by activating the “Navigation-Line” but doesn’t work good (or I am not used to it)
Also, some Apps (i.e. Googles Keep Notes, Clever Tanken) complain about missing Google Play Services (?) now where before they had no problems.
Could it be that this version of MicroG has some problems?
Kind regards
Reiner Schmidt
Also I have encountered that some Music-Titles cannot be transferred again (via mtp, adb push or ssh) onto the phone.
Looks like some issues with character set as at least some of those have unusual characters within their names (i.E. “?”). Before that this was not a problem and also on my other handy (S7, unofficial q from 18.05 from katharine.chui) the same files have no problems at all.
Example from Patti Smith/Horses:
“Land: Horses , Land of a Thousand Dances , La Mer (De) - 1 - 07.ogg”
or Phil Collins/But seriously:
“Do You Remember? - 1 - 03.ogg”
On mtp the device is then blocked (libmtp-error: Could not send object) from the PC (Linux) after that and needs to be reconnected/remounted.
Kind regards
Reiner Schmidt
with Q flavour…
this, is R test !
1 Like