Good luck …
This new build has Voip calls working? Since the last one has this issue. Or nothing solved?
1 Like
I don’t think so. I don’t own a Samsung device. But as far as I know, there is no VOIP
1 Like
Unfortunately, I couldn’t get your image to work on my Redmi 4X (santoni).
First boot is looping on :
Summary
--------- beginning of main
06-20 07:31:06.947 2192 2192 D vndksupport: Loading /vendor/lib64/hw/hwcomposer.msm8937.so from current namespace instead of sphal namespace.
06-20 07:31:06.949 2192 2192 E HAL : load: module=/vendor/lib64/hw/hwcomposer.msm8937.so
06-20 07:31:06.949 2192 2192 E HAL : dlopen failed: library “vendor.display.config@1.0.so” not found
06-20 07:31:06.949 2192 2192 I ComposerHal: falling back to gralloc module
06-20 07:31:06.949 2192 2192 D vndksupport: Loading /vendor/lib64/hw/gralloc.msm8937.so from current namespace instead of sphal namespace.
06-20 07:31:06.950 2192 2192 E ComposerHal: failed to open framebuffer device: Invalid argument
06-20 07:31:06.950 2192 2192 E android.hardware.graphics.composer@2.1-service: Could not get passthrough implementation for android.hardware.graphics.composer@2.1::IComposer/default.
06-20 07:31:07.793 1476 1476 W : Waiting for SurfaceFlinger, waited for 189237 ms
06-20 07:31:08.795 1476 1476 W : Waiting for SurfaceFlinger, waited for 190239 ms
06-20 07:31:09.796 1476 1476 W : Waiting for SurfaceFlinger, waited for 191240 ms
06-20 07:31:10.798 1476 1476 W : Waiting for SurfaceFlinger, waited for 192242 ms
06-20 07:31:11.560 686 686 I chatty : uid=1000(system) /system/bin/surfaceflinger expire 11 lines
06-20 07:31:11.800 1476 1476 W : Waiting for SurfaceFlinger, waited for 193244 ms
06-20 07:31:11.948 2201 2201 D vndksupport: Loading /vendor/lib64/hw/android.hardware.graphics.composer@2.1-impl.so from current namespace instead of sphal namespace.
06-20 07:31:11.952 2201 2201 D vndksupport: Loading /vendor/lib64/hw/hwcomposer.msm8937.so from current namespace instead of sphal namespace.
06-20 07:31:11.954 2201 2201 E HAL : load: module=/vendor/lib64/hw/hwcomposer.msm8937.so
06-20 07:31:11.954 2201 2201 E HAL : dlopen failed: library “vendor.display.config@1.0.so” not found
06-20 07:31:11.954 2201 2201 I ComposerHal: falling back to gralloc module
06-20 07:31:11.955 2201 2201 D vndksupport: Loading /vendor/lib64/hw/gralloc.msm8937.so from current namespace instead of sphal namespace.
06-20 07:31:11.956 2201 2201 E ComposerHal: failed to open framebuffer device: Invalid argument
06-20 07:31:11.956 2201 2201 E android.hardware.graphics.composer@2.1-service: Could not get passthrough implementation for android.hardware.graphics.composer@2.1::IComposer/default.
06-20 07:31:12.801 1476 1476 W : Waiting for SurfaceFlinger, waited for 194246 ms
06-20 07:31:13.803 1476 1476 W : Waiting for SurfaceFlinger, waited for 195247 ms
06-20 07:31:14.805 1476 1476 W : Waiting for SurfaceFlinger, waited for 196249 ms
06-20 07:31:15.807 1476 1476 W : Waiting for SurfaceFlinger, waited for 197251 ms
06-20 07:31:16.808 1476 1476 W : Waiting for SurfaceFlinger, waited for 198253 ms
06-20 07:31:16.953 2210 2210 D vndksupport: Loading /vendor/lib64/hw/android.hardware.graphics.composer@2.1-impl.so from current namespace instead of sphal namespace.
Thanks anyway, I’ll attempt again later !
It looks you don’t have the right vendor sources. From which Android are you coming ?
This one : [UNOFFICIAL BUILD] Xiaomi Redmi 4(X) (santoni)
Produced by /e/ “community” Docker, untouched, was working fine 
Btw latest Xiaomi firmware for my testing device was for Android 7.1 … https://xiaomifirmwareupdater.com/firmware/santoni/
Don’t know if it’s related, but I wouldn’t be surprised it would …
As I have written, there are xiaomi device where a downgrade isn’t working. I see only one two things you can do:
- try GSI
or - wait til eOS is on Android 10, but that will need some month
1 Like
Thanks for your advices, I’ll wait for Q as it is just for testing 
But who said anything about Samsung? I own a Moto G6 Play.
So no VOIP means the gsi rom is still unusable, right? Sad.
You built the rom and didn’t test it yourself? That’s incredibly weird.
Alot of people are building roms for none owned devices. I have build for around 20 different devices which I don’t own. So that’s absolute not weird.
It’s always written that the rom is untested and everyone can decide to try.
Because I answer hunderds of questions here, I can remember/known always know which device the user owns. So pls. be patient, when I have talked about a different device.
This GSI is running on my daily driver, So it’s tested as much as I can do.
I never have used VOIP because it makes no sense for my. I ony can say, calling via Telegram or Whatsapp is working fine.
I have learned, that VOIP needs special drivers which are NOT open spources and not available in most custom roms, especially for for Samsung devices. That’s why I have written my comment.
And once more: Pls be patient. we are all users which are doing best to get the best for other users. If you don’t like something do it better for your own and share it for the others !!!
6 Likes
I also spend time building ROMs for devices I don’t own to offer users a chance to test /e/ on their own device, and I find your message offensive.
@harvey186 provided a ROM for testing purpose, what’s incredibly weird is to complain instead of helping and sharing !
5 Likes
Pl note some of the users on the forum are putting in a lot of time and effort to build ROM’s for other users. Most of the time they do not have the specific devices.
To mock such efforts is not acceptable. If you do not trust such builds - Do not use them.
There are a large number of users who do test out these builds and share their feedback. We value this feedback and based on this feedback decide which builds to add to the official list.
I would like to personally thank all those who have put in their valuable time and made such builds.
6 Likes
Im’ deeply agree.
I come back to you harvey because i remeber that you suggested thois topic to me to try eos on my xiaomi red note 8.
I took some informations about custom roms available around this device and it seems that much kind of firmware or driver are not available, producing some bugs with camera and bluetooth.
I would like to help and have more skills to try your GSI properly
-
Is there a vm to girstly have a look or test this img with virtual configurations ? (For fun and test ahah)
-
How do you build it ? Where do you find informations to create the right vendors ?
-
How do you analyse a device to know what to install on it ?
Thank you for all you work !
1 Like
No way to use it on any VM
The GSI is ONLY system image. vendor will not overwritten
Use treble info or treble checker app
1 Like
@andrelam
Flashing GSI on FP3, is there any difference to the procedure I have written?
I’m asking for a german user which want install a GSI. And because the normal rom flashing is different, I think it’s better to inform me/him before trying.
? Never tried to install gsi on fp3.
OH, my bad, I thought you have build one for your FP3.
I did but never flashed it. When FP3 for /e/ came out i assumed it was GSI, but i was wrong
I’ am preparing to follow these instructions again when my new XZ1C arrives. I just want to clarify the follwoing step:
In my TWRP, the option to format the data partition is under the ‘Wipe’ menu. To Wipe the date partition, you would need to choose ‘Advanced wipe’ (also under the ‘Wipe’ menu.)
What I think the instructions mean is
-
Reboot in recovery
-
Select ‘Wipe’
-
Select ‘Format Data’ and on the following screen type ‘yes’ to confirm. (Do not use ‘Advanced Wipe’ to wipe the data partition. This is important)
Have I understood correctly?
Thanks
(And when you’re experimenting with recovery, make sure you have an up-to-date backup of your data partition, in case you manage to perform the wipe by accident or stupidity 
)
Yes, that’s absolute right
2 Likes