Related
I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.
Click to expand...
Click to collapse
READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:
doesn't work as a result of flashing this;
initiates a nuclear meltdown, or;
doesn't permit your alarm clock to function normally.
By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.
Click to expand...
Click to collapse
Downloads:
click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)
Features:
[*]Compiled with UBERTC 4.9
UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
based on CM13
more to come!
Known issues in post #2
Changelog in post #3
Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.
Credit where credit is due
@Hashcode, because we wouldn't have CM on our kindles at all without him.
@BuQQzz for some mentoring & advice
@transi1 for porting CM13 and providing some useful fixes for build errors
XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD
Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-29
Last Updated 2016-08-07
Known issues
Bugs affecting all CM13-based ROMs on the kindle
Screen artifacts when playing video from Snapchat, Vine, etc.
Audio chops in and out often
Other bugs currently afflicting the other CM13 ROMs for this device
Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
Play Store & Setup Wizard FCs
CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)
Changelog
08/07/2016
experimental backtracking to kernel 3.0.84+
July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
07/01/2016
doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
reverting from UBERTC toolchains to native CM/AOSP one
05/20/2016
defecting to BlissRoms-Devices GH for newest device config files
05/2016 security patches from AOSP, et al.
04/27/2016
refreshing CM sources & obtaining latest sources from transi1
04/09/2016
revert the 4/4 kernel reversion; back to 3.0.101(+)
carry in latest edits from transi1 to try to fix the camera
04/04/2016
revert to kernel 3.0.72+
first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
03/29/2016
initial build!
Roadmap
The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.
Layers/RRO theming support
Custom boot animation (or at least one scaled to the kindle's screen size)
Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
Publication of a custom .gapps-config file for use with opengapps packages
I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.
So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.
Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.
Some updates...
I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.
More updates...
It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:
I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.
Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.
Finally, some planned changes:
I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
Obvious name change in the ROM, mentioned earlier.
Replacing CM's theme engine with RRO(?)
CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.
Good version,thanks. But it often wifi reconnect , can it fix?
wizard_mini said:
Good version,thanks. But it often wifi reconnect , can it fix?
Click to expand...
Click to collapse
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
monster1612 said:
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
Click to expand...
Click to collapse
It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time
Android system cost battery drain more than screen, is it normal?
wizard_mini said:
Android system cost battery drain more than screen, is it normal?
Click to expand...
Click to collapse
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
wizard_mini said:
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
Click to expand...
Click to collapse
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
sirp0p0 said:
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
Click to expand...
Click to collapse
It's a good solution,, I fix it, thanks
monster1612 said:
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
Click to expand...
Click to collapse
I use 4hours screen on and 7hours screen off cost 92% battery.
wizard_mini said:
I use 4hours screen on and 7hours screen off cost 92% battery.
Click to expand...
Click to collapse
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
monster1612 said:
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
Click to expand...
Click to collapse
Thanks. I am expecting it!
** This guide is depreciated, there is a new updated guide here**
If you are planning on using LineageOS 14 for this guide, you can bypass all of this except configuring location backends and battery optimization by heading to https://lineage.microg.org and downloading their ROM.
All download links as well as a link to a list of Open-Source applications to replace commonly used Play Store apps are in the third post.
*This will NOT work with MIUI Global, as the Play Store is already included in the ROM by default.*
I will be continuously updating this guide for everyone as I stumble upon more supported ROMs, more MicroG flashable zips, and other misc. edits. This is made with Android Marshmallow and Nougat in mind as it is all I have tested on, however this may work on older releases of Android with Xposed support or ROMs with Signature Spoofing. This has also only been personally tested on the XT1607 variant.
In order to sync calendars and contacts from your Google account, you must flash the Google Sync Addon by ale5000. If you want swipe gesture typing on the AOSP keyboard, you must flash Shadow53's swipelib.zip. Shadow53 also has a No-Gapps zip package that includes F-Droid, Firefox, and several other apps.
One final thing: This is not for everyone. There was a point in time I didn’t ever think I could go without the Play Store, but ever since I have I don't want to go back. There are numerous pros to switching to a Google-free android setup such as much better battery life, more privacy on your device, a world of open-source alternatives to popular applications, and more. If you have any questions, or if any of this seems daunting if you are newer to things of this nature, please do not hesitate to ask for help. I will try the best I can in my free time to help. Thank you for taking the time to read this, let’s go ahead and start.
*Disclaimer* Your warranty is now void if you modify your phone. I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Click to expand...
Click to collapse
*This first post is for ROMs without native Signature Spoofing support. A list of those with native spoofing can be found in the second post as well as the guide for ROMs that include native signature spoofing.*
What You'll Need:
1. Your Phone with at least 80% battery, preferably 100%.
2. A computer to transfer files to phone
3. You must have Root Access. This can be native root or Magisk root.
4. Your ROM of choice
5. Download the correct Xposed SDK and Xposed APK for your version of Android. The Xposed SDK version may differ for your device.
6. MicroG Unofficial Installer ZIP and Google Sync Addon (optional) by ale5000 or any of Shadow53's MicroG flashable files (download links in third post)
7. Your favorite backup method if you wish to back up such as Titanium Backup, MyBackup Root/Pro, etc.
8. Third Party App Store/APK downloader such as Yalp Store if not wishing to use all open source apps
9. A working Google account
Click to expand...
Click to collapse
Alrighty, let’s finally get into the steps.
1. Make sure you have downloaded the requirements.
2. If you wish, backup the data you want. This should not erase any files stored on an SD card, but I cannot guarantee.
3. Boot into a custom recovery, I am using TWRP
4. Use the standard wipe data options
5. Flash the files in the following order:
Your ROM of choice
MicroG Unofficial installer
Xposed SDK
Custom kernel if using one
6. Just to be safe and to avoid any potential complications, now reboot the device and set up the basics. Afterwards, boot back into recovery.
7. In recovery, wipe Dalvik/ART cache only (Not really required, I always recommend it though just to be safe)
8. Go into Settings —> Security —> Turn Unknown Sources on to allow for APK installs.
9. Install the Xposed Installer APK
10. Open Xposed, grant any permissions/root permissions if it asks for any. Go to download, and search for FakeGApps. Download and install. Next go into the Modules tab of Xposed, and check the box next to the module. Reboot to activate (A soft reboot may work, but I recommend a full reboot.) Installing this allows MicroG to bind to the system and spoof the required signatures.
11. Open MicroG in the app drawer, and allow all permissions it asks for. While in here, turn on Google Device Registration
12. After allowing all permissions, go into Settings. Go to Accounts —> Add Account —> Google Account. Sign into your Google Account. This is necessary to allow certain applications that require Google Play Services to work properly.
13. After signing in, head back into MicroG, go under Google Cloud Messaging and enable.
14. In MicroG settings, head to the UnifiedNLP settings. Under the Configure location backends section, open WiFi Location Service and select Mozilla Location Service and grant any permissions asked. Under Configure address lookup backends, select Nominatim.
15. Finally, in Settings, go to Location and change the mode to High accuracy.
16. Check MicroG's Self-Check to see if everything has been set up properly, and if so, you are good to go!
Click to expand...
Click to collapse
*This post is the steps for ROMs that natively support Signature Spoofing. There is a list at the bottom of this post of those that currently support it
What you will need:
Your Phone
The ROM that supports Signature Spoofing and the kernel of your choice
MicroG unofficial installer and (optional) Google Sync Addon by ale5000 or one of Shadow53's MicroG installers
Magisk Root Manager (Optional)
About 20-30 minutes of your time
Click to expand...
Click to collapse
Steps:
1. Backup anything you want to have backed up. I recommend backup up your Contacts and Calendar events if you have those synced to Google
2. Boot into Recovery on your phone
3. Perform a standard wipe in TWRP
4. Flash the ROM
5. Flash the chosen microG zip file(s)
6. (Optional) Flash Magisk and your favorite kernel
7. (For crDroid Only)If you are flashing crDroid, you need to head over to Settings --> Miscellaneous and turn on the Signature Spoofing toggle
8. Go into Self-Check in microG, and tap the text that says "System grants signature spoofing permission", and allow microG that permission.
9. Still in MicroG, head back to the main part of the app. Open UnifiedNLP.
10. Select the pre-installed location backends.
11. Sign in to your Google account if you wish
12. You're done!
Click to expand...
Click to collapse
Moto G4 Play ROMs with Native Signature Spoofing
crDroid v3.8.1 - Android 7.1.2
ViperOS Coral - Android 7.1.2
TipsyOS - Android 7.1.2
AEX - Android 7.1.2
AICP (@ki's build) - Android 7.1.2
Glassrom Official - Android 7.1.2
MicroG Project has released an unofficial fork of LineageOS 14 that now includes signature spoofing and MicroG components. You will not need to follow anything in this guide except configuring location backends if you download their LineageOS build. There is no Play Store functionality added, although F-Droid (an open source app store) is included by default. You can add the Play Store with a zip that Shadow53 provided on their website (link in post below) More info can be found on their website
Flashable Packages and App Replacements
There are several different MicroG flashable zip files to choose from. ale5000 has one that includes MicroG, several location backends, and the Play Store. Shadow53 has MicroG and several other zip files such as an F-Droid package, the Swipe Libs for gesture typing on the AOSP keyboard, and several more.
Downloads:
MicroG Unofficial Installer - ale5000
Shadow53's Downloads for MicroG, F-Droid, and more
Now alternatives to apps you might commonly use such as Twitter, Facebook, Gmail, etc. can be a bit difficult to find at first. I stumbled upon a list that a user by the name of Datenschutz has compiled on GitHub that has a good collection of alternative open-source applications. Also, you can alternatively download APK files of certain apps such as Netflix, Messenger Lite, etc. if you don't find a suitable replacement.
Some open-source apps that are found on F-Droid I use daily are:
Flym - RSS Reader
QK SMS - SMS App
Twidere - Twitter Client
Toffeed - Facebook web-client
Newpipe - YouTube player
K9 Material - Mail app
ApkTrack - Checks for updates on APKs installed
Hi,
a Google account isn't required for Google Cloud Messaging (but it is required for many other things).
Also the official Play Store and contact / calendar sync apk work with microG (if needed).
I have created some tools to help setup microG (they are in my signature).
ale5000 said:
Hi,
a Google account isn't required for Google Cloud Messaging (but it is required for many other things).
Also the official Play Store and contact / calendar sync apk work with microG (if needed).
I have created some tools to help setup microG (they are in my signature).
Click to expand...
Click to collapse
I will definitely take a look into this, thank you! Any success on Nougat at all?
fireball0093 said:
I will definitely take a look into this, thank you! Any success on Nougat at all?
Click to expand...
Click to collapse
I'm using microG on Nougat and KitKat, and I can say that it works perfectly (but I patch the framework for signature spoofing instead of using Xposed).
Moto G4 Play (Harpia XT1607) specific so I guess I am not too far off topic: Is there a Nougat ROM available that has signature spoofing built it?
Given my bad experience with Xposed on my old Galaxy Nexus, I really only want to use a ROM with signature spoofing built it. If I have to compile it myself that would be okay but it would be nicer to have a ROM with built-in support. And since I don't think Xposed runs on Nougat yet, that is not an option anyway.
For my old Galaxy Nexus I've been using the Unlegacy project, compiling my own ROM with the signature patches built it. But although I've see "official" Nougat ROMs announced for the G4 Play (LineageOS, AOKP, AOSxP, etc.) either I can't find a link to the correct source code/manifest files or, as in the case of LineageOS I can't get it to compile (complains of missing component(s) even though I've used the provided scripts to pull what should be all the needed items from my phone).
I really want to get back to the non-Google experience I have on my Galaxy Nexus using microG. Thanks for any help!
n76 said:
Moto G4 Play (Harpia XT1607) specific so I guess I am not too far off topic: Is there a Nougat ROM available that has signature spoofing built it?
Given my bad experience with Xposed on my old Galaxy Nexus, I really only want to use a ROM with signature spoofing built it. If I have to compile it myself that would be okay but it would be nicer to have a ROM with built-in support. And since I don't think Xposed runs on Nougat yet, that is not an option anyway.
For my old Galaxy Nexus I've been using the Unlegacy project, compiling my own ROM with the signature patches built it. But although I've see "official" Nougat ROMs announced for the G4 Play (LineageOS, AOKP, AOSxP, etc.) either I can't find a link to the correct source code/manifest files or, as in the case of LineageOS I can't get it to compile (complains of missing component(s) even though I've used the provided scripts to pull what should be all the needed items from my phone).
I really want to get back to the non-Google experience I have on my Galaxy Nexus using microG. Thanks for any help!
Click to expand...
Click to collapse
I am currently looking into hopefully a method for Nougat, give me about a day to see if it works for me.
@fireball0093: If you compile from sources there the patches here instead to patch the compiled code there are the tools linked here.
ale5000 said:
@fireball0093: If you compile from sources there the patches here instead to patch the compiled code there are the tools linked here.
Click to expand...
Click to collapse
@ale5000: What ROM are you compiling from source for a Harpia (I hope that will work on a xt1607 flavor)? Got a URI I can use for repo init?
Thanks!
@n76: I just given the link of the generic signature spoofing patch that should theoretically work on all ROMs, I haven't compiled any ROM.
ale5000 said:
@n76: I just given the link of the generic signature spoofing patch that should theoretically work on all ROMs, I haven't compiled any ROM.
Click to expand...
Click to collapse
Thanks, I have been able to successfully use that patch on my personal builds of the Unlegacy ROM (Marshmallow and Nougat) for my Galaxy Nexus.
I just haven't been able to successfully build a ROM, even without the patch, for my Moto G4 Play.
n76 said:
I just haven't been able to successfully build a ROM, even without the patch, for my Moto G4 Play.
Click to expand...
Click to collapse
Sorry, I can't help with this.
Hallo,
i found a list of Roms supporting signature spoofing in the MicroG Threat. CRdroid is availible for Harpia and it is listen in the ROMS-List. Have anybody testet crDroid 2.1 for Harpia with MircoG?
Links:
https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141
gueschmid said:
Hallo,
i found a list of Roms supporting signature spoofing in the MicroG Threat. CRdroid is availible for Harpia and it is listen in the ROMS-List. Have anybody testet crDroid 2.1 for Harpia with MircoG?
Links:
https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141
Click to expand...
Click to collapse
Nice find, thank you!
Looking at the crDroid source code repository at https://github.com/crdroidandroid it does look like the patch for signature faking is in there. (We should probably have the page at https://github.com/microg/android_packages_apps_GmsCore/wiki/Signature-Spoofing updated to include crDroid).
But I am a bit leary about trying the ROM linked to at https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141 as, despite the title of the XDA thread, it does not seem to be an official build. It looks like the official builds for the project are at https://androidfilehost.com/?w=devices&uid=23991606952610065 and are all built by "crdroidandroid" and there is no Moto G4 Play build there. The "[ROM][OFFICIAL][7.1.1] crDroid v2.1" links to a ROM built by SubhrajyotiSen on a different page so I am a bit hesitant to install it.
But this is interesting enough that I will try to build the ROM myself using the official sources from the crDroid project and see what happens.
it may be an inofficial Build, but it is mentioned on the G+ - Page of crDroid!
https://plus.google.com/communities...6/stream/d3e3f57f-b974-41f2-8740-97dbdd38056c
I went and installed crDroid here on the forums and also flashed the MicroG installer after flashing crDroid. I can confirm that signature spoofing is available and works. Under Settings, you just have to go to crDroid Settings, scroll down to Miscellaneous, and toggle Allow signature spoofing. Then go into the Self Check section in MicroG and tap "System grants signature spoofing permission" and allow MicroG to have that permission, and then the only thing you have to do to is configure the pre-installed location backends and you're good to go. I'll edit the second post and this thread to include this find, thank you @gueschmid
*Edit*
Actually, would people prefer me to edit this guide and leave it up as a Marshmallow-only guide and then create a second one for Nougat with our device? Just to keep it a bit clean
fireball0093 said:
I went and installed crDroid here on the forums and also flashed the MicroG installer after flashing crDroid. I can confirm that signature spoofing is available and works. Under Settings, you just have to go to crDroid Settings, scroll down to Miscellaneous, and toggle Allow signature spoofing. Then go into the Self Check section in MicroG and tap "System grants signature spoofing permission" and allow MicroG to have that permission, and then the only thing you have to do to is configure the pre-installed location backends and you're good to go. I'll edit the second post and this thread to include this find, thank you @gueschmid
*Edit*
Actually, would people prefer me to edit this guide and leave it up as a Marshmallow-only guide and then create a second one for Nougat with our device? Just to keep it a bit clean
Click to expand...
Click to collapse
Thanks for trying this out. I think I will have the time to follow your lead next week. It will be good to excise GApps from this phone.
VoLTE is important for me, is it working on this crDroid build?
n76 said:
Thanks for trying this out. I think I will have the time to follow your lead next week. It will be good to excise GApps from this phone.
VoLTE is important for me, is it working on this crDroid build?
Click to expand...
Click to collapse
I don't have a carrier that uses VoLTE, but I took a look in the Changelog on some posts and it seems to have support for it on crDroid
Updated the guide to include crDroid in the second post. I have been messing around with Tingle in my spare time but I cannot fully grasp the concept as I don't have much experience using tools like that. If I do succeed in the future, I'll edit that in as well.
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!
Neutrino Kernel began as an effort to keep the stock LineageOS 15.1 kernel up-to-date with the latest linux-stable releases and has since evolved into an intensive crash course in maintaining my own custom kernel. Although some of you would accuse me of modesty, I think it's important to acknowledge that I am a "kernel developer" in the same way that Amy Schumer is a "comedian". That is to say, my work is highly derivative and built on the backs of individuals who are far more talented than I am. My role here is to have a vision, establish a design philosophy, and use the resources at my disposal to bring that vision to fruition.
Those of you who've perused my staging repo will know that I'm very particular about cleanliness. All changes and additions are vetted based on viability and purpose. Neutrino is based on kernel.lnx.4.4.r35-rel, pure CAF source for Android 9.0 tracking and upstreamed to the latest linux-stable release. I have manually rebased Essential's stock kernel source on top of CAF using relevant OEM commits from PPR1.181005.034. All major features and patchsets are assembled on independent staging branches of this codebase base and merged into the release repository.
I do not commit changes that I cannot justify or explain, and I do not go on indiscriminate cherry-picking sprees. There are a handful of developers that I highly respect, and who's projects have served as inspiration for my own. My intention is to incorporate the best of what they've brought to the table in a way that most effectively achieves and enhances this project's design goals.
I like to think that Neutrino is relatively subdued in terms of "features", with a stronger focus on optimizations over fluff. That being said, there have been quite a few additions which I feel have merit in terms of increased performance and/or efficiency provided the former does not compromise the later:
Revamped EAS implementation for Pie
sultanxda's CPU/GPU Boost Drivers
Dynamic SchedTune Boosting
Maple I/O Scheduler
Broader subsystem support for Power Efficient Workqueues
KCAL Color Control
Backlight Dimmer
Fsync Toggle (enabled by default)
GPU Underclock @ 180 MHz
CPU (partial) Overclock, Silver Cores @ 2035 MHz
Boeffla Wakelock Blocker v1.1.0
Wireguard Support
VDSO Support
Treewide memory allocation/overflow patches from mainline
OOM Reaper and various memory management enhancements to improve LMK
Treewide compiler warnings corrected
Built with self-compiled Clang 8.0.3 and GCC 8.2.0 toolchains, with a local initialization sanitizer and polly optimization flags
INSTALLATION:
**Neutrino now utilizes AnyKernel2 zip format for universal compatibility**
As a result, you can now flash this kernel on just about anything including Oreo/Pie custom and stock ROMs. The only requirement is that your firmware is current and up-to-date with PPR1.180905.036 at a minimum. Flashing on older firmware will result in broken input detection and a non-functional touchscreen.
That being said, this is an EAS kernel and is best suited for use on EAS-compatible ROMs. Just because it can be flashed on stock does not mean that you should do so. Installation on ROMs which do not natively support EAS (such as stock) will likely result in sub-optimal battery performance and I will not entertain any complaints stemming from the use of Neutrino on ROMs which are incompatible with EAS. Stock support is a perk and an experiment on my part, please do not make me regret giving you the ability to flash on stock, I will drop public support for it if this disclaimer is routinely ignored. If you choose not to heed my recommendations, you are doing so at your own discretion.
For ease of use, I would recommend using an app with built-in zip flashing functionality such as EX Kernel Manager or FK Kernel Manager. Of course, I cannot expect all of you to utilize a paid app for installation and as such, conventional installation via TWRP is certainly possible as well.
Neutrino will preserve existing Magisk installation during kernel update, meaning if you already have Magisk installed on your device you need not worry about reflashing Magisk when updating your kernel. If you do not already have Magisk installed and desire root access then Magisk zip must be flashed following kernel zip via TWRP.
DOWNLOADS:
Current releases can be downloaded here.
Archival builds (boot images) for lineage-15.1 can be found here.
SOURCE & SPECS:
Neutrino Kernel Source
Neutrino Staging Repo
Changelog
Linux Kernel Version: 4.4.166
CAF Release: LA.UM.7.4.r1-03900-8x98.0
Neutrino Kernel Version: hercules
Clang Version: neutrino clang 8.0.0-r348460
Build Date: 20181206
@return.of.octobot Awesome! Thanks for bringing us upstream updates! So if I've understood it correctly if I do flash the root version and want to take an ota update, I'll have to revert to stock kernel for the lineage os version I was on or flash the non root version that you've provided us with before updating?
You're as awesome as you are humble. Thank you for this. Life is getting easier and easier for common users thanks to contributions like this. Awesome.
Arju said:
@return.of.octobot Awesome! Thanks for bringing us upstream updates! So if I've understood it correctly if I do flash the root version and want to take an ota update, I'll have to revert to stock kernel for the lineage os version I was on or flash the non root version that you've provided us with before updating?
Click to expand...
Click to collapse
When I had magisk installed and was running lineage... The OTA program didn't care about signatures...
Since it's not a Delta... It's not patching anything... Just overwriting what is currently there... So it SHOULDN'T matter...
Sent from my PH-1 using XDA Labs
rignfool said:
When I had magisk installed and was running lineage... The OTA program didn't care about signatures...
Since it's not a Delta... It's not patching anything... Just overwriting what is currently there... So it SHOULDN'T matter...
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Hey, great to see you here. I remember you from the Nexus 6 forums. Thanks for the answer
Arju said:
Hey, great to see you here. I remember you from the Nexus 6 forums. Thanks for the answer
Click to expand...
Click to collapse
Yeah... I couldn't help myself... When I found out buying this phone was a direct thank-you to Andy Rubin...
Sent from my PH-1 using XDA Labs
Arju said:
@return.of.octobot Awesome! Thanks for bringing us upstream updates! So if I've understood it correctly if I do flash the root version and want to take an ota update, I'll have to revert to stock kernel for the lineage os version I was on or flash the non root version that you've provided us with before updating?
Click to expand...
Click to collapse
rignfool said:
When I had magisk installed and was running lineage... The OTA program didn't care about signatures...
Since it's not a Delta... It's not patching anything... Just overwriting what is currently there... So it SHOULDN'T matter...
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
He is right, I was recommending that the unrooted image be flashed prior to OTA but you could also certainly restore the boot.img that was originally included in invisiblek's build for maximum peace of mind. I would tend to agree that it doesn't actually matter as the OTA should be installing a completely new image on the opposite slot so I'm not sure what difference it would make, I was just leaning my instructions towards the safe side, perhaps I'll try and clean them up.
only for lineage can it work on aosp rom?
Sent from my PH-1 using Tapatalk
kakabobo said:
only for lineage can it work on aosp rom?
Click to expand...
Click to collapse
Yeah, it's literally built from Lineage source with upstream Linux kernel merged in. I wouldn't recommended flashing this on AOSP any more than I would recommended flashing the stock Lineage kernel on an AOSP build. Even if it booted I imagine there's a good chance it would break things to the point of being unusable. That being said, I haven't tried it so I'm only speculating. If you do, make sure you've got a copy of your ROMs stock boot.img to recover with. But seriously, I wouldn't.
return.of.octobot said:
Will be uploading 4.4.118 images within the next day or two, currently experimenting with merging the latest CAF tags into upstream source. Jury's still out on whether or not that's going to prove successful but I will be releasing standard linux-stable builds regardless.
Click to expand...
Click to collapse
Without further ado, 4.4.118 images are available for download here.
Same deal as before, built from unadulterated upstream linux-stable source. Stock and Pre-Patched Magisk variants available.
I did manage to get a CAF-based version of this kernel building and booting, however it broke my touchscreen and is clearly not ready for public consumption. So, until further notice we're going to stick with the 'if it ain't broke..' philosophy, although you may or may not see me releasing some experimental builds in the future.
For now, enjoy 4.4.118
***OP updated for 4.4.118 release, revised comprehensive installation instructions***
return.of.octobot said:
***OP updated for 4.4.118 release, revised comprehensive installation instructions***
Click to expand...
Click to collapse
That's for the build today right?
shooterlgk said:
That's for the build today right?
Click to expand...
Click to collapse
In theory these images should work on any LineageOS install, regardless of build date, but yes it's compatible with both the 02/26 and 02/28 releases from invisiblek. I've updated the screenshot in OP which shows this kernel installed on the latest Lineage OTA.
return.of.octobot said:
***OP updated for 4.4.118 release, revised comprehensive installation instructions***
Click to expand...
Click to collapse
flashed your kernel with magisk support on todays (28th) lineageos build. Magisk is not passing safteynet.
edit: followed your instruction to patch the boot img using magisk and now it passes safteynet. had to use the non patched on from here.
Arju said:
flashed your kernel with magisk support on todays (28th) lineageos build. Magisk is not passing safteynet.
edit: followed your instruction to patch the boot img using magisk and now it passes safteynet. had to use the non patched on from here.
Click to expand...
Click to collapse
Good to know, I'll have to make note of your findings in the OP. I would've never figured that out myself as I've got xposed installed and to the best of my knowledge my SafetyNet checks will always fail because if it. I've really just been offering the prepatched images because I thought it would be helpful to allow some to bypass the step of patching manually. However, I'll have to consider whether it might be a better idea to just provide the clean image with instructions on how to patch it.
return.of.octobot said:
Good to know, I'll have to make note of your findings in the OP. I would've never figured that out myself as I've got xposed installed and to the best of my knowledge my SafetyNet checks will always fail because if it. I've really just been offering the prepatched images because I thought it would be helpful to allow some to bypass the step of patching manually. However, I'll have to consider whether it might be a better idea to just provide the clean image with instructions on how to patch it.
Click to expand...
Click to collapse
So this is what I did.
1. Flashed lineage os. Set it up.
2. Flashed your kernel (non magisk version) using fastboot and booted back into rom. (Not sure if this is necessary as I later on flash the patches version by magisk manager).
3. Install magisk manager. Have the non magisk version of your boot image on my phone. Patch it with magisk manager.
4. Transfered the patched boot image to computer.
5. Flashed the patches boot image using the computer (fastboot). Reboot into system.
6. Safetynet check passes.
Arju said:
So this is what I did.
1. Flashed lineage os. Set it up.
2. Flashed your kernel (non magisk version) using fastboot and booted back into rom. (Not sure if this is necessary as I later on flash the patches version by magisk manager).
3. Install magisk manager. Have the non magisk version of your boot image on my phone. Patch it with magisk manager.
4. Transfered the patched boot image to computer.
5. Flashed the patches boot image using the computer (fastboot). Reboot into system.
6. Safetynet check passes.
Click to expand...
Click to collapse
Thanks for sharing. I essentially went through the same process to patch these images myself after they were built, perhaps there is some kind of security measure in place where the boot.img needs to be installed to the same device it was patched on? I find it strange that it would successfully root the device, but not pass SafetyNet. I'll think on that and figure out if it makes more sense to just release unpatched builds in the future.
return.of.octobot said:
Yeah, it's literally built from Lineage source with upstream Linux kernel merged in. I wouldn't recommended flashing this on AOSP any more than I would recommended flashing the stock Lineage kernel on an AOSP build. Even if it booted I imagine there's a good chance it would break things to the point of being unusable. That being said, I haven't tried it so I'm only speculating. If you do, make sure you've got a copy of your ROMs stock boot.img to recover with. But seriously, I wouldn't.
Click to expand...
Click to collapse
I flashed it on AOSIP without issue. Not sure if it's considered the same as AOSP.....
return.of.octobot said:
Thanks for sharing. I essentially went through the same process to patch these images myself after they were built, perhaps there is some kind of security measure in place where the boot.img needs to be installed to the same device it was patched on? I find it strange that it would successfully root the device, but not pass SafetyNet. I'll think on that and figure out if it makes more sense to just release unpatched builds in the future.
Click to expand...
Click to collapse
I wouldn't realy mind and I think it would make it easier for you too. If the patching is unique per phone then it makes sense that we patch it ourselves. But we need upstreamed updated kernels!!! so don't stop doing those!!
Arju said:
I wouldn't realy mind and I think it would make it easier for you too. If the patching is unique per phone then it makes sense that we patch it ourselves. But we need upstreamed updated kernels!!! so don't stop doing those!!
Click to expand...
Click to collapse
Yeah of course, no sooner had I uploaded 118 than 119 was pushed. I'm not sure if I'll be able to get one out for each release before the next one comes out, but I'm going to be keeping these updated a frequently as I can. Anyway, I was only speculating about device-specific images, but I'm going to try and flash an image that was patched by my buddy and see if I can reproduce any issues. Regardless, I'll likely stick to uploading unpatched images in the future.
LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T715 ONLYModel: SM-T715 (LTE) - gts28ltexx - 8" screen, Exynos 5433 SoC, LTE
This is the ONLY model that the ROM will work on.
There is NO ROM for the T710, T810 or T815 in this thread. Questions about T710, T810 or T815 will be completely IGNORED.
For T710 please use the equivalent ROM at its separate XDA forum thread.
For T810 please use the equivalent ROM at its separate XDA forum thread.
You MUST READ posts 1-3 (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
bluetooth
wifi
GPS
brightness
audio through loudspeaker
audio through headphone jack
audio over bluetooth
SELinux enforcing
DRM level 3 (SD definition)
deep sleep
RIL - mobile data and telephony/SMS/Cell Broadcast - some limitations for telephony audio options apply, see below
vibration and haptic feedback
hardware buttons and lighting
What doesn't work
fingerprint. As retiredtab wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
the team will not spend anymore time looking at fingerprint. If you need fingerprint to work, stay with stock Samsung ROM.
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 streaming media, stay with stock Samsung ROM.
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. While recent builds solved the touchscreen issue, you still might see excessive battery drain until you perform another reboot.
For telephony audio, currently only the loudspeaker option is working. If you try to use/switch to bluetooth audio during a phone call, the audio stack will go wild and afterwards loudspeaker will stop working too until you perform a reboot.
Please note that for an incoming call, it might take a couple of seconds until both sides can hear each other.
I have invested a lot of time trying to troubleshoot the audio routing, and this is for sure a device-specific issue most likely due to the the old Samsung binaries so chances are almost zero to get that fixed.
Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
LineageOS team for the upstream source code.
@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/
A special shout out to retiredtab for providing the T710 ROM and code here which is the base for this ROM. Also this ROM would not have been possible with all the help and mentoring he provided during the past 6 months of development. Also many thanks to lpedia and bluess57 for their outstanding hints and tips.
All past contributors of the exynos5433 code, especially ananjaser1211 for his major contributions and @ripee for working on prior gts2 builds until end of 2021.
@rINanDO for his lmkd spam fix in 18.1.
Alpha testers: simon-edwards for the many hours testing and helping troubleshooting RIL, SELinux policies and various gapps options; Don K and Sir Thopas for addional RIL model testing.
@bluess57 for his excellent code donations for the gts2 LTE models.
retiredtab and lpedia for providing the blueprint for this forum entry and the FAQ in post #2 and constantly improving it. This work is just a little contribution standing on strong shoulders of previous contributions.
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/metterschlg/android_kernel_samsung_universal5433
Device Tree
https://github.com/metterschlg/android_device_samsung_gts2-common-selinux
https://github.com/metterschlg/android_device_samsung_gts28ltexx
Vendor
https://github.com/metterschlg/proprietary_vendor_samsung
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5e
Build manifest can be found at
https://github.com/metterschlg/local_manifests/blob/lineage-18.1/gts28ltexx.xml
Build environment setup is docmented (as code) at
https://github.com/metterschlg/los-devel-scriptsQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid April 2022 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. I use official TWRP 3.6.1_9. Get it from
https://twrp.me/samsung/samsunggalaxytabs280ltexx2015.htmlQ6. 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. I plan to do so. I will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be quickly tested to make sure the ROM 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.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 this post. 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 and I'm using it, but that could change with any revision and changes by Google. However I 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 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 T710, T810 and T815.Q22. Does this ROM have any wifi connection issues?A22. This ROM's wifi has been stable on the specified device ever since lpedia and retiredtab determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q23. Is this ROM secure so I can do financial transactions?A23. 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.Q24. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA ROM?A24. Downloads are at
https://sourceforge.net/projects/los4sgt/files/los18.1/
Please note that there are two builds for every date. Start with the enforcing build, if you hit issues, flash the permissive boot image to determine if your issue is related to SELinux. If you have Magisk installed, you first need to patch the permissive boot image with the Magisk app before flashing.
If your initial enforcing build install does not have working RIL, you might need to fix SELinux labeling of your EFS partition. To do so, use ADB in root mode. Please note that ADB root needs to be enabled in the developer options of your device. Then use the following commands from a PC connected via ADB:
Bash:
adb root
adb shell
# Check if SELinux relabeling is required, do not modify anything
restorecon -R -v -n /efs
# If you see some "Relabeling..." output, run the real relabeling
restorecon -R -v /efs
Release notes
June 18, 2023 Release
June 2023 LineageOS & Android security fixes. >5500 files changed.
May 14, 2023 Release
May 2023 LineageOS & Android security fixes. >5600 files changed
April 23, 2023 Release
April 2023 LineageOS & Android security fixes. >4600 files changed.
March 26, 2023 Release
March 2023 LineageOS & Android security fixes. >27000 files changed.
February 18, 2023 Release
February 2023 LineageOS & Android security fixes. >21000 files changed.
January 22, 2023 Release
January 2023 LineageOS & Android security fixes. >4200 files changed.
December 17, 2022 Release
December 2022 LineageOS & Android security fixes. >3800 files changed.
November 13, 2022 Release.
November 2022 LineageOS & Android security fixes. >4000 files changed.
Kernel improvements by Ananjaser
Starting with these builds I will only publish the SELinux enforcing ROM. If you encounter issues that might be SELinux-related, please first flash the boot_permissive-<date>.img as boot image and re-try to help me identify if the issue is SELinux-related.
October 22, 2022 Release.
Initial public release. First 18.1 T715 ROM with working RIL, also first 18.1 T715 ROM with SELinux in Enforcing mode. T710/T715 common code based on retiredtab's work for T710 so all his latest changes apply as well.
Reserved #3
Reserved #4
Reserved #5
Congratulations on this release @metterschling and @retiredtab , great to see!
@metterschling If you don't mind a couple of comments about your scripts, you need not have created a patch for my script. You could have just forked mine and pushed your changes to it. No need to complicate things for novice builders. Secondly, I'm sure your gts28lte tree can be a source of inspiration for the other 3 variants so as to build a complete set. Thirdly, you may be able to let gts28wifi users flash your builds if you add gts28wifi as a TARGET_DEVICE, to make it easier to cover more users in the meantime. Fourthly, you clone so many repos when it could be cleaner to fork then substitute your forks in the roomservice. This could avoid potential repo syncing errors.
ripee said:
@metterschling If you don't mind a couple of comments about your scripts, you need not have created a patch for my script. You could have just forked mine and pushed your changes to it. No need to complicate things for novice builders. Secondly, I'm sure your gts28lte tree can be a source of inspiration for the other 3 variants so as to build a complete set. Thirdly, you may be able to let gts28wifi users flash your builds if you add gts28wifi as a TARGET_DEVICE, to make it easier to cover more users in the meantime. Fourthly, you clone so many repos when it could be cleaner to fork then substitute your forks in the roomservice. This could avoid potential repo syncing errors.
Click to expand...
Click to collapse
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
metterschling said:
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
Click to expand...
Click to collapse
@ripee I've pushed a new version of the build environment setup script, following your guidance. Please let me know if there are more areas of improvement, very much appreciated!
November build lineage-18.1-20221113-UNOFFICIAL-gts28ltexx.zip uploaded. Please see FAQ #24 for the download link.
November 13, 2022 release notes:
November 2022 LineageOS & Android security fixes. >4000 files changed.
Kernel improvements by Ananjaser
Starting with these builds I will only publish the SELinux enforcing ROM. If you encounter issues that might be SELinux-related, please first flash the boot_permissive-<date>.img as boot image and re-try to help me identify if the issue is SELinux-related.
Enjoy!
metterschling said:
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
Click to expand...
Click to collapse
If gts28wifi users get an error that their device is not gts28ltexx, then yes it would be necessary to add it as a target device in the tree. Lineage uses the networkstack repo from google, which you can tell cuz they track the aosp remote, so in this case we have nothing to fork and substitute. Only a patch of google's own repo would be convenient.
Just to clarify, since there has been discussion about the WiFi version (t713), can this ROM be safely flashed on one?
Also I believe I have a t715Y... Would this t715 ROM work on it?
(I have three Tab S2 units -- two t713 models and a t715Y.)
Thanks
KeepingItCuttingEdge said:
Just to clarify, since there has been discussion about the WiFi version (t713), can this ROM be safely flashed on one?
Also I believe I have a t715Y... Would this t715 ROM work on it?
Click to expand...
Click to collapse
The T713 and T715 have completely different chipsets. T713 is msm8976 and T715 is exynos5433.
If your T715Y is known as "gts28ltexx" OR "gts28lte" as described in post #1, then you can flash this rom on it. You can download an utility called devcheck by flar2 to verify. Your device name will be shown in the system tab under device.
https://play.google.com/store/apps/details?id=flar2.devcheck
metterschling's code checks for gts28lte,gts28ltexx using this below
https://github.com/metterschlg/andr...s28ltexx/blob/lineage-18.1/BoardConfig.mk#L17
KeepingItCuttingEdge said:
Also I believe I have a t715Y... Would this t715 ROM work on it?
Click to expand...
Click to collapse
Most likely, ROMs for the T715 work on the T715Y according to some XDA posts. Like this one. I don't own a T715Y, so can't test myself.
December build lineage-18.1-20221217-UNOFFICIAL-gts28ltexx.zip uploaded. Please see FAQ #24 for the download link.
December 17, 2022 release notes:
December 2022 LineageOS & Android security fixes. >3800 files changed.
If you are coming from a previous version of these builds, you can dirty flash, otherwise please perform a factory reset and format data before installing this ROM.
Enjoy
Hi friends, after loading from TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar on my SM T710, my tab gets stuck on booting with lineageos graphics. I made the backup with TWRP if I upload the files can I repair the tab as before?
mikelosat said:
Hi friends, after loading from TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar on my SM T710, my tab gets stuck on booting with lineageos graphics. I made the backup with TWRP if I upload the files can I repair the tab as before?
Click to expand...
Click to collapse
If I understand correctly, you picked the gts28ltexx version which is for the SM-T715. If your device is the SM-T710 (gts28wifi) I'd strongly recommend to use the ROM and matching TWRP linked in this thread.
If your device is SM-T715, please see FAQ #5 in post #2 of this thread. I use the downlevel TWRP because newer ones did not work for me.
I use a SAMSUNG SM-T715 device just as described:
Model: SM-T715 (LTE) - gts28ltexx - 8" screen, Exynos 5433 SoC, LTE.
To be able to install the ROM I used "TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar"
After several attempts I could neither restore the BACKUP nor start the operating system. I had to do a complete WIPE and at that point lineageos advanced, now I'm having problems, I don't have the gapps I downloaded version 11 for ARM but despite having enough space it gives me an error "70" not enough space. I have no google services and no PLAYSTORE, I am in a critical situation, how can I install the google PlayStore? I can't even add gmail account from settings, it's a disaster.
metterschling said:
If I understand correctly, you picked the gts28ltexx version which is for the SM-T715. If your device is the SM-T710 (gts28wifi) I'd strongly recommend to use the ROM and matching TWRP linked in this thread.
If your device is SM-T715, please see FAQ #5 in post #2 of this thread. I use the downlevel TWRP because newer ones did not work for me.
Click to expand...
Click to collapse
Finally I come to the conclusion, after fully formatting my SAMSUNG SM T715 the ROM started up, the problem was the wrong recovery, using the version indicated in the guide above everything started up correctly.
Unfortunately this ROM is full of bugs and its use is useless, below I will list all the problems it causes during use:
1. 4g calls don't work, during the call you can't hear anything either incoming or outgoing.
2. Bluetooth only works with music while in call it remains mute.
3. the only way to call is to keep the speakerphone open otherwise the call will be silent.
4. Whatsapp is impossible to use and only allows you to use it in beta.
5. Smart Switch as for whatsapp does not work with custom ROMs
6. Does not sync contacts even though sync has started.
It's really a shame after all these hours to find that you've only wasted so much time.
Maybe I've done something wrong, I don't rule it out, maybe someone will be able to give me some advice.