Is there a special reason why you are using the branch e-0.9-p- with Android security patch level July, 5 2020 and not the branches e-0.10-p or e-o.11-p- with Android security patch level August or better September 2020?
Thanks to @argon3030 and @SuzieQ. This tablet is looking good for me with OpenLauncher.
By the way to anyone following the installation instructions. They do not work for me with TWRP 3.4 (the sideload fails, complaining about not being able to make a directory). TWRP 3.3 works fine, though.
Yes, the reason there hasn’t been a new build from me in a few months, is that the build fails if I set the version higher than 0.9. Not sure why it won’t build anything newer than 0.9 with the July 2020 security patches. I’ll try it again this weekend…
Good news Galaxy Tab S2 9.7 Wi-Fi people! Whatever was causing the builds to fail has apparently been fixed. I gave it another try today, and was able to build the latest e-0.14 for gts210vewifi with no problems. I have the image running on my tablet right now, it all looks good.
Without knowing, I suspect the reason is a lack of staff. Over a hundred devices are maintained by I don’t know how few developers. And monsieur @rhunault can’t duplicate either.
The Galaxy Tab S2 9.7 Wi-Fi (2016) ‘gts210vewifi’ is maintained and nurtured by the official LineageOS team via LOS 17.0. But an external oneman show is developing and maintaining even based on LOS 16.0 and simultaneously LOS 17.1 - even with 'D’aily OTA updates. So there is plenty of activity.
Whether the announcement of official /e/ OS ‘Q’ support from 9th week 2021 will become a reality, I guess we will have to wait with patience and besonnerheit.
Until then, I will switch from LineageOS back to argon3030’s unofficial /e/ OS ‘9-Pie’ ‘Q¹’, because degoogled /e/ OS ‘9-Pie’’ is my personal favourite. Thanks for building and sharing,@argon3030
¹Update
‘9-Pie’ instead of ‘Q’ [kuː],
Thank you for the correction, @argon3030. It doesn’t have to be AOSP Android 10. A well-maintained AOSP Android 9 pie is also a fantastic degoogled /e/ OS ‘P’ edition.
I had not seen that ‘Q’ upgrade schedule before, thanks for linking to that @SuzieQ . To be clear, the 0.14 build I just posted is still Pie, it is not Q. I’ll attempt a 0.14 ‘Q’ build, and if successful, I’ll post it.
Edit: The ‘Q’ build failed pretty quickly, so no ‘Q’ build yet.
Just installed it, stuck on /e/ logo then keep rebooting to recovery, don’t know why… any suggestions please? I did not format just tried to flash it on top of the official build.
New June 2021 build available for download. /e/ 0.18.
Note: After upgrading to this build, the web browser wasn’t working for me. I had to go into the browser settings and select a Secure DNS server from the drop-down list, and then everything worked.
@nottolino I’m simply building the sources as they are. If you believe you’ve found some bugs, I’d recommend reporting them to the dev team via Gitlab.
@zjabri I don’t believe flashing an unofficial build over top of an official build will work. Try formatting first, and then installing.
That’s a good question @nottolino I’m not sure what’s required to implement OTA. I haven’t looked into that feature yet.
The update process is fairly straightforward: Browse to the download link and download the latest build. Then reboot into Recovery mode, select “Install” and browse to your Downloads folder and select the file you downloaded.
I picked up an ex-display model of this tablet this week, and I’m really pleased with how this build runs on it, and with the ease of installation. (I’ve put Lineage and MicroG on a couple of phones recently, and this was significantly easier than that.)
In case it helps anyone, the trickiest step for me was restarting after the TWRP install in a way that didn’t cause TWRP to be overwritten with the standard recovery. I found that I needed to hold VolDown and Power until the screen goes black, then release them instantly… so far this is all as the instructions say - but then I had to immediately hold Home, VolUp and Power to reboot into recovery.