Yes, they probably did their annual commit session
3 months later,
espresso3g : 167 downloads
espressowifi : 203 downloads
12 months later,
espresso3g : 1095 downloads
espressowifi : 1326 downloads
FWIW, hereās a logcat I managed to capture right now.
The adb session died on its own at the end of the log.
[final edit Fri 7 Jan 20:41:42 GMT 2022 ] Build abandoned. Out of date stuff removed. See next post
I have spent quite a lot of time this week trying and failing to make some up-to-date builds for this device. I had thought about leaving my device on @Android-Andiās latest unofficial 0.9-nougat
build, which works pretty well, but the temptation to try and make something a bit more up-to-date was too great, and the weather here has been too bad to be doing much outside, soā¦
First I tried a CM-14.1
build of Lineageos4microg, using Docker, but I could not get it to build.
Then I tried a v0.19-nougat
build of /e/OS, building the traditional way with (lunch, mka bacon, etc
). I eventually managed to get it to build, by removing some of the built-in apps, but the build will not run: it black screens, after showing the splash screen.
I have decided that life is too short to spend more time getting /e/OS to run on a device that is just a bit too old, small and feeble to really do it justice.
My device is now running with a āD-I-Yā lineage4microg, plus sync to /e/'s cloud services, created as follows
-
@Android-Andiās LineageOS 14.1 ROM from here
-
using the Nanodroid stable zip files from here
-
patched to allow signature spoofing using
NanoDroid-patcher-23.1.2.20210117.zip
-
F-droid, Privileged Extension, Aurora Store and Aurora Services installed using
NanoDroid-fdroid-23.1.2.20210117.zip
then updated via F-Droid -
MicroG installed using
NanoDroid-microG-23.1.2.20210117.zip
, updated by adding and enabling the MicroG repo in F-Droid
-
-
Apps installed from F-Droid - DAVx5, Fennec, NextCloud, NextCloud Notes, K-9 Mail, Open Launcher
All of that gives me something aproaching /e/ OS, but with a sensible launcher, MicroG EN Framework working by default, up-to-date email and notes apps, and mature, trusted app stores. Itās not perfect, and itās a bit laggy, but it will do for casual use.
I āinstalledā some other Apps by copying from my daily driver (Xperia XZ1 Compact, running e-0.20
Custom build) using Android Backup and Restore Tools - WhatsApp, Facebook Messenger, and a couple of other apps that ājust workā without my having to enter account details again
So thatās it for me building trying to build for this device: itās been fun and frustrating in about equal measures, but Iāve learned quite a bit in the process. Now to get ready for testing v0.21
releases
Might be the combination of repos youāve used.
On my personal builds Iāve used some combination of lineageos sources and sources from unlegacy-android. Those UA parts depend on some other changes in the frameworks part of android, kernel and hardware repo and blobs.
https://gerrit.unlegacy-android.org/q/topic:āomap-ddk-1.14ā+(status:open%20OR%20status:merged)
Thanks. It looks like building /e/OS and/or LOS4microg is solvable, and would be an interesting problem to solve, but I think I will focus my efforts on more recent, more powerful devices. My espressowifi device is now working well enough for me, with the setup described above
How to use both /e/OS and Linux PostMarketOS Community pre-built image on Galaxy Tab 2
install instructions for Phosh and XFCE4 images
works running from a SD card
as explained in Installation - Flashing - From SD Card Our device can boot a SD card, USB stick or other external storage.
.
preparation in a way to easily switch between /e/OS and PostmarketOS
from your actual Android_OS install file (AP_Stock_Samsung_Firmware.tar.md5 or Custom_Android_Based_OS_like-e-is.zip), extract the boot.img and copy it to your TWRP folder in internal storage (/sdcard/TWRP)
Download the pmOS pre-built image
from the download page
insert a MicroSDcard into your Computer
and find its name by running
$ lsblk
make sure it is the right one as you will overwrite everything on it. Use a path without partition number at the end,
such as /dev/mmcblk0, or /dev/sdd
decompress the downloaded file and write it to your MicroSDcard :
$ xz --decompress --stdout /path-to-pmos-samsung-espresso10.img.xz | sudo dd of=/dev/name-of-your-SDcard bs=4M status=progress
Wait until the command completes and eject the SD card.
If you are on Windows, see here.
insert the MicroSDcard into your device, and boot it into TWRP
using the mount feature, unselect all /partitions except āMicroSDcardā,
using the install feature, switch to āinstall imageā rather than āinstall ZIPā
navigate to the ā/external_sd/boot.imgā, and flash it to the /boot partition
reboot system
The rootfs image will boot right into postmarketOS. You are done with installing postmarketOS, congratulations!
default login is user and password is 147147
to restore your /e/Android_OS
boot the device into TWRP mode,
and simply using the install feature, switch to āinstall imageā rather than āinstall ZIPā
navigate to the previously stored ā/sdcard/TWRP/boot.imgā, and flash it to the /boot partition
to restore your PostmarketOS
boot the device into TWRP mode,
and simply using the install feature, switch to āinstall imageā rather than āinstall ZIPā
navigate to the ā/external_sd/boot.imgā, and flash it to the /boot partition
.
.
Linux PostMarketOS on samsung Tab2 7.0" all variants (espresso7)
.
Linux PostMarketOS on samsung Tab2 10.1" all variants (espresso10)
.
the ādual-bootā should work also for others devices in the community list :
.
https://wiki.postmarketos.org/wiki/Devices
Hi Folks, is there any chance to get a /e/OS 1.x or 2.x running on this device?
Hello @SupaKorni, welcome to this Forum.
unfortunatly not because last /e/ versions possible to build are :
- 0.21 for Nougat
- 0.21 for Oreo
- 0.23 for Pie
there are no sources available for :
- Quince Tart
- Red Velvet Cake
- Snow Cone
- Tiramisu
- Upside Down Cake
- Vanilla Ice Cream
Ah, thx.
So there is a possibility for a build with 0.21 Nougat instead of 0.9 in this version?!
Theoretically yes, but I could not build due to error with OMAP4 hardware sources.
doesnāt it the fix ?
Yeah, could do. Will try in the next days
I also needed to apply this fix and one minor other error
https://review.lineageos.org/c/LineageOS/android_hardware_ti_omap4/+/198574
Will upload ROMs later
Wasnāt uploaded full and now is extremely slowā¦ will try later