yashsingh1/xdaforums huggingface dataset:
[/e/OS Project] superbraz:
yep,

from here - Post 678 from @guidol

i used last twrp (3.7.0) - but i don´t think thats relevant
[/e/OS Project] Ge-Ghost:
ok. and what version of open_gapps-arm you have used for install lineage-14.1-20220107-UNOFFICIAL-v2awifi.zip ?

have you reboot after have install lineage-14.1-20220107-UNOFFICIAL-v2awifi.zip bedore install open_gapps-arm.... ?

after have you reboot directly to TWRP for install e-1.9-q-20230318-UNOFFICIAL-v2awifi.zip or have you make other thing before ?
[/e/OS Project] superbraz:
i didnt installed any gapps, the eOS has an own appstore...

i booted on lineage 14.1 and than reboot to twrp, wipe cache and data > and installed e-1.10
[/e/OS Project] Ge-Ghost:
and for the steps you did like me ?

because I always have a blank screen after displaying the name of the tablet model.
[/e/OS Project] menner-xda:
Yes, since all versions of /e/OS 1.Xq are based on LOS 17.1 / Android 10 (the "q" in the /e/OS version name).
[/e/OS Project] menner-xda:
Here you can find /e/OS 1.11q for v2awifi (SM-T900). It is also based on LineageOS 17.1 and Android 10 with security patches as of April 2023:

File-Upload.net - e-1.11-q-20230517-UNOFFICIAL-v2awifi.zip

Datei: e-1.11-q-20230517-UNOFFICIAL-v2awifi.zip. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.

www.file-upload.net

And here's the boot.img that you can patch with the magisk app to root the tablet (this time it isn't magisk-patched already):

File-Upload.net - e-1.11-q-20230517-UNOFFICIAL-v2awifi.boot.img

Datei: e-1.11-q-20230517-UNOFFICIAL-v2awifi.boot.img. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.

www.file-upload.net
[/e/OS Project] Desperado_22:
Thx... updated with no problems.
[/e/OS Project] Ge-Ghost:
hello

after installing and reboot, I see the Galaxy Tab PRO SM-T900 logo, and then the screen goes black with the display backlight still active, but nothing else happens.

I have make this :

1 - with Odin3_v3.14.4 I setup official rom for SM-T900 : T900XXUANB5_T900OXXANB2_HOME.tar.md5

2 - Reboot

3 - Verify rom boot fine

4 - with odin I root SM-T900 with CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5

5 - Reboot

6 - Setup twrp-3.7.0_9-0-v2awifi.img.tar

7 - Reboot

8 - shutdown

9 - reboot on TWRP

10 - Wipe Cache and Data

11 - Install ROM : e-1.9-q-20230318-UNOFFICIAL-v2awifi.zip OR lineage-17.1-20210510-UNOFFICIAL-v2awifi.zip

12 - For lineage-17.1-20210510-UNOFFICIAL-v2awifi.zip install too open_gapps-arm-10.0-mini-20220215.zip

13 - Reboot

have-you idea ?
[/e/OS Project] menner-xda:
See post #15 of https://xdaforums.com/m/superbraz.2133407/ in the current thread:

It seems that LineageOS 17.1 (or /e/OS 1.x-q) only works if LineageOS 14.1 was installed before.

I was also running LineageOS 14.1 before I installed LineageOS 17.1 (and eventually /e/OS).
[/e/OS Project] rdcflorida:
Need help, hints, clues.

Trying to install LineageOS on a Samsung Galaxy Tab Pro SM T-900, Android 5.1.1, Build LMY47X.T900UESBPL1.

Followed the steps given, using TWRP twrp-3.7.0_9-0-v2awifi.img.tar

upon booting I get an e with a bouncing ball.

I have tried LineageOS 17.1 build of TechDriver and get similar boot results a smile with a circle moving

====

just saw some posts indicating need Lineage OS 14.1 v2awifi installed before

------

just installed Lineage OS 14.1 from guidol, it works

my next goal is to install LineageOS 17, then learn how to build
[/e/OS Project] menner-xda:
Probably you have to install LinrageOS 14.1 before you install LineageOS 17.1, see the previous post.
[/e/OS Project] bdlc794:
Hello I managed to install this rom successfully and everything has worked great. I could not however get the IR/Infrared sensor to work and was wondering if this is something anybody else was experiencing. I know not many people use this feature anymore but I still use the IR Remote app from f-droid.
[/e/OS Project] joostnl:
Amazing work, keep it up! Look alot smoother then 14.1 with fully kiosk browser and home assistant! Any home assistant users with setting tips?
[/e/OS Project] jumatemi:
Hi. Updated 1.11 without problems over version 1.9.

Do not format the DATA partition and keep all data and applications. Thank you very much for the great effort.

This veteran Tablet continues to work better than the first day, :).
[/e/OS Project] jumatemi:
I use this tablet with the home assistant application for android.

It also works very well.
[/e/OS Project] joostnl:
I have sometimes freezes and battery failure. Do you use the native app of home assistant? I use kiosk browser at the moment
[/e/OS Project] menner-xda:
Here you can find /e/OS 1.14q for v2awifi (SM-T900). It is also based on LineageOS 17.1 and Android 10 with security patches as of July 2023:

File-Upload.net - e-1.14-q-20230827-UNOFFICIAL-v2awifi.zip

Datei: e-1.14-q-20230827-UNOFFICIAL-v2awifi.zip. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.

www.file-upload.net

And here's the boot.img that you can patch with the magisk app to root the tablet (original build, not yet magisk-patched):

File-Upload.net - e-1.14-q-20230827-UNOFFICIAL-v2awifi.boot.img

Datei: e-1.14-q-20230827-UNOFFICIAL-v2awifi.boot.img. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.

www.file-upload.net

It's a fresh build - I didn't test it on my device yet.

(Also I didn't test if IR works.)

FYI, /e/OS release notes are here

Releases · e / os / 🚀 Releases · GitLab

GitLab Enterprise Edition

gitlab.e.foundation
[/e/OS Project] joostnl:
Did you dirty flash?
[/e/OS Project] menner-xda:
No, I didn't find time to update my tablet device. But dirty flash should work.
[/e/OS Project] menner-xda:
sorry, looks like the new image /e/OS 1.14q isn't booting properly. Reverting to /e/OS 1.11q is successful. I'm making a new, clean build of /e/OS 1.14. I'm hoping this will resolve the issue.
[/e/OS Project] joostnl:
Did someone have scheduled reboot? I hope there was a faster way then tasker
[/e/OS Project] joostnl:
The tablet is loosing wifi connection when idle, did you solve this anyway?
[/e/OS Project] kost80:
Would this /e/ OS version also work for SM-T520?
[/e/OS Project] menner-xda:
No, it's only for SM-T900. But somebody else built /e/os for SM-T520, see

[UNOFFICIAL BUILD] Samsung Galaxy Tab PRO 10.1 (n2awifi)

Device info https://wiki.lineageos.org/devices/n2awifi Rom https://www.androidfilehost.com/?w=files&flid=300814 Please Note: This is an Untested build. Please try at your own risk.

community.e.foundation
[/e/OS Project] menner-xda:
maybe this is due to some power saving settings.

Also, there used to be an "Wifi-Fixer" app on F-droid. But it looks orphaned.
[/e/OS Project] menner-xda:
I was using Phoenix from F-droid some time ago. It needs root. And I don't know if it still working on Android 10.
[/e/OS Project] joostnl:
I have a flickering screen sometimes and the battery is pretty dead for a wall tablet not a big problem. Did someone replace the battery or took it out completely?
[/e/OS Project] menner-xda:
I had the same problem, and I found a simple and cheap solution somewhere on the net:

the battery connector of the SM-T900 isn't attached firmly after some years, and thus has a high electrical resistance. This leads to screen flickering and even reboots, when the CPU load is high and battery is lower than ~ 70 %

I could easily fix this problem. The back is just clipped onto the front frame. You'll find instructions how to remove the back on the net. I unplugged the battery connector and reconnected it a few times to clean the contact. After that, the flickering was gone, and now the tablet works fine, even with battery less than 50%.
[/e/OS Project] joostnl:
That really made an improvement, only a fast reload is now happening
[/e/OS Project] kost80:
I have already tried it. It is Android 7 and is full of bugs, almost nothing works.
[/e/OS Project] joostnl:
Did you manage too get it working?
[/e/OS Project] Max-Vador:
Hi, thanks for your job. Will you release a new update ?

1.11 installed working fine .

Can't install 1.14

i can't launch some games like clash of clans, FC.

Can you change file explorer ? It crashes verty often

Web email and basics works very smooth
[/e/OS Project] menner-xda:
Hi Max-Vador,

I'm hoping to find time build and test a current version in the next weeks.

The /e/OS file manager has problems with the large tablet screen. It works in Android's split screen mode, though. (In the list of open apps, tap and hold the app's icon, select "spit screen".) You can also install some other file manager like Amaze.

I won't change the /e/OS image and the apps that are delivered with /e/OS. I'm hoping they'll fix file manager some time. But /e/OS is targeted for phones, not for tablets, A.F.A.I.K.

If I'll find more time, I want to activate zram, since app swapping or starting large apps sometimes takes very long. I suppose this is caused by insufficient RAM.

But for games this old tablet probably hasn't enough CPU or GPU power.
[/e/OS Project] Max-Vador:
Thanks, for the reply, and for your time😉

i tried to use another file manager but the system use the default one when i try to open a file. i'll try amaze.

games were working well on HOS 14.1 (old ones like clash ...)

My tab is running fast for every day use (emails, web) thanks again for your work.
[/e/OS Project] jumatemi:
Sorry for the delay in responding.

No, I have not found a solution, sometimes it disconnects. I'm looking at putting an automated relay to stop and activate the load from HA, maybe when I connect the load I can reactivate the Wifi connection.

I'm also trying the program recommended here, Wifi Fixer.
[/e/OS Project] joostnl:
Let me know if you found something, i tried various things no result. Wifi fixer is not giving great results i also think its not reactivating with a daily reboot.
[/e/OS Project] menner-xda:
I built /e/OS 1.17q recently, but unfortunately it doesn't boot on my SM-T900 tablet. /e/OS 1.17q is the last /e/OS release based on Android 10 (Q). I'll try again.
[/e/OS Project] theAlexPS:
Hi, I tried this android 10 build, but Im stuck with the boucing logo. Read on the first page, that I need to install Lineage 14 before. hooooowever, there seems no way to transfer the old image to flash it with twrp.

twrp doenst mount on the pc a drive.
[/e/OS Project] theAlexPS:
I flashed a stock image back to get access to the storage, but now if I want to flash twrp it always fails.

I first flashed by accident an "combined" image with debug tools and only afterwards the stock rom.

any ideas?
[/e/OS Project] joostnl:
For the storage part you should use an sd card always works for me.

Images are always dangerous, I'm no expert but the newest firmware will maybe work? No guarantee
[/e/OS Project] menner-xda:
logcat shows a crash in SystemServer related to ConsumerIrService in all of the non-booting /e/OS images. After several builds that didn't boot I found out that github.com/exynos5420 pushed some changes on 2023-Jun-10, including some changes in the IR stack. I'm trying to build with previous versions of github.com/exynos5420.
[/e/OS Project] joostnl:
Thank you for the feedback! I sadly lack the skill too help.
[/e/OS Project] menner-xda:
I managed to build the latest version of /e/OS-q for v2awifi at last - it is /e/OS-1.17q.

e.foundation has stopped development of /e/OS-q recently, so this is the last version.

And it is not very useful though, since it looks like the last AOSP q / Android 10 / LineageOS 17.1 security patch was in February 2023.

But there are a few updates of Exynos5420 BLOBs and the the /e/ updates.

e Release notes say:

Browser update including security patches

microG update with upstream

...

v1.17-q · e / os / 🚀 Releases · GitLab

Please welcome /e/OS 1.17! 🚀 We are proud to deliver the /e/OS 1.17. Enjoy all the new...

gitlab.e.foundation

IR still isn't working, but it wasn't working earlier, I suppose.

The changes in exynos5420 obviously are not working in v2awifi,

Comparing f619d47b93ce8226d3b8fc0f142bf0137dcfaf34...239f426e9054f15952d30ab5718c29635871140a · exynos5420/android_device_samsung_universal5420-common

Contribute to exynos5420/android_device_samsung_universal5420-common development by creating an account on GitHub.

github.com

I uploaded the image to AndroidFileHost

https://www.androidfilehost.com/?fid=11701882489785031414

and to file-upload.net which is better, because it has a download counter, so I can see if there are interested owners:

https://www.file-upload.net/download-15250001/e-1.17-q-20240103-UNOFFICIAL-v2awifi.boot.img.html

Magisk-patched boot image is https://www.androidfilehost.com/?fid=11701882489785031412

and https://www.file-upload.net/downloa...40104-UNOFFICIAL-n2awifi.magisk.boot.img.html
[/e/OS Project] menner-xda:
I achieved notable performance improvements by activating a swapfile (/data/swap/swapfile). You'll need Magisk rooting and the Magisk module

Android 7+ Swapfile Mod​

GitHub - janithcooray/lin_os_swap_mod: increases the SWAP memory by an additional 4GB or 8GB for Android 7.0 or above

increases the SWAP memory by an additional 4GB or 8GB for Android 7.0 or above - janithcooray/lin_os_swap_mod

github.com

The Exynos5420 kernels 3.4 support zswap. It is not activated by default, though. But if you enable memory swapping to a swap partition or swap file (f.i. by this Magisk swapfile module), zswap is implicitly also activated. The kernel compresses two memory pages into one page, and only if the compression ratio is insufficient, the kernel will swap out the page to the swap file.

Before that, the tablet sometimes wasn't reacting on input for up to a minute. With swap enabled (I started with only 1 GB), these blockings are now very rare.

You can check if swap is working, on a terminal or adb shell:

$ free

(should show swapfile)

$ grep -r . /sys/kernel/debug/zswap

(should show compressed pages (stored_pages) and swapped out pages (reject_compress_poor))

Im my case, zwsap is used well, and > 95% of the pages are compressed and not swapped out.
[/e/OS Project] menner-xda:
I could try to build /e/OS-1.17-q for n2awifi, if you're still interested. Since my build for v2awifi is now working (without IR, though).
[/e/OS Project] bmwdroid:
Do you think it's worth a try flashing it onto P900?

I know I would before have to edit build.prop.

Don't need the pen anyhow and the stable running 14.1 on it is nearly two years old.

The LOS 17 for it I never got working properly.
[/e/OS Project] menner-xda:
AFAIK SM-T900 v2awifi and SM-P900 v1awifi are very similar. But the v2awifi image probably won't install and boot on a v1awifi.

Currently I'm running the /e/OS-1.17q (LOS 17.1) build for n2awifi (SM-T520) on may old Atom-based notebook. This 'll take many hours. Thereafter I'll run the build for v1awifi (SM-P900). If successful I'll upload both images to AndroidFileHost. Hopefully tomorrow or the day after tomorrow.

You can test then. But since this is Android 10 and not Android 7, you probably can't update dirty, you probably must backup, wipe the data partition, and restore data.

My build of /e/OS-1.x-q is running fine and smooth on my SM-T900. So chances are that the build for SM-P900 will also run smoothly. But I can't test it.
[/e/OS Project] menner-xda:
for SM-T520 n2awifi build, see

[ROM]|SM-T520|SM-T900|[UNOFFICIAL] LineageOS 17.1 | Android 10

I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! Special thanks to Exynos5420 team and LineageOS for all the sources. Use SM-T900 build...

xdaforums.com
[/e/OS Project] bmwdroid:
That's what I know as well.

Afaik the update-script at least contains info about the devices. So if I edit it and change device info it might work already or do you know of any other files that contain device info?

No problem flashing cleanly as I think it's mandatory anyhow when changing ROMs.

I gladly will
[/e/OS Project] menner-xda:
https://xdaforums.com/m/bmwdroid.5763685/ .

here's the freshly built /e/OS-1.17-q for v1awifi SM-P900. It is untested yet, since I don't have such a device.

IR and MHL won't work, don't know about the stylus.

ROM: /e/OS v1.17-q v1awifi image

Boot: boot image that could be patched by Magisk

Boot: boot image already patched with Magisk
[/e/OS Project] menner-xda:
/e/OS-1.17-q v1awifi is uploaded now. I hope it'll run on your device.
[/e/OS Project] piero-e:
hi,

thanks for the effort,

download link in first post is dead.
[/e/OS Project] menner-xda:
which link? Both file-upload.net and androidfilehost.com are not working with some mobile browsers, like the /e/OS chromite browser, I found out today. But mobile Firefox Klar or desktop browsers should work.

See also my post here: https://xdaforums.com/t/rom-sm-t520...neageos-17-1-android-10.4274047/post-89260260
[/e/OS Project] menner-xda:
Do you mean the "schicks-digital" link? That ROM is /e/OS 1.8 and obsolete. I recommend the current build, see

this new thread: /e/OS for SM-T900 and SM-T520
[/e/OS Project] bmwdroid:
Will give it a try today and tell you the result.
[/e/OS Project] bmwdroid:
@menner-xda thank you very much.

Didn't have much time to test yet but it is stable since flashing 2h ago.

AND camera is working.

Will soon flash magisk and start using swap file as this ROM is consuming RAM like hell.

Will as well test CPU governor later but as CPU load is very low I doubt that will be usefull.

Built-in file explorer and UI=Bliss Launcher are buggy.

No proper access to SD card as content is shown but trying to install apk from there fails as it crashes.

Preferring Total commander anyhow which accesses and installs apk on SD.

UI stays always in portrait mode no matter what settings say (although settings display turns).

Nova Prime Launcher works as desired.

Will keep on reporting.
[/e/OS Project] menner-xda:
@bmwdroid , thanks for the feedback. Yes, I agree, Bliss launcher and file manager are not the highlights of /e/OS.

But you can change these easily. And on the other hand, it's usable from the beginning, since it's got signature spoofing and MicroG and AppLounge and a reasonable browser for webview. Adding these to a naked LineageOS would require patching after each OS update.

That's the reason why I choose to build and use /e/OS in favor of LineageOS. Not only on my tablet. On my and my wife's phone we also run the official /e/OS-r, which gets updated every month without hassle.
[/e/OS Project] bmwdroid:
Changing UI is no problem but I've got no clue how to make another file explorer as standard.

That's why I can't install the swap Magisk module as built-in explorer chrashes permanently when Magisk opens it.

Do you know if MicroG would collide with playstore when flashed additionally?

Bought some apps like Netguard from there and would like to use full version.

Generally e/OS is still running flawlessly and snappy.
[/e/OS Project] menner-xda:
... built-in explorer crashes permanently when Magisk opens it ...

I suggest to run Magisk (and thus the Files app) in Android split screen mode. In the list of running apps, just TAP AND HOLD drag the round icon of an app to the left or right. My experience is: if the Files app has got less screen real estate, it doesn't crash.

... Do you know if MicroG would collide with playstore when flashed additionally? ...

I'm running a paid app (german DWD Wetter App) from the google play store, without permanently enabled Google Playstore. I'm using FakeStore2PlayStore Magisk Mod, and I documented somewhere, how I did this. It is utilizing a patched Google Playstore app.

b.t.w., my Files app doesn't crash any more, even in full screen mode. It did in early /e/OS releases, but it didn't crash now for months. Maybe it healed itself when running in split screen mode.

I'm also thinking about enabling swap right in the /e/OS image as default. So one wouldn't need to root the tablet with Magisk to take advantage of zswap. But I don't know how to do this yet.
[/e/OS Project] bmwdroid:
Gonna try this and tell you the result.

Am going to test swapper which is running on my old T325 to enlarge RAM if your a.m. method doesn't work.

Edit: your "split screen" hint helped.

Nevertheless Magisk is telling me "unzip error" when trying to install.

Will test with new download again.
[/e/OS Project] menner-xda:
You cannot directly install the swapfile mod zip, that you download from github "release". That was my mistake as well. There are installation instructions inside the zip, as far as I remember.
[/e/OS Project] bmwdroid:
As it's just the source code I've repacked the module part.

Didn't help so I'm gonna look into that again.

Fun fact: although Bliss launcher comes with e/OS and needs RAM, the LineageOS Trebuchet launcher uses 72MB RAM as well.
[/e/OS Project] joostnl:
With running fully kiosk browser the the ram usage is only 1.6gb without swap. Do you think swap will make an difference?
[/e/OS Project] menner-xda:
no, probably not. I had got freezes for 10, 20, 30 seconds, f.i. when switching between my newspaper reader app and the browser or messenger app. All of them need much RAM. These freezes are rare now.

In kiosk use cases, rooting is no good idea, anyway.
[/e/OS Project] menner-xda:
By accident, I found this possible explanation today, on https://divestos.org/pages/faq

"Use the built-in home launcher instead of a third-party launcher. On modern Android the app switcher/overview is handled by the launcher (Quickstep) and most replacement launchers do not actually implement this, which results in both launchers always running."
[/e/OS Project] bmwdroid:
Forgot to say that Trébuchet can't be selected.

Only Bliss and, in my case, Nova are available.
[/e/OS Project] vochong:
Hi @menner-xda,

Thanks a lot for your /e/OS image. It has transformed a pathetically slow SM-T900 (running LOS 14) to a fast running machine.
[/e/OS Project] menner-xda:
Thank you for the feedback. That's sort of surpising, since /e/OS is LineageOS + microG + Accounts + AdvancedPrivacy + BlissLauncher + AppLounge + Maps + Mail + Murena.io Sync.

LOS 17 / Android 10 might be faster than LOS 14 / Android 7. Or maybe you had LOS14 augmented with GApp/PlayStore, which is consuming memory and bandwidth.

My experience is the same: unless you don't open complex web pages, or many apps at a time, the SM-T900 is still usable with /e/OS (since normally you won't need GApps).
[/e/OS Project] vochong:
I believe microG and its apps in your /e/OS image play a significant role. GApp/Play Store tends to consume a substantial amount of the device's memory. Thanks again.
[/e/OS Project] menner-xda:
On my SM-T900 v2awifi, I'm now on Android 11! See this thread.
[/e/OS Project] Max-Vador:
Hi, i've just updated my tab to 1.18r .

Dirty flashed from /e/OS 1.11 and removed the .db file as suggested.

running fine from now.using nova launcher.

Thank you for the job.
[/e/OS Project] tejljr:
Question: I installed the module on my n1awifi running Lineage, but it says swap is at 0. Did I do something wrong?
[/e/OS Project] menner-xda:
does the zswap device show up in a root shell (su)?

# ls -l /sys/kernel/debug/zswap
[/e/OS Project] MichelleChristiana92:
Hi

Thanks so much for redirecting me to this thread.

So I am currently running TWRP 3.5.1 - from what I read I need to update to the latest 3.6.0 to install /e/OS17.1? Can I do that by flashing the new .img through the old TWRP or do I need to go back to stock and then reinstall TWRP? Couldn't find that explained.

Are the issues you came across above now solved? I am definitely not as familiar with all of this as you are and if P900 becomes laggy due to low RAM I would be clueless. What is benefit of swapfile and did you manage to install it? Is it doable to install playstore (or patched version) or difficult also have a paid app I would like to use? Just wanting to be positive of what I am doing as I am enjoying a working tablet and would be sad if I broke it.

Thanks for all your help!