Related
Thread created by hbenz2008 but now maintained by me CWGSM3VO:
Requirements:
- Unlocked JBBL/KKBL bootloader. Builds are bootloader specific.
- Updated KKBL recovery, can find one here: https://twitter.com/dhacker29/status/583847256589213696
- Updated JBBL recovery, can find one here: http://downloads.blissroms.com/Recovery/Recovery/moto_msm8960_jbbl/
Builds can be downloaded from:
- CMxlog: http://www.cmxlog.com/12.1 and choose your device.
- CyanogenMod: http://download.cyanogenmod.org/ and choose your device.
GApps:
- DHacker gapps:
4-25-2015: https://www.androidfilehost.com/?fid=96042739161893996
6-07-2015: https://www.androidfilehost.com/?fid=24052804347756927
- Delta gapps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
What works:
- Phone
- WiFi
- GPS
- SMS/MMS
- Mobile Data
- Camera/Camcorder
- HDMI
- Bluetooth
- Call Recording
- Tethering (WiFi: Yes / USB: Yes / BT: Yes)
- USB storage
- F2FS for /data, /data/media and /cache (recovery/kernel dependant)
Known issues:
- The "calc bug". This affects some users. This is due to the GPU crashing. A fix may be hard to nail down. Workaround is to disable H/W layers + force GPU rendering via devopts.
- HDMI. Depends on TV. Works 100% on some, not others (in my testing) -- statusbar/navbar is visible and small scaling issue (statusbar cut off somewhat). Reported not working on AHD.
- Bluetooth; some reported issues with different car makes/models. For me personally, it's worked with a variety of headsets and devices (decks, etc). Tethering appears to work for me, some reports of issues. Issues reported with wearables being paired and WiFi not working or requiring BT to be activated after WiFi connected.
- MMS; most issues can be tracked to incorrect APN settings, please verify with your provider (or try searching this or CM11 threads)
- WiFi; some users have reported issues connecting to certain brands of APs and/or band-mode; most reports isolated to security protocol being used (WPA vs WPA2)
- Clock resets to 1970. Thanks to @MaicolS for using this solution successfully: http://forums.androidcentral.com/an...-update-can-t-connect-google.html#post4323256
- Snapchat crashes sending video. @VlitalityX found this solution: Developer Options->Drawing->Turn on "Force RTL layout direction" then turn it off.
- Alarms not firing or repeating. Disable Automatic Network Date & Time in Settings->Date & Time. Appears to be an issue with RTC writes and/or QCom time_daemon.
- Some reports of GPS not working, try this fix: http://forum.xda-developers.com/showpost.php?p=56659808&postcount=5264
Reporting issues:
- Please ensure your signature includes device, rom, etc to help if posting in the thread.
- Provide a logcat capture if possible, otherwise enable aplogd.
- Enable aplogd, see here: http://forum.xda-developers.com/showpost.php?p=59620294&postcount=2327 and provide logs. You can safely leave this enabled.
- Open a JIRA bug report, see here: https://jira.cyanogenmod.org and provide logs.
Notes:
- There are unofficial builds provided in this thread and should not be used when filing reports with JIRA.
- When coming from another ROM (non-CM) a clean-wipe is recommended (backup your data + internal sdcard data)
- Some users have had issues clean installing CM12.1 - one workaround known is to install CM11 first then upgrade to CM12.1
- The Xposed framework is not supported. Please uninstall/remove it and any modules before reporting issues.
Tips:
- I use TWRP
- I use DHacker's GApps package and let Google via my account update everything as need be.
- For me, a "clean wipe" is formatting the following: /system, /cache, /data and /data/media. Backup anything of value from /data and /data/media before doing this. Flash ROM, flash GApps, reboot. Authorize your PC USB connection on the phone after enabling Developer Options and test adb from the Android SDK.
- When performing a "dirty flash" (upgrade) I manually wipe /cache and dalvik-cache before rebooting to UI.
- For KKBL to JBBL issues with downgrading, see this: http://forum.xda-developers.com/showpost.php?p=63091712&postcount=4465 and this: http://forum.xda-developers.com/showpost.php?p=56963255&postcount=702
- Drained to 1% battery and boot-looping? Try this: http://forum.xda-developers.com/showpost.php?p=61728073&postcount=3754
- If your CM build is 1+ month older than what you plan to flash/upgrade, it is recommended you do a clean flash.
So far, I had some issues with network, apparently it's losing WiFi connection randomly . The Play Store takes a long time to download or update apps or get "Retry" messages.
None of those issues here,however i had some unfortunately dialer stopped,it corrected itself after couple reboots.
Downloaded es file explorer as fx explorer couldn't get into System files.
GPS still hosed in my case
I forgot to mention: during the flashing, a mount error appear, but the ROM booted, normally. Happened to you to?
No but flashing was really quick I was surprised.under a min maybe then it took bout 5 min to reboot.but no errors
Hummmm, strange... What recovery are you using? I flashed dHacker's one, before flashing the ROM.
And something happened just now: I rebooted the phone and the DPI as changed! All the things are smaller now. Weird...
Most likely need to reflash.using twrp 7.1 and flashed dhacker gapps.
note: cant write to System file yet
I know this is for KKBL, but can this be built for JBBL? How is the overall feel of the build anyways?
Sent from my ATRIX HD using XDA Free mobile app
douglasvbarone said:
I forgot to mention: during the flashing, a mount error appear, but the ROM booted, normally. Happened to you to?
Click to expand...
Click to collapse
FYI he said SD card doesnt work yet
doesnt work in what capacity?
lngwca said:
FYI he said SD card doesnt work yet
Click to expand...
Click to collapse
Well, that kills it for me then. Will have to wait. I have all my music and photos on my SD card.
doing a nandroid backup now, but photos in SD can be seen .Once done, i will test music...
Anyone can post a gps.conf from a working gps whether it be jelly bean or kitkat.
... will be appreciated. Under System/etc
very smal file 2kb or so
both music and photos in SD can be manipulated just fine
iBolski said:
Well, that kills it for me then. Will have to wait. I have all my music and photos on my SD card.
Click to expand...
Click to collapse
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
hbenz2008 said:
both music and photos in SD can be manipulated just fine
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
Click to expand...
Click to collapse
Ahh, gotcha. I thought there was NO access to the SD card. So, it's just write access. I know under Lollipop, they were supposed to make it work better than they did under KK. Supposedly, it's a setting where you can say give it all access or only to it's own directories. Supposedly though, many apps might have to be rewritten to get this, so if the app hasn't been updated to ask for the new permission, then it won't work.
lngwca said:
FYI he said SD card doesnt work yet
Click to expand...
Click to collapse
The tweet:
Everything except SD YouTube video seems to work on RAZR HD
Click to expand...
Click to collapse
Has nothing to do with SD card, it means SD YouTube videos (SD - Standard Definition, as opposed to HD - High Definition).
his tweet said "Everything except SD YouTube video seems to work on RAZR HD "
so sd as in resolution. i asked him if he could try viralpopup or tubemate. might try this on the weekend to see how this feels.
oh and can someone upload a mirror pls? page won't load 2 download.
ps it's a cm12 port not AOSP too from his threads on twitter
absolutely true, the challenge for now is to gain access to editing system file.
kabaldan said:
The tweet:
Has nothing to do with SD card, it means SD YouTube videos (SD - Standard Definition, as opposed to HD - High Definition).
Click to expand...
Click to collapse
hbenz2008 said:
both music and photos in SD can be manipulated just fine
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
Click to expand...
Click to collapse
try root explorer to edit system files
http://www.reddit.com/r/Android/comments/2m7fqo/i_wanted_to_keep_a_chart_going_of_apps_we_know/
check play store if you bought/have titanium backup
they pushed an update for support. now if only they updated their UI....
confirmed, works-root explorer-
my bad... just thought that he missed a comma. lol also every ones sd wasnt mounting
LineageOS 13.0 (Marshmallow) {un,}official builds for the Droid 4
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Use these builds on your own risk!
Builds:
Current official builds:
https://download.lineageos.org/maserati (Droid 4)
(When migrating from CM (official and unofficial) or Lineage unofficial, flash this first (manually mount /data in TWRP before flashing and unmount it afterwards) and then directly flash the new image without rebooting)
Su addon for official builds: http://droid.cs.fau.de/lineage-13.0/addonsu/ (The official addon doesn't currently install on Omap4)
Current unofficial manual builds:
https://droid.cs.fau.de/lineage-13.0/
Old official CM nightly builds and snapshots:
https://droid.cs.fau.de/Official_CM_Builds/maserati/ (Droid 4)
Old manual builds:
https://droid.cs.fau.de/cm-13.0/test/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2017-03-25:
Sync with LineageOS (March security level)
2017-03-02:
Sync with LineageOS
2017-02-19:
Fix 10 kernel security bugs
Add SGX Omap4-changes
Sync with LineageOS
2017-02-10:
Sync with LineageOS (January security patchlevel)
2017-02-01:
Sync with LineageOS
2017-01-11:
Sync with LineageOS
Rebrand to lineage
2016-01-21:
Official CM13 nightlies: http://review.cyanogenmod.org/#/c/129192/
2016-01-16:
Added SELinux rules to allow fsck on stock-partitions and fixboot to unmount safestrap-partition
Graphics glitches fixed
zRAM uses 2 compression streams now
2016-01-14:
Implemented LiveDisplay/Color Calibration
2016-01-13:
More fixes for switching CDMA devices to GSM
T-Mobile CZ APN corrected
2016-01-11:
Preferred network type is now set earlier
Audio-routing through dock-audio (desk/car) added
Mouse-pointer (USB/Lapdock) fixed
2016-01-08:
Camera no longer crops pictures in portrait mode
USB storage integration added
Initial root-mode setting fixed
Migrated from busybox to toybox, busybox is gone
Fixed duration of boostpulse in power HAL
2016-01-06:
VZW data fixed
Reboot to recovery fixed
Wifi configuration updated
Widevine blobs updated (from sprout)
2016-01-04:
Adoptable storage fixed
Many kernel patches to filesystem-, block- and mmc-layers
2015-12-25:
Fixed internal storage for real. You need to manually remove /data/system/storage.xml and reboot when upgrading from previous builds. After that the internal storage will be the primary sd.
2015-12-24:
Fixed crashes of com.android.phone on GSM/UMTS (XT894/XT912)
Configure internal storage like expected in M (can't be adopted, would kill safestrap)
Fixed GPS initialization failing most of the time
Run wifi calibration at an earlier stage
Workaround for VZW data: toggle airplane mode after boot once
Something which needed ffmpeg and imagemagick
2015-12-18:
Switching of preferred network fixed
SELinux rules updated
SELinux is now enforcing
2015-12-14:
Audio-routing fixed
2015-12-11:
Capacitive buttons on {umts_,}spyder are no longer recognized as an external stylus, but as buttons
SELinux policies updated
Update widevine from mako
Added (very slow) emulation of idiv-operations not supported by Omap4 but required by newer blobs (gapps swype, widevine)
2015-12-07:
First build for most devices
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data
WiFi
GPS
Camera
HDMI
Playback of DRM-protected content (using Widevine from sprout)
Reboot to recovery
What's not working:
Probably most everything else, including, but not limited to:
Data encryption (due to safestrap)
Gapps:
OpenGApps
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
Installation:
You need a recovery supporting SELinux
A version of Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
These versions (both unofficial and official) automatically switch to GSM/UMTS without installing additional patches.
Source / Repositories:
maserati device-support: https://github.com/LineageOS/android_device_motorola_maserati/tree/cm-13.0
omap4-common device-support: https://github.com/LineageOS/android_device_motorola_omap4-common/tree/cm-13.0
omap4-common kernel: https://github.com/LineageOS/android_kernel_motorola_omap4-common/tree/cm-13.0
local manifest to build cm-13 for the Motorola Omap4 devices: http://droid.cs.fau.de/lineage-13.0/local_manifest.xml
XDA:DevDB Information
LineageOS 13.0 on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Beta Release Date: 2017-03-25
Created 2015-12-14
Last Updated 2017-04-05
Good job
Thanks again!
Excited.
Installed 151214 this morning over the top of 151210.
The "low in call volume " issue appears to be fixed, as per the notes above; I've had a few phone calls this morning with only one issue:
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?
hahahaha thanks stargooo one step more for our droid 4!
Hi,
Shobai said:
Installed 151214 this morning over the top of 151210.
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?
Click to expand...
Click to collapse
All low-level audio-routing problems should be fixed, this sounds like a problem with the IncallUI (it probably did not specify that the audio should be routed over the headphone out). Haven't looked there yet...
Cheers,
Michael
Thanks Michael, much obliged!
Apologies for the double post! @stargo, I think this may have been mentioned in the CM12 thread - I've got "Playback control" turned on under Buttons, but a long press of the volume keys doesn't have any effect on playback. The volume keys work properly for volume, though.
Thanks again!
Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?
LuH said:
Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?
Click to expand...
Click to collapse
Flash the build from the 14th.
Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?
Septfox said:
Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?
Click to expand...
Click to collapse
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!
So has the build from the 14th fixed the DATA issue?
By no LTE/CDMA support right now, does that mean I wouldn't be able to receive emails and online push notifications unless I am on WiFi or they are Text/SMS based?
hi, can i have noob question? is there some tutorial how to make own build (i have tried to google what to do in which order but i didnt have much luck - create folders, get local manifest, init repo but when and how get omap4 common files required for build...)?
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
So by finding this out, it would seem that the Data connection for any provider is not functioning due to a permissions issue in which the OS cannot write the given APNs from the "search" function to the file which stores the data... is that correct?
Hi,
Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
Click to expand...
Click to collapse
Great
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
Does it work after a reboot, too?
Or do you then need to toggle airplane mode again? It might be that toggling airplane mode is what actually causes the connection to be established. Judging from the radio logs I have seen, the RIL responds with an error after bootup and toggling airplane mode might fix it.
Btw, for the people on UMTS: I'm testing a fix for the crash of com.android.phone after boot.
EDIT: Confirmed by @joojoobee666: toggling airplane is enough to get data working
Cheers,
Michael
Bobcus Leper said:
Flash the build from the 14th.
Click to expand...
Click to collapse
Yup, switching Vibrate on touch off in sounds settings helps from this build on. Thanks, I have decided to make this my primary system, so far great impression
Bobcus Leper said:
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!
Click to expand...
Click to collapse
I second that; especially Trebuchet, Settings, dialer, contacts and messaging are way more responsive. I clean installed system (1218 build; wipe /system, install just this and Open GApps Pico) with keeping data from 12.1, it went pretty smooth.
Also it's been laying in standby for about 12 hours now, Wi-Fi on, and it's still charged ~96%. Either it's a battery level reading bug and will soon drop fast, or huge improvement over L - usually I'd lose 10% - 20% at least.
GREAT JOB I was looking forward to CM 13 since June. However, right after flashing GAPPS the processes crash and can't make any progreses. Doesn't matter if I use Slot 1 or 2, already tried mount no-mount /system and /data.
Hi,
this thread aims at keeping the LineageOS 13.0 version alive for the Moto G 2015 (osprey) device with current security patches from LineageOS (branch 'cm-13.0'). The build here has already a history in this thread on XDA - it may be worth to scroll through it to find additional information.
The build has got the following features:
LineageOS 13 with current security patches
Patched for microG (see https://microg.org, signature spoofing as switchable permission)
Squid kernel for the Osprey device (own fork)
LineageOS Jelly Browser
Current Android System Webview
CMUpdater is not part of this build
Renewed CA-certificates from AOSP master branch
VoLTE (may not work in all cases!)
Current build data
Download here
AOSP tag android-6.0.1_r81
Security string 2018-06-01
Android System Webview on M66 (stable, taken from LineageOS 14.1)
Contains the fix for the KRACK attack against WPA2
Root access included (can be switched on/off in developer settings)
Unofficial microG-build as 2nd build variant
Download here
Hardened build with pre-installed microG apps. For more information, see https://lineage.microg.org/
(This is an unofficial build for LineageOS 13 f. osprey based on the work described on the project page)
Different from the 1st build, the following features apply, everything else is the same:
No root available (can be flashed separately)
Pre-installed microG apps (see lineage.microg.org page)
SQLite 'secure delete' feature enabled
Access to /proc/net blocked for user apps
Enhanced Privacy Guard (1): Switches for motion sensors and other sensors available
Enhanced Privacy Guard (2): Switches for read phone state and storage (read/write) available
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Cloudflare DNS (1.1.1.1) as default fallback
Privacy-preferring default settings
Source Code links
LineageOS: https://github.com/LineageOS
Kernel: https://github.com/MSe1969/android_kernel_motorola_msm8916/tree/mse_cm13
microG patch: https://github.com/microg/android_p...aster/patches/android_frameworks_base-M.patch
microG-Build: https://github.com/lineageos4microg
local manifest: https://github.com/cm13-microG/local_manifests
hardening features: see reserved post further below
Installation instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.
Pre-Requisites
Get familiar with the hardware keys of the Motorola Moto G 2015 (osprey) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume key to the reboot recovery option and select with power key)
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
Download the most current .ZIP file of this ROM and place it to your phone's internal memory or SD card
If you wish to install Google apps (GApps), please refer to the GApps section further below
An unlocked bootloader (read the warnings carefully and backup your data!
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it.
However - I recommend to use the TWRP recovery linked here. The following instructions are based on TWRP.
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (see above) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and spefify "Dalvik", "System", "Cache" and "Data" to be wiped.
Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
GApps
The following instructions only apply for the 1st variant, do not flash Gapps over the "microG build":
You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device.
Choose ARM as platform, Android 6.0 and the flavor of your choice. I recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications you have no use for. The 'microG patch' in this ROM has no negative impact on installing Gapps.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd).
Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe.
If you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process.
(Note: If you wish to get rid of GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps. When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 13.0 - be patient, the first boot after flashing a new ROM takes quite long!
microG Installation
These instructions apply to the 1st 'default' variant, not the 'microG build' (which has already microG installed)
The ROM is patched for the use of microG, but it does not contain the microG system components.
The best way to obtain them is to include the microG repository into the F-Droid store as described on the microG Download page, where you will also find links for the direct download of the .apk files.
Please refer to the official installation instructions. However, there are three pieces of information, which are explained on the microG pages, but unfortunately not directly in the installation instructions, so I would like to point them out here:
Download the 'unstable' Gms Core version 0.2.4-105-... to avoid "outdated play services" warnings
The Location Provider functionality is included in Gms Core, but also available as separate application. I recommend Gms Core - however, the explanation is not included in Gms Core, but only here
To grant the signature spoofing permission, go to Settings - Apps - Advanced (the 'gear' icon) - App Permissions - Spoof package signature; it is not possible when you enter the individual app's permissions menu
Credits
Android Open Source project (AOSP)
LineageOS project
squid2 (Kernel)
microG project
XDA:DevDB Information
Osprey LineageOS 13 with microG patch, ROM for the Moto G 2015
Contributors
MSe1969
Source Code: https://github.com/cm13-microG/local_manifests
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2017-10-23
Last Updated 2018-07-24
Change Log
June 20th, 2018
Announcement to discontinue the cm-13.0 builds - please visit my Lineage OS 14.1 microG thread, which continues with LineageOS 14.1
June 10th, 2018
Security string 2018-06-01
May 22nd, 2018
Security string 2018-05-01
Android System Webview M66
Cloudflare DNS as default (instead of Google)
Privacy-preferred default settings
Kernel fix for in-call sound issue
April 11th/12th, 2018
Security string 2018-04-01
Android System Webview M65
March 16th/17th, 2018
Security string 2018-03-01
Squid Kernel r22c (Oreo)
Renewed CA certificates from AOSP master branch
Bugfix of date/time reset on reboot, when no carrier sync
Bugfix in microG build: Always skip GMS page in SetupWizard
February 19th, 2018
Update after ASB merge in LineageOS 13.0
Webview now on stable M64
February 10th, 2018
Security string 2018-02-01
Squid Kernel r22c (Oreo)
Privacy Guard enhancements
Further security hardening in 2nd "microG build" variant
January 16th, 2018
Security string 2018-01-01
Squid Kernel r22 (Oreo)
System Webview switched back to M63-stable
2nd build variant "unofficial microG build"
December 21st, 2017
Security string 2017-12-01
Squid Kernel r21 (Oreo) forked
Recent Jelly build
Android System Webview 64.0.3282.30 (beta)
November 24th, 2017
Security string 2017-11-01
Squid Kernel (Nougat) forked and merged 3.10.108 updates from kernel.org
October 23rd, 2017
Fix of KRACK attacks
Security string 2017-10-01
AOSP tag 6.0.1_r81
Android System Webview updated to M64
Squid Kernel (Nougat)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Historical entries from this thread:
September 21st, 2017
Security string 2017-09-01
AOSP tag 6.0.1_r80
Jelly updates
Fix of 'Blueborne' attack (part of Sept. security patches)
September 2nd, 2017
Security string 2017-08-01
Android System Webview updated to M60
July 14th, 2017
Security string 2017-07-01
June 14th, 2017
Security string 2017-06-01
Android System Webview updated to M59
May 28th, 2017
Replaced Gello with new LineageOS Jelly Browser
Android System Webview updated to M58
May 26th, 2017
Security string 2017-05-01
April 17th, 2017
Security string 2017-04-01
AOSP tag 6.0.1_r79
March 24th, 2017
Security string 2017-03-01
Included Kernel from cm-14.1 branch to regularly receive sec. patches
March 13th, 2017
Security string 2017-02-01
February 21st, 2017
Security string 2017-01-01
Rebranded LineageOS
Security Hardening (microG build)
Details about additional security hardening in the "microG build"
1. SQLite 'Secure Delete' feature
This sanitizes deleted data by overwriting it with zeroes, rather than having it persist within SQLite's free list.
Backport from Oreo, see https://android-review.googlesource.com/q/topic:"secure_delete"
2. Restrict SET_TIME_ZONE permission to system apps
Backport from Oreo, see here
3. Enhanced Privacy Guard (1) - Sensor permission switches
An own sensor template to control access to motion sensors (ask mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard. Commits: (1), (2), (3)
4. Enhanced Privacy Guard (2) - Switches for 'Read phone state' and 'Storage'
The existing AppOps to read the phone's IMEI and to control access to the SD card have been made accessible.
This is a cherry-pick of the proposed LineageOS change here
5. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. This is the main commit. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitorhas been bundled
6. Access to timing information in /proc restricted
To prevent side-channel attacks as described here, the respective Oreo patch has been back-ported.
7. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
8. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 14.1 (all setting can be changed at any time later):
Privacy Guard is enabled on install (proposal during Setup)
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sweet..
Nice. Good to see this as separate post.
Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?
shadowbone said:
Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?
Click to expand...
Click to collapse
I haven't observed this behavior on my device, can you provide some more details?
MSe1969 said:
I haven't observed this behavior on my device, can you provide some more details?
Click to expand...
Click to collapse
It isn't that big a difference but perhaps I could provide you a log, if that could help.
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Thanks - will have a look later
MSe1969 said:
Thanks - will have a look later
Click to expand...
Click to collapse
Sure thing.
Also, is this volte supported or should I flash the volte patch ? Because I can't seem to get it work. I am on the latest build.
VoLTE
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.
MSe1969 said:
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome
Click to expand...
Click to collapse
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added
Erick_Summer said:
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.
Click to expand...
Click to collapse
Well, if you meant taking a log, there are plenty. The one I used is 'matlog'. You can get it from playstore.
rahul9999 said:
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added
Click to expand...
Click to collapse
I used this post and its patches always as a base for my test builds. Tried now the most current MM patch , which was uploaded in October - same result, does not work on my device.
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.
MSe1969 said:
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.
Click to expand...
Click to collapse
Yeah, I use the betterbatterystats from xda. I guess I will try and do a dalvik cache clear and if possible do a clean rom flash in the near future and try again. Else, it must be some device specific issue.
Anyway thanks a lot for your time. I appreciate it.
My daily ROM, please update.
The best ROM tk!
kurapika7 said:
My daily ROM, please update.
The best ROM tk!
Click to expand...
Click to collapse
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.
melp57 said:
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.
Click to expand...
Click to collapse
have a better use of ram
LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLYModel: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. DRM level 3 (SD definition)
10. deep sleep
What doesn't work
1. fingerprint. As I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
I will not spend anymore time looking at fingerprint. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working.
4. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
3. All past contributors of the exynos5433 code.
4. @rINanDO for his lmkd spam fix in 18.1.
5. beta testers: lpedia, Yogi555 and CuckooPenguin
6. lpedia for building the public T710 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.
Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux
Device Tree
https://github.com/retiredtab/android_device_samsung_gts2-common-selinux
https://github.com/retiredtab/android_device_samsung_gts28wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid August 2021 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use my unofficial TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/Q6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. We plan to do so. lpedia will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What's working" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that, @pflyaz has kindly make a guide in post #37.Q9. Can I report a bug with respect to the ROM?A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.
The ONLY exception is that if you are coming from LOS 18.1 with the April 5 2022 security patch or later, you can dirty flash the latest security patch build.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per post #11. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 18.1 code modifications in the future?A19. I don't anticipate any major modifications. There may be some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the rom up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a LTE or S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T715, T810 and T815.Q22. Can I load this ROM on a variant device like LTE or S-pen version?A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device.
ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen.Q23. Does this ROM have any wifi connection issues?A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q24. Is this ROM secure so I can do financial transactions?A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q25. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA rom?A25. Downloads are at
https://sourceforge.net/projects/lpedia-sf/files/gts28wifi/
Monthly release notes
June 10, 2023 release notes
1. Incorporates June 5 as per https://review.lineageos.org/q/topic:R_asb_2023-06
May 8, 2023 release notes
1. Incorporates May 5 as per https://review.lineageos.org/q/topic:R_asb_2023-05
Apr 18, 2023 release notes
1. Incorporates Apr 5 as per https://review.lineageos.org/q/topic:R_asb_2023-04
March 19, 2023 release notes
1. Incorporates Feb 5 and Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02 and https://review.lineageos.org/q/topic:R_asb_2023-03
Jan 8, 2023 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
Dec 12 release notes
1. Incorporates Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
Nov 12 release notes
1. Incorporates Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
Oct 9 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
Sept 11 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Fixes non working touchscreen and hardware buttons when powering up with power cable plugged in and device turned off. However, the recommendation is still to unplug your charger, wait 30 seconds before pressing power button when your device is turned off.
https://github.com/retiredtab/andro...mmit/7e0657629efedc7f06f6f6fb57199fca0b4e8ea6
https://github.com/retiredtab/andro...mmit/e17c44d2e282d67b243a1c99ce62127e83052c4f
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/6db8e690141a98e5cf9e6952c3572c127c0cf8ea
Aug 10 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Fixes saving of color profile in live display during a reboot/shutdown.
https://github.com/retiredtab/andro...mmit/01b1ed6ba8c268a19762031415fde1b4e45d4ac3
3. Fixes offline battery charging by writing rules to allow charger to access certain files. This removes the previous workaround. Thanks to @simon-edwards for providing an adb logcat that showed the denials.
https://github.com/retiredtab/andro...mmit/041ae45960170e68410b059f4f709e9c14b79a99
July 23, 2022
1. Added argosd to improve wifi throughput as per https://github.com/retiredtab/andro...mmit/c181aa0c5192e46a5a03d4451e2648481a520c0f
2. Incorporates July 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
3. Incorporates a workaround for offline charging.
https://github.com/retiredtab/andro...mmit/9d019f0a3be789850a9add18d042990631f05b44
Previously, if the device was off and you plugged in a charger, it would show a battery icon and this would display indefinitely giving no sign of charging animation. With this workaround, the battery icon is displayed for a few seconds and then a white circle with a charge symbol inside it is shown to indicate it's charging.
After a few seconds, the screen will go blank and continue charging. The side effect of this workaround is that in order to turn on the device, you first must unplug the charger and then turn on your device. If you try to turn on the device with the charger cable plugged in, it won't turn on.
June 12, 2022
1. Removed vibrator code from gts2-common as wifi only models don't have vibrator motor (only LTE models).
https://github.com/retiredtab/andro...mmit/e54aee73a98e3cef6e74f96c1815cec9c82ff10d
https://github.com/retiredtab/andro...mmit/dd846b06378182398c55b57b2edc2537369bd509
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
May 12, 2022
1. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
2. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ.
Reserved.
Initial public build called lineage-18.1-20220411-UNOFFICIAL-gts28wifi.zip. The sha256sum file is provided as well to ensure integrity of download.
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.
Congratulations on the awesome release!
New build called lineage-18.1-20220512-UNOFFICIAL-gts28wifi.zip
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
May 12, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already
2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
4. If you are upgrading from the April 11 build, you may dirty flash the May 10 build. If you are NOT coming from the April 11th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.
Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim
kimrosebush said:
Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim
Click to expand...
Click to collapse
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
lpedia said:
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
Click to expand...
Click to collapse
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim
I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.
This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.
https://forum.xda-developers.com/t/...rsions-devices.3098071/page-367#post-86885091
It's also shown up in other roms like
https://forum.xda-developers.com/t/...7-1-04-30-2022.3937956/page-100#post-86885353
This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.
Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.
kimrosebush said:
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim
Click to expand...
Click to collapse
Good to hear!
Note that you don't have to be quite so brutal about wiping absolutely everything for a 'clean' flash. I manually wipe Dalvik / ART Cache, Cache, and System, and then Format Data. I have never reformatted the SD.
If you have any further trouble, I suggest you try starting again with a clean flash and a different gapps package, or try doing without any gapps, as @retiredtab has recommended in the post above.
In my experience, some gapps packages, or sometimes just a particular version of a gapps package, don't work with some ROMs. I have not tried opengapps, but I can confirm that BiTGApps-arm-11.0.0-R45_signed.zip does work on my T710 with this particular ROM version.
I personally like BiTGapps because it installs only the bare minimum needed (Google services and Play Store; doesn't even automatically run Google Setup) and doesn't have to be installed before first boot. So it's possible to install LOS, boot the system, make sure everything's working, then go back into TWRP and install gapps. If any problems turn up, this approach also makes it easier to tell whether it's something to do with LOS or with gapps.
You could also try running LOS without any gapps, and if you decide you want gapps after all, install BiTGapps without having to clean-flash and start again.
I just installed this rom two days ago. It has been working great. Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message. Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Would you have any idea what is going on or how I should deal with this?
Thanks,
MC
Dr_MC said:
Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message.
Click to expand...
Click to collapse
On April 6, @lpedia and I had a PM discussion about signing builds.
lpedia wrote
Code:
"About signing builds ... an issue with just using the default test-keys signature is that someone can easily create
their own builds and pass them off as someone else's, possibly adding malicious or just plain bad code, and their
package would look just like the original."
I replied
Code:
"For our purposes, maybe we should just include the sha256sum and recommend that the users verify
them to ensure the file downloaded correctly and it wasn't modified?"
To get stop seeing that trust message, goto settings, privacy, trust, turn off build signature.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
I can't see the Crave app in Aurora Store. I use the app devcheck to check for root access and the screenshot clearly shows it's not rooted.
There's nothing in my code to enable root. In fact, I don't even want root on my devices.
For Crave, you can try using Magisk and it's hide root function to see if that will fool Crave into thinking the device is not rooted.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
I did installed the above root checker app and got the same message. That is, the T710 rom, by default is NOT rooted. I don't know why Crave would say it's rooted.
I believe root checker's main function is to verify that your rom is "rooted" so when it says "root access is not properly installed.", it's trying to tell you that your attempt to use Magisk or similar type app to root the rom was unsuccessful.
BTW, you are better off using devcheck as it's an excellent ad-free utility that I use on a regular basis to help develop this rom vs the ad-infested root checker app. While devcheck isn't open source, it's written by flar2 who is a xda member here.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
Root Checker Basic says "Sorry! Root access is not properly installed on this device" when asked to confirm root status on an unrooted device. So as far as that app's concerned, it just means "I can't confirm it's rooted". Which is to be expected if it isn't rooted and you haven't even tried to root it.
If that isn't the app you're using, see if you can find out what it means to your particular root-checker app.
Dr_MC said:
Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
Did the CRAVE app work on this device when it had the stock Samsung ROM? Do you have to register devices to receive this service? If so, might it need to be re-registered? Because its device ID will have changed.
Thanks for suggesting devcheck. It says I'm unrooted. Perhaps Crave noticed the unlocked bootloader or the custom ROM.
It did work with stock. It was registered, twice in fact. I deleted both, registered it again. The ap still says I'm rooted. Oh well, that's ok, I can use crave through a browser.
BTW do you know where I can find the stock keyboard?
Thanks
Dr_MC said:
BTW do you know where I can find the stock keyboard?
Click to expand...
Click to collapse
If you mean the Samsung keyboard - sorry, no, I don't. I switched to a different keyboard years ago. Google's GBoard has similar functionality, I think. MS SwiftKey is OK, too - has the best (most relevant) suggested text of any of the keyboards I've tried.
ROM working fine for me after trial and error with various gapps. FWIW I ran into the "just a sec " with opengapps. I finally had some joy by flashing the rom, but not gapps. Boot the ROM and completely setup it up Lineage. Then I restarted and flashed open gapps. When I rebooted everything came uo fine and has been solid eversince. Kudos your you gentlemen for fixing the Wifi ! Its been nice to have it work stably.
LineageOS 18.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
What doesn't work
1. fingerprint. As I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
I will not spend anymore time looking at fingerprint. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working.
4. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
3. All past contributors of the exynos5433 code.
4. @rINanDO for his lmkd spam fix in 18.1.
5. beta testers: lpedia, Yogi555 and CuckooPenguin
6. Yogi555 for building the public T810 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.
Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux
Device Tree
https://github.com/retiredtab/android_device_samsung_gts2-common-selinux
https://github.com/retiredtab/android_device_samsung_gts210wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid August 2021 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use TWRP 3.5.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. Yogi555 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 make a guide in in post #16.Q9. Can I report a bug with respect to the ROM?A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.
The ONLY exception is that if you are coming from LOS 18.1 with the April 5 2022 security patch or later, you can dirty flash the latest security patch build.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per post #14. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 18.1 code modifications in the future?A19. I don't anticipate any major modifications. There may be some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the rom up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a LTE or S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T715, T810 and T815.Q22. Can I load this ROM on a variant device like LTE or S-pen version?A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device.
ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen.Q23. Does this ROM have any wifi connection issues?A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q24. Is this ROM secure so I can do financial transactions?A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q25. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA rom?A25. Downloads are at
https://sourceforge.net/projects/retiredtab/files/SM-T810/18.1/
Monthly release notes
June 9, 2023 release notes
1. Incorporates June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
May 9 release notes
1. Incorporates May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
Apr 18 release notes
1. Incorporates Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
Mar 19 release notes
1. Incorporates Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
Feb 17 release notes
1. Incorporates Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
Jan 11. 2023 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
Dec 12 release notes
1. Incorporates Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
Nov 21 release notes
1. Incorporates Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
Oct 9 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
Sept 11 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Fixes non working touchscreen and hardware buttons when powering up with power cable plugged in and device turned off. However, the recommendation is still to unplug your charger, wait 30 seconds before pressing power button when your device is turned off.
https://github.com/retiredtab/andro...mmit/7e0657629efedc7f06f6f6fb57199fca0b4e8ea6
https://github.com/retiredtab/andro...mmit/e17c44d2e282d67b243a1c99ce62127e83052c4f
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/6db8e690141a98e5cf9e6952c3572c127c0cf8ea
Aug 10 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Fixes saving of color profile in live display during a reboot/shutdown.
https://github.com/retiredtab/andro...mmit/01b1ed6ba8c268a19762031415fde1b4e45d4ac3
3. Fixes offline battery charging by writing rules to allow charger to access certain files. This removes the previous workaround. Thanks to @simon-edwards for providing an adb logcat that showed the denials.
https://github.com/retiredtab/andro...mmit/041ae45960170e68410b059f4f709e9c14b79a99
July 13, 2022
1. Added argosd to improve wifi throughput as per https://github.com/retiredtab/andro...mmit/c181aa0c5192e46a5a03d4451e2648481a520c0f
2. Incorporates July 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
June 11, 2022
1. Removed vibrator code from gts2-common as wifi only models don't have vibrator motor (only LTE models).
https://github.com/retiredtab/andro...mmit/e54aee73a98e3cef6e74f96c1815cec9c82ff10d
https://github.com/retiredtab/andro...mmit/dd846b06378182398c55b57b2edc2537369bd509
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
May 10, 2022
1. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
2. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
April 10, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T810 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ.
Reserved.
Initial public build called lineage-18.1-20220410-UNOFFICIAL-gts210wifi.zip. The sha256sum file is provided as well to ensure integrity of download.
Yogi555 has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
April 10, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T810 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.
Tried the beta build and everything seems to be working. I'll observe once it goes into deep sleep and see if WiFi will lose connection (usually 24 hours) on the other 18.1 build. Loaded all my paid apps without issues. Only gripe is the Netflix with DRM L3. Will look into another thread where they spoofed it.
I'll give it a try. Other LOS 18.1 roms wifi not working.
@retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin thx very much for your work.
Until yesterday mine was on ripees build from 20211103 which was stable and working but didn't seem to get any further updates than 20211208.
Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.
Flashed it with Magisk 23. (wanted to make sure that Gapps didn't interfere)
1st boot was fast, setting it all up.
Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).
Wifi connection there as soon as it wakes up.
So I gave BitGapps a go and flashed ARM64 which worked (isn't specified in "Q12" and as far as I remember only ARM worked on ripees build).
Fiddling around a bit installing paid apps and others.
Everything seems to be fine especially for a beta version.
For others who want to change from ripees version to this one:
On mine it worked to restore "Data" via TWRP (partition got wiped again before) what makes it much easier to switch.
Each app I use seems to be working under the new ROM without problems.
Fun fact: button backlight after restoring is as short as it was set in the prior ROM.
bmwdroid said:
Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.
Click to expand...
Click to collapse
The reason I write MUST is that not all TWRP from the official TWRP site work properly. For example, when I was initially building the 18.1 tree back in July/Aug 2021, I needed mtp and adbd to work in TWRP T710 for debugging purposes.
Despite the change log claiming both were fixed, not a single version worked wrt mtp and adbd. I knew this way back in Dec 2020 and you may have even seen my post #124 since you were post #122 and #126 in the same thread.
So in order to get 18.1 up and running, I fixed TWRP T710 myself as I explain at
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2_9-for-samsung-sm-t710.4430335/
So for T710 users, I know my TWRP build is rock solid as I have easily used it more than 150 times when making the 18.1 rom.
Another example. During the summer of 2020, I upgraded the OS on a Samsung S4 phone for my friend. I went to official TWRP website, downloaded the latest and much to my surprise, the touchscreen didn't work at all. I used an older TWRP version and it worked fine.
Bottom line: even though it's on the official TWRP website does not mean it's tested or working properly. In the case of the S4 TWRP with the non working touchscreen, it's obvious there was zero testing done.
That's why we will test ALL our 18.1 builds for the "what works" functionality in post #1 before uploading to the general public.
bmwdroid said:
Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).
Click to expand...
Click to collapse
By sheer coincidence, I already had the above in my private build on March 27 as I wanted to test it to make sure it works before adding it into github. Yes, I test even 1 line of code change myself no matter how trivial.
The 1 line of code needed is documented at
https://review.lineageos.org/c/LineageOS/android_device_samsung_s3ve3g-common/+/292889
I will put this change into my github so that it gets built with the May 5 security patches.
bmwdroid said:
Wifi connection there as soon as it wakes up.
Click to expand...
Click to collapse
My github repo has always had the S2 wifi blobs after @lpedia and I fixed it on Aug 7, 2021 as per
https://github.com/retiredtab/propr...mmit/3984c2ef6852794a939b8eda689fc477705d5c86
As you can see in my github history, that reversion back to S2 wifi has never changed since Aug 7, 2021.
bmwdroid said:
Fun fact: button backlight after restoring is as short as it was set in the prior ROM.
Click to expand...
Click to collapse
Without looking through the 1000's lines of code or more, the above functionality exists probably in the hardware/samsung repo
https://github.com/LineageOS/android_hardware_samsung/tree/lineage-18.1/hidl/light
and the settings are probably saved in some directory, but the display menu for the button backlights isn't shown until I put in that one commit above. That is, the OS knows to use the saved settings, but without the menu overlay, it doesn't show the menu itself.
retiredtab said:
The reason I write MUST is that not all TWRP from the official TWRP site work properly. For example, when I was initially building the 18.1 tree back in July/Aug 2021, I needed mtp and adbd to work in TWRP T710 for debugging purposes...
Despite the change log claiming both were fixed, not a single version worked wrt mtp and adbd. I knew this way back in Dec 2020 and you may have even seen my post #124 since you were post #122 and #126 in the same thread....
Click to expand...
Click to collapse
Well I gotta admit I didn't check adb and mtp in that TWRP.
I probably saw your post but might not have paid attention as they referred to T710 and as I own T810 I judged them as not relevant for me.
retiredtab said:
...
Bottom line: even though it's on the official TWRP website does not mean it's tested or working properly. ...
Click to expand...
Click to collapse
That's what I've noticed as well for T325.
retiredtab said:
..My github repo has always had the S2 wifi blobs after @lpedia and I fixed it on Aug 7, 2021 as per
https://github.com/retiredtab/propr...mmit/3984c2ef6852794a939b8eda689fc477705d5c86
As you can see in my github history, that reversion back to S2 wifi has never changed since Aug 7, 2021....
Click to expand...
Click to collapse
I just mentioned wifi functionallty for those users of T810 having problems with ripees ROM after version 20211103 and looking for a stable version regarding that feature.
retiredtab said:
......Without looking through the 1000's lines of code or more, the above functionality exists probably in the hardware/samsung repo
https://github.com/LineageOS/android_hardware_samsung/tree/lineage-18.1/hidl/light
and the settings are probably saved in some directory, but the display menu for the button backlights isn't shown until I put in that one commit above. That is, the OS knows to use the saved settings, but without the menu overlay, it doesn't show the menu itself.
Click to expand...
Click to collapse
The settings seem to be in the file /data_mirror/data_de/null/0/org.lineageos.lineagesettings/databases/lineagesettings.db
When opening in DB Browser I found:
In table "secure" the lines
46 "button_backlight_timeout" (value 1000 [probaly for milliseconds as I set it to 1s in ripees ROM]) and
47 "button_brightness" (value 1.0).
In table "system" the line
47 "button_backlight_only_when_pressed" (value 1).
Never worked with .db files myself before but for the knowing it might be interesting if they want to fiddle around a bit.
New build called lineage-18.1-20220510-UNOFFICIAL-gts210wifi.zip
Yogi555 has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
May 10, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already
2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
4. If you are upgrading from the April 10 build, you may dirty flash the May 10 build. If you are NOT coming from the April 10th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.
@retiredtab just flashed it onto 20220410.
1st try very dirty (not wiping anything) resulting in bootloop.
2nd flash (after wiping system+caches) of ROM, Bitgapps28-arm, Magisk23 made it start.
Magisk had of course to patch boot.img again.
Thx very much.
Due to a post in the T710 regarding gapps, I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.
This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.
https://forum.xda-developers.com/t/...rsions-devices.3098071/page-367#post-86885091
It's also shown up in other roms like
https://forum.xda-developers.com/t/...7-1-04-30-2022.3937956/page-100#post-86885353
This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.
Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.
T710 thread post #8, #9 and #10.
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
I wanted to express my sincere thanks to @retiredtab and @Ipedia for your work on the ROMs for the T710 and T810. I have both devices and had previously used the @ripee versions in thread (2) [ROM][UNOFFICIAL][11] LineageOS 18.1 [T710][T715][T715Y][T810][T815][T815Y] | XDA Forums (xda-developers.com). But that 18.1 version had some noticeable bugs and wasn’t being maintained.
Thanks to @bmwdroid ’s April 15 post directing us to this forum, I have been experimenting with this ROM since then on both the T710 and the T810. Based on my pretty heavy usage, I can declare both to be excellent. Most notably, the WiFi is rock solid. The T810 and the T710 (especially) are outstanding hardware, and being able to run Android 11 is a huge boost in the device’s intrinsic value.
I have experienced a couple of random BSOD-equivalent crashes over the past month, but the tablet always immediately restarted. I am going to try and learn how to provide the necessary to the developers so, if it happens again, they can have the necessary evidence. Since I am a decent techie, but not a developer, I decided to write up the complete upgrade procedure I followed so others who come to this forum may benefit. See my next post.
PS: I put this post on both the T710 and the T810 threads since I have both devices.
Tab S2 T710 and T810 Upgrade Procedure Using LineageOS 18.1 ROM by retiredtab
These installation instructions work for both Tab S2 T710 and T810. I have both devices and have tested on both. I am a Windows guy, so these instructions assume a Windows PC. I am a lifelong techie guy and an Android enthusiast. But I am not developer, so these instructions should work for any competent newbie who is a decent techie, but I realize there may be alternative approaches for those who have deeper tech knowledge than me.
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 TGab S2 to your PC via USB and download onto the micro-SD card three files:
Retiredtab’s latest Lineage 18.1 ROM from lpedia-sf - Browse /gts28wifi at SourceForge.net (T710) or retiredtab - Browse /SM-T810/18.1 at SourceForge.net (T810)
open_gapps-arm-11.0-pico-20220215.zip from The Open GApps Project
Magisk-v24.3.apk from Release Magisk v24.3 · topjohnwu/Magisk · GitHub
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.
Comments:
I saw retiredtab’s comments about OpenGApps quality. However, this version works well for me. I had previously tried the latest MindTheGapps (which hung) and BiTGapps (which doesn’t include the Google restore functionality that I use.)
Magisk is optional if you want/like root. I do!
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.
Installed 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 steps 2 and 3 again.
Step 4 – Backup your stock ROM
In TWRP, select Backup, Select Storage to choose your micro-SD card, check all the boxes, and then swipe Backup.
Step 5 – Install ROM and GApps.
In TWRP, select Wipe, then Advanced Wipe.
Select all partitions except Micro SD Card.
Swipe to Wipe.
Back, Back again, then Format Data
Type yes, and hit check.
Back, Back, Back, and select Install.
Select your micro-SD storage.
Select the Lineage-18.1 ROM.
Add more Zips, and select open_gapps.
Swipe to confirm Flash.
Installation took about 3 minutes.
Wipe Cache/Dalvik, and Swipe to Wipe
Reboot System
Step 6 – Build your Android 11 Tab S2
First boot into Lineage was less than a minute, and then the Lineage boot animation took less than 2 minutes before “Hello” appeared.
On each build I’ve done I see “Speech services by Google keeps stopping” error once Hello appeared.
I assume this is one of the known OpenGApps bugs.
Clicking Close App makes it go away, and later Google replaces the module anyway.
Set up your Android device per your preference. I have loads of Apps so it takes me a long time. If you are less of a pack-rat, it shouldn’t take long!
At the end of the initialization process, be sure not to choose the Replace Lineage recovery option, otherwise TWRP goes away.
I have found that, by not installing Magisk initially, Google restores all my Apps, including the sensitive ones such as Peacock, Netflix, Disney+, etc. And when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
I recommend leaving tablet completely alone until Google has finished its “Copy Apps and Data” from my other tablet. 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 copy process, but I load my layout from backup at this time)
Microsoft Swiftkey
Default USB = File Transfer
Window/Transition/Animator Scale all set to Animation Off
Screen timeout 30 minutes, and screen saver Clock
Battery %age next to icon
FX File Explorer
Microsoft Edge as default browser (with AdBlock enabled and Google as search and sync to my PC)
Raindrop, for all my bookmarks
Advanced restart menu (to allow reboot into TWRP).
Step 7 – Make Root
Restart Tab S2 into TWRP.
In TWRP, Install Magisk-v24.3.apk.
Reboot System
In Android install Magisk-v24.3.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!
I do a final and full TWRP backup once the device is solid.
Note:
I found the fingerprint reader sometimes works to unlock the Tab S2. Per other discussions on this thread, looks like I got lucky!
pflyaz said:
Tab S2 T710 and T810 Upgrade Procedure Using LineageOS 18.1 ROM by retiredtab
Click to expand...
Click to collapse
Thanks. I updated FAQ to point to post #16 for newbies.
Hi just a question regarding Q5
A5. You MUST use TWRP 3.5.2_9.
Is there a reason for this! I'm only asking because I have 3.6.0.9-0 installed so just wondered why its a must.
Edit - ignore the message above I didn't see post 9 when reading this on my tablet but do now I am on PC.
Had this running now for the last 5 hours, everything seems to be fine but I'm seeing very slow WiFi speeds. Coming straight from (lineage-18.1-20211103-UNOFFICIAL-gts210wifi) where I was getting a constant speed over 330mb I'm now only getting 110 dropping down to 70 at best.
lojelo said:
Had this running now for the last 5 hours, everything seems to be fine but I'm seeing very slow WiFi speeds. Coming straight from (lineage-18.1-20211103-UNOFFICIAL-gts210wifi) where I was getting a constant speed over 330mb I'm now only getting 110 dropping down to 70 at best.
Click to expand...
Click to collapse
@retiredtab Maybe just a wild guess, but might this commit be related? In my understanding argosd is a daemon that controls the CPU governor so that CPU performance can be adopted to network bandwith requirements. Shouldn't that be activated for Wifi models as well?