Related
/* Intro */
3 months after the first functional Xposed for Lollipop by @rovo89 was introduced,
now here comes *somewhat* functional Xposed for Samsung Lollipop firmware.
Embrace yourself.
/* Technical background */
Why were Samsung users left out of the Xposed party?
Because Samsung has massively customized ART runtime included in their firmwares compared to AOSP.
And plus, because the system partition has so little space left, they have additionally implemented xz decompression on top of ART.
Those 2 main reasons has differentiated Samsung's ART from the rest of the ROM's ART.
More technical information on post 2.
/* Disclaimer */
Your warranty is now void.
I am 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 project
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Prerequisite */
Due to my skills limitation, only deodex'ed ROMs are supported for now.
For more explanations, checkout post 2.
/* Supported firmwares */
Every ARMv7(32-bit) Samsung Lollipop Android 5.0 deodex'ed firmware should work.
But please note that I have tested this only on Galaxy S4, Note 3 and S5.
For 64-bit, please check http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 by @wanam
For 32-bit on Android 5.1, I cannot develop on it as I don't have any 32-bit devices capable of running Android 5.1.
/* Before you download ... */
Donate to @rovo89
Donate to @wanam
Show your thanks to @_riddle
Without these people, this would not have been possible at all.
/* Details about binaries */
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
-O3 and other compiler optimizations added
Release separated to "exynos" and "snapdragon" versions for more compiler optimizations
Optimize everything enabled
/* Download */
Attached below on XDA
/* How to install */
1. No matter what you do, back-up first.
2. Install XposedInstaller app from http://forum.xda-developers.com/showthread.php?t=3034811
3. Flash the attached Xposed framework zip on the custom recovery.
/* How to uninstall for V1 ~ V7 */
1. Flash the attached Xposed uninstaller zip on the custom recovery.
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
/* Technical information and Q&A */
Q: What took you so long?
A: @rovo89 has explained himself. http://forum.xda-developers.com/showpost.php?p=58949255&postcount=3
Q: Okay, you don't seem like a better developer than @rovo89. How did you do it?
A: Of course not. This is the main reason why deodex'ed ROM is a prerequisite.
Samsung has implemented all sorts of funny stuffs on their version of ART. See the link above.
To workaround this, converting a ROM to deodex'ed format somewhat brings back the oat formats to *AOSP-like* dex format(Huge thanks to @_riddle).
After deodexing is done, we can use source-built ART binaries with minimal modifications.
But due to my coding skills, I had to modify core-libart.jar to make it work again.
The core-libart.jar differs from every single device out there and it'll be a real headache to match with 1 ART binary version. That's why I've included the core-libart.jar on the installation zip file.
The included core-libart.jar has 2 different versions to correspond on the type of ROM user is using.
1 : Firmwares with appStartup
2 : Firmwares without appStartup
After deodexing, installing new ART stuffs, we can start the boot-up sequence.
Unfortunately again, /system/bin/installd passes some arguments that AOSP version of dex2oat do not understand. To bypass this, I've patched oat tools to ignore unimplemented arguments.
Now we can see the good old "Android is upgrading" pop-up and go have a cup of coffee while it dexopts all those hundreds of bloatwares.
Q: Fantastic, but now I get a continuous logcat burps - http://pastebin.com/MxeAE76n
A: To avoid that, that's why I've put 2 different versions of core-libart.jar. But unfortunately on those cases, my installer has failed to recognize which version your ROM uses.
During the installation, the installer will output a message on which core-libart.jar is installed on your system.
After you see that logcat stuffs, please change to the opposite version of core-libart.jar the installer told you.
So for example, if the installer says core-libart1.jar is installed, extract the zip and replace /system/framework/core-libart.jar with core-libart2.jar within the zip.
Q: How do I deodex my ROM?
A: @joeldroid and @svadev have an awesome tool for you to deodex your ROM.
Go check http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857 and http://forum.xda-developers.com/galaxy-s5/general/tool-deodex-tool-android-l-t2972025
Both worked flawlessly for me.
Q: Gimme tha sources!
A: https://github.com/arter97/android_art/tree/samsung-lollipop
Q: AAA and BBB modules are incompatible!
A: Most likely because they don't support Touchwiz Lollipop *yet*.
Q: You mother father gentleman, you bricked my phone!
A: Unfortunately, I had tested those only on 3 devices which, ironically, has the same processor. Maybe Exynos family is not support, I don't know.
I told you to back-up beforehand. Post log and we can probably work together and add your device/ROM supported.
/* Changelog */
v75
Xposed v75 merged
(Fixes boot issue with latest Android 5.0 firmwares)
Method changed to use @wanam's XposedBridge
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
V6
Xposed v71 merged
Possible performance degradation issue fixed
Releases renamed to "exynos" and "snapdragon", now the "exynos" version is properly optimized for Exynos processor
Uninstaller added
Optimize everything enabled
V5
Xposed v65 merged - Now compatible with alpha4
Do not attempt to use uninstaller provided by rovo89, it will brick your device for now - TODO
V4
ART runtime & Xposed binary changes by rovo89 merged - Fixes logging and some other misc issues
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
Few core-libart.jar smali durps fixed
-O3 and other compiler optimizations added
Release separated to "generic" and "krait" versions for more compiler optimizations
Generic - Devices with Exynos or other non-Krait Snapdragon SoCs; If you don't know which to choose, go with Generic.
Krait - Devices with Quadcore Krait Snapdragon SoCs.
V3
Another version of core-libart.jar added for GT-i9505 compatibility
(Firmwares without isMdfEnforced)
This update is unnecessary for devices which already runs Xposed with no issues.
V2
Source code modification attempted to hopefully fix boot issues with devices like Galaxy Alpha.
https://github.com/arter97/android_art/commit/eed217701cc2d3a57f940c5bd69b393c768777a9
This update is unnecessary for devices which already runs Xposed with no issues.
/* Known issues */
- Galaxy Alpha users apparently get a bootloop with this.
A kind user provided a logcat, will look into it ASAP.
Solved with V2.
- GT-I9505 users apparently get a continuous Google Apps FCs with this.
Solved with V3.
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Sweet! Any chance of supporting the S6 in the future?!
Damn no support for s6 edge
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
Looks great though. No decomiling involved
SuperSmashedBro said:
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Click to expand...
Click to collapse
Exactly same .
Goood good
works fine on my galaxy s5 dous BOC2
xposed moudle and install apk normally works fine
darkera13 said:
Exactly same .
Click to expand...
Click to collapse
Which one is the original method yours or arter's?
I'm confused?
AMAZING!!!!!
arter you're genius!
noobiedev83 said:
Which one is the original method yours or arter's?
I'm confused
Click to expand...
Click to collapse
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
It should at least give you credit for that because I do remember seen your post a week ago
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
Um, no offense but your method quite differs from mine.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Your guide did not help me in anyways.
And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
arter97 said:
Um, no offense but your method quite differs from mine. And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Click to expand...
Click to collapse
You know what you do. Dont lie yourself.
To be honest, i tried both methods and @arter97 's methods worked for me without any hassle.
Kudos to you for making this work.
noobiedev83 said:
It should at least give you credit for that because I do remember seen your post a week ago
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/showpost.php?p=60747729&postcount=2645
and here http://forum.xda-developers.com/showpost.php?p=60748574&postcount=29
darkera13 said:
You know what you do. Dont lie yourself.
Click to expand...
Click to collapse
Stealing is the least thing to do on my mind, as I have gone through the same thing over and over.
Ask my Twitter's followers.
I can personally guarantee you that I have not stolen anything from you.
Ask me how I did it more specifically, I'll happily explain it to you.
Working on Note 4 PopRocks Rom N910T
arter97 said:
Please note that I have tested this only on Galaxy S4, Note 3 and S5.
Click to expand...
Click to collapse
You think this will work on Albe95 S6 Rom port (GT-I9505)? :fingers-crossed:
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, dexter93 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-12-12
Reserved
Changelog
20150921-1824: Changelog: Fixed recovery issues <<-- building
20150918-1152 : initial release [5.1.1_r16]
Downloads
haxynox-6.0-i9300-20151211-2331.zip 236.6MB
33aeb6e59ec686818cd4088502b75fd1
haxynox-i9300-20150921-1824.zip 208MB
MD5:130cea4633f0e9b278aeb3def6d67d08
Reserved
GApps
For Marshmallow 6.0 Roms I recommend the PICO version of OpenGapps
http://opengapps.org/
I have tested @dankoman s GApps ZERO package with this ROM and it works fine.
Here is the link
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
If you want to use anything else, please feel free to post about your experience, but be aware that if you GApps package of choice doesn't work on this AOSP rom, you'll need to convince the GApps maintainer to take a look into it. That being said I am happy to talk with any maintainer.
mcgi5sr2 said:
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, mcgi5sr2 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-09-21
Click to expand...
Click to collapse
^
That is what we always needed. Finnaly someone made it. THANK YOU!
Is there any screen shoots? And do we need GAPPS or is it included? I will try the rom. Thanks for taking your time to make annother ROM for our old S3
@mcgi5sr2 Hey man, I really commend you for doing this. All I've seen lately is Archi, Moster, & co.'s work (Apologies to the many unmentioned) being used as "base" for other users "projects", and of course all the real work is going on at source in the aforementioned dev's repos. I feel XDA has become a really unoriginal and user- (rather than dev-) oriented place recently.
Of course, you're not radically rewriting the fundamental Android code like the PA team did with Hybrid, but with such a ***ch of a chipset* it's pretty sick that you've taken it head-on to get AOSP up.
Sorry if this was a bit aggrandizing, I've just been tired of the constant stream of Sammy ROM ports and zip kangs.
By the way, you refer to yourself: "Ivan_Meler, mcgi5sr2 and myself", I think it should be "Ivan_Meler, dexter93 and myself"?
* "If you've ever glanced upon the sources" ... you bet you ... a glance was too much, I'm scarred ...
Thread cleaned, if you think you spotted a bug please attach logfiles and/or what you tried to fix it yourself etc.
Whiskey
Forum Moderator
Excellent, thanks for creating a thread for haxynox. Better than people posting in the slim/omni thread.
Any idea on how to fix the fact im getting bootloops on this particular rom?
I waited a long time for this! Thanks to all team :highfive::highfive:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
it's pure AOSP code ... without cyanogenmod 12.1 modifications.
if i understood correctly
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
lukewilliams418 said:
Any idea on how to fix the fact im getting bootloops on this particular rom?
Click to expand...
Click to collapse
Could you provide a little more info please?
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
No, in fact it has a lot less, but that is the point.
b0unty said:
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
Click to expand...
Click to collapse
The sources are all freely available, feel free to use them
lukaaa477 said:
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
Click to expand...
Click to collapse
see above...
myshakugan said:
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
Click to expand...
Click to collapse
Yea,sure it does,but i mean something else.
What i mean is, is there anything specific to the device changed, eg. Ram management,performance gains,optimizations etc.
mcgi5sr2 said:
Could you provide a little more info please?
No, in fact it has a lot less, but that is the point.
The sources are all freely available, feel free to use them
see above...
Click to expand...
Click to collapse
I used the latest version of TWRP to wipe all data and then I Installed the haxynox zip file with TWRP and then it just goes in a bootloop.
Bootloop
Enviado desde mi GT-I9300 mediante Tapatalk
any fix for this bootloop???
CottonmouthOS
A security and privacy focused mobile operating system based on CopperheadOS that is MicroG friendly.
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
This ROM is based on the great CopperheadOS ROM with signature spoofing enabled to allow MicroG framework. There will be changes to make the signature spoofing spoof ONLY the Google service signatures and ONLY usable/allowable by MicroG services ONLY. The new name CottonmouthOS is a way to distinguish from CopperheadOS builds, because of the signature spoofing patches.
Prerequisites coming from other ROMs :-
Have latest March factory image installed.
Instructions :-
Download the CottonmouthOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Features of CopperheadOS ROM
Note :-
CottonmouthOS is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team
Mar-V-in for MicroG
razorloves for inspiration
References :-
Copperhead homepage
Documentation
Instructions used to build
Sources
MicroG patch
If anyone wants to reupload to a better file hosting site please do.
OLD OP
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
- Mirror 1
- Mirror 2
- Mirror 3
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
Does copperhead have the pixel navbar animation?
File not yet uploaded
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
+1
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
That is strange. Will reupload.
EDIT: Done see OP
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
ChongoDroid said:
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
Click to expand...
Click to collapse
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
jahrule said:
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
Click to expand...
Click to collapse
Yeah CopperheadOS uses the stock recovery iirc. They do it like this to use verified boot iirc. I personally loved COS on my Nexus 5 and missed it on my pixel.
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Thank you for building this, I tried and failed miserably. Will flash it today :good:
Fdroid Keys and BuildSystem
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
KShion619 said:
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Click to expand...
Click to collapse
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
smilingtux said:
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
Click to expand...
Click to collapse
Please see the build instructions in the op that I posted.
Ideally, I would like to make another rom that has the restricted sigspoof added so we could have an option for microg
jahrule said:
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
Click to expand...
Click to collapse
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
KShion619 said:
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
Click to expand...
Click to collapse
The keys are compiled in so, no.
jahrule said:
Please see the build instructions in the op that I posted.
Click to expand...
Click to collapse
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
smilingtux said:
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
Click to expand...
Click to collapse
You seem to ask for a docker.
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
Hit thanks if you like my work.
Downloads : "removed by moderator"
Gapps :== "removed by moderator"
Nano recommended
Twrp :== "removed by moderator"
Don't flash magisk, right now root not supported.
What's working ---
WiFi
Mobile data
bluetooth
mobile data
hotspot
gcam
magisk
If you want to root your pie rom
just simply flash the magisk zip file via twrp.
then install the magisk manager apk manually and open that then you can the installed magisk version.
also you can check your rooot via rootchecker apk
Test this build and let me know the issue, so we could fix those issue.
Special thanks to all oxygen team and all group mates, who provides logs.
Testing thanks
@Cirno
@remicaa
@luciano Henrique
@Mario Resurrected
Credits:
MactavishAO
Hard_rock83
Mokee Development Team
LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Mokee Open Source Project
Version Information
Status: stable
First android 9? Things are coming! Thank you for the hard work.
Android-9.0(Pie)
It's just first build which booted properly. So there would be lots of bugs.
Let me know the bugs, so we could work on fixing bugs.
fgaurano said:
First android 9? Things are coming! Thank you for the hard work.
Click to expand...
Click to collapse
It's just first build, so there would be lots of bugs, let me know the bugs, so we could fix them.
Gapps?
MI MAX 2 cihazımdan Tapatalk kullanılarak gönderildi
OTA uptades avaible?
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
not
finger print,
double click open the screen
not blutouth
not xposed
Theseusperse said:
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
Click to expand...
Click to collapse
GCam 6.1 working on oreo
Which twrp to be used?
ridershahmir said:
GCam 6.1 working on oreo
Click to expand...
Click to collapse
How?!?! What APK are you using for the Mi Max 2? I've tried everything, even wiped my phone and used every ROM out there and can't get anything to work. I'm specifically talking about the latest 6.1 GcCam from the Pixel 3 (Pixel3Mod) with the latest low light enhancement features from the new photo core. I'd love to know how you got it working on the Mi Max 2 on Oreo.
None of the ones on this list work for me so far:
https://www.celsoazevedo.com/files/android/google-camera/
And that's literally all of them as far as I know, including highly specialised device variants. As far as I'm aware it's Pie only.
cem_uar said:
not
finger print,
double click open the screen
not blutouth
not xposed
Click to expand...
Click to collapse
What can you expect from an alpha build .lol. isn't it enough you got pie.
scissordragonboy said:
What can you expect from an alpha build .lol. isn't it enough you got pie.
Click to expand...
Click to collapse
Is camera working on pie?
reversegear said:
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Click to expand...
Click to collapse
If you want to handle this Pie project you can compile from source.
My trees are open on GitHub.
Downloading. Is there a problem with IMEI?
Hucksley said:
Downloading. Is there a problem with IMEI?
Click to expand...
Click to collapse
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
Camera? Totally not working?
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
I'm already using rom and I want to thank you for your great work.
I will use it until the next updates come out and I will notify any unknown bug so far.
Thanks again for the work!
(Sorry for the English)
hard to download
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.