Android 14 - /e/OS 2.7 GSI - Release- unofficial

I think it presently does not work in anonymous mode :frowning:

This may be a /e/OS error in 2.7 and not a problem with the GSI, I’ll need to investigate further.

Right now I’m already building Release Candidate 3, which will include broader support for MTK devices

1 Like

I hate to ask but could you test RC2 on:

rephone® (6/128 GB like Gigaset GS5 pro)?

I need to know if just adding the interfaces was enough, or if this device needs to inherit prop files from the device configuration

I’ve offered you my support from the beginning and that I’ll do what I can if you tell me what information you need. So there is no reason to hate any questions. Ask as often and as much as you need and I’ll do my best, as will you.

At the moment, I’m overnighted. It’s now 04:09 CET in EU-Europe. I’ll test the rephone later today. Now I need to sleep for a few hours. Good night!

4 Likes

Right now, Release Candidate 2 should have the device compatibility that Andy’s Lineage21 GSI does.

IE: It should work on everything.

If it does not, that’s not a problem because @ronnz98 has begun work on his own GSI; he will be able to pump builds out faster than I can and his GSI has configurations in it that mine does not.

From here on out, I will divert my energy toward helping him with the GSI he is making in hopes that something really special will be able to be produced.

4 Likes

The GSI I’m developing is not the same as a port because it is source-build specifically to be a GSI

Test N°13

rephone® (6/128 GB like Gigaset GS5 pro)
SoC: MediaTek Helio G85 - k69v1_64_k419
Stock Android 12 (A12) Kernel: 4.19.191
No custom recovery


Installation sequence

A. :white_check_mark: working ~ iode-5.8-20241214-arm64_ab_release.img by @iode.tech

B. :white_check_mark: working ~ 2.6.3-t-UNOFFICIAL-gsi_arm64 by @colors

C. :x: /e/ does not boot ~ eos-u-2.7-rc2-20250109-gsi_arm64_vN by @Null
System only starts up to the rephone-logo, but not into the e-system. No e-logo > Bootloop.

D. :white_check_mark: working ~ lineage-21.0-20241118-UNOFFICIAL-arm64_bvN.img by @AndyYan

2 Likes

@Xxpsilon Ok, Release Candidate 3 will contain instructions for MTK phones, thank you buddy!

ok here you go:

eos-u-2.7-20250110-gsi_arm64_vN.zip
https://share.freepro.com/63b94cf2-6a9e-4ef2-aa1f-c0769d112744

Thanks to the instructions and help from @Null I could build my first GSI.
Hopefully it does also work…

5 Likes

Downloading to test now, this build contains MTK information so it should boot on rephone but I am not sure if it was implemented correctly, this will probably take a bit of troubleshooting.

@Xxpsilon Buddy can you test this build on your device?

It is safe, it boots properly! Now we just need feedback from a MTK user!

1 Like

I test several devices within the next three hours :stuck_out_tongue_winking_eye:

Awesome!! Really have high hopes for this build!

I could now also upload to Sourceforge… I overlooked a leading blank previously :crazy_face:

eos_u_2.7_20250110_gsi_arm64_vN.zip

1 Like

eos_u_2.7_20250110_gsi_arm64_vN by @ronnz98


Test N° r1

rephone® (6/128 GB like Gigaset GS5 pro)
SoC: MediaTek Helio G85 - k69v1_64_k419
Stock Android 12 (A12) Kernel: 4.19.191
No custom recovery


:x: /e/ does not boot ~ eos_u_2.7_20250110_gsi_arm64_vN by @ronnz98
System only starts up to the rephone-logo, but not into the e-system. No e-logo > Bootloop.

:ballot_box_with_check: Cross-check :white_check_mark: works ~ lineage-21.0-20241118-UNOFFICIAL-arm64_bvN by @AndyYan






Test N° r2

Gigaset GX6 (5G rugged) GX6
SoC: MediaTek Dimensity 900 5G
Stock Android 13 (A13) Kernel: 4.19.191
No custom recovery, no LineaageOS; no /e/OS


:white_check_mark: works ~ eos_u_2.7_20250110_gsi_arm64_vN by @ronnz98
Successful restart starting with oranage Gigaset logo, then animated white e-logo with slogan my data MY data, then the device can be fully set up. WLAN/Wi-Fi can be used immediately. e-Browser runs smoothly; e App Lounge has the known problems in anonymous mode

Bravo! @ronnz98, great performance :clap: :clap: :clap:

2 Likes

I do not know much about GSIs yet, but is
gsi_arm64_vN (eos_u_2.7_20250110_gsi_arm64_vN)
diferent from
arm64_bvN
lineage-21.0-20241118-UNOFFICIAL-arm64_bvN ?

Both devices:
arm64 A/B, system-as-root, seamless updates, dynamic partitions

vS is not rooted where vN is

1 Like

@AndyYan Naming rules

v: Vanilla, i.e. no GAPPS
N: No Superuser
S: With PHH Superuser

Yes but the way the device files are presently set up, using vS results in a non-rooted ROM because I removed SU from it lol

eos_u_2.7_20250110_gsi_arm64_vN by @ronnz98


Test N° r3

Gigaset GS4 (GS4
SoC: Mediatek Helio P70 MT6771T
Stock Android 11 (A11) Kernel: 4.14.186
No custom recovery


Installation sequence

A. :white_check_mark: working ~ VoltageOS-microg-arm64-ab-3.6-20240827-UNOFFICIAL by @cawilliamson

B. :white_check_mark: working ~ iode-5.8-20241214-arm64_ab_release.img by @iode.tech

C. :x: /e/ does not boot ~ eos-u-2.7-20250110-gsi_arm64_vN.img by @roonz98

D. :white_check_mark: working ~ lineage-21.0-20241118-UNOFFICIAL-arm64_bvN by @AndyYan

E. :white_check_mark: working ~ 2.6.3-t-UNOFFICIAL-gsi_arm64 by @colors