perhaps because some devices have physical buttons ?
No, it literally won’t call ‘recent applications’ without this code, regardless of whether the devices have physical keys or not.
Great news! the next release will be a Release Candidate as I’ve resolved this last issue!
I’ve been able to confirm the following:
- the addition of Superuser
- Fixed recent apps
3 Likes
Does it still make sense to download the 3.08 GB system.img in view of the upcoming Release Candidate?
1 Like
On a Samsung J6(j6lte) I have/had this running:
IMG-e-1.14-q-20230816320942-dev-treble_arm64_avN.zip (~1.1GB)
I still need to get the device, but I was wondering about the 3GB, too.
Thus I have waited to download so far
1 Like
I’ll make a new topic without clutter for the Release Candidate of the GSI, since bring-up is done.
This thread was mostly for others interested to learn how to bring up a GSI
The old System.img has a broken recent view for applications, it is incomplete and was only posted for debug purposes. Wait until the new System.img is released.
I will see about doing OTA updates, I can do it but I don’t want to pay for hosting for it lol
Don’t download it, an actual release candidate with everything fixed is coming in under 10 hours
1 Like
I knew I posted about it, because there were some issues:
Your Samsung J6(j6lte) with architecture arm64_a** (A-only) is not compatible with the @Null A/B build arm64_ab
I totally understand that, but I’m sure I can help in that regard as well so we can find a hosting solution if OTA update should work.
Yeah, was wondering about that, as I don’t have the device at my hands and it’s been a long while. I also have this in my J6 project folder:
lineage-20.0-20230814-UNOFFICIAL-gsi_arm64_vN.img.xz
Nothing about A/B there… maybe need the device back first
1 Like
gsi_Arm64_vN was coined by Andy, the ARM64 in it means this:
arm: ARM 32-bit (deprecated)
a64: ARM 32-bit with 64-bit binder
arm64: ARM 64-bit
Ah, I have patched in Root by default in the Release Candidate build, but I may remove it at a later date depending on how people feel about it.
What do you folks think, do you want this to be installed rooted or prefer to leave it stock?
OT, but ofcourse I got two reasons to get the device:
And @piero may point me to:
https://wiki.postmarketos.org/wiki/Samsung_Galaxy_J6_2018_(samsung-j6lte)
my GSI should work on your phone lol
I believe you may just need the 64bit vendor files… I’m not positive but if Lineage21 GSI works for you, so will my GSI
How about:
Galaxy A3 2017 SM-A320F-FL-Y (a3y17lte)
&
Galaxy A3 2016 Exynos (a3xelte)
In general, I got lots of older Samsung, up to ~2019. Anything should get out?
Is there a list on all GIS/Treble devices, somewhere?
As a rule of thumb they need 64 bit vendor files and to test if it works try Andy’s Lineage21 GSI
I don’t have a Samsung J6. You have me confused with @make-nz
I also have a working a64_bvN device with @AndyYanGSI lineage-20.0-20241118-UNOFFICIAL-a64_bvN-vndklite. I couldn’t get LOS 21.0 GSI to boot, so it would probably only work with a corresponding /e/OS-T GSI.
Yes,
a very old and a bit unclear one here :
.
.
have a read there :
The 6 ways to build pmos for samsung-espresso10 and flash it to the device (tested by Piero-e)
and there :
How to “dualboot” androidOS / postmarketOS (Piero-e 's contribution)
build pmos for running system from the SDcard is my recommandation in this case.