LineageOS 18.1 chronometer bug - Moto X4 Questions & Answers

LineageOS 18.1 chronometer bug - Moto X4 Questions & Answers

Regards; i have the XT1900-01 model with the 1/feb/22 nightly version of LOS.
I often put some alarms on the clock app chronometer, but since some time i realized that when the chronometer's timer ends the phone shuts down inmediatly in response not leting time for beeping, or maybe some 5ms short sound can be listened. This happens when i playing some music (i didn't tried in another conditions) and it happens either if i have or not earphones (bluetooth); besides this happens in whatever clock app, i mean the native of LOS or the google clock app.
Curiosly, this s**t also happens when i try to play some multimedia content (videos) on social apps like ig/fb stories and it's very anoying, but it happens very randomly and i cannot predict it.
Aditional info:
* I tested this issue with older versions of LOS (same android version) with the same result.
* Native clock app version: it says "11".
* Google clock app version: 7.1 (104664356) (lastest available on Play store as today).
* Gradually increment of volume is disabled in both alarms and timer.
* I tried before to wipe cache for clock apps, google apps and also clearing dalvik caché with no different results.
* I have TWRP 3.5.2_9-0 for (clearly) payton, but i also had before the LOS native recovery with no different behavior on this issue.
* The issue happens either if device is rooted (magisk 24 for sure and 23 as i remember) or not.
* I tried to install some magisk modules before, with safetypass related things; but i'm unsure if this changes could have affected for this issue.
* For being detailed, device's bootloader is unlocked and "verity mode is disabled".
* I have instaled new LOS versions before via LOS system channel.
I hope to have been specific with my problem, thanks for reading this (i think this is my 1st post lol).

Related

[INFO][HELP][FIXES][HOW TO] Collection of Help - Info postings for the Nook Color - x

HELP
I've got a problem with my Nook Color (BNRV200)
Tired of searching for a thread that tells you what to do when you need to install, fix a problem, need a recovery, etc. I have compiled a number of links to various threads by developers and others that answer questions that get asked a lot. This post is intended to give a site that will make finding these answers easier than a regular search. It will have a list of threads and posts with various helps, have a topical list of problems and sites which address those topics, links to common sites and app needed to get what both Noob and seasoned members need to work with and on Nook Colors.
You choose to make changes, flash ROMs, etc. it is your choice. You assume all responsibility for what ever happens. I list these links because I know they have helped and work for me as well as many others. If you need help with a particular problem addressed in these links, ask on those threads.
If you use information in any of these links make sure to click on the thanks button both here and in those links. If you want to write a thank you note also, that to is fine, but does not add to the "Thanks" counter. These people have worked hard for free that we can have greater enjoyment and fun with our tablets. Most get nothing for their time and effort so "thanking them" is their greatest return and the least the rest of us can do in appreciation. Credit and kudos are given by Authors Names in Post #2
By Topic(A)
Add Network speed to Status Bar. Post#3
Android.process.media force close or crash Click here Also make sure all Google apps are updated, defrost frozen ones, update in play, refreeze (Mine was Gmail) (Thanks bowguy)
(B)
Boot Loop Problems (2)
Bootable CWM Recovery SD (v5.5.0.4 and now v6.0.1.2) (1)
(C)
Change "Status Bar" or "Navigation bar" colors or heights (for two rows of status info). Post#3
Change perceived DPI, rotation behavior, fullscreen, permissions on a per app basis Post#3
(D)
Dual Boot Nook (12)
(F)
Faster bootup
To get faster bootup you can disable the boot animation and save about 30 seconds from boot up time by adding "debug.sf.nobootanimation=1" to the build property file in the /system folder. This is a pain though if you keep up with the nightlies regularly like I do. I got tired of editing the file for every update or reversion if there was a problem with the newer nightly. So I created a script that goes into the Userinit.d folder that checks build.prop on every boot and adds the line if needed without any further intervention. The first boot after installing a new nightly will have the boot animation but no more till the next install when the process will repeat all automatically. Download the AutoNoBootAnimationScript.zip in attached files below, unzip, follow the included instructions and enjoy.
Faster SD card access. Instructions bottom of Post#4
Freeze/Disable applications (1)
(G)
Google Play says, "This app is not available for your device"
Get Xposed Framework in Post#3, download "PlayStore Fixes", set Fake density 240, Check No Restrictions Patch. Clear Google Play Store data, reboot enjoy.
(H)
Home button / icon stopped working, defrost / enable android Keyguard
How can I make my ROM run smoother, have more free memory or have longer battery life. Post#4
How to play flash video on Android 4.4 Kitkat in Dolphin Browser (14)
How to do a Logcat (13)
(I)
I wiped, erased, formated my /ROM (#2) partition (2)
Installing CM11 and get Status error 7 or other problems - Must use CWM 6.0.4.7+ or TWRP 2.6.3.0 (Download below)
Installing new CM11 and latest Gapps and no Google Play. Problem /system is too small.
The Prefered way to fresh install latest nightlies: If you do a conventional (no repartition) install using the smaller 01/05 Gapps and install the other Goople apps through Google play. They install into the /data directory instead of the /system. You can do this also with Gmail, Sound search (ears), Google TTS and Hangouts.
Alternate experimental adventurous way. There are two .zips available that will repartition your Nook and give you more /system space and /Data space.
Dweatons mod of Leapinlarswork, Repart.zip, is here and will yield 1.1Gb /System, 2Gb /Data, and 3.6Gb /Media.
Mine is here and will yield 1.1Gb /System, 4.5Gb /Data, and 1Gb /Media. You must get and use a reformat 5,6,7,8.zip after the running the repartition.zip for dweatons get Leapinlar's here. For mine get it here. the difference is for his you must install with CWM before 6.0.3.6, mine works with 6.0.4.8. Reverts to B&N Stock /system are available here.
Installing CM on EMMC CM11 (8), CM10.2 (9), CM7 or CM10 (6)
Installing CM on SD (3)
(M)
Make Play Store show All apps in listings Post#3
Modifying partition sizes original (5) Modified for CM11 and CWM 6.0.4.8 (15)
More SD card storage Use a 64 Gig SD Micro. Instructions bottom of Post#4
(N)
Nook won't boot (7)
(P)
Put Play Store link in App info window Post#3
(R)
Recovery boot loops (1)
Repairing partitions, blank screens and cannot flash new roms (2)
Restore Nook Color to Stock, (4)
Running Netflix app in CM 10 and 11 (11)
(S)
Screen touch sensitivity a little off. Try Nook Screen Recalibrate in Google Play
SD Card install tips Leapinlar's Tips post #2
Stock Nook Color Roms Leapinlars (1.4.3), Dizzy Dens (1.4.1)
(V)
Video Flicker in CM11 Crackle, Hulu and other video sites and apps, update to CM11 nightly 4/22+ or (10)
Volume / Sound to low. Try Speaker Boost in Google Play. Caution:
Mine works great @ 50% boost. Be very careful above 40%, go slowly and safely. If you want to rename the DSPmanager goto post #6. If you have CM 10.2+ (4.2.1) you must do the renaming since the DSP version since then throttles back the sound levels.
(Y)
YouTube updated and asked for update for Google Play Services but Google play has no update. Get Version 4.2.43 here: (11) (At bottom of attached files) Latest (4/20/2015) New update on Youtube and / or Google Play problems. Solution here: http://forum.xda-developers.com/showpost.php?p=60241045&postcount=54
(W)
Where can I get:Gapps http://wiki.cyanogenmod.org/w/Gapps
Latest Nightlies http://download.cyanogenmod.org/?device=encore&type=nightly
Recoveries (download in attached files below)
Stable versions http://download.cyanogenmod.org/?device=encore&type=stable
Older releases of CM 10 or CM11 http://techerrata.com/browse/cm/encore/nightly List of Authors of Post
To whom credits and thanks are due!
See Post (#2)
If you know of other Help, Info, etc sites post a reply I'll check it out and include it in the lists above. Even if the post are not on Nook Color forum, If it worked for you on your Nook, post a reply with your Rom version and I will check it out and consider adding it to this list.
Recoveries The recoveries I have are listed below and can be downloaded in the attached files box. The MD5 sum files are in the MD5 sums for recoveries zip. Download it, un-zip it, and check with the approriate recovery. These are for the Nook Color (BNRV200)
CWM Recoveries3.2.0.1 - Good for CM7 Eyeballer or nemith
5.5.0.4 - Good for CM7 thru CM10.2 Racks
6.0.1.2 - Good for CM7 thru CM10.2 - LeapinLar
6.0.5.0 - Must have for CM11 5-16+ Nightlies eMMC & SDCard installs - polymath257
6.0.5.1 - Latest Available - rjwil1086TWRP Recoveries2.3.1.0 - From TWRP Site
2.4.1.0 - Eyeballer
2.6.3.0 - Must have for CM11 thru 5-15 nightly (use 2.4.1.0 for pre CM11) - Eyeballer
2.8.3.0 - Must have for CM11 for 5-16+ nightlies - rjwil1086(nba#+5)

[INFO][HELP][FIXES][HOW TO] Collection of Help - Pt2
By Author of Post
Dean Gibson
Repartitioning the NC to 1-5 Gb, 2-4Gb and 5-1 Gb: (5) http://forum.xda-developers.com/showthread.php?t=1094371
Eyeballers
Install CM7 or CM10 + Recovery to EMMC: (6) http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color
Leapinar
Tips: (1) http://forum.xda-developers.com/showthread.php?p=25354258#post25354258
EMMC Repair: (2) http://forum.xda-developers.com/showthread.php?p=28457126#post28457126
Nook Color Installation Guide for CM7/CM9/CM10/CM10.1/CM10.2/CM11 on SD: (3) http://forum.xda-developers.com/showthread.php?p=32921666#post32921666
nismopc
Running current Crackle TV 4.0.3 on CM11 Nightlies: (10) http://forum.xda-developers.com/showthread.php?t=2634964
Nootered
Restore to Stock: (4) http://forum.xda-developers.com/showthread.php?t=931720&highlight=fix+boot
pastordl
Running current Netflix app in CM 10 and 11: (11) http://forum.xda-developers.com/showthread.php?p=44626173#post44626173
Repartion and reformating zips for CM11 and CWM 6.0.4.8: (15) http://forum.xda-developers.com/showpost.php?p=54401912&postcount=4177 (From Dean Gibson's work, also Leapinlars and Dweaton)
paxChristos
[Tutorial] How To Logcat (13) http://forum.xda-developers.com/showthread.php?t=1726238
RileyGrant
Dummies Guide to Fixing 'My Nook Won't Boot' (7) http://forum.xda-developers.com/showthread.php?t=949699&highlight=boot+zip
Steven676
CyanogenMod 11 Nightly Builds for Nook Color: [Read first three posts]: (8) [FONT=&quot]http://forum.xda-developers.com/showthread.php?t=2629337[/FONT]
surviveland
[Guide][Flash]How to play flash video on Android 4.4 Kitkat - xda-developers (14) http://forum.xda-developers.com/showthread.php?t=2548001
Tausaur
Dual Boot (12) http://forum.xda-developers.com/showthread.php?t=1275859
Tdm
CWM 6.0.4.7 Touch Recovery Ramdisk (http://forum.xda-developers.com/showpost.php?p=51446977&postcount=19015) http://forum.xda-developers.com/showpost.php?p=51446977&postcount=190

Customize Rom or Apps without being a developer - Xposed Framework
Customize Rom or Apps without being a developer - Xposed Framework
From Rovo89's thread
In this thread, I'm presenting a framework which gives you the possibility to modify your ROM - without modifying any APK (developers) or flashing (users)!
Click to expand...
Click to collapse
Get Xposed Framework and install instructions Click on "click to show content" box
For the framework:
Download the Xposed Installer APK and install it
Launch the Xposed Installer, go to the "Framework" section and click on "Install/Update"
Reboot
Done!l
You can verify this by starting the Xposed Installer again. If app_process jumped back to an older version (or none at all), you probably have a ROM with S-On or similar, which reverts any changes to /system after a reboot. Then you can try to flash this file: http://forum.xda-developers.com/show...postcount=2308
For any modules you want to install:
Download <module>.apk and install it
Launch the Xposed Installer and go to the "Modules" section (you will also get there if you click on the notification warning you that the module is not enabled yet)
Enable the module by checking the checkbox
Reboot
Done!
For information & help with Xposed Framework go to Rovo89's thread.
Once you have installed the Xposed Framework you can get many of the modules under the Download tab in the framework app.
There are also a large number of modules at this thread made for module developers to list their work. If the Modules indicate they are made for a specific phone or tablet they may not work on others. If you try and it does not do what it says it will do, contact the module maker, not rovo89, unless it is his module, ie: "Make Play store show all apps" or just un-install the module. No guarantees they will help. Some only have one tablet and only develop for what they have.
A Short list of some of the things you can do using Xposed Framework and modules.
These do all work with CM11 current nightlies and CM 10.2 last nightly, 1/19/14
For more info on Modules listed install Xposed Framework and click on Download tab
Change color of status bar / notification bar. Xposed Framework - X Blast tools. Plus lot more. By femblack.
Network Speed Indicator - by fatminmin. With 123 below the up down speed can be shown in two readable rows. ** This will not work with CM10.2 Stable with the 3.0.8 Kernel or the updated hack fix kernel
Play Store link in app info - by qwerty12 - Does what the title says
App settings - by Tungstwenty & Rovo89 - What it is: This is an Xposed module that allows changing generic settings on a per-app basis. "Generic settings" means settings that are global to all applications, such as: perceived DPI, rotation behavior, fullscreen, etc..
Play Store Fixes - Rovo89 - Make play store show all apps
Enable SwiftKey predictions in more places - by qwerty12 - Email address website and filter list fields.
123 Dimension Editor. - by Hamzahrmalik - Change various UI dimensions: Status bar height, Navigation bar height and others. I doubled the height of my status bar and shrunk my navigation bar.
Cool Tool: - by Deviant Studio Software - Monitor various system info in floating window or in Status Bar. I have time, day, date, Free Memory and Battery Temp in two rows of my status bar.
Status bar volume. - by Niko001 - Move the volume bar over the status bar.
I do like things my way. That is what Android is noted for.
This Module "Workaround for Netflix on CM10/CM10.1" works on most any CM10 thru 10.2 Rom.
From Kaepernick's post.
"Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue.
Click to expand...
Click to collapse
Get it here.
*** Make the Xposed Framework persist through a CM ROM update with script "90-xposedpersist.sh" (in the 90-xposedpersist.zip), put the ".sh" file in the /system/addon.d/ folder. Available here See Post #4 there for specifics here***
Image 1. Cyan status bar & navigation bar, network speed indicator & X blast options.
Image 2. Play Store button in app info.
Image 3. App Settings screen.
Image 4. Home screen with dual line expanded status bar, Cool tool info and Net work speed.

Run CM10 & 11 smoother and get more free memory
Tips to help CM10 and CM11 run smoother, less laggy, etc.,
and have more free memory on your Nook Color
and maybe even a little longer battery life.
These are a collection of tips that have been collected from various post in XDA, personal sharing with others, and as a result of my own desire to try to improve things where I can. I have tried everything listed here and each adds a little to smoothness(s), free memory(f) or battery(b) life. My CM11 flashed Nook runs quite smoothly, with free memory at desktop running from 110 to 160 Mb and six to eight hours of battery life depending on type of constant use. This is on a nearly three year old tablet. I have partitions set to 5Gb data and 1Gb media. All apps are in the tablet. I also have a 32Gb Sdcard. I also have over 220 apps including system apps. I use my tablet from 6-8 hours or more a day.
Unless noted all apps mentioned are available through Google Play. I recommend the apps, etc., because they work for me. I get nothing out of it except the joy of helping others. Like everything try at your own risk. This includes app I have on my Nooks. If you have other programs you can try adjusting them as I have and see how it helps, or not. Trying and finding out what does and doesn't work is half the fun.
Free and simple
On all CM10 and CM11: (s) Try lowering your maximum clock speed to 1000, or even 800mhz in System, Performance Processor, Maximum CPU frequency. Many have reported improved smoothness at slower speeds. Faster can run ahead of itself and actually make things jittery. Make sure to check Set on boot to retain settings.
CM11: Use 5/17+ nightly.
On all: System Settings ( some may only apply to CM10 or 11 List:
Wifi, advanced,Uncheck Network Notification (b)
Keep Wifi on during Sleep, only when plugged in (b)
Scanning always available, uncheck (b)
Wifi Optimization, checked (b)Sound,Set quiet hours (your sleep time)(b)
Touch sounds, screen lock sound, volume adjustment sound and Charging Sounds, Enable, all unchecked (b)DisplaySleep (set time for max time you want screen to stay on before going to sleep, shorter time saves more battery)(b)Developer Options,Kill app back button, checked, (Allows you to kill kill app by long pressing back button)(b)Performance,CPU governor, (Lower on list will give faster response but use more battery, Default is "ondemand". Try the others and stick with what suits you the best.) Make sure to check Set on boot to retain settings.If you haven't activated the "Developer Options list":In "About Tablet, Build Number, tap ten times till it states "Developer Options turn on."
AdFree: (b) Available on Slideme.com Stops adds in browsers and most all App with add banners. Saves time by not downloading the adds.
On All: ((f,b) Freeze / Disable unused (unusable) apps in System.(b,s,f)
Don't delete them since any ROM update you install will replace them, freezing / disabling them will last through an update. The stock App manager allows you to disable most of these. Titanium Backup and Rom Toolbox Pro can freeze more but do cost, though I think they are well worth the price for what they deliver. There are some free "App freezer" programs available. I've only tried Chef's App Freezer, check the ratings and comments.Android Keyboard (ASOP) - I use Swiftkey (lite is available)
Camera - (No camera in Nook, no need of file)
Com.android.smspush. No phone text.
Gmail and / or Email and Email Services (if you use another E-mail client, ie:K9)
File Manager ( if you uses another ie Root Exporer (Speedsoft) or Root Browser (Jrummy))
Google search - Definately slo-o-ows things down
Key Chain - if you don't use lock screen
Mobile Data and Mobile Network Configuration - No phone, no need
One time Init - only used on first install once
Picasa uploader - If you don't use Picasa
Print Spooler - If you don't use it.
Sound Recorder - No Microphone, no need
Sound Search for Google Play - If you don't use it
Talk back - If you don't use or need it.
Trebuchet - If you use another Launcher.
Voice+ - No Microphone or phone, no need.
If you use a different clock than stock, calendar etc you can freeze / disable the stock version. Example: I use Dejaoffice to link with Outlook on my PC so I freeze Calendar storage, calendar, and calendar sync.
Change app permissions: (f,b) (for apps that run at startup and then stay in memory even when you not running them.)
I use App settings, it requires Xposed Framework to run but once set up does it's thing in startup, changes permissions, and closes. To get the Xposed Framework go here.
The most common causes of this problem are the following permissions: receive boot completed, vibrate, and wake lock. Not all apps can have these turned of. App settings has the ability to launch the program from is menu. Try turning off a permission, save, menu (launch). If it works great, if not go back and turn that permission back on.
The following is a list of Apps I changed permissions on and which permissions I disabled to keep them from persisting / sticking in memory:Advanced Task Manager: receive boot completed, and wake lock.
Alarm Clock Extreme: read phone state, receive boot completed, vibrate, and wake lock.
BusyBox Installer: receive boot completed, and wake lock.
CPU Master Pro: receive boot completed.
Crackle: receive boot completed, vibrate.
DejaOffice: vibrate.
Elixer: vibrate, and wake lock.
Evernote: receive boot completed, and wake lock.
Google Play Services: receive boot completed, and wake lock.
Kyo-Tux Aeon HD: vibrate.
News and Weather: receive boot completed, and wake lock.
Nook: receive boot completed, vibrate, and wake lock.
Pandora: receive boot completed.
RoboForm: receive boot completed
ROM Manager: receive boot completed, and wake lock.
The Weather Channel: receive boot completed, vibrate.
Titanium Backup: receive boot completed, vibrate.
Winamp: vibrate.
YouTube: receive boot completed, vibrate.
Advanced Task Manager: (b,f,s) Put the widget in dock, set your ignore list in app. One press and all unwanted apps go bye-bye.
My Ignore List:
Adfree, Elixer Widget, Alarm Clock Extreme, K-9 mail, Nova Launcher, Swiftkey, Speaker Boost, Pie Pro, Earthquakes, AFWall+, Clipper+, DejaOffice, Tasker, 360 Security.
Not so Simple but worth the time, still free
Replace DSPManager with Speaker Boost: (f,b) Get more volume and save EMMC memory.(DSPManager 18Mg - Speaker Boost 1.7 Mg=16.3Mg saved) Get more info here.
Replace Trebuchet with Nova Launcher: (s) does more, has more adjustments. (Does take more memory but pays back in smoothness)
LagFix (fstrim) Free. (s) Use two to three times a week. (s,b)
Use Elixer widget to replace other widgets: (f,b) and save Memory 45 meg (for Battery widget, Wifi state and stats widget, free memory and CPU stats) - 12 Meg for Elixer = 33 Emmc memory saved.
Rom toolbox lite: Settings: (f,b,s) (some of these may need Pro)
Under performance.Settings, Main Preferences, Boot Delay, 40 seconds.
Task Manager, Tap on Task Manager on top left of screen.You can change the Minfree memory settings, with CM10 I found strict to work the best. So far with CM 11 custom settings of 30 FA, 40 VA, 65 SS, 75 HA, 90 CP, and 100 EA setting works well.) I set them then save them into custom settings). Make sure to update to 5/17 nightly.
Start up killer, add Elixer, Google play services, The Weather Channel, and YouTube. (keep them out of active (service) memory or minimize there active size.)
Ignore List. 360 security (or your antivirus app), AdFree, AFWall+, Android system, Clipper+, Earthquakes, Elixer Widget, K-9 Mail, Mobile Data, Nova Launcher, Pie Pro, Rom Toolbox Pro, Speaker Boost, System UI, Tasker.SD Boost. You can change the size of the cache to both internal and external SDcard. I find with my class 4 Sandisk SDcard a setting of 4096KB works best. A benchmark is available to test your settings. If you have a faster card ie: Class 10 you can try larger cache sizes and save as custom.
Not Free but worth it (IMHO)
Upgrade to Nova launcher Prime:
In Nova Settings: (s)
Look and Feel, Scroll and Animation speeds (faster than light) (s)
New Apps - check Auto Add Short cuts, (make sure to turn off auto add in Google Play.)
Labs - Check the following, Big Grid size options, Widget Image Async List, Widget Image Cache, Restore Widgets Faster. (s)
Upgrade to Rom Toolbox Pro, LagFix (fstrim) Premium (scheduling trims): Get more bells and whistles and help support the developers.
Upgrade to 32 or 64Gb Class 10 SD card - Buy a 32Gb Class 10 SD card, about $20.00 + ship, prepare as usual and you'll cut your access time to the SD card buy about half. I can do a 2Gb recovery backup in about 5 and 1/2 min. With my Class 4 it takes just shy of 11 minutes.
More Memory Buy a Sandisk 64 Gb Class 10 Micro SD card, about 40.00 + ship, and partition the whole card as one Primary partition, format as FAT32, Sectors/ cluster 32 (16384 bytes) using "MiniTool Partition Wizard Home Edition" available for free here. I have donated to MiniTool since I use it for all kinds of partitioning,(resizing, moving, copy, etc.), on PC's and all kinds of flash memory. I started with the partition set to 30,451.33, copied my data from my 32G sdcard. It worked great and with SD boost set to 4096 all SD access was noticeably faster. So I used Partition Wizard to resize the card to the full capacity, the program changed the size and copied all the files in about 20 minutes. Plugged it into the Nook Color and went from 17 GB free to 47 Gb Free. It is a bit slower than the 32Gb & and the bootloader doesn't list CWM or TWRP recovery kernel or ram on the SD, but oh the storage. I can put over 40, 2 hr AVI or MPEG movies on the card and still have better than 20Gb free.
If you have other Apps, tricks, tweaks that you have tried and found to help. Please reply and I will try them out and list them if they do add to the smoother, longer, freer Nook.

Netflix on CM11 on SD
Good source of info. Thanks! Confirming that latest Netflix is working on SD. See that thread

If you use Speaker Boost try this to save memory.
Ever since CM7 and Nook Color Tweaks, in has been necessary to find a way to boost the sound output of our little wonder tablet. I tried several an ended up using Speaker Boost. I have found that I no longer need to use DSPmanager. The problem is that freezing or disabling the app doesn't keep it from installing in memory and using 18meg of precious RAM. Renaming the file with.bak extension or deleting it works after a reboot but, if you like to keep up with the nightlies like I do it is re-installed with every update. It gets to be a pain using a file manager to do this every day. So let your Nook do the repetitive work.
So I have worked up three quick and easy ways to rename the file.The best and easiest is the last.
1. Is a Tasker task. This was the first one I used and I setup a widget so I. Can rename with one tap. The.xml file can be imported as a task into Tasker.
2. Is an apk made from the Tasker task. It works the same way just doesn't need Tasker to work.
3. A script file that can run at every boot, check if DSPManager.apk exists, and rename it. This eliminates having to rename it and reboot after every ROM update as it is renamed before the app is loaded. It is only 279 bytes and is the only file that has to remain to work. In the 90RnamDSP scripts.zip below are three files. One that goes into userinit.d folder, an instruction.txt file and an installation script that sets everything in place just by running it.
I want to thank LeapinLar for the help he gave debugging the rename script. This was my first script and had to get everything in proper order and get the syntax correct. What I learned help me build and debug the installation script in a few hours.
Download, unzip, import, install, etc, and enjoy.

Thanks, nice job
Might check the links for the 6.x recovery threads

webyrd said:
Thanks, nice job
Might check the links for the 6.x recovery threads
Click to expand...
Click to collapse
Checked and corrected, Thanks.

pastordl... check pm about a couple of link issues

DizzyDen said:
pastordl... check pm about a couple of link issues
Click to expand...
Click to collapse
Thanks, guess we know where the missing link is.

problem with latest YouTube and Google Play apps not working
For problem with latest YouTube and Google Play apps not working, Go here:
http://forum.xda-developers.com/showpost.php?p=60241045&postcount=54

[ROM][6.0][AOSP][{Un,}Official] LineageOS 13.0 (Marshmallow)

LineageOS 13.0 (Marshmallow) {un,}official builds for the Droid 4
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Use these builds on your own risk!
Builds:
Current official builds:
https://download.lineageos.org/maserati (Droid 4)
(When migrating from CM (official and unofficial) or Lineage unofficial, flash this first (manually mount /data in TWRP before flashing and unmount it afterwards) and then directly flash the new image without rebooting)
Su addon for official builds: http://droid.cs.fau.de/lineage-13.0/addonsu/ (The official addon doesn't currently install on Omap4)
Current unofficial manual builds:
https://droid.cs.fau.de/lineage-13.0/
Old official CM nightly builds and snapshots:
https://droid.cs.fau.de/Official_CM_Builds/maserati/ (Droid 4)
Old manual builds:
https://droid.cs.fau.de/cm-13.0/test/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2017-03-25:
Sync with LineageOS (March security level)
2017-03-02:
Sync with LineageOS
2017-02-19:
Fix 10 kernel security bugs
Add SGX Omap4-changes
Sync with LineageOS
2017-02-10:
Sync with LineageOS (January security patchlevel)
2017-02-01:
Sync with LineageOS
2017-01-11:
Sync with LineageOS
Rebrand to lineage
2016-01-21:
Official CM13 nightlies: http://review.cyanogenmod.org/#/c/129192/
2016-01-16:
Added SELinux rules to allow fsck on stock-partitions and fixboot to unmount safestrap-partition
Graphics glitches fixed
zRAM uses 2 compression streams now
2016-01-14:
Implemented LiveDisplay/Color Calibration
2016-01-13:
More fixes for switching CDMA devices to GSM
T-Mobile CZ APN corrected
2016-01-11:
Preferred network type is now set earlier
Audio-routing through dock-audio (desk/car) added
Mouse-pointer (USB/Lapdock) fixed
2016-01-08:
Camera no longer crops pictures in portrait mode
USB storage integration added
Initial root-mode setting fixed
Migrated from busybox to toybox, busybox is gone
Fixed duration of boostpulse in power HAL
2016-01-06:
VZW data fixed
Reboot to recovery fixed
Wifi configuration updated
Widevine blobs updated (from sprout)
2016-01-04:
Adoptable storage fixed
Many kernel patches to filesystem-, block- and mmc-layers
2015-12-25:
Fixed internal storage for real. You need to manually remove /data/system/storage.xml and reboot when upgrading from previous builds. After that the internal storage will be the primary sd.
2015-12-24:
Fixed crashes of com.android.phone on GSM/UMTS (XT894/XT912)
Configure internal storage like expected in M (can't be adopted, would kill safestrap)
Fixed GPS initialization failing most of the time
Run wifi calibration at an earlier stage
Workaround for VZW data: toggle airplane mode after boot once
Something which needed ffmpeg and imagemagick
2015-12-18:
Switching of preferred network fixed
SELinux rules updated
SELinux is now enforcing
2015-12-14:
Audio-routing fixed
2015-12-11:
Capacitive buttons on {umts_,}spyder are no longer recognized as an external stylus, but as buttons
SELinux policies updated
Update widevine from mako
Added (very slow) emulation of idiv-operations not supported by Omap4 but required by newer blobs (gapps swype, widevine)
2015-12-07:
First build for most devices
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data
WiFi
GPS
Camera
HDMI
Playback of DRM-protected content (using Widevine from sprout)
Reboot to recovery
What's not working:
Probably most everything else, including, but not limited to:
Data encryption (due to safestrap)
Gapps:
OpenGApps
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
Installation:
You need a recovery supporting SELinux
A version of Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
These versions (both unofficial and official) automatically switch to GSM/UMTS without installing additional patches.
Source / Repositories:
maserati device-support: https://github.com/LineageOS/android_device_motorola_maserati/tree/cm-13.0
omap4-common device-support: https://github.com/LineageOS/android_device_motorola_omap4-common/tree/cm-13.0
omap4-common kernel: https://github.com/LineageOS/android_kernel_motorola_omap4-common/tree/cm-13.0
local manifest to build cm-13 for the Motorola Omap4 devices: http://droid.cs.fau.de/lineage-13.0/local_manifest.xml
XDA:DevDB Information
LineageOS 13.0 on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Beta Release Date: 2017-03-25
Created 2015-12-14
Last Updated 2017-04-05

Good job

Thanks again!

Excited.

Installed 151214 this morning over the top of 151210.
The "low in call volume " issue appears to be fixed, as per the notes above; I've had a few phone calls this morning with only one issue:
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?

hahahaha thanks stargooo one step more for our droid 4!

Hi,
Shobai said:
Installed 151214 this morning over the top of 151210.
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?
Click to expand...
Click to collapse
All low-level audio-routing problems should be fixed, this sounds like a problem with the IncallUI (it probably did not specify that the audio should be routed over the headphone out). Haven't looked there yet...
Cheers,
Michael

Thanks Michael, much obliged!

Apologies for the double post! @stargo, I think this may have been mentioned in the CM12 thread - I've got "Playback control" turned on under Buttons, but a long press of the volume keys doesn't have any effect on playback. The volume keys work properly for volume, though.
Thanks again!

Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?

LuH said:
Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?
Click to expand...
Click to collapse
Flash the build from the 14th.

Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?

Septfox said:
Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?
Click to expand...
Click to collapse
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!

So has the build from the 14th fixed the DATA issue?
By no LTE/CDMA support right now, does that mean I wouldn't be able to receive emails and online push notifications unless I am on WiFi or they are Text/SMS based?

hi, can i have noob question? is there some tutorial how to make own build (i have tried to google what to do in which order but i didnt have much luck - create folders, get local manifest, init repo but when and how get omap4 common files required for build...)?

Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).

Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
So by finding this out, it would seem that the Data connection for any provider is not functioning due to a permissions issue in which the OS cannot write the given APNs from the "search" function to the file which stores the data... is that correct?

Hi,
Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
Click to expand...
Click to collapse
Great
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
Does it work after a reboot, too?
Or do you then need to toggle airplane mode again? It might be that toggling airplane mode is what actually causes the connection to be established. Judging from the radio logs I have seen, the RIL responds with an error after bootup and toggling airplane mode might fix it.
Btw, for the people on UMTS: I'm testing a fix for the crash of com.android.phone after boot.
EDIT: Confirmed by @joojoobee666: toggling airplane is enough to get data working
Cheers,
Michael

Bobcus Leper said:
Flash the build from the 14th.
Click to expand...
Click to collapse
Yup, switching Vibrate on touch off in sounds settings helps from this build on. Thanks, I have decided to make this my primary system, so far great impression
Bobcus Leper said:
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!
Click to expand...
Click to collapse
I second that; especially Trebuchet, Settings, dialer, contacts and messaging are way more responsive. I clean installed system (1218 build; wipe /system, install just this and Open GApps Pico) with keeping data from 12.1, it went pretty smooth.
Also it's been laying in standby for about 12 hours now, Wi-Fi on, and it's still charged ~96%. Either it's a battery level reading bug and will soon drop fast, or huge improvement over L - usually I'd lose 10% - 20% at least.

GREAT JOB I was looking forward to CM 13 since June. However, right after flashing GAPPS the processes crash and can't make any progreses. Doesn't matter if I use Slot 1 or 2, already tried mount no-mount /system and /data.

[Q] Device crashing with certain apps on recent LineageOS

Recently I've been having issues with my Xperia Z (C6603), the device is crashing (hard reboot), but only with certain apps/app versions.
The apps that always crash the device are:
- Firefox Focus (org.mozilla.focus): 8.0.25 works, anything recent doesn't
- Firefox Preview (org.mozilla.fenix): 2.2.0 works, anything recent doesn't
- Reddit (com.reddit.frontpage) (never had an older version than current)
Things I've tried:
- Official Lineage 15.1 2020-02-21:
-- Device crashes
- Unofficial Lineage 16.0 2019-10-20; Phone wiped with only GApps Micro installed:
-- Device crashes
- Stock 5.1.1 10.7.A.0.228; Phone wiped, bootloader locked:
-- Works fine, the apps do not crash the device
- I've looked at logcat but don't see any errors, it just starts the activity and then shuts down. I am not an expert on debugging however...
- From what I've seen, any other app (~157 user apps installed) works perfectly fine
Is anyone else experiencing this (with specific apps) and do you know if any of the recent unofficial LineageOS 16 ROMs don't have this problem?
What other steps could I take to pin down this problem?
I prefer to run an official Lineage ROM, or at least something recent that is built in a transparent way.
Thanks in advance ?

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for SM-T710 - June 10, 2023

LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLYModel: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. DRM level 3 (SD definition)
10. deep sleep
What doesn't work
1. fingerprint. As I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
I will not spend anymore time looking at fingerprint. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working.
4. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
3. All past contributors of the exynos5433 code.
4. @rINanDO for his lmkd spam fix in 18.1.
5. beta testers: lpedia, Yogi555 and CuckooPenguin
6. lpedia for building the public T710 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.

Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. 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/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. 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:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
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, OpenGapps, and MindTheGapps. OpenGapps is being removed as per post #11. Do your own research as to what is the most reliable gapps option for you.
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:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
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/

Monthly release notes
June 10, 2023 release notes
1. Incorporates June 5 as per https://review.lineageos.org/q/topic:R_asb_2023-06
May 8, 2023 release notes
1. Incorporates May 5 as per https://review.lineageos.org/q/topic:R_asb_2023-05
Apr 18, 2023 release notes
1. Incorporates Apr 5 as per https://review.lineageos.org/q/topic:R_asb_2023-04
March 19, 2023 release notes
1. Incorporates Feb 5 and Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02 and https://review.lineageos.org/q/topic:R_asb_2023-03
Jan 8, 2023 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
Dec 12 release notes
1. Incorporates Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
Nov 12 release notes
1. Incorporates Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
Oct 9 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
Sept 11 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Fixes non working touchscreen and hardware buttons when powering up with power cable plugged in and device turned off. However, the recommendation is still to unplug your charger, wait 30 seconds before pressing power button when your device is turned off.
https://github.com/retiredtab/andro...mmit/7e0657629efedc7f06f6f6fb57199fca0b4e8ea6
https://github.com/retiredtab/andro...mmit/e17c44d2e282d67b243a1c99ce62127e83052c4f
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/6db8e690141a98e5cf9e6952c3572c127c0cf8ea
Aug 10 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Fixes saving of color profile in live display during a reboot/shutdown.
https://github.com/retiredtab/andro...mmit/01b1ed6ba8c268a19762031415fde1b4e45d4ac3
3. Fixes offline battery charging by writing rules to allow charger to access certain files. This removes the previous workaround. Thanks to @simon-edwards for providing an adb logcat that showed the denials.
https://github.com/retiredtab/andro...mmit/041ae45960170e68410b059f4f709e9c14b79a99
July 23, 2022
1. Added argosd to improve wifi throughput as per https://github.com/retiredtab/andro...mmit/c181aa0c5192e46a5a03d4451e2648481a520c0f
2. Incorporates July 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
3. Incorporates a workaround for offline charging.
https://github.com/retiredtab/andro...mmit/9d019f0a3be789850a9add18d042990631f05b44
Previously, if the device was off and you plugged in a charger, it would show a battery icon and this would display indefinitely giving no sign of charging animation. With this workaround, the battery icon is displayed for a few seconds and then a white circle with a charge symbol inside it is shown to indicate it's charging.
After a few seconds, the screen will go blank and continue charging. The side effect of this workaround is that in order to turn on the device, you first must unplug the charger and then turn on your device. If you try to turn on the device with the charger cable plugged in, it won't turn on.
June 12, 2022
1. Removed vibrator code from gts2-common as wifi only models don't have vibrator motor (only LTE models).
https://github.com/retiredtab/andro...mmit/e54aee73a98e3cef6e74f96c1815cec9c82ff10d
https://github.com/retiredtab/andro...mmit/dd846b06378182398c55b57b2edc2537369bd509
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
May 12, 2022
1. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
2. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ.

Reserved.

Initial public build called lineage-18.1-20220411-UNOFFICIAL-gts28wifi.zip. The sha256sum file is provided as well to ensure integrity of download.
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.

Congratulations on the awesome release!

New build called lineage-18.1-20220512-UNOFFICIAL-gts28wifi.zip
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
May 12, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already
2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
4. If you are upgrading from the April 11 build, you may dirty flash the May 10 build. If you are NOT coming from the April 11th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.

Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim

kimrosebush said:
Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim
Click to expand...
Click to collapse
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]

lpedia said:
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
Click to expand...
Click to collapse
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim

I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.
This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.
https://forum.xda-developers.com/t/...rsions-devices.3098071/page-367#post-86885091
It's also shown up in other roms like
https://forum.xda-developers.com/t/...7-1-04-30-2022.3937956/page-100#post-86885353
This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.
Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.

kimrosebush said:
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim
Click to expand...
Click to collapse
Good to hear!
Note that you don't have to be quite so brutal about wiping absolutely everything for a 'clean' flash. I manually wipe Dalvik / ART Cache, Cache, and System, and then Format Data. I have never reformatted the SD.
If you have any further trouble, I suggest you try starting again with a clean flash and a different gapps package, or try doing without any gapps, as @retiredtab has recommended in the post above.
In my experience, some gapps packages, or sometimes just a particular version of a gapps package, don't work with some ROMs. I have not tried opengapps, but I can confirm that BiTGApps-arm-11.0.0-R45_signed.zip does work on my T710 with this particular ROM version.
I personally like BiTGapps because it installs only the bare minimum needed (Google services and Play Store; doesn't even automatically run Google Setup) and doesn't have to be installed before first boot. So it's possible to install LOS, boot the system, make sure everything's working, then go back into TWRP and install gapps. If any problems turn up, this approach also makes it easier to tell whether it's something to do with LOS or with gapps.
You could also try running LOS without any gapps, and if you decide you want gapps after all, install BiTGapps without having to clean-flash and start again.

I just installed this rom two days ago. It has been working great. Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message. Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Would you have any idea what is going on or how I should deal with this?
Thanks,
MC

Dr_MC said:
Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message.
Click to expand...
Click to collapse
On April 6, @lpedia and I had a PM discussion about signing builds.
lpedia wrote
Code:
"About signing builds ... an issue with just using the default test-keys signature is that someone can easily create
their own builds and pass them off as someone else's, possibly adding malicious or just plain bad code, and their
package would look just like the original."
I replied
Code:
"For our purposes, maybe we should just include the sha256sum and recommend that the users verify
them to ensure the file downloaded correctly and it wasn't modified?"
To get stop seeing that trust message, goto settings, privacy, trust, turn off build signature.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
I can't see the Crave app in Aurora Store. I use the app devcheck to check for root access and the screenshot clearly shows it's not rooted.
There's nothing in my code to enable root. In fact, I don't even want root on my devices.
For Crave, you can try using Magisk and it's hide root function to see if that will fool Crave into thinking the device is not rooted.

Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
I did installed the above root checker app and got the same message. That is, the T710 rom, by default is NOT rooted. I don't know why Crave would say it's rooted.
I believe root checker's main function is to verify that your rom is "rooted" so when it says "root access is not properly installed.", it's trying to tell you that your attempt to use Magisk or similar type app to root the rom was unsuccessful.
BTW, you are better off using devcheck as it's an excellent ad-free utility that I use on a regular basis to help develop this rom vs the ad-infested root checker app. While devcheck isn't open source, it's written by flar2 who is a xda member here.

Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
Root Checker Basic says "Sorry! Root access is not properly installed on this device" when asked to confirm root status on an unrooted device. So as far as that app's concerned, it just means "I can't confirm it's rooted". Which is to be expected if it isn't rooted and you haven't even tried to root it.
If that isn't the app you're using, see if you can find out what it means to your particular root-checker app.
Dr_MC said:
Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
Did the CRAVE app work on this device when it had the stock Samsung ROM? Do you have to register devices to receive this service? If so, might it need to be re-registered? Because its device ID will have changed.

Thanks for suggesting devcheck. It says I'm unrooted. Perhaps Crave noticed the unlocked bootloader or the custom ROM.

It did work with stock. It was registered, twice in fact. I deleted both, registered it again. The ap still says I'm rooted. Oh well, that's ok, I can use crave through a browser.
BTW do you know where I can find the stock keyboard?
Thanks

Dr_MC said:
BTW do you know where I can find the stock keyboard?
Click to expand...
Click to collapse
If you mean the Samsung keyboard - sorry, no, I don't. I switched to a different keyboard years ago. Google's GBoard has similar functionality, I think. MS SwiftKey is OK, too - has the best (most relevant) suggested text of any of the keyboards I've tried.

ROM working fine for me after trial and error with various gapps. FWIW I ran into the "just a sec " with opengapps. I finally had some joy by flashing the rom, but not gapps. Boot the ROM and completely setup it up Lineage. Then I restarted and flashed open gapps. When I rebooted everything came uo fine and has been solid eversince. Kudos your you gentlemen for fixing the Wifi ! Its been nice to have it work stably.

[UNOFFICIAL][ROM]ALPHA LineageOS 19.1 for SM-T710 - June 12, 2023

LineageOS 19.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLYModel: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. DRM level 3 (SD definition)
10. deep sleep
11. camera
1. fingerprint is completely removed in 19.1. When I tested it in March 2022, it wasn't compatible with keystore2 and as I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
it never worked properly after deep sleep. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. workaround to disable scoped storage. In 18.1 there was a workaround to disable scoped storage, but that no longer works in 19.1. So if you have a lot of apps or data on an external microsd, the performance may be severely degraded.
4. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems.
5. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
6. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. In alphabetical order.
@ananjaser1211
- helping out with libGLES_mali problem when I couldn't figure out why T810, for 3 months, wasn't booting with graphics
- answering more 5433 related questions wrt to certain features.
@bluess57
- joining the team and helping fix some of the legacy code problems
- pending code commits to come in the future
@bmwdroid
- testing many pre ALPHA builds and reporting the results
@CuckooPenguin
- testing many pre ALPHA builds and reporting the results, but sadly his T810 was killed by a cat (true story)
exynos5420 team
- making suggestions regarding radare2 debugger/code analyzer when I couldn't figure out why T810, for 3 months, wasn't booting with graphics
Kyle Harrison
- giving me a clue on how to fix the binder/keystore2 problem with msm8916 which ultimately led me to fix the same problem on the exynos5433 devices
- sharing his code on his github repos where I could study his commits to help bring up 19.1
- making code commits on LineageOS wrt to legacy devices like ours
- sharing the repopicks necessary to bringup 19.1
@lpedia
- testing many pre ALPHA T710 builds starting in April 2022 and reporting the results
- verifying my build instructions work so that the technically inclined can build this from source
- building, maintaining and most importantly, testing the T710 18.1 builds before monthly security patches release
- volunteering to build, maintain and test T710 19.1 builds
@metterschling
- reaching out and joining our group to help with code and fix problems
- testing many pre ALPHA builds and reporting the results
- pending code commits to come in the future
@pflyaz
- testing many pre ALPHA builds and reporting the results
- writing install instructions for the newbies
@simon-edwards
- reaching out and joining our group to help with code and fix problems
- testing many pre ALPHA builds and reporting the results
@tarkzim
- helping me fix the gpsd crash problem because I was missing the libutils library in my Android.bp file
- sharing his code on his github repos where I could study his commits to help bring up 19.1 especially wrt to hal audio 2.0 and camera 1.0
@Yogi555
- testing many pre ALPHA builds and reporting the results
- building, maintaining and most importantly, testing the T810 18.1 builds before monthly security patches release
As you can see, it's truly a team worldwide effort in getting this ALPHA 19.1 build out.

Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. 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
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/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. 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 April, 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.5.2_9. Get it from https://github.com/retiredtab/android_device_samsung_gts28wifiQ6. 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 #5.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:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
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://forum.xda-developers.com/t/...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:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
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/lpedia-sf/files/gts28wifi-19.1/

NOTE: lpedia has personally tested each build on his device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
June 12 , 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-06
May 7 , 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-05
Apr 18 , 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
March 20 , 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
Feb 12 , 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-02
2. Use stock android.hardware.power for CPU/SoC management so little cores can go as low as 400Mhz. Previously, the minimum clock speed was 1200Mhz and this may have caused some overheating. See
https://github.com/retiredtab/andro...mmit/8480e024cb15d82b9d418c44efd9257db173b49e
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-01
Dec 12, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
Oct 10, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10
Sept 11, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/8068a4a66ae7c576973807b392e686110126150c
Aug 11, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-08
2. Initial ALPHA release to public.

Reserved.

Tab S2 T710 Upgrade Procedure for the LineageOS 19.1 ROM by retiredtab
These installation instructions work for both Tab S2 T710 and T810, starting from a device running stock Android 7.0. I have both devices and have tested the procedure on both. I am a Windows guy, so these instructions assume a Windows PC. I am a lifelong techie guy and an Android enthusiast. My current “production” devices are Samsung S22 Ultra and Samsung Tab S7, but I do love the size and performance of the Tab S2 T710 so am extremely happy that @retiredtab and @lpedia have been successful at making Lineage 19.1 run on the Tab S2. But I am not developer, so these instructions will work for any competent newbie who’s looking for LOS 19.1 on their Tab S2 tablet. I do realize there may be alternative approaches for those who have deeper Android tech knowledge than me, but this procedure does work every time.
Step 1 – Preparation
Update your Tab S2 to the latest stock software.
Install a micro-SD card into your Tab S2.
Enable Developer Options – tap Build Number seven times.
In Developer Options, turn on USB debugging.
Connect your Tab S2 to your PC via USB and download onto the micro-SD card three files:
Retiredtab’s latest Lineage 19.1 ROM from lpedia-sf - Browse /gts28wifi-19.1 at SourceForge.net (T710) or retiredtab - Browse /SM-T810/19.1 at SourceForge.net (T810)
NikGapps-core-arm64-12.1-20220709-signed.zip from https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/
Magisk-v25.2.apk from https://github.com/topjohnwu/Magisk/releases
Magisk is optional if you want/like root.
Download to your PC TWRP_3.5.2_9_SM-T710_20210719_Unofficial.tar from retiredtab - Browse /SM-T710/TWRP at SourceForge.net (T710) or twrp-3.5.2_9-0-gts210wifi.img.tar from Download TWRP for gts210wifi (T810)
Download to your PC Odin, from https://technastic.com/wp-content/uploads/2020/02/Odin3_v3.14.4.zip, and extract the zip.
Step 2 – Install TWRP Recovery
Power off your Tab S2.
Launch Odin on your PC and press OK.
Power up your Tab S2 into Download mode by holding down Home+VolDown+Power.
Then at the Warning screen hit VolUp.
Connect your Tab S2 via USB to your PC, and you should see Added!! in Odin.
Click AP in Odin and select the downloaded TWRP.
In Odin Options, uncheck Auto Reboot.
Click Log tab again.
Click Start in Odin.
Installing TWRP only takes a couple of seconds.
You will see progress in the Log, and Pass at the top of Odin when done.
Step 3 – First boot into TWRP
This part is tricky!
Power down your Tab S2 by holding down VolDown+VolUp+Power.
IMMEDIATELY the screen goes blank, hold down Home+VolUp+Power.
Keep holding down until you see the TWRP home page.
If you end up booting into Android rather than TWRP then you will have to repeat Step 2 and Step 3 again.
Step 4 – Backup your stock ROM
In TWRP, select Backup, Select Storage to choose your micro-SD card, check all the partition boxes, and then swipe Backup.
Confirm your backup is good
In TWRP, select Wipe, then Advanced Wipe.
Select all partitions except Micro SD Card (and USB OTG).
Swipe to Wipe.
Back, Back again, then Format Data
Type yes, and tap check.
Back, Back, Back, and select Restore.
Select Micro SD card and your backup.
Restore all partitions and allow restore to complete.
Reboot to System, and confirm you are back to stock.
Step 5 – Install ROM and NikGApps
In TWRP, select Wipe, then Advanced Wipe.
Select all partitions except Micro SD Card (and USB OTG).
Swipe to Wipe.
Back, Back again, then Format Data
Type yes, and tap check.
Back, Back, Back, and select Install.
Select your micro-SD storage.
Select the Lineage-19.1 ROM.
Add more Zips, and select nikgapps.
Swipe to confirm Flash.
Install takes about 3 minutes.
Wipe Cache/Dalvik, and Swipe to Wipe.
Reboot System.
Step 6 – Build your Android 12 Tab S2
First boot into Lineage is less than a minute, and then the Lineage boot animation takes less than 1 minute before “Welcome to LineageOS” appears.
At the end of the initialization process, be sure not to choose the Replace Lineage Recovery option, otherwise TWRP goes away.
Set up your Android device per your preference. I am a mainstream Google/Google Play Apps user, and I have loads of Apps, so it takes me a long time to install my Apps and set the tablet up for daily use. If you are less of a pack-rat, it shouldn’t take long!
I have found that, by not installing Magisk initially, I can restore all my Apps, including the sensitive ones such as Peacock, Netflix, Disney+, etc. All Apps run normally, and when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
I recommend leaving tablet completely alone during the initial Apps and Data restore process. When I get impatient and fiddle around as it’s copying I’ve seen crashes.
Once all copying is done, do your unique Android setup. My go-to Android settings are:
Nova Prime Launcher (actually, gets selected during the initialization process, but I load my layout from backup at this time)
Microsoft Swiftkey
Screen timeout 30 minutes, and screen saver Clock
Dark theme off
Disable taskbar.
Plain dark blue wallpaper
Touch, screen locking, and charging sounds off
Battery %age next to icon
Default USB = File Transfer
Developer Options enabled, and USB and Rooted debugging selected
Window/Transition/Animator Scale all set to Animation Off
FX File Explorer
Microsoft Edge as default browser (with AdBlock enabled and Google as search and sync to my PC)
Raindrop, for all my cross-platform/device bookmarks
Advanced restart menu (to allow reboot into TWRP).
Step 7 – Make Root – Optional
Restart Tab S2 into TWRP.
In TWRP, install Magisk-v25.2.apk.
Reboot System
In Android install Magisk-v25.2.apk.
Open Magisk and select zygisk in settings.
Restart again.
You now have root. I test by enabling root in FX File Explorer and granting root.
Step 8 – All done! Enjoy!
I do a final and full TWRP backup once the device is solid on Lineage 19.1.

On lineage-19.1-20220811-UNOFFICIAL-gts28wifi.zip I don't have an onscreen keyboard. I rebooted into TWRP and tried the GBoard Add On, but after that stil no onscreen keyboard. Installed it with NikGapps core and retried with full. If you use full, something from Google keeps crashing.
In system settings with full NikGapps, only keyboard available is Google speak option.
Both were Clean Installs.

djcasl said:
I don't have an onscreen keyboard.
Click to expand...
Click to collapse
We found another way to workaround the missing on screen keyboard. @lpedia tested with the Google login accounts and I tested it with Bluetooth numeric PIN. It's documented back in post 1 to say
=== begin ===
keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
=== end ===

retiredtab said:
We found another way to workaround the missing on screen keyboard. @lpedia tested with the Google login accounts and I tested it with Bluetooth numeric PIN. It's documented back in post 1 to say
=== begin ===
keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
=== end ===
Click to expand...
Click to collapse
I can try again. However, I went to languages and input and there was no keyboard option whatsoever. I tried manage keyboards, but could not activate one as well. To me it looked like there was no onscreen keyboard installed at all. So I couldn't use this workarround.
Update:
So I reinstalled, but one thing I didn't do is change initial language to Dutch. So now I am going see if I can restore my device, but so far it hasn't found my backup. Or asked to restore it. Don't know how I can reinitilaze that if not asked at setup.
Update 2: Reinstalled with NikGapps Omni this should have google setup and google restore. But didn't get question to add google account during setup. After adding account didn't get a question to restore data.

New build called lineage-19.1-20220911-UNOFFICIAL-gts28wifi.zip
NOTE: lpedia has personally tested each build on his device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
Sept 11, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/8068a4a66ae7c576973807b392e686110126150c

Error!

retiredtab said:
New build called lineage-19.1-20220911-UNOFFICIAL-gts28wifi.zip
NOTE: lpedia has been personally tested each build on his device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
Sept 11, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/8068a4a66ae7c576973807b392e686110126150c
Click to expand...
Click to collapse
Thanks for the charging fix. Now my tablet does not get hot while charging. That's great!
But the charge does not show more than 76%. I have left it for 2 days untouched but it does not go above 76%. It did this even before the 9/11/22 version. Unless I need to recalibrate battery??? Never had to do that before.

chappatti said:
But the charge does not show more than 76%. I have left it for 2 days untouched but it does not go above 76%. It did this even before the 9/11/22 version. Unless I need to recalibrate battery??? Never had to do that before.
Click to expand...
Click to collapse
I suggest the following:
1. boot into TWRP and see what the battery % is. If it's not 100%, let it charge to 100%.
2. After charged to 100%, boot into OS and see if it's at 100%.
3. If OS shows 100%, it's fixed. If not, repeat steps 1 and 2 at least 3 more times.

retiredtab said:
I suggest the following:
1. boot into TWRP and see what the battery % is. If it's not 100%, let it charge to 100%.
2. After charged to 100%, boot into OS and see if it's at 100%.
3. If OS shows 100%, it's fixed. If not, repeat steps 1 and 2 at least 3 more times.
Click to expand...
Click to collapse
ha! will try....

retiredtab said:
I suggest the following:
1. boot into TWRP and see what the battery % is. If it's not 100%, let it charge to 100%.
2. After charged to 100%, boot into OS and see if it's at 100%.
3. If OS shows 100%, it's fixed. If not, repeat steps 1 and 2 at least 3 more times.
Click to expand...
Click to collapse
Still does not charge to 100% outside Twrp.
OK. So in Twrp it goes to 100% and on reboot it says 100% . But then again when it discharge, it will not charge above 76%. I repeated the process, but outside Twrp it does not charge above 76%.
Any ideas??

chappatti said:
Still does not charge to 100% outside Twrp.
OK. So in Twrp it goes to 100% and on reboot it says 100% . But then again when it discharge, it will not charge above 76%. I repeated the process, but outside Twrp it does not charge above 76%.
Click to expand...
Click to collapse
I'll answer the above in the T810 thread since that's what you have, but @lpedia and I have been using the 19.1 T710 since mid April and we would have noticed if it stops charging at 76%. I'll let lpedia comment since he uses the 19.1 T710 as a daily driver more than I do.

New build called lineage-19.1-20221010-UNOFFICIAL-gts28wifi.zip
NOTE: lpedia has personally tested each build on his device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
Oct 10, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10

it charges just fine for me

haircut313 said:
it charges just fine for me
Click to expand...
Click to collapse
Just for reference, the charging weirdness was not a device or ROM issue. It was on a T810 (the report of the issue was posted to this thread by accident), and was discussed on the T810 LOS 19.1 thread. It turned out that the device had an app that was interfering with battery charging. Removing that app fixed the problem.

Its working so smooth I like it! The only problem I found is the audio when I play videos in VLC player, didn't play the audio. Can't hear anything. ah! And sometimes my tablet reboots

Kyrat said:
Its working so smooth I like it! The only problem I found is the audio when I play videos in VLC player, didn't play the audio. Can't hear anything. ah! And sometimes my tablet reboots
Click to expand...
Click to collapse
@Kyrat - does VLC audio work otherwise, eg to play music? If not, you probably have the same problem as I came across with some versions of VLC. There's no audio output at all with VLC's default audio output method, AudioTrack. Changing that to OpenSL ES fixed the problem for me.
That setting is in VLC Settings > Extra settings > Audio > Advanced > Audio output.

Database Develop

welcome