Related
Thats my first productive creation for XDA, so dont be to hard to me
I don't like to have features, which I never use, so I always disable or remove everythink i dont need.
On my custom roms I always diable the multi user mode by adding the following line to the build.prop:
Code:
fw.max_users=1
I was annoyed to edit this file after each ROM update.
So I created this module. It just adds the above mentioned line to the build.prop.
It is really simple, but now I don't need to edit the build.prop.
Maybe for someone this can be useful.
It works with:
- Android 6.x (Tested on OnePlus X and OnePlus 3 with CM13)
- Android 7.x (Tested on LOS 14.1 and OxygenOS 4.5.x)
v1.3: Update to Magisk Template 1400 (14.0).
Looks good but I would change the modid to something other than template. This is in the config.sh file and defines the folder it uses under /magisk. Anyways I used your zip as a template for my own build.prop edits that I will post shortly. I'll throw a little credit your way too.
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
dima-82 said:
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
FHC1998 said:
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
Click to expand...
Click to collapse
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
dima-82 said:
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
Click to expand...
Click to collapse
It depends on the device, I originally tested on a few, and some needed this line.
For instance, I tested your module on my device (ZenFone 2 laser) and it worked perfectly without the line, but on my friend's ZenFone 2 it kept showing the UI even though not allowing creating more users.
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
mp3deviant721 said:
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
dima-82 said:
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
Click to expand...
Click to collapse
The build I'm running is 7.1.1. Haven't tried 7.1.2 yet. Yes on the "nightly" build.
Sent from my ONEPLUS A3000 using Tapatalk
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Here is the module on my device :silly:
dariomrk said:
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Click to expand...
Click to collapse
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
dima-82 said:
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
Click to expand...
Click to collapse
Oh, I didn't see that, I will check if it does the exactly same thing (probably yes)...
---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------
Just checked it out, and yes it does the exactly same thing
Please I need multiuser enable magisk module for Android 6
dima-82 said:
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
Here
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
dima-82 said:
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
Click to expand...
Click to collapse
Yes have other 5 modules
You installed / activated only this very one module and got a bootloop?
Before I created this module I edited the build.prop manually. And if you make a mistake there, you will get a bootloop as well.
May be your OS does not support this property.
I tested on my devices only, and it worked always.
Eventually you can try an other module from @FHC1998, which should do the same:
https://forum.xda-developers.com/showpost.php?p=71936097&postcount=3
jhobc said:
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
Click to expand...
Click to collapse
You could eventually try this mod:
https://forum.xda-developers.com/apps/magisk/module-single-user-mod-t3639486#post73160966 by @seebz
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.
This module patches OPLongshot's code so that it produces PNG screenshots, as it should, instead of JPEG screenshots (ew!). It patches only the VDEX/ODEX files, which have no signature on them — only the APK is signed, which we do not modify, so OPLongshot still retains system signature privileges. The original APK is included to avoid version mismatches (although I don't think there will be much issue even if it isn't includd).
Note that the OPLongshot was taken from the OnePlus 5T's system image. YMMV for other devices on OxygenOS (or even HydrogenOS?).
The current version uses the version of OPLongshot from OnePlus 5T OxygenOS 5.1.0/5.1.1 (same), with version 1.1.0.180328153957.6a699c8.
Remember to clear Dalvik/ART cache after installing this.
GitHub repository (also details of how the patch is done).
Download zip (temporary until the Magisk repo bot refreshes)
any plan for OP5?
h20ray said:
any plan for OP5?
Click to expand...
Click to collapse
Could you upload the APK and odex/vdex files?
Are you going to port it to OnePlus 3/3T devices?
Does it works with the OP5 ?
angelsel said:
Could you upload the APK and odex/vdex files?
Click to expand...
Click to collapse
I've attached the latest the OPLongshot folder (taken from the latest OB14 for the OP5 and zipped). Looking forward to the modifications for this version as well for the OP5, whenever you get the time. Thank you!
shadowstep said:
I've attached the latest the OPLongshot folder (taken from the latest OB14 for the OP5 and zipped). Looking forward to the modifications for this version as well for the OP5, whenever you get the time. Thank you!
Click to expand...
Click to collapse
Do you plan to compile from OB15?
V5 doesn't work on the last OB 14(5T)
Nemo Aeternam said:
V5 doesn't work on the last OB 14(5T)
Click to expand...
Click to collapse
Same here
We will no longer update this great module
We? Hope for an update! jpg must die..
Sent with much love & Android. OnePlus 5T
Would be great to see an update, no longer works on Pie for OP6.
This was meant for the OnePlus 5T stable builds only (as the title states); I don't use the beta builds, nor do I own a OnePlus 6. That the modified vdex even worked on the beta builds and non-5T builds was not intentional.
Someone else can follow the method I have detailed to create modules for the OnePlus 6 and the 5T open betas.
The current version works on OxygenOS 5.1.5 for OnePlus 5T (the APK did not change from 5.1.4 to 5.1.5).
angelsel said:
This was meant for the OnePlus 5T stable builds only (as the title states); I don't use the beta builds, nor do I own a OnePlus 6. That the modified vdex even worked on the beta builds and non-5T builds was not intentional.
Someone else can follow the method I have detailed to create modules for the OnePlus 6 and the 5T open betas.
The current version works on OxygenOS 5.1.5 for OnePlus 5T (the APK did not change from 5.1.4 to 5.1.5).
Click to expand...
Click to collapse
About vdex2dex, did you use it with the entire AOSP tree or do you have a standalone version with dependencies?
If you do have a standalone version (which I couldn't find) can you provide it?
tanish2k09 said:
About vdex2dex, did you use it with the entire AOSP tree or do you have a standalone version with dependencies?
If you do have a standalone version (which I couldn't find) can you provide it?
Click to expand...
Click to collapse
I used it with the entire AOSP tree. Sorry.
Can i just use it in Oneplus 3??
Sent from my OnePlus3 using XDA Labs
Is there any timeframe on when Pie support for this module will be implemented? It worked fine for me in the previous beta version, and now I can only take screenshots with the module disabled since I updated my OP5T today.
zland said:
Is there any timeframe on when Pie support for this module will be implemented? It worked fine for me in the previous beta version, and now I can only take screenshots with the module disabled since I updated my OP5T today.
Click to expand...
Click to collapse
Yes, we need this mod. Sadly I can't do it myself.. but maybe I can help you out with the needed files, OP?
OP Longshot seem to still be at ver. 1.1.0...
but there is a new folder inside the path of OP Longshot called "lib". Inside that folder is a folder called arm64, and inside arm64 are two files calling "libencryptjni.so" and "op_encrypt.so" maybe these are the reasons the old magisk module won't work? i don't know for sure, but i know that these folders and files aren't present in the magisk module.
I would buy you a beer OP, for updating this mod. :good:
moeq123 said:
Yes, we need this mod. Sadly I can't do it myself.. but maybe I can help you out with the needed files, OP?
OP Longshot seem to still be at ver. 1.1.0...
but there is a new folder inside the path of OP Longshot called "lib". Inside that folder is a folder called arm64, and inside arm64 are two files calling "libencryptjni.so" and "op_encrypt.so" maybe these are the reasons the old magisk module won't work? i don't know for sure, but i know that these folders and files aren't present in the magisk module.
I would buy you a beer OP, for updating this mod. :good:
Click to expand...
Click to collapse
I followed the instructions as mentioned in the GitHub readme, and I ended up successfully getting a modified version.
Sadly though, it doesn't seem to work on android P
I have updated the module, based on OOS OB20 (OP5T) but should also work for OB22 (OP5). Cheers.
Google Dialer v37 & Contacts v3.7.7 on Stock ROMs (any ROM really) August 1st, 2019
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
Link to the thread in V20's apps section HERE
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
as always, my latest updates and newest files can be found in this shared Google Drive folder
This link has been changed, the correct one is above. I had (wanted) to move this project to a separate dedicated account that was not so personal. Reshare the folder to yourself using Google Drive and/or update your bookmark.
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-(arm64)-33.0.247985459-publicbeta-3998624.apk
Contacts-com.google.android.contacts-3.5.51.247103087-2209215.apk
OLD Changelog:
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
- updated all the framework files to match the ones in the latest release from opengapps
- removed LGInCallUI app as it is not completely necessary in this particular project
arm64 zips
Phone-com.google.android.dialer-37.0.260231449-publicbeta-4339080.apk
Contacts-com.google.android.contacts-3.7.7.260733580-2243311.apk
April 25th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785841.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209036.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785840.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209035.apk
All files can be found and downloaded from my shared Google folder (above) or attached to this post (below).
March 27th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta-3785464.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
February 22nd, 2019
- updated both apps to latest version of each as supplied by Google. App versions are below...
arm64 zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570857.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570850.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
questions or comments? leave a reply here and I will see it. I don't visit here often but I should get back to you either immediately or within 2-3 weeks.
~syndre
- I don't think it's necessary, but by request (and to avoid confusion) I have made a Android 9.0+ PIE compatible flashable zip to install just the dialer's framework.
January 22nd, 2019
- Updated apks to latest versions from Google
Phone-com.google.android.dialer-28.0.229824408-publicbeta-3464836.apk
Contacts-com.google.android.contacts-3.3.3.226019458-2171201.apk
-I uninstalled any updates to the phone and contacts app I had installed, and flashed the non-magisk version on to my V30+, both apps are working fine.
-I copied those files into the magisk template I've been using and zipped that to create a magisk installable version. I have not tested this one but I assume it will work for those who use it.
- expect arm versions within the next week.
downloads are attached below, to this post.
December 20th, 2018
I am still not sure why it was happening, but the Phone app started randomly force closing on me a few days ago. I do a lot of playing around with mods and stuff so it could just be me. I have updated and tested both of the zips being released today, and the app is working again for me. I use a stock Oreo LG ROM. Everyone who hasn't had this issue or if you're on another device or on AOSP, ignore this paragraph. Theres a few files different in here from the previous version, so please flash this update so I know we're all on the same page. ty
- Updated dialer to latest apk from Google: v27.0.225573798-publicbeta-3347328.apk
- Updated/changed a couple framework related files to get the app to stop force closing on my device.
- arm (32) versions made and posted, too. Make sure you use the correct zip for your device!
New files can be found attached onto this post below and/or in the drive folder linked to above.
November 26th, 2018
updated phone to today's release from google
These are a little different from the previous (Nov 26) version, if you experience any issues at all please let me know!
attached below, and also available HERE
November 26th, 2018
updated arm64 apk's
arm update soon
flashable zips are attached below
November 15th, 2018
seems like they always put one out after I post... v26 is supposed to officially have dark mode in the dialer app (now both phone and contacts).
attached below
November 13th, 2018
my last post in this thread
Updated APK's to versions:
Phone-com.google.android.dialer-25.0.220310144-3118535.apk
Contacts-com.google.android.contacts-3.2.4.220343473-2161331.apk
both regular and magisk flashable zips are attached to this OP.
You can also find everything related to this project here in this shared drive folder.
New Favorites Section and Dark Mode on display in this Screenshot Album...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above is still not Google official, but easy to manipulate. See thread started by @JonnyTrulove HERE!
October 27th, 2018
Updated arm64 APKs to Google's newest version of each, both released today:
Phone-com.google.android.dialer-25.0.218361296-3118167.apk
Contacts-com.google.android.contacts-3.1.6.218196352-2149637.apk
I'll upload zips with version 25 for arm devices soon. I'm literally on my phone, typing this from a pitch dark cabin in the woods in the Midwest U.S. with someone sleeping a foot away from me.
Download arm64 zip to flash directly to system, also attached below OP
Download arm64 zip packaged as a magisk module, instead, also attached below OP
LINK CHANGED/UPDATED
Link to my NEW shared drive folder.
October 8th, 2018
arm64 versions with new contacts v3.1.3 update
arm64 version with new contacts v3.1.3 update -Magisk Module
I built these and edited this top post totally on mobile, I hope it works..
I'll fix[/IMG] the rest later
it has just come to my attention that some people (on other devices) are having problems because I never switched over to the 2018 dialer framework in these zips. Both versions have always been there, I just had it named in such a way that the 7.0 version wax being used.
I have changed it over to the newer Oreo 8.0 framework, and will use that from today onwards.
Any issues because of this on LG phones? Please leave a response about it.
download 8.0 framework below, or here
October 3rd, 2018
Updated all apk's involved, and put together an arm version so I could use it on my older arm devices.
arm64 version for V30 and newer phones, magisk'd
arm64 version that writes directly to /system partition
arm version for your older phones , magisk'd
arm version that writes directly to /system partition
I have also attached the same 4 zips to this top post. They must have raised the file size limit recently or something ¯\_(ツ)_/¯
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
unattached file DL count -
arm64:3640 | arm64-magisk: 1332 | arm:398 | arm-magisk: 436
syndre said:
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Link to the thread in V20's apps section HERE
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
Thanks
Click to expand...
Click to collapse
You don't need to move contacts to the system. Just the phone app.
TotallyAnxious said:
You don't need to move contacts to the system. Just the phone app.
Click to expand...
Click to collapse
Ok, and?
I like it in /system, where it won't get accidentally removed.
I assume since you took the time to comment that you think its better installed as a user app for some reason.. I'm curious now, what is/are those reasons?
Putting apps like that on the system partition makes no difference in functionality, and saves space it would otherwise be taking up on /data...
Your stock contacts app comes out of the box on /system, most if not all gapps packages put contacts onto /system.
There are many, many apps that will work on either system or installed as a user app.
I put it there because I like it there. phone and contacts in my installer come together as one package. There's no reason to not keep it simple and put both apps in the same destination.
Thanks for commenting, I guess... but I don't know why you are telling me something I'm well aware of.
Once you have the framework and permission files on the system partition for the phone app, you can sideload that APK too onto /data, if that's what you prefer.
I don't plan on changing anything, and look forward to later in the day when I'll hopefully forget about being confused about why you needed to mention this, especially with zero context.
Sent from my LGE V30+ using XDA Labs
I used this on my phone - I previously had Contacts from the Play Store and a modified copy of Phone from Martin.077 (I was using version 20). Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me with a retail US998+ on Verizon, and this is mostly stock firmware. I say mostly stock because I have the Verizon modem flashed - signal strength at my home doesn't seem as good with the V30 as it was with my Droid Turbo, so I've been experimenting.
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
tagor said:
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
Click to expand...
Click to collapse
Installing any of my zips from this thread will not do anything to your stock dialer app (as far as I know).
You will have to go into the phone settings and switch which one you want set as the default.
To use stuff in the google one, you must set google phone as default.
If you ever need to update your PRL or anything like that, you will have to switch it back to the LG contacts app, or else the dialer "secret codes" wont do anything.
I should have mentioned that in the OP..
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
hitokage004 said:
Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me
Click to expand...
Click to collapse
Replying to myself to indicate this apparently isn't correct (based on info from another thread). I didn't know when people referred to visual voicemail, they were referring to the text transcription stuff. I have a Google voice number that isn't really used, but I've seen the transcriptions on the website from people who misdialed and left a message - I wasn't particularly impressed and had to listen anyway.
It was mentioned that there is configuration files that will make it work though, so what I said is partly correct - as the voicemail tab shows in the Google dialer when using this version. The modified version I used before didn't have that tab.
EDIT - See below.
ChazzMatt said:
Visual Voicemail is not transcription. Visual Voicemail is merely a list of voice messages so you can pick and choose the order you wish to listen or even delete without listening. It MAY also include voicemail-to-text transcription, but that is not the purpose of the visual voicemail definition. Early visual voicemail applications (from when the name came) did not have voicemail-to-text transcription and was called that because you could SEE the list of messages on a video interface.
https://www.lifewire.com/what-is-visual-voicemail-3426762
https://en.wikipedia.org/wiki/Visual_voicemail
__________
If they were referring only to voicemail-to-text transcription, they are wrong. That can be INCLUDED in a "Visual Voicemail" service, but is not what visual voicemail means.
Google Voice does have "visual voicemail" (list of messages on the website) as well as having voicemail-to-text transcription (website, text, and email). Both my wife and I have Google Voice numbers and I appreciate both the text and email transcriptions I receive.
Click to expand...
Click to collapse
:good:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
saxena1 said:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
Click to expand...
Click to collapse
thats fine just please don't forget to mention where you got it from
syndre said:
thats fine just please don't forget to mention where you got it from
Click to expand...
Click to collapse
Already mentioned you name
please update your post regularly ?
saxena1 said:
Already mentioned you name
please update your post regularly
Click to expand...
Click to collapse
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
syndre said:
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
Click to expand...
Click to collapse
How do I get VM to show up in the Google dialer?
I have my stock T-Mobile VM app installed.
Sent from my LG-H932 using XDA Labs
Contacts installed fine, but not the dialer. I get "App not installed". Anyone know how to fix this?
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
nobdow said:
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
Click to expand...
Click to collapse
This doesnt need root or TWRP. Just download and run the apk.
You don't need root? I've got no where to put the zips (but I don't have root)
The APK for contacts installs but phone does not install on my v30 h933 - the package installer sometimes doesn't even give an error and other times it just says "not installed".
I can't get the apk to install either.
Sent from my LG-H931 using Tapatalk
Yeah, can't get it to stick on a stock 932.
You can use this without root, but the bootloader must be unlocked and TWRP installed. Unlocking the bootloader and installing TWRP doesn't require you to install a root app like Magisk.
For those who want to use the Google Dialer (aka Phone) without unlocking the bootloader - I used Martin.077's patched copy previously. With that version though, you'll have to wait for them to update it - it can't use the updates from Google in the Play Store. Google Contacts will install and update from the Google Play Store without any modifications.
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.