Yeah, it is all the more gratifying because the Samsung Galaxy A3 2017 SM-A320FL is not officially a ‘Treble Project’ device. Just because bright minds have found a way to adjust the partition structure, GSI ROMs work now. That’s great. Thanks again for your work. I will mention it at every appropriate place.
A mistake on my part. Try makes smart. With help of @harvey186 I had to find out, that the Treble Compatibility Checking App ‘Treble Check’ gives wrong information. The A3 2017 SM-A320FL is an A/B Device and works with arm64_bvS images.
@harvey186, I need your advice and your know-how, please - having had some delicate moments with LeOS ‘R’ today. My Xiaomi MI A2 works (now again) with LOS 17.1 + LineageOS Recovery. But my curiosity is bigger than the fear for a device brick.
I want to install your eOS-Q-Full-_arm64_bvS-20201017 exclusively by fastboot. Do I have to delete any partitions before - and if so, which ones?
This is my second test with now ‘treblezied’ Galaxy S7 SM-G930F ‘herolte’.@harvey186’s build eOS-Q-Full-_arm64_avS-20201017 booted up with the first start, queried the SIM pin and wirelessly connected to Wi-Fi 802.11ac.
Figure 5 and 6: In Dark Mode the directory name on the microSD card is not recognized because of the font color.
The quirk “only restarting the phone after about 10 minutes” as known from the first test is also present here. What could be the reason for this?
Yes, that it is due to my hardware configuration is most likely. I know your GSI ROMs by now and know that they work very well on official ‘Treble Project ready’ devices. I will try to make the S7 ready in a different way ‘Treble Project ready’.
I still have problems with WLAN, today I installed your latest /e/ GSI version.
With the “old” version I also had problems with WLAN, after a few days it didn’t work anymore, even switching it off and on via the icon didn’t bring a solution. A reboot and the WLAN was working again.
Today, after the update, I noticed that the WLAN is supposedly not connected, I connected “manually” to the WLAN network again, but the display came up anyway, not connected, but it worked anyway.
After a restart I have to connect “manually” again, then I get the message that it is not connected, but the connection is still working.
This should be just for your information, I want to use as little WLAN as possible anyway, except when downloading large files and then turn it off again immediately.