yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Original Android Development] ahlugo:
Pls help me, how do you resolve rotation issue in sm-t530?

I first restore in stock later I install lastest twrp -> install lineage 17.1 and rotation stopped working, upgrade to 18.1 with the recomended wipes hoping it would work again, but no.

Do I have to return to stock?
[Galaxy Tab 4 Original Android Development] SteinbeckFan:
Just did a fresh flash of 17.1 with all the recommended wipes. Rotation WORKS. Under Settings, Display, Advanced, Rotation settings, set Auto-rotate screen to on. Rotation should work.
[Galaxy Tab 4 Original Android Development] wizardinio:
i've installed march and january versions for sm-t 531/ Sim card isn't working. but in january update metteo wrote that sim card has been fixed. how fix that?

Or what version should i try with 3g modem working?
[Galaxy Tab 4 Original Android Development] SteinbeckFan:
Just spent the better part of a week troubleshooting Bluetooth. I could pair to my desktop but file transfers would immediately fail. The cause? In the installation instructions:

"Wipe > Advanced wipe > Select system, data, cache and dalvik/art cache (and, if you want to clean more, select even internal storage, which deletes all the content in /sdcard) and do swipe to wipe. When it finishes, go to home page"

What we aren't told is that after the data partition is wiped, it MUST be formatted in TWRP, under Wipe, Format Data. If the data partition isn't formatted, received files have nowhere to go and file transfers will fail.

In changelog_known_issues.txt, a reference is made to /efs/bluetooth/bt_addr. When I browse to /efs in TWRP, there is no bluetooth dir or a file named bt_addr. And yet Bluetooth works. So don't know what that's all about.
[Galaxy Tab 4 Original Android Development] chalofito:
I confirm!!! this version is the best build for battery consumption and I don't have unexpected reboots like later versions.
[Galaxy Tab 4 Original Android Development] moji2013:
I can't use simcard on t531 3g also

Doesn't detect i've inserted a new simcard

Idk which build works with simcart just mention it if you figured it out
[Galaxy Tab 4 Original Android Development] SteinbeckFan:
The problem was on my end and not with the build. When adding a new Wi-Fi network, under Advanced options, a hidden network can be specified. Still that didn't work. Using a 5GHz band, and using a lower control channel, suddenly things worked. Maybe it's my funky Asus router. All I know is that both 2.4 and 5GHz band ssid's are hidden, and I can connect to either one now. I prefer the 5GHz band as it's less crowded and the transmit link speed is 150 Mbps, which is over double the speed of 2.4GHz, which seemed really sluggish.

Some people say that hiding the SSID doesn't add much to Wi-Fi security. Still, I prefer not to advertise my Wi-Fi to the casual hacker. I use WPA2 with a very long and complex key
[Galaxy Tab 4 Original Android Development] Gene-13:
Is that correct to assume that the battery drain problem (affected versions are 2022.02 and 2022.03) is not solved in this build?
[Galaxy Tab 4 Original Android Development] JoseJavierCM:
I am waiting for some brave person to verify that the battery life is normal to update, while I stay in 20220120.
[Galaxy Tab 4 Original Android Development] moji2013:
How do you guys update? I do a clean install each time with new builds

Is there a way to download the new builds and update via twrp recovery ?
[Galaxy Tab 4 Original Android Development] matteo0026:
I haven't tested the builds, but you are the first one to report drains. So, be sure to start in a clean way before updating your tablet.
[Galaxy Tab 4 Original Android Development] p3pp8_bis:
Nope, almost everyone of us who tested new builds can confirm a huge battery drain. Going back to january build solves the issue.
[Galaxy Tab 4 Original Android Development] matteo0026:
Sources side, I haven't touched anything since that build, except for the startup time, where I've slimmed down the init stuff
[Galaxy Tab 4 Original Android Development] p3pp8_bis:
OK, so i think we need to try with a clean installation, as you suggested.
[Galaxy Tab 4 Original Android Development] Gene-13:
I'm definitely not the first one who reports the problem. Page 14 of this thread since #262 is full of it. I even intentionally didn't report it myself to avoid flooding.

The problem: the battery discharges in less than a day (compared to more than 7 days before). It discharges not linearly, but in several discrete steps, i.e. it might take some hours before it gets to 92% and then it jumps rapidly to 48%, then it again takes some hours before it makes another jump to less than 10%.

Affected versions: 2022.02, 2022.03 (both tested myself) and probably 2022.04 (not tested myself).

Clean install doesn't help, tested myself and by others (e.g. by JoseJavierCM, s. #262).

Going back to 2022.01 (dirty flash) solves the problem.
[Galaxy Tab 4 Original Android Development] Gene-13:
What exactly did you remove? Could you provide a link to the git commit(s)?

If it would be a problem resulting from merging some Lineage changes I would expect my other Lineage-18.1 devices would also be affected (have three other devices with Lineage-18.1) - but this is not the case. So the problem should result from some matisse* related changed.
[Galaxy Tab 4 Original Android Development] matteo0026:
https://review.lineageos.org/c/LineageOS/android_device_samsung_msm8226-common/+/325314

This is the commit where I've touched something more.
[Galaxy Tab 4 Original Android Development] Gene-13:
It's quite hard to review this commit because it contains quite a lot of less related changes ("CPU properties, hardware initialization", "failing commands"). But because of the following keywords "CPU", "power", "cpufreq/scaling_min_freq" I would say the likelihood it's the cause of the problem is very high.

Could you please revert this commit completely and provide us a build with this commit reverted so that we are sure it's the cause. If so we can then go through all the changes from this commit and discuss every single one (I should however say that I'm not familiar with android development but with development in general).

The questions arising from a quick view:

1. Why should the hardware be configured on "boot_completed" instead of on "init"? What about the processes starting before "boot_completed", why should they access "unconfigured" hardware?

2. Why did you remove the two "cpufreq/scaling_min_freq"-related lines?

p.s. From the development point of view it would be better if you split this commit in multiple ones. Every single commit should be as small as possible addressing one single problem/issue, e.g. "remove command 1 as it fails and not necessary on this device", "fix command 2 fails" (instead of removing it), "move hardware configuration from init to boot_completed" (provided this is really the right thing to do), etc.
[Galaxy Tab 4 Original Android Development] moji2013:
I'm also experiencing huge battery drain + t531 not detecting sim card (page 14)

I installed ( cleaned installed ) february build ( latest build before april )

i charge tablet up to 100% then close all running apps and lock it

but after 6 hrs it just drops to 20%
[Galaxy Tab 4 Original Android Development] ginodman:
No battery drain for me
[Galaxy Tab 4 Original Android Development] moji2013:
Looks like my tablet doesn't go into deep sleep mode

T531 running on february build

which build are you using? ( is it april build?)
[Galaxy Tab 4 Original Android Development] ginodman:
Yes , the latest april one. March was also OK
[Galaxy Tab 4 Original Android Development] moji2013:
just did a clean install with april build

after installing the build

when i go to file manager > internal storage is just NOT there

when i connect tablet to pc via cable there is NO internal storage listed

can't even take screenshots in tablet saying couln't save screenshots

what did I do wrong? always did a wipe before installing

clean install == wiped everything ( except micro SD and otg )

connected tablet to pc via cable

coppied zip file

and installed

-----

update:

when i boot into recovery mode and connect tablet to pc everything works fine == internal storage is listed

---

update 2:

just tried it with january and march build still problem with internal storage not showing up

I mean did I do something wrong? I always wipe everything before doing a clean install
[Galaxy Tab 4 Original Android Development] matteo0026:
I've found the issue. By touching the ramdisk, CPU governor is set to performance instead of interactive. I'll fix it in the next build.
[Galaxy Tab 4 Original Android Development] SteinbeckFan:
Please read my post #282. It solves your problem. You need to format the internal storage with twrp.
[Galaxy Tab 4 Original Android Development] moji2013:
Thanks man , i mean your installation guide in post #282 MUST be added to first page

After wiping did a format just as you said and everything works fine now

You just made my day thank U
[Galaxy Tab 4 Original Android Development] moji2013:
What about sim card issue in t531?

Sim card ia not detected by tab
[Galaxy Tab 4 Original Android Development] Gene-13:
Could you please provide a bit more information? What exactly do you mean by "by touching the ramdisk"? Is it something happening at runtime or do you mean the kernel configuration, i.e. adjusting the ramdisk settings changes the governor related ones?
[Galaxy Tab 4 Original Android Development] moji2013:
T531 april build

Seems like issue is solved on this build, tablet does go into deep sleep mode

Haven't had the time to see for myself about charching durability since i just did a clean install yeasterday

But here is a screenshot (compare it to page 15 february build)

Just be sure to format data after wiping everything in twrp under wipe menu (post #262)

But sim card is still not detected in this build
[Galaxy Tab 4 Original Android Development] matteo0026:
Is it detected in the previous builds?

What I meant by saying "touching the ramdisk" is that I edit some files called init.*.rc (mainly, init.qcom.rc). These ones tell the device what to do in different boot stages, like starting some services or setting different properties. Now probably, instead of setting to interactive governor, tab stays into default performance one.
[Galaxy Tab 4 Original Android Development] moji2013:
I've only tested february and april build and these two builds don't detect sim card
[Galaxy Tab 4 Original Android Development] moji2013:
April build deep sleep update:

After a clean install right after booting to os everything worked fine and tablet did go to deep sleep post #308

But after first restart tablet doesn't go to deep sleep anymore (screenshot below )

Figured it might help with your troubleshooting in the next build
[Galaxy Tab 4 Original Android Development] Gene-13:
To be honest I still don't understand why you've used the words "touching the ramdisk" - I don't see any ramdisk related changes in 325312, 325313, 325314 (these are the recent commits you've changed the init.*.rc files in).

I would however like to point out what I see in 325314 and what I mean could be the reason for the reported problem.

You've renamed the property to react on from "dev.bootcomplete" to "dev.boot_completed". There is however no such property as "dev.boot_completed", its correct spelling is "sys.boot_completed" (i.e. sys and not dev). The correct spelling was used in init.qcom.power.rc line 143, but while merging the content of init.qcom.power.rc and init.qcom.rc you've changed "bootcomplete" to "boot_completed" but forgot to change "dev" to "sys".

Provided my analysis is correct all the lines after "on property:dev.boot_completed=1" are simply not executed.
[Galaxy Tab 4 Original Android Development] moji2013:
April build deep sleep update 2:

I powered off the tablet (to keep batery from draining) and booted it up about 7 hrs ago

Now deep sleep works (screenshot below)

IDK for sure but i think maybe problem you mentioned occures on RESTARTS only and not on powering tablet on
[Galaxy Tab 4 Original Android Development] grindim:
GPS is not working. Caught satellites on the stock firmware, but don’t want on this one, I flashed the stock back, it works.
[Galaxy Tab 4 Original Android Development] miquatro:
Why is there no cpu hotplugging driver in this? Im on Tab4 SM-T330NU and all the cpu cores are always active and is using a lot of battery on idle. even lineage 16 and 17.1 dont have cpu hotplugging, only cm12.1 and 14 have cpu hotplugging. Is this problem just for me??
[Galaxy Tab 4 Original Android Development] Gene-13:
All releases since 2022.02 / all LOS-Versions (16, 17, and 18) are broken - misspelled property name dev.boot_completed instead of sys.boot_completed. Use the January 2022 release until a fixed build is published.
[Galaxy Tab 4 Original Android Development] miquatro:
Omg thank you so much!! The jan release works!! and the battery is waaay better!! Thanks!! :))
[Galaxy Tab 4 Original Android Development] deetateron:
I have installed the 20220120 ROM and my wifi connection is not working on the initial setup. When I try to skip it, I get stuck on the Just A Sec Screen for hours. Please Assist.
[Galaxy Tab 4 Original Android Development] moji2013:
Did you wipe everything? (Even the internal storage? )
[Galaxy Tab 4 Original Android Development] Tony_320:
somebody did this on sm t533 device (matisevewifi) i have problem with find rom with android 11
[Galaxy Tab 4 Original Android Development] davestuarts:
I havent't had to use my tablet for a month or so, but needed it now. As the battery is still an issue, I've dirty flashed flashed back to the Jan build from March build, as others have and all seems fine. It's mostly security patches, so I'm in no rush although security is important.
[Galaxy Tab 4 Original Android Development] MorganShady:
guys, for the moment you can try to download naptime from google play store and enable aggressive doze (needs permission via adb), i use the latest build and with this app, the battery drains less fast.
[Galaxy Tab 4 Original Android Development] deetateron:
Yes I did. Got around it by disabling the Google Initial Setup APK.
[Galaxy Tab 4 Original Android Development] SteinbeckFan:
deleted
[Galaxy Tab 4 Original Android Development] hamstrings:
Greetings,

I tried to connect my wired Xbox 360 controller but (while I am not experienced in Android development) I suspect the xpad driver is not part of the kernel.

GitHub - paroj/xpad: Linux Kernel Driver for the Xbox/ Xbox 360/ Xbox One Controllers

Linux Kernel Driver for the Xbox/ Xbox 360/ Xbox One Controllers - paroj/xpad

github.com

If this is the case, can we get the xpad driver in the next build? In the meantime I can attempt to build kernel modules for myself but I assume others may find it useful as it is a feature taken for granted on most other Android devices out of the box.

Respectfully,

hamstrings
[Galaxy Tab 4 Original Android Development] moji2013:
It's been almost two months

I was kinda wondering why there are no new builds being published after april one?

For battery issue i kinda wanted to switch to january build which didn't have deep sleep issue but peoblem is my tab is 3g uses sim cart and i get stuck on the startup page saying insert simcart and there is no skip button on that build

I hope you understand why i'm desperately checking for new builds
[Galaxy Tab 4 Original Android Development] JoseJavierCM:
I think it is a problem of gapps and not of the rom, try to install the rom without gapps and if everything goes well look for other gapps to see if it solves it.
[Galaxy Tab 4 Original Android Development] moji2013:
I've tested january up to may builds

One thing i've noticed may build is like january build cpu switches between diff clocks but doesn't go to deep sleep even when all apps are closed ( screenshot below)

But in april build device did go to deep sleep sometimes but only worked at full clock or deep sleep ( screenshot below)

What i'm trying to say is that is it normal if device doesn't go to deep sleep? In may and janiuary build

Tab 4 10.1 t531

Update:

Deep sleep works see post #333
[Galaxy Tab 4 Original Android Development] matteo0026:
So, the commit that I've done wasn't that wrong, but it needs some more work. That's because I've excluded it from this build. At least it doesn't drain that much while the device is in use.
[Galaxy Tab 4 Original Android Development] Cyntil8ing:
Trying to download the 530NU. I'm getting "No mirrors found".
[Galaxy Tab 4 Original Android Development] omiFast:
mee too ..
[Galaxy Tab 4 Original Android Development] moji2013:
Maybe i judged too soon

Been testing it for the last two days

Thing is after closing all apps cpu imediately switches to 300mhz clock

And it takes more time for device to go into deep sleep

So deep sleep works but maybe its better to say it requires more time of inactivity to be enabled
[Galaxy Tab 4 Original Android Development] matteo0026:
Ok then, if it works, it's fine. If it takes more to be enabled, probably some apps require CPU to do some actions that keep it up, and not deep sleeping. It's possible, it isn't a problem
[Galaxy Tab 4 Original Android Development] matteo0026:
I'm going to upload the builds on Telegram because on AFH mirrors aren't present. I've checked right now. The link is in the first post. Thanks @Cyntil8ing and @omiFast for reporting me it too.
[Galaxy Tab 4 Original Android Development] andreas__:
Thanks, download via telegram worked.

Deep sleep working within seconds after screen off.

But when ADB is connected, it will stay at 300 MHz. But I guess this is normal.

So thank you again for your new release!
[Galaxy Tab 4 Original Android Development] matteo0026:
If you are connected via ADB (I guess with a cable), every device when is in charging mode, it doesn't go deep sleep.
[Galaxy Tab 4 Original Android Development] juma93:
Hi, thank you for your work!

I'm trying to understand how to replicate the build procedure in order to add some patch to enable signature spoofing needed by MicroG (as I'm having issues with the "easy" Magisk+LSPosed+FakeGapps path).

Do you have some Docker container, or some script to collate the repos, or just a repo to clone to use as an entry point, to then follow the usual LineageOS build procedure?

Thank you!
[Galaxy Tab 4 Original Android Development] Tres_Tigers:
Am I correct to assume from the pictures, that the Chipset is not getting an overclock?

Asking as the specs of this Tablet are terrible for even Android 5, so not having any sort of boost and just a OS change doesn't sound good at all.
[Galaxy Tab 4 Original Android Development] paschoaal:
Hello Matteo and everybody,

thanks for the hard work here.

I was able to get everything running except the 3g / Sim card issue

I have a SM-T531, brazilian version. This means official support only went so far as to the 4..4.2.

This other XDA thread kept me from trying to flash your ROM straight from 4.4.2: https://xdaforums.com/t/trouble-flashing-lineage-os-14-1-on-sm-t531.3664109/

So, I had to search for the 'samfirm' software and find a suitable 5.0.2 to start the process with.:

Having done that, I did install a couple of your builds. A newer one from April 2022, and another from October 2021. In between those, I found a comment from you in this thread, in which you say you got the Sim Card issue fixed. https://xdaforums.com/t/rom-unofficial-matisse-millet-lineageos-18-1.4292943/page-11#post-86296201

So I went to Android File Host and got yours "lineage-18.1-20220120-UNOFFICIAL-matisse3g" from the T531-T532 section but... the Sim Card is still not recognized, as if it had never been inserted.

This Sim Card works normally on my personal phone. Also, and more important, it worked on the very tablet, the T531, with Stock Android 4.4.2, and also with the intermidiary upgrade to Android 5.0.2. So, I guess, it's not the Sim Card, nor the slot.

I also found Jonathan Mohammed's Modem Rom, published way back in 2017. I tried to install it from recovery mode, but it broke the system and I had to re-install Lineage.

So, everything is great, except for the Sim Card / 3g / mobile phone functionality.
[Galaxy Tab 4 Original Android Development] Grim1:
do you have another source? I get no mirrors on the download. other files works fine. just not the OS itself
[Galaxy Tab 4 Original Android Development] matteo0026:
In the first post, there's the link to download the builds in telegram, which are not available in afh
[Galaxy Tab 4 Original Android Development] Xandireczek:
Could someone please upload twrp-3.6.2_9-0-matisse.zip? Because afh still does not see mirrors
[Galaxy Tab 4 Original Android Development] matteo0026:
I'll do that as soon as possible. I'll post in the right thread when they'll be uploaded on my telegram channel.
[Galaxy Tab 4 Original Android Development] maleadt:
The Telegram channel has TWRP builds for matissevewifi (SM-T533), but I can't find a ROM for this particular piece of hardware. Is there no such ROM / are the builds compatible (the installer script refuses to flash) / am I SOL?
[Galaxy Tab 4 Original Android Development] matteo0026:
I confirm you that no builds are available. Unfortunately, I don't have that much time and knowledge to get an enough stable build.
[Galaxy Tab 4 Original Android Development] Strizay:
Is Android 12 in the works? Does everything function on this rom at this point? Is the latest Android version on this rom 11?
[Galaxy Tab 4 Original Android Development] moji2013:
Bro its way better than stock android 5

Its android 11 i think
[Galaxy Tab 4 Original Android Development] matteo0026:
I've tried to build android 12, but it doesn't boot. Android 11 I guess it'll be the end for the Tab 4, as a lot of more legacy devices.
[Galaxy Tab 4 Original Android Development] d_a_ugono:
How does the S2 manage to run Android 12 then despite being much older than the Tab 4? Many other legacy devices also have Android 12 ROMs.
[Galaxy Tab 4 Original Android Development] jimVmax:
Hi

Any links for the

lineage-18.1-20220611-UNOFFICIAL-matissewifi.zip​

Download please link is not working..

( Job sorted... I found your Telegram page, its all updated and working well. )

With thanks and keep up the good work..

Take care

J
[Galaxy Tab 4 Original Android Development] Tres_Tigers:
That is because Android 12 requires a 64 bit CPU and the SOC in the Tab 4 only supports 32 bit.
[Galaxy Tab 4 Original Android Development] Tres_Tigers:
This is be cause they have a 64 bit chip, the Variant that received the Android 12 ROM, has a Exynos 4210 Dual CPU.

From a quick glance around the internet, I've seen that it is 64 bit, so it is absolutely able to run Android 12.

This Tablet and many other Android devices before 2016, only have a 32 Bit CPU, so they can not run Android 12 and onwards.
[Galaxy Tab 4 Original Android Development] d_a_ugono:
That's cap. S3 Neo has the same processor as the Tab 4 10.1, and that has an Android 12 ROM.

Exynos 4210 Dual isn't 64-bit.
[Galaxy Tab 4 Original Android Development] Tres_Tigers:
I don't know as to how they did it then, but Android 12 requires a 64 Bit CPU, it does not support 32 like older versions did.

It might be possible to force the 64 but os to run for a 32 bit soc, but I don't build or mess with roms, so it's probably way easier said than done.
[Galaxy Tab 4 Original Android Development] berik_t530:
Hello Matteo,

I have tried since yesterday to download your image for SM-T530 - unfortunately without success. File: lineage-18.1-20220611-UNOFFICIAL-matissewifi.zip - but I always get an error message "OOPS! no mirrors found. ", could you please check and correct ?

Thanks in advance!
[Galaxy Tab 4 Original Android Development] moji2013:
Page 1 use mirror which is on telegram channel
[Galaxy Tab 4 Original Android Development] mma151:
Hi

thanks for your time, I appreciate it

I installed the matisse3g but simcard doesn't recognized

it's a common problem?