yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bocanea:
Hello,

thank you for your fantastic work to make this old but good devices work - I love it.

I have only ony question: would it be possible to include the feature:

“android.hardware.se.omapi.uicc”.

into the immage. It is needed to suport eSIM cards on physical sim Cards like eSIM.me. It is supposedly already in other LineageOS images included. Thus it would be possible to have more than one SIM Profile.

Thanks

Bocanea
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the_pretzels:
Is there anyone experiencing problems with Play Store and GBoard?

I've I stalled bitGapps OMNI then the keyboard stopped working. Then I tried to update it through play store but anything I try to download there keeps pending forever
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] yxo 6o6uka:
I'm using the gboard from bitgapps across multiple phoval roms on this device, and on other devices, including some very old ones (bitgapp's gboard is available for android 7). For a couple of years. No issues. Installed with Omni and also standalone from addons available separately. It's more likely something on your device. Here are some thoughts:

- the gboard version from the current bitgapps may be better suited for legacy devices, including this T320. Imho. It's more responsive while plenty more functional than stock android. The latest gboard is fancier, however at the expense of extra cpu/net, which makes the initial kb popup sometimes sluggish. In other words - the failed upgrade may be a welcome feature rather than a "problem" [grin]. fwiw, i purposely suppressed the upgrade on all my legacy devices.

- the gboard from bitgapps does not require playstore (i believe the only addon app). It works great with microg roms, w/o play store; in which case you won't get nags about upgrades.

- if getting gboard upgraded to latest is a preference, i would try to wipe storage for the app (reset app), if that fails - dirty fllush just the gboard add-on and if that fails - reflush clean the entire stack. Omni if having phone app is ok, or core + gboard addon for a tighter config. (i'm sure lecturing re try = backup is redundant.)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] TheHitMan:
You need to install BiTGApps or GApps in general before first boot.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the_pretzels:
Thankyou gentleman. I flashed the rom again and then it worked without problems. I've used bitGapps OMNI again.

My only problem now is related to the Wifi. It drops everytime
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
Please check my Post #182

[ROM][T320][T325][Android 13] Unofficial LineageOS 20.0 Nightlies Tab Pro 8.4 Wifi/LTE (mondrianwifi/lte)

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! If you want to check - please make backup. Better to store all partitions. What works...

xdaforums.com
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] simonfeng0668:
Even the newrst version 20230527， The image is upside down during video playback！
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] francesc5358:
Good morning everyone.

I have the latest version installed, lineage-20.0-20230527-UNOFFICIAL-mondrianwifi, everything is fine except that it is not fluid.

When I browse the system, it is fluid, but when you open an application or write something, it starts to be slow.

I have reinstalled and installed everything several times just in case it left something behind, but nothing.

I know it only has 2gb of ram, but in previous roms from mondrianwifi it has always been smooth.

Is there anything that can be done? or is it like that.

Any suggestions.

Sorry for using a translator, my English is not very good.

Thank you very much.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Craftyawesome:
Just to clarify, did you factory reset or wipe data partition or did you just reinstall?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] francesc5358:
Sorry for the delay.

I don't reinstall. I do the whole process as indicated in any rom. I have tried others without problems of fluidity. But this one that seems to work everything slows down.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Shot-Gun:
There's a way to disable the auto shutdown when the battery is 0%?

I've removed the battery and now the device is plugged directly on the USB charger.

Thanks in advance!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Roca7878:
Hello Anyone can help me .

I am a beginner .

My ant have a old SAMSUNG GALAXY TAB PRO SM-T320 . T320xxu1bqb2 . europe Swedish . WI FI version

I have download lineage-20.0-20230527-UNOFFICIAL-mondrianwifi.zip and

twrp-3.7.0_9-0-mondrianwifi_fota.img

if anyone could point me in the right direction what to do now

Have download odin and how can i run twrp in to tablet ?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
@Roca7878

Something to read.

Install LineageOS on mondrianwifi | LineageOS Wiki

wiki.lineageos.org

And search on YouTube : how to install Lineage OS on Samsung galaxy tabpro 8.4 mondrianwifi.

Read at first the instructions and than you can follow the YouTube video step by step.

Rooting is not necessary.

Important is to use the original USB cable and start Odin as admin.

How to use Odin3 Flash Tool to flash Stock firmware etc. on Samsung Devices

This tutorial lists detailed steps on how to use Odin downloader / Odin Flash Tool to flash Stock Firmware, Custom ROM, Recovery, CF Auto Root, Root Files and other patch files on any Samsung Android Smartphone or Tablet. Also, download the latest version of Odin3 Downloader.

odinflashtool.com
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
Make sure that you knows the combo buttons to boot into recovery and download mode.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Roca7878:
bierma32​

Thanks for the info and links .

Have studied it carefully now and will probably solve it .( I hope ) .

Waiting for the original usb cable . My ant Will leave it in a few days.

The GApps which I install in the end .

which one do you think I should install .

shall I take Core or is it better to take Mini variant ?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
@Roca7878

Look at first Post : Bitgapps. allways the smallest Version.

I have installed the aurora store that is Google free, mostly you will find all apk there.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] simonfeng0668:
Back camera preview : wrong rotation on preview in default app still caused on build 20230527.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Roca7878:
hello .

i have install Lineage OS and direct after gapps .

but gapps install failed .

i have install the smallest core variant .

Lineage OS runs but without gapps.

i have install BiTGApps-arm-10.0.0-v2.7-CORE (1).zip .

maybe arm 13 is better ?

do i need to reinstall evrything and start over or can i go to recovery mode and try to install gapps arm 13 Immediately .
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
You have to install ARM 13, that is for Android 13 or LOS 20
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
Boot to TWRP and Flash the Bitgapps.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] TheHitMan:
Package selection is wrong.

You need Android 13 BiTGApps.

BiTGApps

Google Apps Package

bitgapps.io
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Roca7878:
Thanks everyone .

bierma32​

TheHitMan​

Its work great now . BiTGApps-arm 13 was better

Thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] epy0n218:
Does anyone here use Intune? I am able to install the Intune Company Portal app, but when I go to create the work profile, it says:

Can't set up device

This device doesn't allow encryption, which is needed for setup.

I didn't install Magisk, so I haven't rooted the device. Any suggestions?

Thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bmwdroid:
Afaik encryption hasn't got anything to do with rooting.

Imho it is either possible to turn on encryption when setting up the device first time after flashing the ROM (too long ago so I don't remember), or if not then, it is a feature not included in this ROM.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Craftyawesome:
For anyone wanting to use something that requires play integrity device pass, here is a Magisk 27.0 boot image with a patched kernel string. Just flash it to boot using TWRP (and do typical PIF stuff).

Thanks to @Umgak for doing most of the debugging, I just had to figure out the last few details to get it to actually work.

If you want to patch your own boot image instead of using what I've attached, here is a vague guide (advanced).

Spoiler content hidden.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Joam281:
First of all, good afternoon and thank the developer for all the work done.

I would like to know if we have Android 14 working for this rom it says?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Gamblor2:
Hello, Thankyou @phoval for an excellent ROM. I believe @Joam281 could be asking for an Unofficial LineageOS 21.0 from am excellent developer 😉
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] yxo 6o6uka:
My tab pro have been having sporadic wifi disruptions similar to what other users in this thread have reported in this 20.1 thread and I think in 18.1. The drops were often happening in public roaming.

I finally sorted it out - wifi works well in 2.4GHz and 5GHz for control channels 36-48, but does not see my 5GHz network if the control ch is in 149-161 range.

The router is a nice asus with 5GHz in N/AC mix mode and 80 MHz bandwidth, WPA2/AES security. I'm reasonably sure the router is not at fault since all other devices on the network - about a dozen - all work well when the control ch is 149, 153, 157, or 161. Just this tab pro refuses to see the 5GHz on 149 network, tho no issues with 5GHz on 36 ch.

Could be tab's h/w and that's what I'm researching.

Does anyone have 5GHz connectivity issues on control ch 149/153/157/161? TIA!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] retiredtab:
So Samsung stock rom and Valera's LineageOS 17.1 and 18.1 build both see channel 149 on 5Ghz.

However, starting with phoval's 18.1 builds, it does not see channel 149 on 5Ghz. After 3 days of troubleshooting, I found the problem. There's no reason why stock wifi conf was used.

This commit below

https://github.com/phoval/android_d...mmit/4e417eedef54ca07e540e5429169a93c2313548d

stops working with channel 149. If you use Valera's 17.1 and 18.1 wifi drivers, it fixes the problem.

If you want/need 5GHz channel 149, follow these steps.

1. Download and unzip my zip file
2. Backup your files and current rom.
3. Boot into TWRP. I'm on TWRP 3.6.2.9.
# Mount the system as read write
4. Touch Mount, then System
5. open terminal or command shell on your PC (not terminal in TWRP)
6. cd into the directory where you downloaded my wifi-drivers.zip
7 # push and overwrite existing wifi files
adb push WC* /system/vendor/firmware/wlan/prima
# WCNSS_cfg.dat: 1 file pushed, 0 skipped. 78.1 MB/s (10586 bytes in 0.000s)
# WCNSS_qcom_cfg.ini: 1 file pushed, 0 skipped. 94.3 MB/s (7645 bytes in 0.000s)
# WCNSS_qcom_wlan_nv.bin: 1 file pushed, 0 skipped. 167.4 MB/s (29816 bytes in 0.000s)
# 3 files pushed, 0 skipped. 0.9 MB/s (48047 bytes in 0.051s)
8. # open shell and check with sha1sum
adb shell
9. # cd into /system/vendor/firmware/wlan/prima
cd /system/vendor/firmware/wlan/prima
# check sha1sum with command below
sha1sum WC*
# 32ea3a09be2efdb60fb2f3d2b17bf468db2bb61b WCNSS_cfg.dat
# 1424ceeeccb3217ec393c2b35bb828934a6b6064 WCNSS_qcom_cfg.ini
# 49b4362b8093f9baf831c7403899f3ac97e9ca8a WCNSS_qcom_wlan_nv.bin
# if sha1sum match above, then reboot
10. Reboot back into OS and verify that channel 149 5Ghz is shown.

Note:

1. I have not tested these drivers for anymore than 30 minutes so I cannot comment on their stability or reliability.

2. If these drivers are WORSE, then simply reflash your rom and it will overwrite these ones provided.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Kakakrroto:
Good morning.

My Samsung T320, purchased used in 2023, had battery problems. It consumed quickly and the tablet heated up during use. I bought a new one, but it's not lasting as long. The old one lasted 4 hours from 100% to 0% and this one lasts about 5 hours from 100% to 0% (20% every hour) in continuous use (videos and internet). It's more stable, because with the old one the tablet turned off and when restarted it still had a little charge left. The new one uses from 100% to 0% without shutdowns.

I thought it could be the rom (I have Lineage OS 20.0 and would like to know what I could do to improve battery life:

1) Calibration (please provide methods, ways, programs that I could use to perform an efficient and correct calibration)

2) Programs to monitor and reduce processing and consequently consumption.

3) Wipe and reinstall LineageOS 20.0 ROM

4) Install another ROM to see if it improves consumption (it could be older versions of LineageOS or even other Roms).

5) Clean and Install the Original Samung ROM (it would be a test to see if it fixes anything, restores configuration, etc.).

6) Hardware Problems (components that may be defective and draining load).

Sorry for my English and the long text, but suddenly you already had this problem and used one of the alternatives above with success. or even others.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] yxo 6o6uka:
It's very nice of you, @retiredtab, to jump into this! I switched the drivers and ran into system crashes. I'm sure you are up to something there, I just can't confirm yet. I've benn tinkering w tab recently and blame that for the crashes. Will reimage from scratch and will retest towards the weekend.

I'm also trying to understand the issue better... You mention there is no reason to use stock wifi CONFIG, yet suggested to overwrite the driver binary. Where the files in your zip are from?

Thanks again!

UPDATE: installed ROM from scratch, rebooted into recovery, copied over the 3 files. Rebooted into system. Setup crashes when wifi page is about to show up (after time page).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] retiredtab:
I've been using those drivers on my SM-T320 since I posted on Tuesday and no problems with wifi or system crashes.

I don't know WHY phoval made that commit. There's no explanation on WHY it was done.

When I make a github commit, I list a reason WHY it was done. For example, here's my commit for Feb 5

https://github.com/retiredtab/andro...mmit/2c77417409609ef392a3e8d2316263108467482c

My git commit message tells you WHY updating the sepolicies were necessary.

I got the drivers from Valera's 17.1 tree at

https://github.com/Valera1978/android_device_samsung_mondrianwifi/tree/lineage-17.1/wifi

Even Valera's commit message "rollback wifi driver" doesn't tell me WHY it was done. Was it done because channel 149 wasn't seen? Was it done because these drivers are more stable?

I rebooted my SM-T320 and redid the exact steps I wrote earlier and my wifi works with no system crashes.

I even erased my data (using FORMAT data) and went through setup wizard, entered in my wifi and no system crashes.

To verify I'm using the Valera 17.1 drivers after FORMAT data in TWRP and going through setup wizard, see below.

$ adb root
$ adb shell sha1sum /system/vendor/firmware/wlan/prima/WC*
32ea3a09be2efdb60fb2f3d2b17bf468db2bb61b /system/vendor/firmware/wlan/prima/WCNSS_cfg.dat
1424ceeeccb3217ec393c2b35bb828934a6b6064 /system/vendor/firmware/wlan/prima/WCNSS_qcom_cfg.ini
49b4362b8093f9baf831c7403899f3ac97e9ca8a /system/vendor/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] retiredtab:
For 20, I'm running phoval's last build named lineage-20.0-20230527-UNOFFICIAL-mondrianwifi.zip.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] yxo 6o6uka:
It's a good list of possible situations. Here is a decision tree u may consider:

1. We can safely rule out the ROM as a culprit. There were battery drains earlier, all were fixed. As long as you are on latest 18 or 20, assume the ROM is not at fault.

2. I'd stay on a new battery. It needs to be calibrated. The method I use - charge fully then discharge completely until device turns off (e.g. play a movie). Charge to 100 while device is off. Turn the device on. use it lightly. put on charger and top off to 100.

3. If the current custom setup is precious, use GSam Battery Monitor to identify the app that drains your tab. Otherwise skip to (4). There are many Gsam Bat Mon guides online. That app is very good for finding the draining app. It could be a fun research project. Alternatively remove apps one at a time, giving a few days to test the discharge.

4. Reinstall the latest ROM from scratch. You should have at least 2 days on full battery with a light use of the barebone ROM with just default apps (u have a browser, a music player).

If you get 2+ days - add an app at a time towards your custom setup... checking each app for possible drain.

If you don't get that - either your new battery is not that new, or it's a h/w issue. Could be as simple as a flaky internal connector you didn't plug in all the way when replaced the battery. Could be a s...t new battery.

I've been through this a couple of times - in the end, each time it was the battery. Next common fault is in the charging cable/connector [harassing the battery into confusion]. Just my experience.

There are guides and apps to recondition/save the battery from aging... I find that science moot since a new bat is not too pricy [in US] and lasts easily 3-4 years.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] yxo 6o6uka:
Thanks again. I'll keep tinkering with my setup. I'm sure you got it, I need to understand why I don't see the same. I will also try to trace through the 18.1 thread a possible explanation of the driver switch. phoval has a good deal of credibility, there must be a fair reason. The date on the build / commit may coincide with thread chatter. I vaguely recall folks complaining about wifi issues.

I also coincidently ran into another wifi issue (while on ch 36) - an apparent driver crash while on latest phoval 18.1 with its "native" drivers. Wifi would be lost until reboot. Was downloading gps app maps for offline use. It's consistently reproducible. crashes on 5G, works consistently weel on 2.4G. I'm happy to post 2 log captures for the same crashes while on 5G. Albeit the resolution will most likely be the same - go to Valera's drivers, that dude knew what he was doing, pulling off an impossible camera revival on this device.

[I switch between 18 and 20, but mostly staying on 18, just like look-n-feel better. I'm pretty sure the wifi issues are the same between 18 and 20.]
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] yxo 6o6uka:
This may hold a clue why. A problem at the time was wifi related battery drain.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Craftyawesome:
For me it seems only WCNSS_qcom_wlan_nv.bin is needed to restore channel 149. Haven't tested battery drain yet, but maybe that problem is from the other files.

Also FWIW I think retiredtab uploaded the "init mondrianwifi"/"rollback wifi driver" version of WCNSS_cfg.dat instead of the "init q" version.

Edit: the revert didn't touch this file

Was it quickly after bootup with the wifi icon never showing up? I was having that when I was using the twrp file manager instead of adb push, though IDK why.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] yxo 6o6uka:
That's it! I mis-read line 5 of original instructions as to open a terminal in TWRP. Since patch files were downloaded on tab's sd card, just copied files with `cp` in TWRP terminal.

UPDATE

: @retiredtab 's solution, adjusted per @Craftyawesome suggestion (to only replace WCNSS_qcom_wlan_nv.bin) works very well. It allows the tab to work on 5G ctrl ch 149-161 and also fixes a reproducible 5G on ch 36 wifi crash during a bulk download. No battery issues (no changes after the driver switch) for a few days after the patch was applied. Problem seems solved, thanks to all who chipped in!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] MagicianPe:
Thank you for all the hard work, Installed and it seems to be working fine. Previous version was a Lineage 17.1 but was very slow.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] retiredtab:
For those who want to try my LineageOS 21.0 ALPHA SM-T320 build, see

https://xdaforums.com/t/unofficial-...alaxy-tab-8-4-pro-sm-320-may-12-2024.4671882/

You MUST read posts 1-4 BEFORE even thinking of trying it. If you find this unreasonable, please don't use my builds.

I don't have the SM-T325 and I won't be making any "blind" builds for it. If I don't have it physically, I won't build it. End of story.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] hello_world.c:
Here is one. But then this is the main reason I am still on Android 9 with this tablet, using this ROM.

Yes, there is a lot that can go wrong, you need the absolute best quality SD cards and then still some brands are better than others. But with only 16GB internal storage there is no alternative if you really want to use the device, i.e. with more than just the bare minimum.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] CrushingCultivation:
Hello community,

I'm trying to install: 0. Patched TWRP for FOTA. however when I open it in ODIN is looking for a .tar file instead of .img.

I tried to rename the linked img file to tar, it seems waiting long time in "Analysis" status in ODIN app.

What am I doing wrong?

Thank you!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] pocketrule:
You can't just rename the file. Tar is a compressed file.

At https://twrp.me/ you can download the tar file. As there are no updates anymore, there's no need for the patched version, so you could use the official one.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] CrushingCultivation:
Thank you for the clarification, the latest version 3.7.0.9 is provided only in .img extension on the TRWP website. I tried to install with Odin the previous version /twrp-3.6.2_9-0, however at the start the app shows the TRWP logo but no menu button, it seems stuck...

Bad software version of wrong partition?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bmwdroid:
@CrushingCultivation even older than 3.6. .tar version could be used for flashing latest .img

I remember 3.5.0_9.0 being ok and having a .tar version as well.

Sometimes it helps to flash twrp twice via Odin.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] CrushingCultivation:
Thank you, I installed twrp-3.6.1_9-0-mondrianlte.img.tar, but still the TWRP just shows the starting screen and no additional menu or buttons that are shown on online tutorials...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bmwdroid:
How long did you wait?

I experienced sometimes up to 10' waiting time.

Why didn't you trust my memory? ;)

Will have a look later, what mine is working with atm.

Edit: 37090
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] CrushingCultivation:
Thank you, I tried to install the version 3.5.0_9.0 as suggested, however after 30 minutes the TWRP screen is still stuck.. could be related to the previous LineageOS partition?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
Go back and Flash Stock Rom than try again to install TWRP with Odin
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] CrushingCultivation:
I tried to reinstall the stock rom, working fine and then reinstelled TWRP with Odin, but seems does not move after boot screen... tried three different versions. what could be the problem?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] bierma32:
Have you tried to boot into Stockrecovery ?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] CrushingCultivation:
Will installing the recovery image listed here remove TWRP?

firmware.mobi - firmware::8240

desktop.firmware.mobi

When I try to enter into recovery mode with power+volume up+home, the Samsung always boots into TWRP