yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Original Android Development] cbouillot:
the value is not reliable. The device turn off as the battery is 80 % and need to be plug
[Galaxy Tab 4 Original Android Development] matteo0026:
It isn't a problem of the ROM, it's a problem of your battery. I can get 1% without any problems
[Galaxy Tab 4 Original Android Development] vauzwoo:
Hi matteo, thank you for your great work. Please, I need your help. My WiFi does not connected to my router.

With the ROM 17.1 it`s not a Problem.

Setting the router is WPA2 + WPA3.

Why does not connected on LOS18.1?

What can I do?
[Galaxy Tab 4 Original Android Development] matteo0026:
Probably, the issue can come from the wifi module that it has been built as a module in 18.1. From next build, I can make a kernel with wifi module built in, since I can separate the ROM kernel from the recovery one (otherwise, recovery image didn't fit in its partition).
[Galaxy Tab 4 Original Android Development] Donzi84:
Hi matteo, great work! only 2 problems:

- magnet tablet doesn't recognise original samsung cover

-doesn't recognise 5GHz band wi-fi.

God bless you

Stefano
[Galaxy Tab 4 Original Android Development] matteo0026:
Hi, magnetic sensor doesn't work properly, it's written in known issues. WiFi 5 GHz works fine, I show you in a picture.

Another detail I can give you is that I'm using channel 56 in 5 GHz.
[Galaxy Tab 4 Original Android Development] Donzi84:
Hi Matteo,

to properly works fine 5GHz I switch on off wi-fi bottun many times. I don't now why, I think it's just slowness.

Thank you so much.

Stefano
[Galaxy Tab 4 Original Android Development] Donzi84:
Hi Matteo, have you any experience with battery charge limit app? It was works with standard Room but with your 18.1 not anymore. Could you please help me?
[Galaxy Tab 4 Original Android Development] matteo0026:
You mean ACCA magisk module? I don't know in that case how to make it working. I think it doesn't depend on the ROM, by the way.
[Galaxy Tab 4 Original Android Development] Donzi84:
I mean "battery charge limit" app. Is an app that block the charge at a request level. 80 per cent for example. Don't you use it?
[Galaxy Tab 4 Original Android Development] matteo0026:
Nah, I've never used these apps. By the way, the best app to do this thing is ACC (advanced charging control) magisk module, with even its app ACCA (advanced charging control app) that you can find on f-droid: https://f-droid.org/packages/mattecarra.accapp/
[Galaxy Tab 4 Original Android Development] Donzi84:
I've installed ACC. Did you test ACC in tab 4? What control file do you use?

Thanks in advance

Stefano
[Galaxy Tab 4 Original Android Development] matteo0026:
I've never tested ACC in Tab 4. As I said before, I've never used these apps. By the way, you can control the charging in pretty every possible way. And to help yourself to setup the environment, use the app ACCA
[Galaxy Tab 4 Original Android Development] Achsel:
For testing purposes I installed the ACC Magisk module and the ACCA app on a Tab 4 (SM-T530) and set the charge limit to 80% in the settings. The charging indicator goes out, but charging continues anyway. I finished the test at 85%. On a Galaxy S4 phone with LineageOS 18.1, however, the charging process is correctly terminated at 80%.
[Galaxy Tab 4 Original Android Development] matteo0026:
Ok, alright, then something should have be fixed in the kernel sources. I don't know what, by the way
[Galaxy Tab 4 Original Android Development] rodunks:
Incredible upgrading from Android 5 to 11.. no problems with opengapps. Only thing that may or may not be a relevant issue is Onedrive says it cant connect, even though browser works. Not going to worry about it though, just happy to see it hasn't slowed down at all and the ram usage is less than 1gb.
[Galaxy Tab 4 Original Android Development] Donzi84:
I've testet ACC in Tab 4 8" and works fine. Charging stopped at 80% automatic. A question: when I push home button the tablet wake up in the desktop page closing the old app opening. Do you a method to push home button and wake up the tablet without going to desktop page?

God bless you

STefano
[Galaxy Tab 4 Original Android Development] matteo0026:
I don't think there's a way to do it. You can simply wake up the tablet with power button and you won't go to the home page
[Galaxy Tab 4 Original Android Development] Achsel:
@Donzi84

As already described in my Post 82, the ACCA app switches off the charging symbol in the display on my Tab 4 with 10", when reaching the 80% limit, but the charging is not stopped with connected charger as it is on my S4 phone. Can you leave your Tab 4 with 8"on the charger for longer after reaching the 80% limit to test whether charging is really stopped completely?

It greets you

Axel
[Galaxy Tab 4 Original Android Development] Donzi84:
You have right. The charge doesn't stoped. Have you a solution? With the original ROM I've used battery charge limit app e it was working.

Thanks

Stefano
[Galaxy Tab 4 Original Android Development] Donzi84:
Hi Matteo, I've tested better Acc and it doesn't stop charge on tab 4 sm t335. Could you please test Acc acca on your tablet e let us know if it works fine? Keep your device in charge for long period after percentage you set.

God bless you
[Galaxy Tab 4 Original Android Development] Achsel:
As matteo0026 wrote in Post 83, something in the kernel sources should have to be fixed, perhaps a missing driver for battery charging in the deconfig file or something else. However, I do not have the knowledge to do this. Here is the link to the deconfig file from the Samsung Galaxy S4 phone with LineageOS 18.1, with which ACC/ACCA works.

https://github.com/LineageOS/androi...-18.1/arch/arm/configs/lineageos_jf_defconfig

It would be even better to compare the kernel sources from Android 5.0.2 ROM with those from LineageOS 18.1 regarding battery and charging, which would involve a lot of effort. So I don't think there is a simple solution for automatically turning off the charging function at 80% for the Tab 4 (for example: SM-T335 and SM-T530).
[Galaxy Tab 4 Original Android Development] matteo0026:
I'll inform you about this.

I didn't remove any charger drivers, and I can't make a comparison between Tab 4 and S4 because they have completely different hardware. The best thing is to do a research on ACC and understanding what is needed to make this controller working properly.

doesn't stop charging and some bugs · Issue #114 · VR-25/acc

continueschargeacc-logs-tulip.tar.gz.zip i set a limit where it should stop charging on 70% but still continue to charge. although it doesn't appear to be charging at a glance but on closer look wh...

github.com

This issue can explain even how to make this controller working if in kernel there isn't a support for charging status.
[Galaxy Tab 4 Original Android Development] Achsel:
@matteo0026

Thank you for the link:

https://github.com/VR-25/acc/issues/114

@Donzi84

Installation ACC ZIP file via Magisk:

Copy the ZIP file into the "/storage/emulated/0/Download folder", start Magisk, click on module symbol, then on "Installation from storage" in the top and choose the ZIP file. I tested these two versions, but it doesn't stop charging at 80%.

acc_v2021.8.4_.202108040.zip (Tip from kevin01523 in the first post)

acc_v2021.9.12_(202109120).zip

So I'm waiting for the new build from VR-25.
[Galaxy Tab 4 Original Android Development] Donzi84:
Hi Achsel,

did you try acc_v2021.9.13_(202109130).zip? does it work with Samsung tablet? Does it stop the charge?

Thanks

Stefano
[Galaxy Tab 4 Original Android Development] Achsel:
Even with this version the charging of the Tab 4 with 10.1" is not stopped at 80%. So I wait to see if VR-25 finds an issue in your log file and can fix it.

Thanks

Axel
[Galaxy Tab 4 Original Android Development] Achsel:
@Donzi84

Even with the versions 16.1 – 16.4 the charging of the Tab 4 with 10.1" is not stopped at 80%. As a result, I no longer have much hope, that VR-25 can fix the issue. He hasn't even commented on your log file.
[Galaxy Tab 4 Original Android Development] Donzi84:
the same for me, 16.1 doesn't work. for me is a rom problem, withn the original rom rooted battery charge limit worked well
[Galaxy Tab 4 Original Android Development] FailSafeNow:
I was out on the road today, and I was trying some GPS applications. They couldn't find anything. They had no clue where I was. Has anyone else had this problem? I want to rule out the rom before I go crazy with anything else.
[Galaxy Tab 4 Original Android Development] matteo0026:
GPS works fine. No doubts. I've just tested right now and I got as best precision 3 metres. The only thing is that you have to wait about 1 minute and it's better you are outdoor.
[Galaxy Tab 4 Original Android Development] Donzi84:
it'a a authorizations problem, reinstall the rom and install the gapps immediatly first of start lianage
[Galaxy Tab 4 Original Android Development] Donzi84:
with VR-25 we are arrive to define a kernel problem. Is kernel in the lineage rom?

Thanks

STefano
[Galaxy Tab 4 Original Android Development] Donzi84:
Is it possibile match original kernel with lineage kernel?

SM-T335 | Samsung Galaxy Tab 4 8.0 | PDA/AP Version: T335XXU1BOH1 | Firmware for Region: HUI from ITALY | ID - SM-T335_1_20150819180000_jubgub5sn7 - Sfirmware.com

Samsung SM-T335 Download the latest version of firmware | CSC Version: T335HUI1BOH1 | Firmware version: T335XXU1BOH1 | HUI | ID - SM-T335_1_20150819180000_jubgub5sn7 - Fan club Sfirmware

sfirmware.com

hereby the original rom.

Thnaks in advance

Stefano
[Galaxy Tab 4 Original Android Development] FailSafeNow:
How do you know? I'm willing to try, but I'd like to be sure before I do.

I've installed GPS Status, and the thing gets stuck at "Looking for GPS Location". Is this an authorization problem, like you said? How can I be sure?

Follow-up question: Do I need to wipe Data when I do this? I'll do it if I have to, but, you know, just makes everything that much more work.

Follow-up follow-up: I usually install GApps at the same time that I install the ROM and Magisk. I install all three and then reboot. Is that wrong?
[Galaxy Tab 4 Original Android Development] Donzi84:
- open terminal on smartphone (activ it with developer options)

- write: su press enter

- write: dumpsys package com.google.android.gms | grep -A 30 runtime

let me know if all your permission are true or someone is false
[Galaxy Tab 4 Original Android Development] matteo0026:
It could be even a kernel issue, but who knows which one is... I really don't know!
[Galaxy Tab 4 Original Android Development] Donzi84:
SM-T335 | Samsung Galaxy Tab 4 8.0 | PDA/AP Version: T335XXU1BOH1 | Firmware for Region: HUI from ITALY | ID - SM-T335_1_20150819180000_jubgub5sn7 - Sfirmware.com

Samsung SM-T335 Download the latest version of firmware | CSC Version: T335HUI1BOH1 | Firmware version: T335XXU1BOH1 | HUI | ID - SM-T335_1_20150819180000_jubgub5sn7 - Fan club Sfirmware

sfirmware.com

Is it possible match the kernel of the original version (attached) with kernel of lineage 18.1?

thanks in advance

Stefano
[Galaxy Tab 4 Original Android Development] FailSafeNow:
I wish I knew how to automatically output that to a text file. But...

"granted" appears to be true on all permissions.
[Galaxy Tab 4 Original Android Development] Donzi84:
in developer option active gnss option.

let me know if this solve the problem
[Galaxy Tab 4 Original Android Development] FailSafeNow:
I didn't see any improvement. Now, I'm indoors. I don't know whether that matters. Also, to be sure, I restarted my tablet after making the changes. Was that necessary?

Now, before I restarted, I think my device was actually seeing satellites. GPS Status was showing what appeared to be satellites. And it has a ratio in the corner: "Fix/Sats." It was giving me 0/9, then later 0/12. Just right now, it's not seeing anything. So heck, I don't know what its deal is.

Thinking of getting an external, bluetooth GPS locator, though. (Also been thinking of getting a new damn tablet.)
[Galaxy Tab 4 Original Android Development] matteo0026:
The kernel that I use starts from that base, with linux upgraded version from 3.4.0 to 3.4.113, some more security patches, various fixes adaptions to make it working on LineageOS. I think it's better you ask to VR-25 which driver I should enable in the kernel defconfigs to get that engine working. Or if the charging driver needs some patches. I don't know.
[Galaxy Tab 4 Original Android Development] Achsel:
@matteo0026

Could you publish the contents of the current kernel deconfigs file for the SM-T530 (Matisse) and LineageOS 18.1. Then we could compare this with the deconfigs file for the S4 phone, where ACC works.

https://github.com/LineageOS/androi...-18.1/arch/arm/configs/lineageos_jf_defconfig

Thanks in advance!

Axel
[Galaxy Tab 4 Original Android Development] matteo0026:
android_kernel_samsung_msm8226/arch/arm/configs/lineage_matissewifi_defconfig at lineage-18.1 · LineageOS/android_kernel_samsung_msm8226

Contribute to LineageOS/android_kernel_samsung_msm8226 development by creating an account on GitHub.

github.com

I don't know if it can be helpful, but give a try
[Galaxy Tab 4 Original Android Development] Achsel:
@matteo0026

The Tab 4 has apparently integrated the SMB358 chip from Qualcomm for power management. You have already activated the driver in the deconfig file with correct spelling here:

3673 CONFIG_CHARGER_SMB358=y

Written in the wrong order, but deactivated, the driver is here again:

2263 # CONFIG_SMB358_CHARGER is not set

When I compared two other deconfig files for the matisse, I noticed that two drivers for power management and for the LCD display are not activated in your deconfig. Perhaps the activating will bring something to let work the ACC app.

2996 # CONFIG_SAMSUNG_DEBUG_DISPLAY is not set

4077 # CONFIG_SEC_PM_DEBUG is not set

https://git.sphere.ly/twrp/android_...mmit/d7a4bfa9a791e4d6e881ffffa38c4e860f52c594

https://github.com/S3NEO/android_ke...arm/configs/msm8226-sec_matissewifi_defconfig

It greets you

Axel
[Galaxy Tab 4 Original Android Development] Nimakea:
This rom is awesome but there is a big problem in both lineageos and crdroid.and that is boot speed in t331(i dont know if it is on other models)

It took 48 seconds to pass galexy tab logo

And took 19 seconds to pass lineageos and crdroid logo.

(In total that took 67 secounds and thats so bad .) Please fix it if you can☹️
[Galaxy Tab 4 Original Android Development] matteo0026:
Try the boot.img I've posted you. I've enabled CONFIG_SAMSUNG_DEBUG_DISPLAY and CONFIG_SEC_PM_DEBUG.

CONFIG_SMB358_CHARGER doesn't neither compile. I think it should be fine to keep just the first config. Remember that the boot.img I've made is for matissewifi.

It can't be fixable. ROMs are heavy, so they take long to boot. Situation gets worse every Android version. If you try LOS16, for example, it fully boots in less than 50 seconds.
[Galaxy Tab 4 Original Android Development] matteo0026:
Anyway, new LOS18.1 builds are online!

Changelog:

- September 2021 security patches

- Fixed minimum brightness, now it's really at its lowest point

- Re-enabled Wi-Fi display functionality (before it was disabled because it wasn't supported on legacy devices)

- New recovery with a dedicated defconfig

- Some other more specific things under the hood
[Galaxy Tab 4 Original Android Development] Achsel:
@matteo0026

I converted the boot.img file to boot.tar using 7zip and flashed it using Odin. Afterwards, WLAN no longer worked on my SM-T530 (matissewifi). So I canceled the test for ACC and restored my system backup via TWRP. Then I flashed the new LineageOS update via TWRP. After that, I initially no longer had root rights. So I also had to re-flash Magisk-v23.0.zip, which was not necessary with the August update. ACC does not work with the latest updates from LineageOS and ACC either. I will not do any further tests with ACC. Everything else seems to be working.

Thank you for your support.

Axel
[Galaxy Tab 4 Original Android Development] matteo0026:
To make wifi working with that boot.img, flash September build before. And it wasn't necessary to make a tar file, since you can flash img through either twrp (embedded function install image) and lineage recovery (via fastboot)
[Galaxy Tab 4 Original Android Development] Achsel:
@ matteo0026

Thanks for the tip. Does it make sense to patch the boot.img file beforehand with Magisk and then flash it as magisk_patched-23000_xxxxx.img via TWRP in order not to lose the root rights? But I won't have time to test it until next week.
[Galaxy Tab 4 Original Android Development] matteo0026:
It can have a sense, but I always go in twrp, flash boot.img and then the apk of magisk. Nothing else. No boot.img prepatched
[Galaxy Tab 4 Original Android Development] Achsel:
@matteo0026

Today I flashed the boot.img and then Magisk-v23.0.zip file again via TWRP. WLAN works, but ACC does not work. The Activating of CONFIG_SAMSUNG_DEBUG_DISPLAY and CONFIG_SEC_PM_DEBUG did nothing. The kernel issue for ACC must be in another place!

Thanks for trying!

Axel
[Galaxy Tab 4 Original Android Development] FailSafeNow:
Update: I've gotten the phone to successfully find my location. I don't know whether it was just wrongly configured before, or what. I haven't yet been in a situation to see if it could actively track me, but it was able to find me initially, at least. I also don't know whether we fixed it, or it fixed itself. Still, thank you.
[Galaxy Tab 4 Original Android Development] agterris:
@matteo0026

Thanks for your work on this. I've used an earlier version of this OS you've made on another Tab 4 of mine. I'm trying to set up a new one on stock KitKat that was never taken out of its original packaging but ran into a problem. I am stuck on the Samsung logo screen forever. I loaded the version of TWRP 3.5.2 with Odin, wiped the system, and installed this zip. It feels like I'm missing a step.. have you or anyone else seen this? Appreciate any help.
[Galaxy Tab 4 Original Android Development] matteo0026:
Really tricky situation... I really don't know when to put my hands now...

I don't know what you are missing, honestly. Don't go OT, by the way. And why still using kitkat? Now to install one of my custom ROMs, lollipop firmware must be installed to be able to boot on it.
[Galaxy Tab 4 Original Android Development] agterris:
That was it! I upgraded to stock Lollipop and then proceeded with TWRP and your rom and it booted. Thanks for the quick input. What's OT?
[Galaxy Tab 4 Original Android Development] matteo0026:
Off topic. It means that when you aren't in the topic of this thread.
[Galaxy Tab 4 Original Android Development] matteo0026:
In the latest builds, in the new SetupWizard, when it asks you to put a SIM card (when you haven't inserted one in your tab), in landscape mode "Skip" (or "Next", I don't remember) button isn't shown.

I forgot to mention this issue. Rotate the tablet in portrait mode and you'll have the button.
[Galaxy Tab 4 Original Android Development] mrk2815:
matteo, its skip on the set up of hte teablet. then once you hit skip then theen next ehn you haveh te swifi set up screen and then from tehr everythign is then how its hould be for setting up a tablet.i ahve done this numerous times and so i do know hatt the roms have been built for both LTE and WIFI versions of the tablet.
[Galaxy Tab 4 Original Android Development] matteo0026:
Please, write what you mean in a decent English. I don't understand what you mean. That issue can come up more frequently in tab 4 10.1 model since it's used in landscape mode, usually, while 8.0 is used in portrait mode.
[Galaxy Tab 4 Original Android Development] Analogiker:
@matteo0026 - Thank you very much for your hard work this old device.

I'm trying to recover my old TM530 with your ROM and I'm facing wifi issues. I can't connect to any WiFi Network with my TM530. Sometimes the message 'autentication problem' ist shown.

I append my logcat logfile, maybe you can have a look on it. I'm not a developer, so my knowledge is limited in reading those lines. But something like 'android.hardware.wifi@1.0-service.legacy: Failed to get driver version: NOT_SUPPORTED' takes my attention ;)
[Galaxy Tab 4 Original Android Development] matteo0026:
I know that in logcat appears that sentence, but I want to investigate better about your WiFi network. Is it a 2.4 or 5 GHz network? In which channel is it set? Does it have hidden SSID? A lot of people is using this ROM and I can just say that someone reported that was impossible to connect to hidden WiFi networks (tested by me and it's working)
[Galaxy Tab 4 Original Android Development] Analogiker:
BTW I already tried the most common stuff like switching airplane mode, using fixed IPs.... Always the same result -> no Wifi connection. The Wifi is used by multiple devices (Apple, Android, Tasmota), so I assume its a T530 problem
[Galaxy Tab 4 Original Android Development] Analogiker:
public SSID, 2.4 and 5GHz (Channle 48 and 6), public SSID

tried to use 2.4 only, sadly the same.
[Galaxy Tab 4 Original Android Development] matteo0026:
I have a T530 too, but I've never had these big issues... By the way, I'll analyze what to do.
[Galaxy Tab 4 Original Android Development] matteo0026:
@Analogiker I saw you have done something with bluetooth while getting the logcat... I saw that 2 libs are missing, and one of those I've found online. Can you put the lib I put down below in /system/vendor/lib and get another logcat, always by repeating what you were doing with bluetooth? Of course, the zip file has to be extracted before. To put in that directory the library, I advice you to work in twrp file manager (by mounting system before).

About wifi, I should do some tests, but I need a more direct contact with you. In this way, we can test things faster.
[Galaxy Tab 4 Original Android Development] Analogiker:
Hi, I'm sorry for the delay. Had a on site meeting the last days (Without Internet :( ).

When I came back home the wifi worked without problems. 5GH, 2.4GHz, roaming, restarting the device. Nothing breaks the Wifi Adapter. I really don't know what happened. I leaved the T530 at home and no one touched it. Really strange!!
[Galaxy Tab 4 Original Android Development] VoluntaryMan:
I'm probably missing something obvious, but I haven't flashed any Samsung devices in years. Any help is appreciated.

I'm getting a long hang at the LineageOS boot animation and eventually it just reboots into TWRP.

What I've done:

ODIN flash to "T530NUUEU1BQC1_T530NUXAR1BQC1_HOME"

Boot up and save Bluetooth MAC address

ODIN flash "twrp-3.5.2_9-0-matisse"

Boot to TWRP, wipe all partitions, transfer Lineage and Gapps zips

TWRP flash "lineage-18.1-20210923-UNOFFICIAL-matissewifi" and "open_gapps-arm-11.0-nano-20210929"

Clear dalvik/cache and reboot
[Galaxy Tab 4 Original Android Development] Sayueri:
Try the Gapps pico package. Were you on stock lollipop prior to this? You need to be on the latest stock rom (lollipop) for it to work.
[Galaxy Tab 4 Original Android Development] VoluntaryMan:
Yup. Using Gapps pico fixed it! Thanks Sayueri!
[Galaxy Tab 4 Original Android Development] VoluntaryMan:
Okay, next issue now that it's installed/working:

When I try to update/install apps from the Play Store, I am told that I need to free up space.

This is strange because there aren't any apps installed yet and I don't have anything on the internal storage and Settings > Storage shows over 11GB of free space. I'm assuming it's trying to install to the wrong partition or something like that.

Also I found bluetooth was working fine after a clean install of Lineage with pico-build of OpenGapps so perhaps that bug has been fixed?

Camera does not work, however.

EDIT: full wipe and reinstall of lollipop, then installed lineage. camera works, everything works. realized I don't need Google for what I'm using it for so I just didn't bother reinstalling.