yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Something is very wrong. I install your rom, but then my device won't boot. It just fails to boot normally after a few minutes of boot animation and then reboots into recovery. I've been doing the normal thing: wipe cache, dalvik cache, system, and data; then install rom. I even tried installing your rom all by itself, with no Magisk or GApps, and it still failed to boot. What's going on here?

I'm using a milletwifi, T330nu. I'm installing your latest build: 6-18. It says milletwifi. No dice. I was able to install LightningFast 14.1 from 8-8-2019, and it booted (but it was buggy). But your rom just won't boot. I think it's defective.
[Galaxy Tab 4 Original Android Development] matteo0026:
Could you give me a logcat while device is booting? Otherwise, I can't be able to see what's not going on.

Inviato dal mio Aquaris X Pro utilizzando Tapatalk
[Galaxy Tab 4 Original Android Development] FailSafeNow:
I'd like to, but when I looked in data/adb, there were no stored logcats. And by the way, I tried to install last month's build, and the result was the same.

Any other way to get you a logcat? I honestly would lke to. And thank you.
[Galaxy Tab 4 Original Android Development] matteo0026:
With computer, plug the tablet with usb cable and give this command from cmd/terminal:

adb logcat > log.txt

It should work. Or if it doesn't, you have to give some other commands while when you are in TWRP, always with PC. Search in internet something like: "logcat android device in bootloop" or something like that.

Inviato dal mio Aquaris X Pro utilizzando Tapatalk
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Quick question. Your initial post mentions "ROM Firmware Required". Does this mean I have to start with stock firmware and then install your rom on top of it? Is it wrong to wipe the system partition before installing your rom? And if I need to install the stock rom and then yours, where can I get it, and can I flash it with TWRP?
[Galaxy Tab 4 Original Android Development] matteo0026:
It means that latest stock firmware you installed must have been based on Lollipop. 5.0.2 for matisse devices and 5.1.1 for millet ones. You must flash my ROM via TWRP and you can come from every ROM, except KitKat stock firmware.

Inviato dal mio Aquaris X Pro utilizzando Tapatalk
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Maybe that's the problem then. I wiped the system partition, along with the usual, and installed that LightningFast rom. Then after deciding that rom was too buggy, I wiped the system partition etc and tried to install your rom. I'm guessing some essential part of the stock firmware needed to still be in the system partition in order for this to work. So... how do I get back on the right track? Do I need to reinstall the stock firmware? And how can I do this via TWRP?
[Galaxy Tab 4 Original Android Development] FailSafeNow:
I tried the terminal command. Result: /sbin/sh: exec: line1: logcat: not found

---------- Post added at 01:10 PM ---------- Previous post was at 01:03 PM ----------

I managed to get dmesg and recovery logs. That's all I could get. Do they help even in the slightest?
[Galaxy Tab 4 Original Android Development] matteo0026:
It isn't needed reinstalling stock firmware. If you flashed lightningfastrom and it was ok, so you just have to flash my ROM via TWRP.

Oh, this is unexpected. Damn, I must buy a used tab 4 or a motherboard to repair mine. Otherwise I can't understand nothing about what's happening, even if some users give me feedbacks and they are all different.

Inviato dal mio Aquaris X Pro utilizzando Tapatalk
[Galaxy Tab 4 Original Android Development] mrk2815:
so far so good with your latest build . have been running it as test for 2 days.

---------- Post added at 11:51 AM ---------- Previous post was at 11:47 AM ----------

maybe jsut get a used tab 4 8 inch off of amazon or ebay. so hta way you can get the tes results as yo uexpet and you can develop furhte when lienage drops support for 16.0 then maybe goign ot t the next build wheneve hta wwould be. You build the best stable builds.
[Galaxy Tab 4 Original Android Development] matteo0026:
Thanks, but buying a used tab 4 8.0 is really unthinkable... Too expensive. I can't find nothing below 70-80€ (even more for the matisse devices)... I wanted to find something for max 30-35€. And the only way to stay in this budget is to buy a motherboard on AliExpress for my T530 (matissewifi).

Inviato dal mio Aquaris X Pro utilizzando Tapatalk
[Galaxy Tab 4 Original Android Development] FailSafeNow:
How do you make an operating system when you don't have the device to test it on?

As for getting millets on ebay, mine was only $40. Oh, but the guy selling it thought it was a T231, and it was really a T330NU. Damn, guess I got lucky.

And what was it that made you say "damn"? What was unexpected?
[Galaxy Tab 4 Original Android Development] matteo0026:
Oh, ehm, "damn" is like when someone is likely very frustrated. It was unexpected that "logcat" binary was not found... It's prebuilt in every build.

The point where I arrived with LOS 16 is just thanks to the S3NEO team and all the tester that tried the builds, starting from DJABHipHop, which has 2 tab 4 (1 milletltetmo (T337) and 1 matissewifiue (T530NU)).

Prices are very high in Italy for this tablet, I can't really realize why this happens. Now I have to decide what to do and I have to understand if I'll still have time to work with Android. I finished school, now it's holiday time, which personally I don't want to use all my days by staying in front of my PC and in next months I'll begin to work. You could understand how I'm feeling.

Inviato dal mio Aquaris X Pro utilizzando Tapatalk
[Galaxy Tab 4 Original Android Development] XRed_CubeX:
And I have sometimes tested some builds :o (my milletlte)
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Ok, this is weird. There's more than meets the eye here. I tried installing your rom all by itself, and then wiping the cache and dalvik, and turning down the offer to install TWRP's app -- and it booted. It actually booted. Why should this be different? I have no idea. Did wiping the caches really make a difference? I wiped them before installation. What could possibly be in them after merely installing an OS? Nevertheless, it booted.

I also got it to boot with GApps installed. Steps: do the usual wipes, install rom, wipe cache and dalvik, reboot into recovery again, install GApps, turn down TWRP app both times, reboot. And it worked. Then I rebooted and installed Magisk, and that worked, too. Now I've rebooted and installed TWRP app, and will it still work? I don't know. It seems to be hesitating. The little circle is forming at one end of the curve and then vanishing at the other end over and over. Could this be it? Something as innocuous as TWRP's official app?

AND WE HAVE FAILURE! You saw it here, ladies and gentlemen! That attempt to install TWRP's official app in recovery broke the operating system! Everything was fine until TWRP's app came along like the atom bomb!

It's strange that TWRP's app would give it problems. This has never happened before. And shoot, I forgot to check if there was a logcat. Anyhow, before I did that, I retrieved the dmesg and recovery logs from a previous failure. Maybe they will help you.

And I did another simple test run, since TWRP's app broke things. I installed your rom, GApps, and Magisk straight in a row, no rebooting in between, and then wiped the caches. Booted up fine. Can't wait to experience this rom -- by reputation the most stable post-Marshmallow rom for a Tab 4.
[Galaxy Tab 4 Original Android Development] matteo0026:
Sorry, I forgot to tell everyone that nobody have to install TWRP app because it breaks the system. I don't know why, but it's this. I'll edit the first post. Next TWRP won't have this app, which is useless, expecially for unofficial builds.

Inviato dal mio Aquaris X Pro utilizzando Tapatalk
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Hi. I have some problems to report afterall. First, and perhaps most crucial, it seems that certain Wi-Fi channels do not work. My older Tab 3 detects 9 networks in the area on channels 149 to 161 (2 on 149, 3 on 153, 2 on 157, 2 on 161.) My Tab 4 can't see any of them. Having ruled out other things, it seems that channels really are the problem. What can I do about this? It's the rom, isn't it? I can't think of anything else it could possibly be. Just to be sure, though, I'll do a boot with all Xposed and Magisk modules disabled. Holy smoke, it boots fast without those! And the result is exactly the same. No access on those higher channels. The problem might affect other channels above 48, too, but I can't tell because there's nothing broadcasting on those frequencies.

So, limited functionality for Wi-Fi. A significant problem.

The other problem is color control. I do my color corrections and get the screen looking nice, but then when I turn the screen off and on again, the corrections are gone. The color sliders are still the way I set them, but they're not getting applied. I have to go back into Settings, then Display, then Live Display, then Color Callibration, and click OK again, every time I turn on the screen, or else it's going to be a sickly green. Is there any way around this? Is there anything I can tell the system not to optimize that will at least keep the colors stable until I reboot? Is there any work-around? Can I have a button that does the same thing as pressing OK, just so I don't have to wade through all those menus?
[Galaxy Tab 4 Original Android Development] matteo0026:
About Wi-Fi, I don't know if tab 4 (msm8226) can support those frequencies, and about color calibration, it's a known issue in Samsung devices. I don't know if LineageOS team will fix it.
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Now I'm intrigued. I want to research this. How can I tell if the tablet supports those channels or not? It appears to support 5 GHz connections at any rate. And I would be very surprised if they took away that support, since my Tab 3 connects to those channels just fine. Why would they downgrade like that?

I'm tempted to Nandroid everything and install a stock rom temporarily just to see if this is true.

Elaboration: According to GSM Arena, "WLAN	Wi-Fi 802.11 a/b/g/n, dual-band, Wi-Fi Direct". I don't know what else to look for here. I think some crucial wifi support has been left off of this rom. If you can show me different, please do. I could be wrong.
[Galaxy Tab 4 Original Android Development] matteo0026:
Test on stock ROM and report me the result. We'll know if we need something specific to put the support or if you just have to give up and connect to another band or to 2.4 GHz WiFi
[Galaxy Tab 4 Original Android Development] mrk2815:
thatt has been wwell documented on lineage threads that note not to install the twrp app or you will have error or and bootloops.i never instal that app .i just do my wipe system, data, cache, dalvik, and format internal storage, then reboot ot recovery, install my rom then rreboot to recovery, install my gapps, reboot to recovery install the root of choice and then reboot the system and wait fore the slow puppy to boot and then go through the set up process.

---------- Post added at 01:29 AM ---------- Previous post was at 01:25 AM ----------

matteo0026, so will you build or will the june 2020 be last build.so i can decide if i want to stick with lineage 16., or reflash from a clean build structure to dj hip hops lightning 17.1 rom. if that does happen.just need to know . as the device just serves as a small media server.
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Well, the results are conclusive. The stock rom can see Channel 153 and connect to it. It doesn't see quite as many of the surrounding channels, but that could just be a matter of reception. 153 is the most important channel for my purposes anyway.

So there it is. The custom rom has a problem with upper wifi channels. This could actually be more roms than just yours. Reinstalling the stock rom with Heimdall took some doing, so before I did that, I tried the Lightning Fast version of Nougat, and it had the same problem.

I have workarounds for the things I need to do. For the colors, I use the LiveDisplay Quick Settings tile. Three clicks -- Night, Automatic, Off -- and I'm back where I need to be. (Couldn't we put in a script that applies the color settings every time the display turns on? Should be easy, shouldn't it?) As for network, my biggest problem was that I needed to extend my wifi range using another device as a repeater, and my software didn't have the option to change channels. Then I discovered VPN Hotspot, which can use any channel I want. The best tool for the job, and it's completely free.

Edit: For the sake of completion, before restoring my Nandroid, I did a clean install of your rom and nothing else. No GApps, no nothing. The network I connected to previously just wasn't there, although my other devices saw it just fine. It's a problem in the rom.

Let me say, though, because this is important, I don't think this is a wholesale case of the 5GHz system not working. The device can see channels 36 through 48, and they're part of the 5GHz spectrum. It's those channels from 149 up where we have problems.
[Galaxy Tab 4 Original Android Development] matteo0026:
Don't worry, I'll build for next months, until lineage 17.1 will get as stable as 16. Or anyway, if I'll build a desktop PC, I'll build either 16 and 17.1. As now, my programs are to just stick to 16.

I remember that low 5 GHz channels worked when I had my tab 4 working (I've bought a new motherboard, so when it'll come to my home from China, I'll restart working on it better), but I was using low 5 GHz bands, so something is wrong with sources, I guess. I'll talk with the other developers of s3neo team. Stay tuned!
[Galaxy Tab 4 Original Android Development] mrk2815:
for now i will stick with your 16. rom.if lineage drops support for 16 and you decide to build 17.1 rom i will test that for you as well. I am running the rom on the samsung sm330nu 8 inch tablet. this is my test tablet so i can help you in any way you need for testing.glad you wont drop support. very happy. i do htis for othe XDA developer hat i have devics for.being ding it when i had the nexus 4, nexus 5 , samsung s4 and s5, and now with nexus 6 and 6p as well other android devices i have here . i have had lots of Android devices I would trade device and give devics away. From nexus, to samsung to htc, to motorola to now one plus .
[Galaxy Tab 4 Original Android Development] Dieselpowerman28:
I tried the 16 in my SM T530NU and it was to laggy for me and there wasnt very much customable options. There was no slide up for the app drawer. I went back to my stock rom. I'm hoping a few things get changed around. I will be watching for updates and ect.
[Galaxy Tab 4 Original Android Development] Advanced07:
No s*** sherlock this is lineage what did you expect
[Galaxy Tab 4 Original Android Development] FailSafeNow:
If you want customizable options, you can get them. Sliding up for the app drawer isn't part of the rom; it's just a launcher. It's Trebuchet. It's an application. If you don't like it, it's easy to install a different one. Personally, I use Nova Launcher on all my devices. There's a free version you can get, or a fancier paid version. Nova has the option to swipe up to open the app drawer. But that barely scratches the surface of all the amazing things it can do. You can customize it to the Nth degree. Or maybe you'd prefer Lawnchair, or some other versatile launcher. It's up to you.

If you want to customize even more stuff, Magisk and the Xposed Framework will extend your capabilities immensely. Once you have those, you can install all kinds of modules. Gravity Box is a popular one. It's a real bag of tricks. It can customize tons of things.

What other options did you want? I bet we can find ways to get them all.
[Galaxy Tab 4 Original Android Development] Dieselpowerman28:
Is there anyway I can get Samsung music? I tried everything. Downloaded of off a modded store and through google play store. And they dont work at all.
[Galaxy Tab 4 Original Android Development] DJABHipHop:
Try Q Pluse i'm always adding new features to Q.
[Galaxy Tab 4 Original Android Development] Dieselpowerman28:
I go to check my root access and it says root not installed. I go to developer options to check the root access is on and it is. Wat is going on?

---------- Post added at 03:13 AM ---------- Previous post was at 02:14 AM ----------

Im having the same issue with my root. Did u get urs to work?
[Galaxy Tab 4 Original Android Development] EngineerMind:
I also have a SM-T530NU, do any other users of this model also feel this 16 rom is laggy on it as opposed to the stock Samsung 5.0.2?
[Galaxy Tab 4 Original Android Development] FailSafeNow:
It's working perfectly on my 330NU. I'm using Magisk. Flash in Recovery and Bob's your uncle. I can't speak about any other root methods. Magisk appears to be the preferred one these days.

Not sure what root method you're using. But give Magisk a try. It will actually have the opposite effect of what you're describing. You'll go into the developer options and it will say root access isn't enabled. But it is. It definitely is.
[Galaxy Tab 4 Original Android Development] Dieselpowerman28:
I installed twrp. And I used odin3 to install the root
[Galaxy Tab 4 Original Android Development] FailSafeNow:
I can't speak to your method. But flashing Magisk in Recovery mode has always worked for me. No Odin necessary.
[Galaxy Tab 4 Original Android Development] mrk2815:
do agree with the rest of the posters.on devices that i have wanted root which lately a days i dont do that much with rooted apps .but when i did , i just flashed the magisk installer after i configured my device in TWRP recovery.
[Galaxy Tab 4 Original Android Development] matteo0026:
Hi guys, I inform you of these things:

- next build will have LineageOS android_samsung_msm8226-common repo instead of S3NEO one.

- next build won't have automatic brightness since device hasn't that feature in stock ROM and at hardware level it doesn't have the light sensor.

- my mobo is on the way, so... For the end of July or at the beginning of August I'll get it and I'll try to fix this offline charging, which a lot of users are asking me to fix it... And I can understand that's very useful!

Bye!
[Galaxy Tab 4 Original Android Development] 123ertoi123:
Hey, I have a T532 Turkey variant with Android 5.0.2. Downloaded lineage-16.0-20200618-UNOFFICIAL-mattise3g.zip, put the md5sum file to the same folder, and flashed via TWRP 3.0.0.

The tablet has been sitting idle. So, even if it bricks, I don't really care.

The error I got:

E3004

E: This package is for device: mattise,mattise3g,mattise3gjv; this device is.

E: unkown command [log]

Updater process ended with ERROR: 7

Error installing zip file '/sdcard/lineage-16.0-20200618-UNOFFICIAL-mattise3g.zip'

Full device Info:

Model number: SM-T532

Android version: 5.0.2

Baseband version: T532JUV1BOJ1

Kernel version: 3.4.0-5931460 dpi@SWHC3703#1

Build number: LRX22G.T532JVS1BQB1

KNOX 2.4
[Galaxy Tab 4 Original Android Development] matteo0026:
Hi, wait before giving up. I'm going to upload you a test TWRP which is for matisse3gjv (which is your device) to see if it lets you flashing the matisse3g (T531) build. It's enough you'll flash it in old TWRP (go to install > select install img button) and when recovery asks you where to install the .img file, select recovery.

I'll PM you in some minutes! ;)
[Galaxy Tab 4 Original Android Development] mrk2815:
matteo0026 cant wait to test your new build when they are ready and available. Just let us know and we will try to test it for you.
[Galaxy Tab 4 Original Android Development] matteo0026:
New update with 2020-07 patches is coming out!

Changelog:

- Switched to official Lineage/android_device_msm8226-common, which is a more clean repo

- Fixed mobile data slowdown

- Switched from ondemand to interactive governor

- Updated GPS part with some CRs and bugs fixed

In these weeks, a user with matisse3g told me that SIM isn't working in his device. I want to know if this problem is present in millet3g too. I'm working on it with a tester, so they will be the last builds that will come out. For now, matissewifi and matisselte builds are online yet, millet devices are coming next!

And about SM-T532 (Turkey matisse3g (matisse3gjv, to be more precise)) is on testing. If someone else has this device, don't worry to ask me more details, even in PM.
[Galaxy Tab 4 Original Android Development] FailSafeNow:
So when the build is available, how do we install? Can we just flash on top of your last rom, or do we have to clean install? And how is the wifi situation looking?
[Galaxy Tab 4 Original Android Development] matteo0026:
Always adviced is a clean flash, but you can do a dirty flash too.

About WiFi, I didn't look at it. But I don't think there could be a solution for that...

Builds are all up since one hour! ;)

I tried to change libsec-ril.so on 3g variants (lib taken from matisse3g stock ROM) to see if SIM works now
[Galaxy Tab 4 Original Android Development] mrk2815:
so its it there.i will gladly flash that one for you. has off line charging been fixed or its on the list of things to resolve. How about camera with the new repo. Does thta work or just limitation of the hardware and device.
[Galaxy Tab 4 Original Android Development] mrk2815:
just flashed july build.so far so good.i will use this for a few days to se what happens.
[Galaxy Tab 4 Original Android Development] matteo0026:
No news about them. The status of that things are unchanged if I don't write anything about them. When motherboard comes to my home, I'll work better. But no, actually no news about it too.

The good thing is that I've fixed SIM reading on 3G matisse and millet. That's one step ahead
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Why couldn't there be a solution for WiFi? The hardware is all there. We have earlier examples of the firmware that could do the trick. And all these things do under the surface is add, subtract, multiply, and compare. Why can't this rom have support for the upper WiFi channels?
[Galaxy Tab 4 Original Android Development] mrk2815:
matteo0026 from all your builds this is one of the best and stable builds.battery life is awsome on this tablet.leave it on fora good 2 to 3 days streaming from spotify to youtube netflix.in due time hopefully the tablet can get love for an android 10 or 11 rom if possible. no rush on that front.this is stable and rock solid in performance and battery life.

---------- Post added at 06:37 PM ---------- Previous post was at 06:33 PM ----------

at least when you do a clean install of this rom, its not bootlooping like another rom for the device in lightning android 10 rom that i tried a few days ago. For stability , for now just ended up coming back to this rom. I always test this rom an the lightning android 10 to se what has changed or broken from time to time to compare one build from the next .
[Galaxy Tab 4 Original Android Development] zebetti:
in the stockrom the flip cover is working natively.

However for this rom I can’t install any apps to use function (screen on/off the flip cover).

Perhaps an issue with the sensor?
[Galaxy Tab 4 Original Android Development] mrk2815:
no i dont think the rom supports it. that is what i am thinking .