changing selinux to permissive - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

any help is appreciated:
hello xda, am currently on Quantum 3.56 . att i747., would like to change selinux to permissive. have tried wanam xposed module and selinuxmodechanger app. no luck witb either.
any advice/direction ?
thanks again.
err on the side of kindness

Afaik, selinux has to be disabled in the kernel. Also afaik, no ones been able to do this on aosp/cm based kernels. Only on the TW ones. Not familiar with the AT&T roms though, so not sure about Quantum. Im assuming aosp? There used to be a command you could enter via terminal or init.d, but this doesnt work anymore from what ive heard.

thank you for info. :thumbup:
err on the side of kindness

Related

cyanogenmod, do I need to rebuild the kernel for modules support?

OK guys, Im not a linux-n00b, but am an android n00b. I flashed the cyanogenmod ROM onto my nexus 7 2013, built some kernel modules for it, but insmod'ing it says that function isnt implemented. lsmod says /proc/modules is non-existent. What gives? I thought these custom ROMs came with kernel module support. I downloaded the CM kernel source and their default config has a bunch of features and modules that I don't have after flashing the ROM onto my tablet.
Do I need to re-build the kernel to get all these features? Or did I miss a step and forget to flash on the rest of the stuff.... Thanks...
mikecc said:
OK guys, Im not a linux-n00b, but am an android n00b. I flashed the cyanogenmod ROM onto my nexus 7 2013, built some kernel modules for it, but insmod'ing it says that function isnt implemented. lsmod says /proc/modules is non-existent. What gives? I thought these custom ROMs came with kernel module support. I downloaded the CM kernel source and their default config has a bunch of features and modules that I don't have after flashing the ROM onto my tablet.
Do I need to re-build the kernel to get all these features? Or did I miss a step and forget to flash on the rest of the stuff.... Thanks...
Click to expand...
Click to collapse
What are you trying to add?
And yes you are going to have to rebuild the kernel with the modules you want to add/implement.
Depending on what you are trying to add, my bet is that there is already a kernel out there that has what you are looking for. Start looking at other kernels. I would definitely look into the ElementalX kernel.
-droidshadow

[Q] stock kitkat kernel with selinux permissive?

looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: kind @xluco has built a kernel just for us:
http://forum.xda-developers.com/show....php?t=2756679
ionflux said:
looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: for p600. thanks!
Click to expand...
Click to collapse
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.
injola said:
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.
Click to expand...
Click to collapse
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful
ionflux said:
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful
Click to expand...
Click to collapse
I was trying to edit my last post because I saw that you have tried that kernel.
I have spent way more time compiling kernels over the past 20 years than I care to, which is one reason I haven't tried this task yet. I flashed the pre-kitkat selinux permissive kernel a while back and it simply wouldn't boot. I had saved the stock kernel with online nandroid backup. I reflashed stock kernel and there was no problem. I guess, the same would happen with an any unbootable kernel. I never have built an android kernel though.
Here you go guys, try this.. Stock KitKat kernel with SELinux in permissive mode and Knox removed: d-h.st/uCX
EDIT: slight update with NTFS support / HTCP and Multi-core scheduler support.. all completely stable as they're already in the kernel just not selected
EDIT 2: http://d-h.st/ziH - V3 [19/05/2014] (fixes a small derp in ramdisk)
http://forum.xda-developers.com/showthread.php?t=2756679
Any chance of a p605 kernel with SElinux enabled?
patchseven said:
Any chance of a p605 kernel with SElinux enabled?
Click to expand...
Click to collapse
samsungs opensource website is so slow, it would literally be about 5 hours of download time to get the source, I can do it but it'd be next week now
Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.
patchseven said:
Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.
Click to expand...
Click to collapse
Check the thread over in original development if you haven't already, p605 for jellybean just added

[DEV] AOSP-Based ROM Development Thread

Since joshuabg posted his build of AICP, countless other people decided they would continue his mission of bringing AOSP-based custom roms to this wonderful device
however in doing this people started stealing the AICP thread to talk about compile problems(i know im the biggest offender) so im fixing that.
Post all ROM development talk below so we can attempt to help each other and get the rom problems out of the way and finally get development for this amazing, game-changing, sexy slice android off the ground
Hey guys, if anyone is looking for how to build a rom for the nexus 9(and theyre forced to use a prebuilt kernel) i wrote up a tutorial on how to do that at the top of page 5:
http://forum.xda-developers.com/nex...evelopment-thread-t2995510/page5#post58089268
Based on my convo with Josh, he indicated that disabling SELinux in the prebuilt kernel (with help from USBHost) would assist in allowing the build to boot. However, I honestly do not want to disable SELinux AT ALL. I will find a way to make this work without disabling SELinux.
The issues I had with getting the AICP to boot without a Setup Wizard has stopped loop was 100% to blame on SELinux. ROM was disabled kernel was enforcing, and they didn't want to play nicely together. As soon as I used a kernel with SELinux disabled, it booted right up no problems. Should someone maybe ask flar2 with a mention in here to get his two cents?
SwoRNLeaDejZ said:
The issues I had with getting the AICP to boot without a Setup Wizard has stopped loop was 100% to blame on SELinux. ROM was disabled kernel was enforcing, and they didn't want to play nicely together. As soon as I used a kernel with SELinux disabled, it booted right up no problems. Should someone maybe ask flar2 with a mention in here to get his two cents?
Click to expand...
Click to collapse
i dont think thats right...i could be doing something wrong, but im fairly certain that when i compiled by build i set both the ROM and Kernel to SElinux disabled(or at least enforcing) and the kernel wouldnt even try to boot...
however, i do have to say that im not 100% certain how to disable SElinux in the ROM so i did what i thought would work, so maybe thats why mine doesnt boot...once i figure out compiling this kernel and either praise you or stand by my point
also i havent heard anything of flar2 since november 24th so idk what happened there
zawata said:
i dont think thats right...i could be doing something wrong, but im fairly certain that when i compiled by build i set both the ROM and Kernel to SElinux disabled(or at least enforcing) and the kernel wouldnt even try to boot...
however, i do have to say that im not 100% certain how to disable SElinux in the ROM so i did what i thought would work, so maybe thats why mine doesnt boot...once i figure out compiling this kernel and either praise you or stand by my point
also i havent heard anything of flar2 since november 24th so idk what happened there
Click to expand...
Click to collapse
You could very well be right. All I was speaking from was my experience of every kernel I tried using that didn't have SELinux disabled, the build wouldn't boot.
SwoRNLeaDejZ said:
You could very well be right. All I was speaking from was my experience of every kernel I tried using that didn't have SELinux disabled, the build wouldn't boot.
Click to expand...
Click to collapse
what do you mean by not boot? like exacty? because for me, a kernel not booting means stuck at the google splash screen
The ROM does not control selinux
Only the kernel controls it
Well guys, i finally got CM to build without breaking a few days ago but the kernel didnt work so i did a bunch of testing a research and i think ive concluded that theres something wrong with the build process that breaks the kernels, once i figure out what, we'll have the reliable build system that doesnt rely on prebuilt kernels
on a side note i figured out how to build AOSP with prebuilt kernels
SO we finally have a CM build that can stand on its own and run well(shockingly well, i havent found any problems) and it doesnt rely on USBhost's feature-rich kernel or his prebuilt one that no-one really understands...lol no offense intended usbhost, FIK is pretty damn good
@SwoRNLeaDejZ : selinux is currently disabled so im going to see what happens when i renable it @USBhost : is SElinux disabled the same thing as permisive? im guessing no and which one would be the best to set for a custom rom. im guessing permissive?
zawata said:
Well guys, i finally got CM to build without breaking a few days ago but the kernel didnt work so i did a bunch of testing a research and i think ive concluded that theres something wrong with the build process that breaks the kernels, once i figure out what, we'll have the reliable build system that doesnt rely on prebuilt kernels
on a side note i figured out how to build AOSP with prebuilt kernels
SO we finally have a CM build that can stand on its own and run well(shockingly well, i havent found any problems) and it doesnt rely on USBhost's feature-rich kernel or his prebuilt one that no-one really understands...lol no offense intended usbhost, FIK is pretty damn good
@SwoRNLeaDejZ : selinux is currently disabled so im going to see what happens when i renable it @USBhost : is SElinux disabled the same thing as permisive? im guessing no and which one would be the best to set for a custom rom. im guessing permissive?
Click to expand...
Click to collapse
I built a stock kernel that's so awesome that no one can comprehend or understand it
Haha aren't I awesome lol
About selinux if its disabled
It means it was not compiled with the kernel
so you can't simply enable it
I would recommend permissive on the kernel command line
So it would be easier to debug what is preventing stock kernel from not booting
Because you can see what would have selinux prevented from running
on /proc/kmsg or /dev/kmsg
USBhost said:
I built a stock kernel that's so awesome that no one can comprehend or understand it
Haha aren't I awesome lol
About selinux if its disabled
It means it was not compiled with the kernel
so you can't simply enable it
I would recommend permissive on the kernel command line
So it would be easier to debug what is preventing stock kernel from not booting
Because you can see what would have selinux prevented from running
on /proc/kmsg or /dev/kmsg
Click to expand...
Click to collapse
haha well no one could figure out how to use it(but i did I FIGURED YOU OUT!! YOUR A PHONY!!) jokes aside though
so setting permissive in the boardconfig.mk? :
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
then make menuconfig and re-enable the options you told me to disable in tha PM(i dont fee like typing them out lol)
zawata said:
haha well no one could figure out how to use it(but i did I FIGURED YOU OUT!! YOUR A PHONY!!) jokes aside though
so setting permissive in the boardconfig.mk? :
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
then make menuconfig and re-enable the options you told me to disable in tha PM(i dont fee like typing them out lol)
Click to expand...
Click to collapse
Yep that should do it
If not tell me
USBhost said:
Yep that should do it
If not tell me
Click to expand...
Click to collapse
currently building the boot image(btw im using your flashable zip as a base thanks )
will report back
EDIT: hmm nope it didnt seem to work, i think it might have been my fault ill tryt it again
USBhost said:
Yep that should do it
If not tell me
Click to expand...
Click to collapse
im not sure if its me being stupid or something else but i cant reenable SElinux
im thinking its because i dont know if im specifying the right config file...im not 100%
maybe you could just give me a kernel binary with selinux reenabled but not tonight, i should really get to sleep lol
zawata said:
im not sure if its me being stupid or something else but i cant reenable SElinux
im thinking its because i dont know if im specifying the right config file...im not 100%
maybe you could just give me a kernel binary with selinux reenabled but not tonight, i should really get to sleep lol
Click to expand...
Click to collapse
Lol will do
CM compiles fine for me with prebuilt kernel and a few minor source changes. I have a zip from 1/6/15 if anybody will like to test (I really don't feel like wiping right now lol)
Sent from my SCH-I545 using Tapatalk
joshuabg said:
CM compiles fine for me with prebuilt kernel and a few minor source changes. I have a zip from 1/6/15 if anybody will like to test (I really don't feel like wiping right now lol)
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yeah what im trying to do now is get it to compile now straight from source(figure out why it wont) and also prepare the kernel for build teams to want to take it
i actually have CM(built on the 5th) and my kernel(no changes but selinux disabled(working on it)) running on my tablet right now and im shocked by how smooth it is! its amazing!
zawata said:
yeah what im trying to do now is get it to compile now straight from source(figure out why it wont) and also prepare the kernel for build teams to want to take it
i actually have CM(built on the 5th) and my kernel(no changes but selinux disabled(working on it)) running on my tablet right now and im shocked by how smooth it is! its amazing!
Click to expand...
Click to collapse
CM android_build currently does not support arm64 kernels
Sent from my SCH-I545 using Tapatalk
Just throwing this out there, but if anyone comes up with any type of test builds, or test kernels, that they need someone to flash and try out, let me know. Always more than willing to give some experimental builds a test drive.
joshuabg said:
CM android_build currently does not support arm64 kernels
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I know, which is why I'm going to *hackily implement it*(until Steve finishes his implementation) or cherry pick his attempt and see if I can get it too work
I just got off work(I hate training!!!) And I'll see what I can do about it
I will not deny that anything the CM team will cook up, will be miles better than what I can make but I'm just trying to make it build for a single device, not all of the devices it a super efficient manner
Actually I think I might start some unnoficial nightlies for CM if people want, once I finish my build script then I shouldnt have very much difficulty making it each night
SwoRNLeaDejZ said:
Just throwing this out there, but if anyone comes up with any type of test builds, or test kernels, that they need someone to flash and try out, let me know. Always more than willing to give some experimental builds a test drive.
Click to expand...
Click to collapse
lol bold offer, you're so brave, unlucky for you though, this is a nexus device so if know it boots then we pretty much know everything works so the beta testing isnt as necessary as say on a samsung/htc/lg device,
however, ill see if i can find something i need testing
EDIT: device is now selinux status: permissive(apparently i still dont know how to build kernels...lol but i figured it out)
zawata said:
Yeah I know, which is why I'm going to *hackily implement it*(until Steve finishes his implementation) or cherry pick his attempt and see if I can get it too work
I just got off work(I hate training!!!) And I'll see what I can do about it
I will not deny that anything the CM team will cook up, will be miles better than what I can make but I'm just trying to make it build for a single device, not all of the devices it a super efficient manner
Actually I think I might start some unnoficial nightlies for CM if people want, once I finish my build script then I shouldnt have very much difficulty making it each night
lol bold offer, you're so brave, unlucky for you though, this is a nexus device so if know it boots then we pretty much know everything works so the beta testing isnt as necessary as say on a samsung/htc/lg device,
however, ill see if i can find something i need testing
EDIT: device is now selinux status: permissive(apparently i still dont know how to build kernels...lol but i figured it out)
Click to expand...
Click to collapse
Love the unofficial nightlies idea

switch selinuxmode to permissive?

Hey guys i have a little question. How can i switch to selinux permissive mode? I ask because of the xposed framework. Selinuxchanger app works but is too slow for xposed. Xposed recognizes the enforcing mode... Init.d doesnt work too.My device is lgg3 and i run the actual darkobas build with Johns 777 kernel. Is there another way? Which files i have to change?
Thanks!

[ROM][6.0.1] ☼ 63% Stock ☼ ╟DeoDexed╫Rooted╫DeBloated╢ ► PD1 ◄ 7/15/16

[ROM][6.0.1] ☼ 63% Stock ☼ ╟DeoDexed╫Rooted╫DeBloated╢ ► PD1 ◄ 7/15/16
63% Stockish Rom​Custom Rom for Marshmallow 6.0.1 G925TTMB3EPD1​T-Mobile Samsung Galaxy S6 Edge​★Now Includes Custom Kernel★​
Introduction
This is a stock rom created from the newly released MM firmware for the SM-G925T. I've made the rom using SuperR.'s kitchen. After I upgraded my phone to marshmallow I was excited to get a custom rom up and running.
Unfortunately there weren't many available that would retain wifi calling, so I decided to make one myself. This is the product of many headaches and long nights... hope you like it!​
Announcement
Version 3 has just been released! I have fixed the screenshot crashing error as well as added a reboot to recovery option and disabled the unsafe volume warning. I figured these mods would be OK to add without going beyond the stock look and feel. I found these to be two features that I couldn't live without on any rom. At this point I am going to mark the rom as Stable since I believe I have fixed almost all the issues that were present. If anyone finds anything that needs to be fixed or changed, please let me know so I can start compiling a list for version 4.​
Changelog
Version 3
* Fixed screenshot crashing issue
* Added Reboot Recovery option in the power menu
* Removed unsafe volume warning
Version 2
* Custom kernel set to permissive mode Source Code
* Removal of SecurityLogAgent under system/app
Version 1
* Initial Release
​
Features
*Rooted
*BusyBox
*Debloated
*ZipAligned
*Deodexed - oat2dex
*Init.d Support Added
*T-Mobile WiFi Calling
*Custom Stock Kernel - Permissive
* List of Debloated Apps *
system/app
AllShareCastPlayer
AllshareFileShare
AllshareFileShareClient
AllshareFileShareServer
AllshareMediaShare
AmazonShopping_TMO
AntHalService
ANTPlusPlugins
ANTPlusTest
ANTRadioService
ap_PaymentFramework_spay_tb_production_release_2.0.6
Books
ChocoEUKor
Chrome
ChromeCustomizations
com.mobitv.client.tmobiletvhd
CoolEUKor
Drive
Facebook_stub
FBAppManager
FlipboardBriefing
GalaxyAppsWidget_Phone
GearManagerStub
Gmail2
Hangouts
Kies
KnoxAppsUpdateAgent
KnoxAttestationAgent
KnoxFolderContainer
KnoxSetupWizardClient
KnoxSwitcher
Maps
MSSkype_stub
Music2
Newsstand
OneDrive_Samsung_v2
OneNote_Compact_Samsung
PlayGames
PlusOne
RCPComponents
RoseEUKor
SamsungAccessoryService
SapaAudioConnectionService
SapaMonitor
SecurityLogAgent
SmartcardService
SmartRemote_zero
SysScope
UniversalMDMClient
Videos
Vvm_TMO
YouTube
system/container
ContainerAgent2
KnoxBBCProvider
KnoxBluetooth
KnoxKeyguard
KnoxShortcuts
KnoxTrustAgent
resources
SharedDeviceKeyguard
system/etc
secure_storage
recovery-resources.dat
system/lost+found
system/preloadedmdm
kioskdefault
MyKNOXManager
system/priv-app
AccessTmobile_TMO
AdeptClient
EasyLauncher2_Zero
Excel_SamsungStub
FBInstaller
GalaxyApps_3xh_zero
GearManager
HancomOfficeEditor
KLMSAgent
Lookout_TMO
MILK_US
PhoneErrService
PowerPoint_SamsungStub
RNB
RNBShell
SAMSUNG_PLUS
SamsungPayStub
sCloudBackupAppMOSUpgrade
SCloudService
SendHelpMessage
SHealth4
SimLock_TMO
SmartcardManager
TmoVVM
VRSetupWizardStub
WhitePagesNameId-release_TMO
Word_Samsungstub
​
Download
ROM
►Download◄​
Installation
Download the stock rom from Here. After downloading, flash this using ODIN.
Install the custom recovery TWRP (or whichever you prefer) found Here.
Boot into TWRP, perform a factory reset, then install the rom.
All done!​​
Known Issues
It seems the kernel I made is not creating an adbkey on the device. This will cause issues when using problems that require this such as DroidExplorer, PDANet, etc... I am currently looking into this and will release a version 2 of the kernel and include it in the rom. For now I would suggest using The Sickness's kernel for the S6 Edge found here: http://forum.xda-developers.com/tmobile-galaxy-s6/orig-development/kernels-twisted-kernel-6-0-1-mm-5-11-16-t3377283.​​
Thanks To/Credits
SuperR. - for making a great kitchen!
stangdriver44 - for information and motivation
The Sickness - for guidance and letting me use his work :good:
mjdavis871 - for suggestions, information, and testing
SidRobo - for providing an excellent tutorial for adding reboot to recovery
Edgarf28 - for providing great references :victory:​
XDA:DevDB Information
63% Stock, ROM for the T-Mobile Samsung Galaxy S6 Edge
Contributors
Mortifix
Source Code: https://github.com/Mortifix/SM-G920T
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2016-07-15
Current Beta Version: 2
Beta Release Date: 2016-05-13
Created 2016-04-23
Last Updated 2017-03-06
Reserved
Thanks
Thank. Will check it out.
Is the kernel in this rom permissive?
mjdavis871 said:
Is the kernel in this rom permissive?
Click to expand...
Click to collapse
Enforcing, I guess it would be better to put it in permissive mode instead. I'll change this when I get home tonight.
Mortifix said:
Enforcing, I guess it would be better to put it in permissive mode instead. I'll change this when I get home tonight.
Click to expand...
Click to collapse
That would be awesome....some root apps don't work correctly unless it's permissive.
Sent from my SM-G925T using Tapatalk
Im down to try this sounds great
1. Did you chabge the kernal to permissive?
2. Does video calling work?
The Illest said:
Im down to try this sounds great
1. Did you chabge the kernal to permissive?
2. Does video calling work?
Click to expand...
Click to collapse
It looks like I removed Video Calling but I have added it back. I am also working on setting the kernel to permissive. I will upload the new rom after I've made these changes.
Well I'm having some issues with setting the stock kernel to permissive mode. I may just wait until @arter97 updates his kernel to support W8/T roms and include that instead of the stock kernel until I can learn more about how to edit/build a kernel. I am going to re-upload the the rom with Video Calling fixed and a few other apps left in with the selinux still set to enforcing. I don't think this will be such a bad thing though since the only app I really see that requires permissive is Viper4Audio. From what I've read, I think xposed should still work with enforcing.
Mortifix said:
Well I'm having some issues with setting the stock kernel to permissive mode. I may just wait until @arter97 updates his kernel to support W8/T roms and include that instead of the stock kernel until I can learn more about how to edit/build a kernel. I am going to re-upload the the rom with Video Calling fixed and a few other apps left in with the selinux still set to enforcing. I don't think this will be such a bad thing though since the only app I really see that requires permissive is Viper4Audio. From what I've read, I think xposed should still work with enforcing.
Click to expand...
Click to collapse
Thanks for your efforts, hopefully arter will sort it out for our devices soon.
Sent from my SM-G925T using Tapatalk
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Oh...any chance you can put a list of the debloated apps?
Sent from my SM-G925T using Tapatalk
Been waiting for this sort of rom, thanks.
Not having wifi calling is sort of a deal breaker for me unfortunately though.
I'm looking forward to seeing how this rom develops. .
HobbesG6 said:
Been waiting for this sort of rom, thanks.
Not having wifi calling is sort of a deal breaker for me unfortunately though.
I'm looking forward to seeing how this rom develops. .
Click to expand...
Click to collapse
It seems like it may be something with SuperR's kitchen that's breaking wifi calling. I'm going to see if anyone else is having issues with this and if there's a fix. In the mean time, I am going to try and recreate the rom using a different kitchen.
Mortifix said:
It seems like it may be something with SuperR's kitchen that's breaking wifi calling. I'm going to see if anyone else is having issues with this and if there's a fix. In the mean time, I am going to try and recreate the rom using a different kitchen.
Click to expand...
Click to collapse
I was reading a thread where certain files and apks need to be present for WiFi calling to work. If I find it again, I'll send a link.
Edit: here is the post I saw...it's about adding wifi calling into a rom, but I am sure the info about the files needed can help.
http://forum.xda-developers.com/showthread.php?p=66561762
Sent from my SM-G925T using Tapatalk
mjdavis871 said:
I was reading a thread where certain files and apks need to be present for WiFi calling to work. If I find it again, I'll send a link.
Edit: here is the post I saw...it's about adding wifi calling into a rom, but I am sure the info about the files needed can help.
http://forum.xda-developers.com/showthread.php?p=66561762
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
I have been racking my brain for the past few days trying to figure out whats causing this. I believe like that article is saying that its a permissions issue. I've tried redoing the rom numerous times with different settings but nothing seems to fix the issue. The closest I got was changing the permissions from metadata to sparse_dat. The problem with this was I could not get wifi to enable after using sparse_dat. I have tried odexed and deodexed with a completely stock system and a trimmed system but nothing seems to resolve the issue. I'm thinking this may be something that needs to be corrected with the kernel since that's the only thing that's not changed through my testing. I have tried replacing @The Sickness's kernel in his base rom for the S6 with the stock kernel from the S6 Edge and it does the same thing. The only doubts I'm having about that theory is that I tried using Arter97's kernel and it seems that Wifi calling is not working with that either which would support the theory that it is a permissions issue. The only problem with this is that I don't know what permission would need to be changed or even how to find this as I am still an android OS noob. I'm going to continue doing research to see what I can come up with :fingers-crossed:
Mortifix said:
I have been racking my brain for the past few days trying to figure out whats causing this. I believe like that article is saying that its a permissions issue. I've tried redoing the rom numerous times with different settings but nothing seems to fix the issue. The closest I got was changing the permissions from metadata to sparse_dat. The problem with this was I could not get wifi to enable after using sparse_dat. I have tried odexed and deodexed with a completely stock system and a trimmed system but nothing seems to resolve the issue. I'm thinking this may be something that needs to be corrected with the kernel since that's the only thing that's not changed through my testing. I have tried replacing @The Sickness's kernel in his base rom for the S6 with the stock kernel from the S6 Edge and it does the same thing. The only doubts I'm having about that theory is that I tried using Arter97's kernel and it seems that Wifi calling is not working with that either which would support the theory that it is a permissions issue. The only problem with this is that I don't know what permission would need to be changed or even how to find this as I am still an android OS noob. I'm going to continue doing research to see what I can come up with :fingers-crossed:
Click to expand...
Click to collapse
I'm going to load up @SICKMADEs v1 rom and see if wifi works. If it does, you might be able to isolate the problem.
Sent from my SM-G925T using Tapatalk
Mortifix said:
I have been racking my brain for the past few days trying to figure out whats causing this. I believe like that article is saying that its a permissions issue. I've tried redoing the rom numerous times with different settings but nothing seems to fix the issue. The closest I got was changing the permissions from metadata to sparse_dat. The problem with this was I could not get wifi to enable after using sparse_dat. I have tried odexed and deodexed with a completely stock system and a trimmed system but nothing seems to resolve the issue. I'm thinking this may be something that needs to be corrected with the kernel since that's the only thing that's not changed through my testing. I have tried replacing @The Sickness's kernel in his base rom for the S6 with the stock kernel from the S6 Edge and it does the same thing. The only doubts I'm having about that theory is that I tried using Arter97's kernel and it seems that Wifi calling is not working with that either which would support the theory that it is a permissions issue. The only problem with this is that I don't know what permission would need to be changed or even how to find this as I am still an android OS noob. I'm going to continue doing research to see what I can come up with :fingers-crossed:
Click to expand...
Click to collapse
Take the updater-script from my rom......do the permissions just like I have them in your script.
The Sickness said:
Take the updater-script from my rom......do the permissions just like I have them in your script.
Click to expand...
Click to collapse
I've tried that, no luck I also tried using your exact updater-script minus the sickness folder but still had the same results.
Something else I've noticed is that VoLTE is only working using sparse as well.
I am in the process of trying to use raw_img permissions and old school permissions.
I loaded up twisted v1 and couldn't get wifi calling to connect...maybe I didn't wait long enough...I'll try again later
Sent from my SM-G925T using Tapatalk
Mortifix said:
I've tried that, no luck I also tried using your exact updater-script minus the sickness folder but still had the same results.
Something else I've noticed is that VoLTE is only working using sparse as well.
I am in the process of trying to use raw_img permissions and old school permissions.
Click to expand...
Click to collapse
Then your issue is symlinks then.......did you add them to your script from the system.img?
The Sickness said:
Then your issue is symlinks then.......did you add them to your script from the system.img?
Click to expand...
Click to collapse
I believe so. I used SuperR's kitchen for the entire process so that's what generated the updater-script. I used the system.img to build the project files.

Categories

Resources