Our group focuses on uptime, reliability and stability testing so we rarely reboot unless we have to. We typically try for at least 100+ hours and sometimes can get 28+ days before rebooting to make the new monthly security patch. So when we need to charge our device, we never turn it physically off.
@lpedia and I were the two that solved the wifi problem back in Aug 7, 2021 for ALL S2 tablet users in 17.1 and up. Since then our private and now public T710/T810 builds have always had this patch/commit.
. I have a question about power consumption though: Is it normal that when I am using the tablet, power consumption seems much greater than when on Samsung's stock Android 7? The battery does not drain when the tablet is idle, but when the screen is on AccuBattery says that I am using about 850 mA/h. Mostly I am just browsing the web or reading using Libby.I bought my used T710 in Nov 2020, not for $9, and promptly deleted stock so I have don't have any reference.
Sometimes I do manually when my battery gets around 25% and I'm not close to a charger anytime soon.
flar2, the Canadian developer, for devcheck has his own thread at
While working on another problem with another device using adb logcat (microusb cable connected), I noticed the logcat displays the battery info. So then that led me to think about using adb logcat via wifi.
adb logcat -C | nl | grep sec_bat_get_battery_info 12 05-25 20:16:20.272 0 0 I : [1: kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3882mV),Inow(-330mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
326 05-25 20:16:50.316 0 0 I : [2: kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3895mV),Inow(-258mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
366 05-25 20:17:20.353 0 0 I : [2: kworker/u8:5: 2206] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3894mV),Inow(-281mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
566 05-25 20:17:50.400 0 0 I : [3: kworker/u8:2: 45] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3911mV),Inow(-78mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
896 05-25 20:18:20.446 0 0 I : [1: kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3915mV),Inow(-94mA),Imax(450mA),SOC(61%),Tbat(258),Tchg(0),is_hc_usb(0)
916 05-25 20:18:50.487 0 0 I : [3: kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3914mV),Inow(-96mA),Imax(450mA),SOC(61%),Tbat(258),Tchg(0),is_hc_usb(0)
Nevermind, found the solution myself. After adding the following lines to the gts2-common device manifest haptic feedback started working:
<hal format="hidl">
<name>android.hardware.vibrator</name>
<transport arch="32">passthrough</transport>
<version>1.0</version>
<interface>
<name>IVibrator</name>
<instance>default</instance>
</interface>
</hal>It is incorporated into my device tree so when the June 5th security patches are released, it will be in that build. Thanks. I gave you credit in the commit notes at
If you have random reboots, please follow the instructions in post #1 at
adb root
adb shell
cd /data/tombstones
head -n20 tombs* | more
| 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_gts28wifi Vendor https://github.com/retiredtab/proprietary_vendor_samsung-selinux In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. 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 mid August 2021 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 my unofficial TWRP 3.5.2_9. Get it from https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/ |
| 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. lpedia 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's working" 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 make a guide in post #37. |
| 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 18.1 for this device? | A10. For now, 18.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. Under most circumstances, yes. 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. The ONLY exception is that if you are coming from LOS 18.1 with the April 5 2022 security patch or later, you can dirty flash the latest security patch build. |
| Q12. What Gapps should I use? | A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services. 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. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build. |
| 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 18.1 code modifications in the future? | A19. I don't anticipate any major modifications. There may be 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. This doesn't mean the code is perfect or well organized, but I won't be making any major changes. |
| 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. So I will NEVER build T715, T810 and T815. |
| 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. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA rom? | A25. Downloads are at https://sourceforge.net/projects/lpedia-sf/files/gts28wifi/ |
