A "clean" install to me includes format data in TWRP. If you don't format data, strange things can happen.I have done a clean install I put the password in for speedvault sent backup to SD card thats not sending any annoying notifications anymore.
I made no changes to the device tree as written in the Oct 9 release notes. While I can't test up to 400Mbps, the adb logcat shows argosd is up and running. SeeThough WiFi is terrible again only getting 90mb Max on 1gb connection.
$ adb logcat -C | grep argo
10-13 10:41:48.800 0 0 I [c6] argos_probe: Start probe
10-13 10:41:48.800 0 0 I [c6] argos_probe: parse dt done
10-13 10:41:52.416 0 0 I [c4] sec_argos_register_notifier: sec_argos_l1ss_notifier(dev_num:4)
10-13 10:41:52.416 0 0 I [c4] sec_argos_register_notifier: sec_argos_l1ss_notifier(dev_num:2)
10-13 10:41:52.497 0 0 E : [c5] argos_irq_affinity_setup dev_num:-1 should be dev_num:0 ~ 6 in boundary
10-13 10:41:57.060 0 0 I [c7] init: starting service 'argos-daemon'...
10-13 10:47:23.484 0 0 I [c3] argos_pm_qos_notify: name:WIFI, speed:74Mbps, prev level:-1, request level:0
10-13 10:47:23.484 0 0 I : [c3] argos_freq_lock name:WIFI, CPU_MIN=0, CPU_MAX=0, KFC_MIN=0, KFC_MAX=0, MIF=0, INT=0
10-13 10:47:23.484 0 0 I [c3] argos_irq_affinity_apply: irq277 affinity to cpu_mask:0xF
10-13 10:47:23.484 0 0 I [c3] argos_pm_qos_notify: name:WIFI TX, speed:74Mbps, prev level:-1, request level:0
10-13 10:47:23.485 0 0 I : [c3] argos_freq_lock name:WIFI TX, CPU_MIN=1200000, CPU_MAX=0, KFC_MIN=1000000, KFC_MAX=0, MIF=0, INT=0
10-13 10:47:23.485 0 0 I [c3] argos_pm_qos_notify: name:WIFI RX, speed:74Mbps, prev level:-1, request level:0
10-13 10:47:23.485 0 0 I : [c3] argos_freq_lock name:WIFI RX, CPU_MIN=1000000, CPU_MAX=0, KFC_MIN=800000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:25.489 0 0 I [c2] argos_pm_qos_notify: name:WIFI, speed:100Mbps, prev level:0, request level:1
10-13 10:47:25.489 0 0 I : [c2] argos_freq_lock name:WIFI, CPU_MIN=0, CPU_MAX=0, KFC_MIN=0, KFC_MAX=0, MIF=0, INT=0
10-13 10:47:25.489 0 0 I [c2] argos_irq_affinity_apply: irq277 affinity to cpu_mask:0xF
10-13 10:47:25.489 0 0 I [c2] argos_pm_qos_notify: name:WIFI TX, speed:100Mbps, prev level:0, request level:1
10-13 10:47:25.489 0 0 I : [c2] argos_freq_lock name:WIFI TX, CPU_MIN=1500000, CPU_MAX=0, KFC_MIN=1200000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:25.489 0 0 I [c2] argos_hmpboost_apply: hmp boost enable [5]
10-13 10:47:25.489 0 0 I [c2] argos_pm_qos_notify: name:WIFI RX, speed:100Mbps, prev level:0, request level:1
10-13 10:47:25.489 0 0 I : [c2] argos_freq_lock name:WIFI RX, CPU_MIN=1200000, CPU_MAX=0, KFC_MIN=1000000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:25.489 0 0 I [c2] argos_hmpboost_apply: hmp boost enable [6]
10-13 10:47:27.491 0 0 I [c6] argos_pm_qos_notify: name:WIFI RX, speed:128Mbps, prev level:1, request level:2
10-13 10:47:27.491 0 0 I : [c6] argos_freq_lock name:WIFI RX, CPU_MIN=1500000, CPU_MAX=0, KFC_MIN=1000000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:29.492 0 0 I [c6] argos_pm_qos_notify: name:WIFI, speed:94Mbps, prev level:1, request level:0
10-13 10:47:29.492 0 0 I : [c6] argos_freq_lock name:WIFI, CPU_MIN=0, CPU_MAX=0, KFC_MIN=0, KFC_MAX=0, MIF=0, INT=0
I have done a clean install I put the password in for speedvault sent backup to SD card thats not sending any annoying notifications anymore.
@ lpedia When I 1st installed version 19.1 I upgraded from 18.1 I didn't do a clean install thought I explained this in my 1st post in this topic but looking back I didn't. I used the 12 word encryption key 1st time around I only had 2 options for backup 1 was some online back option the other was choose location but now I have more options!! I sent the backup to the sd card but every time I rebooted the device it kept sending me notifications saying failed backups it was annoying.
What I have noticed now after a clean install is, it is now giving me more locations to backup to, speedvault is working and backing up to the sd card fine but I can also now use one drive I didn't have this option last time I have no idea why this is working ok now I am just happy those notifications have stopped and it's working fine.
So go on and build one.I want other rom i dont like lineage os anymore is waste time test it
I don't use any gapps so please direct your gapps questions to the gapps project or use thisSo i clean installed 20221009 without any GAPPS (full wipe & format) and the wifi still just sits there connected but no internet, even after rebooting it and the router again.
.....
Question: Will I need root to clean any files of folders that stock ROM would leave as residue? Or am I fine with just clean install without rom? ...
Hello, I have just clean installed lineageos 19.1 alpha and it is fantastic!
However, there are some issues I am currently facing, I would greatly appreciate support!
The 18.1 and 19.1 roms that are based on my repos all use "stock" LineageOS bluetooth code. Bluetooth and bluetooth audio are both tested on my builds to a bluetooth usb adapter running on my Lubuntu 20.04 computer. I stream audio over it and it works fine.Critical problems
- Bluetooth crashes while trying to pair a bluetooth mouse (logitech m535)
I tried Bromite 106.0.5249.163 and there's no crash for me.- System reboots for some reason when I go to accessibility settings in Bromite (a browser app like ungoogled chromium)
I don't have any gaming controllers so I cannot verify.- Playstation 4 controller (DualShock4 or DS4) keeps trying to pair over bluetooth, but ultimately fails.
I don't have Samsung physical keyboard to test or verify. The functionality above may require proprietary software or drivers in order to work and won't be included LineageOS.Annoying problems
- Task switcher and search buttons on official samsung tabs2 keyboard does not work.
- Alt + tab switching only brings up the app switcher menu but hitting tab again won't switch programs.
- File manager requires a pixel perfect doubleclick when opening folders, any slight movement cancels the doubleclick.
Already documented in post #1. I will not be spending any time fixing this as there's other priorities.- The system refuses to boot when you try to turn on the tablet while charging when turned off. (Solution is to wait a while after unplugging as you mentioned, and plug again after turning on if you need charging)
That's probably a config.xml file somewhere in LineageOS to display that. If I can easily find that setting, I can put it into the code, but otherwise I won't spend hours or days looking for it.Unimportant problems
- There are some (accessibility) settings to disable vibration, shouldn't it be off by default? (This model doesn't have it)
LineageOS doesn't include one and you can always add one yourself.- A simple notepad software would be nice to have with fresh installation.
The above is a LineageOS app and there's nothing I can do. You can always disable it and download another.- Calendar requires log-in to work, would be nice to have it run locally.
See settings, system, buttons, backlight.Unsure problems
- Physical touch-buttons for menu and back lights up for long/inconsistent periods of time, I couldn't find a setting to disable them or make them light up shorter.
I test all my builds for deep sleep. Every public build I've uploaded does deep sleep properly. Download devcheck by flar2 and you can verify for yourself.- The battery drains faster than stock OS? This could be subjective, I didn't measure using a software.
I downloaded Bromite from github and 106.0.5249.163 is the latest there is. So I suggest that message is false. Personally, I use Brave on desktop + Android. Brave is based on open source chromium and comes with built in ad block + privacy features.- Bromite fails to check for updates, says this could be a vulnerable version. Might require a permission that I'm not aware of since the OS won't pop dialogue for permissions on some apps for some reason (Do you have any suggestion to use as ungoogled chromium? extra points if it exists on F-Droid).
Every build based on my repo has been SELinux enforcing since day 1. The other builds were/are not my work.What's great?
- SELinux is enforced unlike early lineageOS builds
If you came from stock, you MUST as per FAQ FORMAT DATA in TWRP.Question: Will I need root to clean any files of folders that stock ROM would leave as residue? Or am I fine with just clean install without rom? (also thanks a lot for the instructions)
As lpedia wrote, you can get a logcat (also in the FAQ), but there's no guarantee that it will show anything or that I can fix the problem.It is great to avoid many of the unnecessary programs that keeps updating, but I really need the bluetooth mouse to get things up. Is there a way for me to help you? I don't know programming but I could set up some kind of logging setting while pairing if you provide me with instructions.
# connect device to PC, make sure adb debugging is enabled
adb root
adb shell
# temporarily turn off SELinux enforcing
setenforce 0
# Verify it's permissive mode by getenforce
getenforce
# now try all your various bluetooth device pairing that didn't work
# if they work now, let me know and I will send further instructions for you to gather the correct logs.
# if they don't pair, then it's NOT SELinux related.
# reboot OS once you are done
Package Complete: out/target/product/gts210wifi/lineage-19.1-20221110-UNOFFICIAL-gts210wifi.zip
#### build completed successfully (02:29:57 (hh:mm:ss)) ####
Unimportant problems
- Calendar requires log-in to work, would be nice to have it run locally.
Question | Answer |
Q1. Can I build this ROM for myself? Where are the source and kernel source files? | A1. Yes, you can. The source files are listed below. Kernel https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux Device Tree https://github.com/retiredtab/android_device_samsung_gts2-common-selinux https://github.com/retiredtab/android_device_samsung_gts210wifi Vendor https://github.com/retiredtab/proprietary_vendor_samsung-selinux The build manifest and instructions on how to compile from source are at https://github.com/retiredtab/LineageOS-build-manifests The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5e |
Q2. Is this ROM suitable as a daily driver? | A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since July 1, 2022 with no major issues. |
Q3. What do I do if my app xyz doesn't work? | A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work. |
Q4. Why is this ROM laggy and/or buggy? | A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc. |
Q5. What TWRP should I use? | A5. You MUST use TWRP 3.6.2_9. Get it from https://dl.twrp.me/gts210wifi/ |
Q6. Why should I use this ROM? | A6. You don't have to! If you don't like it, go back to your old ROM. |
Q7. Will you offer monthly updates with security patches? | A7. We plan to do so. We will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What works" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release). |
Q8. I'm a newbie. Can you provide step by step instructions? | A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that pflyaz has kindly provided instructions in post #7. |
Q9. Can I report a bug with respect to the ROM? | A9. Yes, but you need to supply the following information. If you don't, I won't look at it. Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password. To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
|
Q10. How long will you build 19.1 for this device? | A10. For now, 19.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors. |
Q11. Do I need to erase everything and format my data before installing this ROM for the first time? | A11. If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM. If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes. |
Q12. What Gapps should I use? | A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. Do your own research as to what is the most reliable gapps option for you. As a courtesy to gapps users, I opened a thread at https://xdaforums.com/t/exynos5433-...on-for-19-1-roms-sm-t710-and-sm-t810.4480041/ for you to discuss gapps. Do not discuss gapps in this thread. Thank you. You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services. If you are going to install any Gapps package, follow the installation instructions given for that particular package. |
Q13. I'm having problems with Gapps. Can you tell me why it's not working? | A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using. |
Q14. Why isn't my post answered? | A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions. |
Q15. What speed up/optimization tips do you suggest? | A15. These steps can make a big difference to performance:
|
Q16. Does this ROM support Magisk so I can root my device? | A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum. |
Q17. Will this ROM ever become official? | A17. With 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/ |
Q18. What is the difference between this ROM and others? | A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc. |
Q19. Will there be any major 19.1 code modifications in the future? | A19. There may be some major modifications along with some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the rom up and running, and fixing all the major bugs - has been done. |
Q20. Why did you fork the trees? | A20. I wanted my own private branch where I could make changes that would only affect my own personal builds. |
Q21. Can you build a variant of this device? For example, a LTE or S-pen version? | A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. |
Q22. Can I load this ROM on a variant device like LTE or S-pen version? | A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device. ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen. |
Q23. Does this ROM have any wifi connection issues? | A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1. |
Q24. Is this ROM secure so I can do financial transactions? | A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes. In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors. If the device is rooted, this would further weaken the security. With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions. |
Q25. How do I turn off the taskbar at the bottom of the screen? | A25. Goto settings, system, buttons and disable taskbar. |
Q26. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the ALPHA rom? | A26. Downloads are at https://sourceforge.net/projects/retiredtab/files/SM-T810/19.1/ |
$ sha256sum lineage-19.1-20220809-UNOFFICIAL-gts210wifi*
85462d9683208423aa439877f23398ebb06a9c7d9ad45fdc59b62e790fd22ba1 lineage-19.1-20220809-UNOFFICIAL-gts210wifi.zip