Related
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Requirements:
Flashtool 0.9.15.0
Rooted SGP311 (on any Android version up to and including 4.4.2) with custom recovery installed.
If you do not meet these conditions, for example, if you are on an unrooted system, here is a guide to get you on a rooted 4.1.2 with recovery:
http://forum.xda-developers.com/showpost.php?p=53063218&postcount=14
This works on locked or unlocked bootloaders. This also works on any customization.
The procedure should work with any pre-rooted Android version but I started with 10.1.C.0.370 (4.1.2) which was rooted with DooMLoRD_Easy-Rooting-Toolkit_v17, patched with remountrebootfix, and equipped with XZDualRecovery.
Limitations:
This process can delete the files on your internal SDcard so back them up. Also, you will have to reinstall all your apps, as they get erased too.
Download link:
Mega
https://mega.co.nz/#F!UkshjY6A!HIW7xGf1E1oa04e0N3b1OA
You only need the zip and ftf files. The txt file is just the checksum if you want to verify that your download is error-free. I strongly recommend that you do the checksum before flashing.
Instructions:
1- Backup before you start messing with your tablet!
2- Put system.flashable.zip in /sdcard of your tablet.
3- Keep SGP311_10.4.1.B.0.109_R2C_VMo_US_CA_PR_NoSystem.ftf on your PC.
4- Disconnect any USB cable that may be attached to your tablet.
5- Reboot to recovery. Preferably to TWRP, but you can make CWM work too.
6- Do not wipe anything.
7- Once in recovery, flash system.flashable.zip.
8- It is important to NOT REBOOT the tablet after this step.
9- Find and use the Power Off option in the recovery and turn your tablet off. In CWM based PhilZ Touch it is under "Power Options" -> "Power Off". In TWRP it is under "Reboot" -> "Power Off". If you see your tablet rebooting, force it to turn off by pushing the power and volume up keys simultaneously (or however else you can!)
10- Open Flashtool 0.9.15.0 and click on the flash icon. Choose flash mode.
11- Navigate to where you have saved SGP311_10.4.1.B.0.109_R2C_VMo_US_CA_PR_NoSystem.ftf and flash this ftf with your tablet in flash mode. To put your tablet in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
12- Reboot and enjoy!
Credits:
I only put the files together. All the credit should go to XDA's [NUT] and DooMLoRD and many others...
I had a few requests from people who upgraded to 4.4 and were not happy with the speed. So I made these file in case you want to downgrade to rooted 4.3.
Enjoy.
Downloading now. Thanks!
hi njajoor
thanks to your guides i was able to flash in quick an easy way all the procedure was smooth.
may i kinow how did you tewk your rooted 4.3 rom or which settings do you recommend to improve the performance of the tab Z?
many thanks again
mame3876 said:
hi njajoor
thanks to your guides i was able to flash in quick an easy way all the procedure was smooth.
may i kinow how did you tewk your rooted 4.3 rom or which settings do you recommend to improve the performance of the tab Z?
many thanks again
Click to expand...
Click to collapse
This is what I do normally, but you may want to change it for you specific needs:
1- In settings:
Wifi, menu, advanced, network notification unchecked; Keep wifi on never; wifi optimization checked
NFC off
Sound, touch sound off; screen lock sound off
Display, sleep after 30 seconds, double tap to wake up checked, brightness set to lowest
Power management, stamina mode on
Keyboard, sounds feedback, sound on key press unchecked
Accounts, email: set sync frequency to 1 hour; Skype: sync off
2- install adaway
3- use titanium backup pro or apps tab in settings to freeze/disable:
Crackle and Netflix (unless you use them)
Anything with the word or logo of Facebook or twitter or social engine in it. You are better off using the browser for these.
If you use both email and Gmail apps, disable Gmail and set it up in email app.
All Google play apps except store and Services
Google plus and hangout
McAfee, reader by Sony, let's start psm, video unlimited, wisepilot
Mobile date, mobile network, sim lock, and sim toolkit (sgp311 doesn't have mobile data)
PO Box touch and Xperia Chinese keyboard (this may significantly reduce your keyboard flickering if not entirely eliminate it)
4- I install greenify, wakelock detector and juice defender on my other Android devices but I've come to believe Sony's stamina does an excellent job and none of that is necessary.
5- Turn gps on only when you use it
6- Remove active widgets from your home screen. I only have the clock and the weather left. If you want to keep the widgets put them on a separate display than the ones you keep your commonly used icons in.
With these settings mine is smooth as butter. I hope yours will be too.
HuiFei - 2 DIN Pure Android 4.2.2/4.4.2/4.4.4 RK3066/RK3188 Car Stereo Radio Head Unit. KGL/KLD/RM/GS/JY/MD/KYD/BN/HA [ROOTED]
This is a new thread for this car dvd that was first reported on comment #2224 of the AN-21 U thread.
Probably you are here because:
you want to root your unit. Only units with ROMs 4.2.2 can be rooted (see below how). The only way to have a rooted 4.4.x is installing a pre-rooted ROM (see below how)
you have a problem (no internet, no sound, buttons do not work, bad mic quality, rear camera image not showing, door opening not showing, etc.
you want to upgrade your unit to a newer software that has sleep mode, personalized music app, personalized functions, root, xposed, can remap buttons, etc.
All this is covered in this post and most of the problems that you can have are summarized in this post too. Please read this first post before asking. And use the search function of the thread, before asking. Thanks.
TRICKS THAT MIGHT SAVE 1000 QUESTIONS ON THE THREAD
Read below and here for basic questions asked and answered 1000 times.
How to root my unit. Only 4.2.2 can be rooted with an app (see below). To have rooted 4.4x you must install a pre-rooted ROM (see below)
Get sound when in reverse (thanx to @Keylo Lo)
here
Engineering/Factory settings password "126" (thanx to @blankers)
This allows you to change logo, sound volume, SWC codification, etc.
Activate USB debugging --> Go to Factory Settings and enter password "adbon".
System sound is low compared to Radio--> Go to Factory settings and change volume levels
GPS button does not trigger GPS app You need to choose predefined GPS app, in Settings--> GPS
Get Into Recovery
1 Press reset button and power button together
2 After about 5 secs release reset button, but keep pressing power button
3 When booting screen appears release power button.
4 It boots into recovery.
--Update 1-- some units without front USB have a different procedure
Firstly power on the unit and then long press the power button and then reset. Then the unit will get three rings and you loose your hand on the power button and short press the power button again. (thanx @netay)
--Update 2-- some others have this procedure (thanx @R4D3N)
1. Turn off the unit by holding 3-4 sec the power button.
2. Hold the RESET button + POWER button for 5 sec
3. Release the RESET button and keep pressing the POWER button for 2 sec
4. Release the POWER button and wait. The Recovery menu appears.
5. With the Volume knob you can move up/down and long press on Volume/Power button to select the option.
Get Into Bootloader
The process is basically the same, with the difference that you need to have the computer attached to the unit via the front miniUSB (if you do not have a front USB, you will have to ask your seller how to get into bootloader mode)
1- boot the unit as usual.
2- plug the front usb of the unit to your computer usb.
3- Then, push the reset button and the power button at once and keep them pushed. The reset button is the tiny pin next to the mp3 sdcard. The power button is the volume knob. You will hear the power cut throught the speakers.
4- Release reset button and keep power button pushed. Now the unit will reboot. You will see nothing, just a black screen. Do not release the power button yet. Your computer will detect a " new hardware", that is the RolckChip. When you hear the windows noise of new detected hardware, you can release power button. It will automatically install the drivers.
------------------------------------------------------------------------------------------------------------
HOW TO UPGRADE YOUR SYSTEM
BEFORE UPGRADING YOUR UNIT YOU MUST KNOW
MCU your unit, there are many (KGL, KGL1, KGL2, KGL3, KGL4, KGL5, KLD, KLD1, KLD2, JY, GS, KYD, MD, BN, HA, MX), If you install the wrong MCU, you will brick your unit.
To know which one you have. Go to Settings -->About
If still not clear, see: here or here.
If you cannot find it here, it probably means that you are in the wrong thread.
Resolution of your unit. 800x480 or 1024x600. If you install the wrong ROM, you will brick your unit.
Chip of your unit RK3066 or RK3188. It does not really matter, ROMs and MCU are compatible between chips.
IT IS ADVISABLE TO BACKUP YOUR SYSTEM BEFORE PLAYING WITH IT
Upgrading is supposed to be a safe operation, but you never know what can happen. So, before updating make sure that:
1- To backup of your system the easiest way is download nandroid root from google play, and do a nandroid backup with TWRP format). Save it in your external SD.
2- make sure you can enter in bootloader mode (see below how to)
3- it is recommended to backup your apps and data (use titanium from google play). The update will do a factory reset.
FOLLOW THIS TO UPGRADE YOUR ROM AND/OR MCU
0- Do a back up (copy the files somewhere safe) of your internal SD card memory. It will be wiped during the process.
1- Download the ROM (Resolution 1024x600 or 800x480) and MCU (KGL, KLD, JY, GS,RM, MX, BN, HA) for your unit.
ROMs--> repository This will get you a file named update.img. There are different "flavors" of ROMs.
Code:
- [user=853627]@coudu[/user] (rooted, stock). Early v4.0 and v4.1 have some problems.
- [user=3590033]@Malaysk[/user] (rooted, with very useful mods, some come with NEXT launcher)
- [user=6041319]@dsa8310[/user] (rooted, almost stock)
MCUs--> Latest MCUs by Malaysk are here . This will get you a file named mcu.img
2- copy the update.img you have chosen to the root of your GPS card.
3- copy the mcu.img for your specific unit to the root of your GPS card (if you do not want to update mcu.img, you can skip this step)
4- insert back the GPS card to the unit. If no window pops up, reboot the unit. At boot, the presence of update.img will be detected and a pop up window will ask you whether you want to update your unit. It will automatically reboot into recovery mode and update your unit. Once done, remove update.img and mcu.img from the root of the gps card or you will be asked every boot for an update.
5- In some Coudu´s (sd partition of 3Gb) and Malaysk´s ROMs versions, it is necessary to do a factory reset just after the first boot so that everything works properly.
6- If you lost buttons or radio after the upgrade --> Go to Factory settings (password 126) and choose the proper canbus for your car and the radio chipset. You can change boot logo if you want.
* If you get Google services error after upgrading to KitKat see this and this
------------------------------------------------------------------------------------------------------------------
THINGS YOU MAY WONDER BEFORE BUYING A HEADUNIT
Code:
[B]- Boot Up:[/B]: time is around 30s.
[B]- GPS[/B]: GPS positions very fast. TomTom, Navigon, Sygic, and regular off-line GPS work. Navigon and Sygic have some problems with some ROMs
[B]- Stand by mode[/B]: Latest ROMs and MCU have the possibility of choosing stand by mode with various times chosen.
[B]- Radio:[/B] radio stations are saved as frequencies
[B]- Bluetooth contacts:[/B] contacts are saved on the device.
- Works fine with Bose system (Audi)
- Possible ground loop noise that needs some tricks to be removed (see section problems)
- Torque works and can run in parallel with A2DP
- ELM327 works (might need special app like CarService in very weird cases)
- Camera works (might be better to get the one with RK3188 chip)
- There is no automatic brightness control because the unit does not have light sensor, but there are apps that can help
- The touch screen is extremely responsive. It works as good as most phones.
-------------------------------------------------------------------------------------------------------------------
HOW TO ROOT AND INSTALL TWRP
Instructions to get root (thanx to @webdude12)
It only works for Android 4.2.2. If you want to root 4.4.x you need to take apart update.img and inject SuperUser app (this is only for experts as @coudu, @Malaysk, @dsa8310 ). The alternative is to install a 4.4.x pre-rooted image and you do not have to do anything else. See below in HOW TO UPGRADE YOUR UNIT section how to do it.
If you want to root your 4.2.2, download Root Master 2.1.1 here
Code:
1- Install the APK.
2- Make sure you are connected to WiFi and you have an internet connection.
3- Open Root Master (do not upgrade to newer version unless you can read chinese, The newest version has different options, all in chinese. Version 2.1.1 just has a button that says "root".))
4- Press root button
5- Chinese characters will flash across the screen.
6- A second popup box will appear, press the purple button.
The app will automatically install SuperUser.
This program connects to servers oversea sending hardware information. The downloads a script that will attempt to root the device. If the first script fails, it downloads additional ones. Future goal is monitor this communication with a data logger and find which script works, so that a unique program can be written to achieve root.------------------------------------------------------------------------------------------------------------------
How to install TWRP recovery (thanx to Abdul_pt from Freaktab and 1-2-Hak and coudu)
You do not really need to install TWRP unless you wanna mod the rom yourself, if you mod roms you will know that already.
- a.t.m. you need a mouse to use TWRP because touch is not working yet
- if you install TWRP, you will not be able to update the update.img and mcu.img the way it was explained above.
If you still want to install TWRP:
Android 4.2.2 800x480
Download files here
And follow the post by 1-2-Hak
Android 4.4.2 800x480
Follow this: this
TWRP for 1024x600
See this post------------------------------------------------------------------------------------------------------------------
TRICKS AND MODDED APPS THAT DO WONDERS
Install app without adb when regular install does not work
Sometimes the app won't install normally and you need to sideload it.. This means that you need a computer and adb wifi. There is another way with which you won't need a computer. You just need to install a terminal emulator (you need root ).
1- Download the terminal emulator app you prefer
2- Download the app you want to install to /mnt/sdcard
3- Open terminal emulator
4- On the terminal navigate to /mnt/sdcard by typing
Code:
- cd /mnt/sdcard
- su
- pm install "NameOfTheApp".apk
Done, you are app is now installed.
Modified Radio Apps
To install radios you need to copy the app using ESExplorer or Root Explorer straight to /system/app in place of MTCRadio.apk
Radio version 4.2.2 800x480
Blue theme (thanx @1-2-Hak)
Rally style Buttons have been moved and skin changed for a Rally like one.
Forest style. Colors have been changed and frequency name is in big.
Radio version 4.4.4 800x480
Blue tint. Stock radio with big names and all in blue shades.
Red tint
Radio version 4.4.4 (Malaysk v1, aka alive)
1024x600. Has animation, in blue tones
[*]Car Service. Allows to use SWC and buttons with 3rd party apps (Latest Malysk ROMs already include it).
Download here (thanx @@KeiserSozeyFr)
If it does not install, copy directly to /system/app
[*]Microntek HeadUnit Service Latest Malaysk ROMs include it. It allows to use SWC with non native apps. It allows to make calls and send messages from Android part of HU, and to show toasts. You can find it straight on Google Play.
There is a modified version (probably outdated) with early start of services here
[*]Moded Music app. Two versions. One is the original with expanded list, so full names can be seen, and the other one has the list integrated in the background so it is always visible.
http://forum.xda-developers.com/showpost.php?p=53352994&postcount=894 (thanx to @dark alex)
anoher one here
[*]Set Loud Latest ROMs do no need it.
Method 1:
Just install this app: http://forum.xda-developers.com/showpost.php?p=53463910&postcount=963 (thanx to @dark alex)Method 2:
You need Tasker or Automagic or similar app.
Set up a task that runs at boot with the following code as "shell command"
am broadcast -a com.microntek.irkeyDown --ei keyCode 44
How to: http://forum.xda-developers.com/showpost.php?p=53553617&postcount=1058
[*]Speed-sincronized volume increase (AKA GALA)
This app will modify the volume of your unit according to the speed. The amount sensitivity can be adjusted.
http://forum.xda-developers.com/showpost.php?p=53441283&postcount=931 (thanx to @dark alex)
[*]PowerAmp Toast (thanx @agentdr8)
This app will show title/album/album art when tracks change while PowerAmp is in background.
http://forum.xda-developers.com/showpost.php?p=53964813&postcount=1461
[*]Rear Camera without icons (icons were included in the KitKat version 4.4.2) (thanx @typos1 and 4pda.ru guys)
http://forum.xda-developers.com/showpost.php?p=56888840&postcount=5096
[*] KLD Launcher 4.4.2 with bigger date
Launcher see picture
---------------------------------------------------------------------------------------------------------
FILE REPOSITORY, FIRMWARES and MCUs for KGL/KLD/GS/RM/JY/MD
Repository (everything is here, firmware up to date, mcus not so much)
More updated MCUs from @Malaysk & @darkleo --> here
Some of the firmwares are... (list not updated)
Custom KitKat 4.4.2 by 4pad.ru (RK3066)
Coudu's 4.4.4 v4.2 (RK3066) (January 2015 release), see here
- Coudu v4.0 and v4.1 have some problems. v4.2 is good (specially releases 150113 for KLD and 150113 for KGL). You might need MTCControlSettings.apk as in these latest releases coudu removed it.
Malaysk's roms (RK3066) w/ and w/o NEXT launcher, also 4.4.4 here
JY Android version is this one
Malaysk's roms (RK3066) version 24/05/15 Download here. It allows the remapping of the radio buttons.
dsa8310 JY rooted ROM 150513 (RK3188) Download here
-------------------------------------------------------------------------------------------------------------------------------
WIKI-Page
Basic info on everything
Another wiki with general info here-------------------------------------------------------------------------------------------------------------------------------
PROBLEMS AND SOLUTIONS FOUND BY THE USERS
Unfortunately the first issues with the promising unit arrived.
@webdude12 got a black screen while driving due to a broken clip (see attachment to figure out which one). One solution is to glue the clip so that it does not get loose. Not doing that can end up in major problems.
Unit might not boot on very hot conditions as it has a thermostate to avoid possible problems. It will work normally when cooled down.
Some apps do not show completely in the screen due to the low resolution.
However, there's a great solutions for that:
- you need root
- install xposed framework (google it)
- probably you need to sideload the apk with ADB as the unit refuses to install it normally.
- install "app settings" module in xposed framework (you can change dpi for individual apps and make them fit in the screen)
When add a google account, it doesn't show under accounts
fix --> http://forum.xda-developers.com/showpost.php?p=53809274&postcount=1303
Wifi or buttons do not work after update to 1.86 or 1.99 firmware versions
- This happens because the MCU or kernel of the new version is not adequate for your unit. Luckily MCUs and kernels are mixable for the same unit.
fix --> Install newest firmware with an older MCU in the usual way. Then install the kernel of a version you know used to work.
To install kernel alone --> Here and files needed here.
Kernel install for doomies (with pics): here
No radio reception
fix --> your ground cable might be loose Sold it back. see this and this and this.
SD card unexpectedly removed // USB unexpectedly removed
fix --> Thanx to @ R4D3N here
Mic sound is awful
-- WARNING --
For any unit, before removing the capacitor with the purpose of separating the BT card from the internal mic, you must make sure (with a multimeter) that the capacitor to be cut interconnects the MIC entry of the BT card with the internal mic. Please note that the capacitor is on the motherboard in the immediate vicinity of the (vertical) BT card (pics on fix for JY units can help you)
fix for JY units --> http://forum.xda-developers.com/showpost.php?p=57982083&postcount=7036
fix for KGL units --> http://forum.xda-developers.com/showpost.php?p=55775852&postcount=3982 and http://forum.xda-developers.com/showpost.php?p=55769511&postcount=3964
fix for KLD units --> http://forum.xda-developers.com/showpost.php?p=56529110&postcount=4592
Bluetooth modules not pairing
fix --> http://forum.xda-developers.com/showpost.php?p=56450438&postcount=4544
Google service error after upgrading to KitKat 4.4.2
fix --> http://forum.xda-developers.com/showpost.php?p=56791126&postcount=4866
and --> http://forum.xda-developers.com/showpost.php?p=56793317&postcount=4925
Wrong door being shown open. Only VW and KitKat 4.4.2
fix --> Go to factory settings, change "Rude"
TomTom not working on KK 4.4.*
fix --> http://forum.xda-developers.com/showpost.php?p=56991862&postcount=5336
--WARNING-- if you installed chainfire SuperSU you have to slightly modify install-recovery.sh. You must substitute /system/xbin/su --daemon & --> /system/xbin/daemonsu --auto-daemon &
TomTom bundle: use maps stored on external SD// Update TomTom maps with map share free// Early start of softwares// SWC from boot/install-recovery.sh
see --> this (thanx to @dsa8310 WARNING: see post #10440 and comments therein when using install-recovery.sh)
summary of early start services commands --> here
Sygic not installing
see --> http://forum.xda-developers.com/showpost.php?p=58983985&postcount=9020
3G USB Dongle not working properly
Probably is due to the USB is underpowered. Use a (externally) powered USB hub. Or follow this how to to power the USBs of your unit.
how to --> http://forum.xda-developers.com/showpost.php?p=58949495&postcount=8949
short version-->http://forum.xda-developers.com/showpost.php?p=58970437&postcount=8983
the following 2-3 pages contain comments about that mod worth reading.
see --> http://forum.xda-developers.com/showpost.php?p=58249825&postcount=7614
Another how to for external powered USB hub--> http://forum.xda-developers.com/showpost.php?p=58979534&postcount=9011
3G connection lost after some drive
see --> http://forum.xda-developers.com/showpost.php?p=58539736&postcount=8162
and --> http://forum.xda-developers.com/showpost.php?p=58982926&postcount=9017
DVR camera not recording or stopping - DailyRoads Voyager app
see --> http://forum.xda-developers.com/showpost.php?p=58648519&postcount=8383
also --> http://forum.xda-developers.com/showpost.php?p=58977534&postcount=9007
Viper4Android not working properly
Check this and look for Viper4Android config here
When I try to install an app, I cannot tap the "install" button
This happens because you are using a screen dimmer. It is a protection function. Just temporarily disable screen dimmer app and you will be able to install the app.
Radio does not show proper pty
Download this modified version (it is v 4.2.2) of RadioMTC
Start apps while booting, you need install-recovery.sh script (included in latest Malaysk ROM)
Read this post to understand how it works. If PowerAmp is auto starting at everyboot, see this
Improve Radio quality by replacing hardware parts. Thanks to 4pda.ru
see --> http://forum.xda-developers.com/showpost.php?p=60895894&postcount=12932
and http://forum.xda-developers.com/showpost.php?p=60896400&postcount=12936
Remap radio buttons. Thanks to 4pda.ru and agentdr8
see -->http://forum.xda-developers.com/showpost.php?p=60941619&postcount=13030
Upgrade RK3066 to RK3188 (needs hardware replacement)
see --> http://forum.xda-developers.com/showpost.php?p=60972222&postcount=13086
or this --> http://forum.xda-developers.com/showpost.php?p=62832292&postcount=18752
Replace damaged touch screen
tutorial --> http://forum.xda-developers.com/showpost.php?p=62832292&postcount=18752
I did not want to create a thread for this but I think it is best kept here then so if anyone want's to copy my signature to add aome links to the other sections here is it for you convenience:
Code:
MTCB Android Headunits: [*URL="http://forum.xda-developers.com/android-auto/mtcb-android-head-units-qa"]Questions & Answers[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-android-head-unit-general"]General[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-hardware-development"]Hardware-Dev[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-software-development"]Software-Dev[/URL]
"MTCB" covers Klyde, HuiFei (KGL), Joyous (Joying is reseller), GS, Eonon and many more vendors. Please check Settings->About tablet -> MCU Version. If it starts with "MTCB-" you are right in above forums.
Please remove the asterisks (*) - That looks like this:
MTCB Android Headunits: Questions & Answers | General | Hardware-Dev | Software-Dev
"MTCB" covers Klyde, HuiFei (KGL), Joyous (Joying is reseller), GS, Eonon and many more vendors. Please check Settings->About tablet -> MCU Version. If it starts with "MTCB-" you are right in above forums.
Click to expand...
Click to collapse
Full Tutorial and clean Rom by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
You can search on this thread to find the files for Android 6.0.1
You need to root and install TWRP for flashin Android Marshmallow
I recently bought a ZTE Axon Mini here in Europe. It is a pretty good phone, the only problem is the software part which has some lag and UI problems.
They certainly can be fixed with a custom rom or rooting and doing changes or by ZTE themselves.
Here I will write the problems
1) The touch responsiveness could be more fast and snappy, when scrolling etc.
2) random lag occurs from time to time, Some other lag issues with the background apps closing etc.
3) Notifications sometimes do not show at all even when keeping aps on whitelist (deactivate mi assistant to solve this)
4) Dolby Audio gets deactivated almost every time you use headhones .
5) Marshmallow release anytime soon?
6) the UI is too heavy for the phone, most stock apps have issues
7) You cannot adjust brightness inside camera app on auto mode, the HDR mode is really not good ( too blurry)
Click to expand...
Click to collapse
Most of these issues have been fixed on 6.0.1 Rom (search thread)
Summary and further tweaks by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
Edit 1--------------------------------------------------
Root method has been found and works on all axon mini models Android 5.1.1
Credit for finding @orbitz52 and @Heze85
http://www.mgyun.com:81/thread-48100-1-1.html
Just translate the page on Chrome and follow the instructions
For 6.0.1 Marshmallow Root you need to have custom recovery and flash supersu via recovery
Edit 2--------------------------------------------------------
Notification issue has been solved (read pages 1-3)
!!IMPORTANT NEWS!!
Custom recovery for axon mini by @Bormental
TWRP 3.0.2 for ZTE Axon mini unofficial.
It works in all Axon mini mods (B2015 and B2016 with or without "Force Touch".
Installation manual:
1. ROOT device (see the manual in this thread).
2. Download the archive with TWRP.
3. Unzip twrp.img to phone's internal storage.
4. Install any terminal emulator from Google Play and open it.
5. Paste these lines one by one to terminal:
Code:
su
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/stock_recovery.img
dd of=/dev/block/bootdevice/by-name/recovery if=/sdcard/twrp.img
6. Keep the file stock_recovery.img in safe place. It is your stock recovery image.
7. Now TWRP is installed. You can run it by holding vol+ and power button when phone is off or just reboot your phone while holding the vol+ button.
HOW TO ENTER RECOVERY WHEN ON BOOTLOOP WITHOUT EMPTYING THE BATTERY by @Crisvendetta
1. Hold volume up and power button the whole time of this procedure until the moment said below
2. Keep holding, the first time the device will be stuck on boot logo for 10 seconds and restart
3.Keep holding until the device is stuck on boot loop for 5-6 seconds before powering down.
4. RELEASE BUTTONS AS SOON AS SCREEN SHUTS DOWN ON THE 5 SECOND BOOT
5.Now Device is shut down
6. You can enter recovery normally by holding power plus volume+
What to do if the phone with android 6.0.1 is suddenly switching off during backup, restore, copying heavy files or installing ROM:
CLICK TO HIDE CONTENT
Install aboot image from 5.1.1
Reboot recovery
Make all needed operations
Return back aboot image from 6.0.1 before rebooting to system
Attention! Android will boot only with proper aboot image installed!
WARNING! Your warranty is now void! Any operation with firmware can break your phone!
Special thanks
1) @Bormental
2) @orbitz52
3) @demenicis
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Issues
I have a lot of problems with this phone. Sometimes apps doesn't work. Most of the times I can't recive notifications, sometimes is laggy, some options doesn't work or change to it's inicial configuration, force touch is not accurate.... A lot! Please ZTE do something!. BTW, how can I solve the notification problem?!
Thank you so much
Korgan1983 said:
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Click to expand...
Click to collapse
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Notification
Crisvendetta said:
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Click to expand...
Click to collapse
Yes, the notification part is the worse. It should be solved in the coming days...
ZTE AXON notifications FIX !
Aitex10 said:
Yes, the notification part is the worse. It should be solved in the coming days...
Click to expand...
Click to collapse
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications. Otherwise, disable Mi-Assistant from the settings/apps.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Also remove the accelerator settings inside the mi assistant / software settings
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
I am also on 5.1.1.
Notification works better with enabling autostart and enabling background settings. I have disabled the Accelerator / Mi-Assistant, Android has its own power management.
Hello,
i did not find MI-Assistant, where exctely?
Crisvendetta said:
Also remove the accelerator settings inside the mi assistant / software settings
Click to expand...
Click to collapse
Hi,
where can i finf mi Assistant??????
ridowski said:
Hi,
where can i finf mi Assistant??????
Click to expand...
Click to collapse
Which version of Axon do you have ?
It seems the ZTE Axon A1R doesn't have mi-assitant or even power manger/ background manager, and it's on 5.1.1
Guess no way to get that without unlocking the bootloader?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
hoppi05 said:
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
Click to expand...
Click to collapse
Inside mi assistant remove the auto run on startup and then press exit the mi assistant.
This last few days every notification has shown on time, I did a fresh factory reset and the applied all the settings. Don't know if that would help everyone but I am satisfied until now
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
I was wondering what is the difference between zte b2015 and b2016 models. I have the b2016 but it seems nothing changes with b2015.
My geekbench 3 scores single core 712 multicore 3107
Antutu 38051 .
Korgan1983 said:
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
Click to expand...
Click to collapse
Indeed, disabling Mi-assistant together with the steps mentioned, solves all notification issues
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
What model is that? Sounds like the US version?
LineageOS 19.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T810 ONLYModel: SM-T810 (wifi) - gts210wifi - 9.7" 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
What doesn't work
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. There has no been no fix for the “Connected to device. Can’t provide internet”. DO NOT ASK when this will be fixed. If/when it is fixed, it will be announced public in this thread.
If this is problem for you, go back to 18.1. In addition, the problem might be a memory leak so the less apps you have installed (like gapps), the better. I rarely see this problem as my setup is very simplistic. I just have Brave browser, Newpipe and Aurora Store.
7. 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
@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_gts210wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
The build manifest and instructions on how to compile from source are at
https://github.com/retiredtab/LineageOS-build-manifests
The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/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 July 1, 2022 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use TWRP 3.6.2_9. Get it from
https://dl.twrp.me/gts210wifi/Q6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. We plan to do so. We will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What works" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum.
Having said that pflyaz has kindly provided instructions in post #7.Q9. Can I report a bug with respect to the ROM?A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# 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/retiredtab/files/SM-T810/19.1/
NOTE: All builds that I upload have been personally tested on my 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 9 , 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-06
2. Whatever LineageOS changed since May5 th patches (about 13,100 files had to be recompiled).
May 6 , 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-05
2. Whatever LineageOS changed since Apr 5th patches (about 6,600 files had to be recompiled).
Apr 13 , 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
2. Whatever LineageOS changed since Mar 5th patches (about 28,000 files had to be recompiled).
March 18 , 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
2. Whatever LineageOS changed since Feb 5th patches (about 24,500 files had to be recompiled).
Feb 12 , 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-02
2. Whatever LineageOS changed since Jan 5th patches (about 12,500 files had to be recompiled).
3. 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 7 , 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-01
2. Whatever LineageOS changed since Dec 5th patches (about 5,900 files had to be recompiled).
Dec 9 , 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
2. Whatever LineageOS changed since Nov 5th patches (about 6,100 files had to be recompiled).
Nov 10 , 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
2. Whatever LineageOS changed since Oct 5th patches (about 10,000 files had to be recompiled).
Oct 9, 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 9, 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.
Bash:
$ sha256sum lineage-19.1-20220809-UNOFFICIAL-gts210wifi*
85462d9683208423aa439877f23398ebb06a9c7d9ad45fdc59b62e790fd22ba1 lineage-19.1-20220809-UNOFFICIAL-gts210wifi.zip
Reserved.
@retiredtab imho you can add back and front camera to the "What works" list.
I recommend to use OpenCamera but built in one works as well.
bmwdroid said:
@retiredtab imho you can add back and front camera to the "What works" list.
Click to expand...
Click to collapse
Camera added. Thanks I forgot to add that to the list earlier.
Tab S2 T810 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.
pflyaz said:
Tab S2 T810 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.
Click to expand...
Click to collapse
No Keyboard at first boot -fix:
This is an excellent ROM !! So thank you for these detailed instructions and links.
I just want to add my experience with a small issue of no keyboard showing up. I fixed this here: https://forum.xda-developers.com/t/...oms-sm-t710-and-sm-t810.4480041/post-87316675
With that fix, this ROM runs without any hitch. I am now fully running this ROM and all apps and settings like I want.
Don't use anything above Basic in NikGapps (see my fix post). Above that one of the Gapp kept crashing and the tablet did not go through set up but stuck on "Tablet starting........"
Once Gboard is working, you can then set up and download any other keyboard you want.
retiredtab said:
LineageOS 19.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T810 ONLYModel: SM-T810 (wifi) - gts210wifi - 9.7" 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
What doesn't work
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, sometimes the keyboard is not shown on the screen or off screen. The workaround is to bring up the built in browser, touch the url panel where the http address is and then press the number key when the keyboard pops up. Leave this browser open like that, then press the home button and try your Bluetooth pairing again.
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
@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.
Click to expand...
Click to collapse
THIS IS A REALLY EXCELLENT ROM!! AND RUNS SMOOTH. SO THANK YOU!
Does this also work on gts210vewifi / SM-T813 if no, why? Will support come?
BATTERY GETTING HOT
I cannot turn Off fast charging. The battery is getting quite hot on charging. The fast charging slide is stuck on the ON position.
chappatti said:
BATTERY GETTING HOT
I cannot turn Off fast charging. The battery is getting quite hot on charging. The fast charging slide is stuck on the ON position.
Click to expand...
Click to collapse
That's been reported already, but "fast charging" doesn't work anyway.
At least not on my device.
5.23V and max. 1.2A (getting down to 0.9A reaching full capacity)
chappatti said:
BATTERY GETTING HOT
I cannot turn Off fast charging. The battery is getting quite hot on charging. The fast charging slide is stuck on the ON position.
Click to expand...
Click to collapse
This "fast charge" commit was introduced April 22, 2021 in 17.1.
https://github.com/universal5433/an...mmit/c70731b9a69523eaa30c1d0c12d26938e4a4c373
I never really ran 17.1 other than to solve the wifi and random reboot problems so I never tested it to see if it worked or not.
However, I don't think it ever worked in 18.1 when I looked at it and definitely not in 19.1. I'll put a note in post #1 to say it doesn't work. When I have time, I'll do some more research and see what it's supposed to do. If it is not meant for our device, I'll remove it from the code in a future update.
Let's also remember that the S2 was released in 2015 and I believe it came with a 2A 10W charger. In this post,
https://forum.xda-developers.com/t/...t810-aug-10-2022.4430349/page-3#post-87309527
I wrote that it took about 3 hours to charge to full from 12% battery remaining.
With a 5870mAh battery in the T810 and assuming perfect charging conditions with no loss due to heat, cable resistance, etc, then (3 hours x 2000mA = 6000mAh) is enough to charge a 5870mAh battery to 100%.
Today's definition of "fast charge" with flagship devices and > 10W chargers is probably getting 60% charge in 15 minutes.
I don't purposely feel the tablet's battery for heat, but I do notice that the ac/usb adapter does get quite warm when it's charging. However, my Apple Ipad ac/usb adpater also gets probably a little bit warmer than the Samsung ac/usb adapter. So if it happens on the stock Apple Ipad, then it likely normal for the Samsung as well.
It's not hot enough to burn your fingers when charging, but I do notice it especially when the ambient temperature is warmer too like during hot summer days. On those days, I try to charge the devices during night time when it's cooler and I never leave them charging if I have to leave the house.
One other thought is that our devices are 7 years old with a 7 year old battery. Depending on how much you have used the device, the battery could be getting to near end of life and that might explain why your battery is getting hot when charging.
I suggest you download devcheck by flar2. It's an excellent ad-free program that helps with developing and testing.
https://play.google.com/store/search?q=devcheck&c=apps&hl=en&gl=US
It has a battery tab which shows the current temperature of the battery, charging or discharging, health, voltage, etc. Maybe you can use it to monitor the battery temperature and report back what it is? If you have an external usb power/amp monitor, that would also help show you how much the device is drawing. Something like this
https://www.electroschematics.com/wp-content/uploads/2019/01/1-USB-Power-Monitor-550x550.jpg
With all the crap features that newer Android versions keep coming out with, it would help everyone if there was a built in battery lifecycle reader that showed how many cycles your battery has gone through and when your battery needs replacing (assuming manufacturers don't glue the crap out their devices).
retiredtab said:
This "fast charge" commit was introduced April 22, 2021 in 17.1.
https://github.com/universal5433/an...mmit/c70731b9a69523eaa30c1d0c12d26938e4a4c373
I never really ran 17.1 other than to solve the wifi and random reboot problems so I never tested it to see if it worked or not.
However, I don't think it ever worked in 18.1 when I looked at it and definitely not in 19.1. I'll put a note in post #1 to say it doesn't work. When I have time, I'll do some more research and see what it's supposed to do. If it is not meant for our device, I'll remove it from the code in a future update.
Let's also remember that the S2 was released in 2015 and I believe it came with a 2A 10W charger. In this post,
https://forum.xda-developers.com/t/...t810-aug-10-2022.4430349/page-3#post-87309527
I wrote that it took about 3 hours to charge to full from 12% battery remaining.
With a 5870mAh battery in the T810 and assuming perfect charging conditions with no loss due to heat, cable resistance, etc, then (3 hours x 2000mA = 6000mAh) is enough to charge a 5870mAh battery to 100%.
Today's definition of "fast charge" with flagship devices and > 10W chargers is probably getting 60% charge in 15 minutes.
I don't purposely feel the tablet's battery for heat, but I do notice that the ac/usb adapter does get quite warm when it's charging. However, my Apple Ipad ac/usb adpater also gets probably a little bit warmer than the Samsung ac/usb adapter. So if it happens on the stock Apple Ipad, then it likely normal for the Samsung as well.
It's not hot enough to burn your fingers when charging, but I do notice it especially when the ambient temperature is warmer too like during hot summer days. On those days, I try to charge the devices during night time when it's cooler and I never leave them charging if I have to leave the house.
One other thought is that our devices are 7 years old with a 7 year old battery. Depending on how much you have used the device, the battery could be getting to near end of life and that might explain why your battery is getting hot when charging.
I suggest you download devcheck by flar2. It's an excellent ad-free program that helps with developing and testing.
https://play.google.com/store/search?q=devcheck&c=apps&hl=en&gl=US
It has a battery tab which shows the current temperature of the battery, charging or discharging, health, voltage, etc. Maybe you can use it to monitor the battery temperature and report back what it is? If you have an external usb power/amp monitor, that would also help show you how much the device is drawing. Something like this
https://www.electroschematics.com/wp-content/uploads/2019/01/1-USB-Power-Monitor-550x550.jpg
With all the crap features that newer Android versions keep coming out with, it would help everyone if there was a built in battery lifecycle reader that showed how many cycles your battery has gone through and when your battery needs replacing (assuming manufacturers don't glue the crap out their devices).
Click to expand...
Click to collapse
Thanks!
I realized it was getting hot because I was browsing while it was charging. If I stopped and just did reading, it cooled off. The right side of the screen was getting hot enough otherwise, and I think there is where battery is?
Overnight on silent charge it charged and is fine. I'll leave it at that.
I confirmed with ananjaser1211 that "fast charging" is not supported by the S2 devices. Our S2 devices charge at the normal rate 2A (or less) over 5V. So this code and it's menu option will be removed in the next build.
I will give more details when I write the release notes and it will also be documented in the github commit.
New build called lineage-19.1-20220911-UNOFFICIAL-gts210wifi.zip
NOTE: All builds that I upload have been personally tested on my 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.
19.1 has been my daily driver since July 2022.
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
retiredtab said:
New build called lineage-19.1-20220911-UNOFFICIAL-gts210wifi.zip.......
Click to expand...
Click to collapse
Just flashed it dirty (not wiping anything) which worked.
Will report if I find anything.
Thx again
Fantastic and totally not count on: a smooth android 12 rom on my tab s2!! All smooth so far. Wifi download is just fine (and stable ). And keyboard present.
Coming from Ripees L18. Already had the right TWRP. Wiped all (except ext. storage) installed rom and NikGapps-core-arm64. After boot also magisk 25.2.
Thanks a lot!
Like everyone else has said this is a nice ROM running so smooth.
Only 1 problem that I need to stop the backup option I need to disabled I don't really use it. I try to change it but it won't let me it keeps reverting back to Seedvault and I don't use it.
lojelo said:
Like everyone else has said this is a nice ROM running so smooth.
Only 1 problem that I need to stop the backup option I need to disabled I don't really use it. I try to change it but it won't let me it keeps reverting back to Seedvault and I don't use it.
Click to expand...
Click to collapse
I fixed this by explicitly changing my backup provider to my Google account during the initial setup. I believe this is a LineageOS "feature", but I can't for the life of me understand why any backup provider needs me to enter and remember twenty words just to do a backup - it's crazy! This is a case of Lineage folks way over-engineering something that should be simple. I suggest trying to change your backup provider in settings as a first step. But I have a vague memory from an early testing cycle that I somehow got Seedvault running and I couldn't stop it. The only fix was to completely rebuild the ROM from scratch and then do the Google backup setup early before Seedvault jumped in. Good luck!
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.