Related
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)/
The main functionality i want is the ability to turn on/off:
Airplane mode
Location Completely (when screen off)
GPS when opening apps that use maps
Mobile data
Can anyone suggest the best way to get this functionality back if its possible?
farquea said:
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)/
The main functionality i want is the ability to turn on/off:
Airplane mode
Location Completely (when screen off)
GPS when opening apps that use maps
Mobile data
Can anyone suggest the best way to get this functionality back if its possible?
Click to expand...
Click to collapse
You could try some of the run shell commands from this thread https://forum.xda-developers.com/u/tasker-tips-tricks/best-run-shell-commands-tasker-t3419204 or use the AutoTools plugin https://play.google.com/store/apps/details?id=com.joaomgcd.autotools
Majority (if not all) of Secure settings stuff is now easily available on AutoTools.
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
farquea said:
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
Click to expand...
Click to collapse
You're gonna have to run that command. It should work fine then.
farquea said:
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
Click to expand...
Click to collapse
What ADB command are you talking about?
farquea said:
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)
Click to expand...
Click to collapse
I'm on Nougat as well and I'm using Secure Settings every day, it works fine for me...
The adb command worked but my bigger problem was that my phone had lost root. All fixed now tho
You can replace Secure Settings with SecureTask plugin. Free and it works great.
kitkat85 said:
You can replace Secure Settings with SecureTask plugin. Free and it works great.
Click to expand...
Click to collapse
Sounds great. Can you please provide a link? Thanks!
AJH101 said:
Sounds great. Can you please provide a link? Thanks!
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.balda.securetask
kitkat85 said:
https://play.google.com/store/apps/details?id=com.balda.securetask
Click to expand...
Click to collapse
Fantastic, thank you.
---------- Post added at 08:07 AM ---------- Previous post was at 07:25 AM ----------
kitkat85 said:
https://play.google.com/store/apps/details?id=com.balda.securetask
Click to expand...
Click to collapse
Forgive me, is this not very similar to the Auto Tools plug in? [emoji4]
AJH101 said:
Fantastic, thank you.
---------- Post added at 08:07 AM ---------- Previous post was at 07:25 AM ----------
Forgive me, is this not very similar to the Auto Tools plug in? [emoji4]
Click to expand...
Click to collapse
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
kitkat85 said:
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
Click to expand...
Click to collapse
Thanks. I will start digging!
kitkat85 said:
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
Click to expand...
Click to collapse
@automess... I have used both and though autotools is 2.99 I find it more user friendly. But both are equally up to task.
digitalpig82 said:
What ADB command are you talking about?
I'm on Nougat as well and I'm using Secure Settings every day, it works fine for me...
Click to expand...
Click to collapse
Hi, I'm in nougat with a ROM but I can't open tasker. I hope anyone can help
@farquea,::if you want to stick with securesettings in noughat,here is the work around i am using, found the fixfrom superSu forum..
Obviously i am using superSu to give root access for secure settings..
First flash superSu in systemless mode in twrp.
After reboot, using terminal emulataor type the following command
su
echo "BINDSYSTEMXBIN=true" >> /data/.supersu
and reflash superSU from twrp..securesettings will be enabled...
Reference :
1) https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
2) https://forum.xda-developers.com/showpost.php?p=66140836&postcount=5493
This may help you if u want to stick with securesettings
vedhavyga said:
@farquea,::if you want to stick with securesettings in noughat,here is the work around i am using, found the fixfrom superSu forum..
Obviously i am using superSu to give root access for secure settings..
First flash superSu in systemless mode in twrp.
After reboot, using terminal emulataor type the following command
su
echo "BINDSYSTEMXBIN=true" >> /data/.supersu
and reflash superSU from twrp..securesettings will be enabled...
Reference :
1) https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
2) https://forum.xda-developers.com/showpost.php?p=66140836&postcount=5493
This may help you if u want to stick with securesettings
Click to expand...
Click to collapse
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
JRJ442 said:
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
Click to expand...
Click to collapse
i think dat also..but not sure if enter both the values, will supersu install in systemless mode?
JRJ442 said:
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
Click to expand...
Click to collapse
I'm using the Magisk interface and Secure Settings just works with the root method that is built into Magisk,
Also thinks like AndroidPay work with Magisk
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Tmobilefan906 said:
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Click to expand...
Click to collapse
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Code:
/sbin/su -c "svc data enable"
axxbat said:
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Click to expand...
Click to collapse
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
axxbat said:
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Click to expand...
Click to collapse
u didn't offend me at all
axxbat said:
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
Click to expand...
Click to collapse
What u mean skipped su perms?
Tmobilefan906 said:
What u mean skipped su perms?
Click to expand...
Click to collapse
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
axxbat said:
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
Click to expand...
Click to collapse
I guess I'm not too worried about it. As long as the task works, I'm fine with it. Haha
Trying to use Secure Tools to disable volume warning Samsung S5 running Marshmallow. I installed everything and ran adb command. No error, but when I search for Secure Tools it says Not Installed. Then I read this doesn't work on Marshmallow?
My phone is NOT rooted. Any help would be much appreciated.
Thanks - Frankie
Frankie-o said:
Trying to use Secure Tools to disable volume warning Samsung S5 running Marshmallow. I installed everything and ran adb command. No error, but when I search for Secure Tools it says Not Installed. Then I read this doesn't work on Marshmallow?
My phone is NOT rooted. Any help would be much appreciated.
Thanks - Frankie
Click to expand...
Click to collapse
I'm confused. What app are you referring to? "AutoTool's secure settings" or the app "Secure settings" or something else that I'm missing?
TASKER and AUTO TOOLS
I guess I forgot to mention that I'm user Tasker to do this... Thank you.
Be very specific what you are using and what you are trying.
Trying to disable high volume warning on Samsung S5
Using Tasker Auto Tools to run a command on my phone that will allow me to override the Volume High Warning on the Samsung S5 phone. It's supposed to enable WRITE SECURE SETTINGS with this command - and the command runs fine but it's not working for me. But when I go back to the app and look for Secure Settings, it's not there.
adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS
Auto tools is a plugin to tasker.
The "adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS" is one of two steps required to give the type of system level OS access this tool needs. The first thing that should be done is to enable "allow modify system settings" for AutoTools.
From the AutoTools Secure Settings page:
To use this, AutoTools needs to be granted permission to change secure settings on your device
If you're on Android 6 or above click here to grant AutoTools the first Settings permission
Then follow these steps to grant AutoTools the Secure Settings permission:
Enable Developer Mode: Go to Android Settings -> About Phone and look for the Build Number option. Touch it multiple times until developer mode is enabled.
Enable USB Debugging: Go to Android Settings -> and look for the Developer Options option. In there, enable the USB debugging option.
Install ADB on your PC: Check here for a quick way to do it.
Connect device to PC: Connect your device to a PC and look on your phone. A prompt should show up asking you to allow your phone to be debugged by your PC. Accept this.
Grant permission: Open a command line on your PC and write
adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS
Congratulations, AutoTools should now be able to use the "Secure Settings" action!
Click to expand...
Click to collapse
Once those things are done ( I typically reboot for no good reason ☺ ), then go to tasker, add an action in a task, then: plugin -> Auto tools -> secure settings (scroll down the list) you'll end up in a screen where you can configure the AutoTools secure settings action.
WOW! I think I did it.. I just hope I can do it again - this was my "test" phone. I think I was messed up by doing the "search" for secure settings because it said it wasn't installed.. Yet I had looked for the secure settings option and didn't find before - although I had already done all the steps. Somehow I got on to a screen that said the app (I forget the exact words) didn't have permission to change the settings, and to press NO if I wanted to allow the permissions - and I pressed no! I had already created the task to disable the warning - but it's been so long, I'm not sure how I did that - but the bottom line is I think it's working.. I had found several sites that said this wouldn't work with Marshmallow unless the phone was rooted, and my phones are not rooted.. so that makes me skeptical, but I did a reboot, and the warning didn't come back. Thanks a ton for your help.. Let's hope I can re-create on the phone that really needs it.
In case this is found by someone else, many of those "how to use secure settings" posts from lollipop and marshmallow predate the (awareness of the) approach used by AutoTools. People spent a lot of effort trying to force an unsupported, outdated app (the original secure settings) to work in a systemless root environment.
I'm sad to say this did NOT work on my test phone.. It looked like it did, but it didn't.
Hi all:
Here is a LineageOS 17.1 ROM for Z5 compact (suzuran).
Download 2022-09-11
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 10.0 (Q)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 September 2022
Using sony blob's from stock version 32.4.A.1.54
Memory issues finally fixed!
Battery consumption significantly reduced! For further reduction, please follow these instructions.
Google Pay does not give an error when starting the app. This does not mean, that payment is working. I can't test it, because I don't use this feature at all. Please report if it's working or not.
Updated aptX encoder blobs.
P2P-Crashes fixed.
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!) There is a version 3.2.3 out there, but with that version I had problems to restore my backups. 3.2.1 is just working perfect for me!
OR use my self built TWRP-version 3.6.2!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Bluetooth
Camera; both built-in camera (Snap) and 3-rd party camera apps.
Snap may be a little bit laggy, please use 3-rd party camera app instead; for example OpenCamera. If you're running into errors, please report.
Enforced SELinux support (see attached screenshot)
Fingerprint
FM-Radio
GApps (pick this version: ARM64, 10.0, pico [tested])
German app AusweisApp2 working (see this post)
GPS
Headset
LiveDisplay (see attached screenshots)
Location services
Notification LED
Offline charging
Phone calls (see attached screenshot)
SafetyNet test passed successfully
Signed build
SMS
Torch
WiFi
These things are NOT (or badly) working:
Camera focus at low distances.
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.
If you have problems with GApps:
Sometimes the SetupWizard of GApps crashes on and on. Then you have to boot into TWRP, mount system, and go into terminal, where you have to delete SetupWizard (see screenshots):
Code:
cd /system/system/priv-app
rm -rf SetupWizard
Reboot.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Benefits:
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Hi Bernie,
First things first : Thank you so much for your amazing work on this device.:highfive:
So hard to find a good, compact and up to date smartphone.
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
On your Los14.1 (i tried with the last one you created, a few days ago) : it would be something like 0.8go ram (so everything run smoother) still without gapps and other apps / settings.
Maybe, now our days, 3go ram is mandatory for android + gapps + 3rd party ...
Ryu--X said:
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
Click to expand...
Click to collapse
I know about that. I've tried with gapps and I can confirm that ram is running out of free space. Sometimes the system is not responding any more (screen is flickering and it seems that nothing happens) and I have to restart it (press power button quite a long time until power menu appears).
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Berni-0815 said:
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Click to expand...
Click to collapse
I can confirm that unfortunately GPS isn't working.
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
casouzaj said:
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
i didn't have this behavior on my tests, but i usually let the system start and wait for few minutes before using it (especially on 1st boot).
Also, i always reboot once after the 1st boot.
Hope it will help
casouzaj said:
after the language selection, my phone reboots on the 'Just a sec', endlessly.
Click to expand...
Click to collapse
Clean install?
That should not happen...
Ryu--X said:
I can confirm that unfortunately GPS isn't working.
Click to expand...
Click to collapse
You have to enable google's location service in location settings. With that, maps is working with correct location; but I don't know if the location comes from gps, wlan or network. It's raining since many days and I don't want to stand outside in the rain and wait for gps connection... :angel:
I've tried to install f-droid and their location services; no better results...
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
Click to expand...
Click to collapse
Yes, I know. The problems are always the closed-source binaries from qualcom and sony that are not properly working on LineageOS versions > 14.1
We're working on it but I'm not able to say if we can fix these issues.
BTW: Is anyone able to make an outgoing call successfully?
Berni-0815 said:
Clean install?
That should not happen...
Click to expand...
Click to collapse
Yup,, every single time!
Sent from my Xperia Z5 Compact using XDA Labs
As I said, that should not happen...
Berni-0815 said:
BTW: Is anyone able to make an outgoing call successfully?
Click to expand...
Click to collapse
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Ryu--X said:
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Click to expand...
Click to collapse
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
I'm not on any aspect a Dev but I give you all my energy on continuing the developpment of this ROM.
Any other support available ?
Berni-0815 said:
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
Click to expand...
Click to collapse
Here it is !
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Berni-0815 said:
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Click to expand...
Click to collapse
Yes exactly , both ways are ok (incoming and outgoing).
Ryu--X said:
Yes exactly , both ways are ok (incoming and outgoing).
Click to expand...
Click to collapse
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
New version out; see 1st post
Berni-0815 said:
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
Click to expand...
Click to collapse
Pretty strange, indeed.
The phone i tested with is on another provider than my z5c.
I got to say that i checked the apn before making my tests, and they were good.
I will retry with the new version tonight .
Thanks
The APN shouldn't matter for regular calls unless you're using Wifi calling or VoLTE, maybe disable both and see if it works.
The S2 wifi blobs have now been incorporated into the Aug 25 17.1 builds.
Please take 10 minutes to read all of post #1 and #2. lpedia and I have spent 5 days troubleshooting this together and want to present our wifi findings. DO NOT USE this thread to report any other problems, it's only for exynos5433 S2 tablet wifi. If this is unreasonable, then stop reading. Thank you.
If your device's wifi is not connecting after a restart and/or wake from sleep, and/or dropping out at random, this could be because the 17.1 code is using Samsung Galaxy S6 wifi blobs instead of its stock S2 wifi blobs. This commit was made in 17.1 at
gts2: Import Galaxy S6 BCM4358 firmware · universal5433/[email protected]
@lpedia has confirmed that LineageOS 17.1 on his T710 has the wifi problems when using S6 blobs, but not after the S6 blobs have been replaced with stock S2 blobs. This appears to fix both non-connection at boot and not reconnecting on wake from sleep. Random dropouts are less common and were not seen during the limited testing, so it's not certain that they're gone.
FAQ
Q1. Will changing from S6 wifi blobs solve all my wifi no reconnect or disconnect problems?
A1. This has only been tested on the T710, and there's no guarantee it will help the other devices. If you want to try, follow the instructions below. Before you try, make sure to back up all your data. The following should write the stock S2 blobs to the /system partition only, but if you make a mistake you could lose your data! Back up first.
It's an easy test to see if the stock S2 blobs will help or not. If your current rom does not connect to wifi after a restart, try our proposed solution. Before you do, reboot your current rom 5 times in a row. After each reboot, see if your wifi connects. After you install stock S2 blobs, reboot your device again 5 times in a row and see if wifi connects. This will easily tell you if the S2 stock blobs have solved this one particular problem or not.
As for wifi not connecting after long/deep sleep, you should notice over 2 or 3 days if wifi connects or not after deep sleep.
Q2. Will this work on SM-T710, SM-T810, etc?
A2. Same answer as A1. It should work on any S2 tablet exynos5433 device that uses the S6 wifi blobs that are the default in 17.1 or Android 10. These instructions are only for exynos5433 devices.
As the thread grows bigger, you can see who is responding back with either positive or negative feedback and what model they have.
Q3. Will this work on RR, Havoc or LineageOS (Android 10 or 17.1)?
A3. The instructions below replace the S6 blobs with the original stock S2 blobs. The instructions provided should work regardless if it's Havoc, RR or LineageOS. All these variant OSes share the same repo (i.e. code and blobs) on github.
Q4. Is this post relevant to Android 9 or LineageOS 16.0?
A4. NO. The github repos show that Android 9 or LineageOS 16.0 used the stock S2 wifi blobs. This was changed to S6 wifi blobs in Android 10 or LineageOS 17.1. I don't know why it was changed to S6 blobs as I'm not involved with that change.
Q5. Why do I need my model and code name?
A5. In order to follow the instructions below, you need to know your model number and it's code name. The model number or device name is settings, about tablet.
You can find the code name at (scroll almost all the way down to the bottom)
Samsung
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
For example, SM-T710 is gts28wifi.
Q6. Does it matter if my wifi is 2.4Ghz or 5Ghz or a mix of both?
A6. When reporting back to us, please state whether your network is 2.4Ghz only, 5Ghz only, or a mix of 2.4Ghz and 5Ghz. In addition, if its a mix, please let us know if it's one wifi network (same ssid) or two separate wifi networks. That is, 2.4Ghz is one ssid and 5Ghz is another ssid.
Q7. If this works, how will this be fixed for the next release of code and the future?
A7. If enough people say it fixes their wifi problems, I can submit a git pull request to Anan to revert the S6 wifi blobs back to S2 wifi blobs.
Instructions
1. Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
Note if you are running Magisk, see posts regarding Magisk if you cannot see rooted debugging.
2. You will need git. There are instructions and download links for installing git on Windows, MacOS, and Linux at Git Guides - install git | GitHub.
3. After you install git, follow the instructions exactly below.
Bash:
# make temporary vendor directory
mkdir temp
# cd to that directory
cd temp
# git the 16.0 stock drivers
git clone https://github.com/universal5433/proprietary_vendor_samsung -b lineage-16.0
# change directory to proprietary_vendor_samsung/<your device>/proprietary/system/vendor/etc
# or if Windows, to proprietary_vendor_samsung\<your device>\proprietary\system\vendor\etc
# where "<your device>" is your device's code, for example gts28wifi for the T710:
cd proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc
# start adb root
adb root
# remount /system as rw (it's read only by default)
adb remount
# start adb shell
adb shell
# delete S6 blobs from wifi directory
cd /system/vendor/etc/wifi
rm bcm*
rm nvr*
# There should be only .conf files left now
ls -al
exit
# you should be back at your desktop terminal prompt now
# now push all stock drivers to /system/vendor/etc/wifi
adb push wifi /system/vendor/etc
# check to make sure it got pushed okay
adb shell ls -al /system/vendor/etc/wifi
# now reboot Android
adb reboot
If the above does not work for you, or if it causes other problems, just reflash the last rom. That will overwrite the /system partition and everything will be restored.
If you do try this, please report back to this thread about whatever happened and include your device and what wifi network you are running.
Reserved.
Thanks for the instructions!
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible. Everything else worked as described.
Observations after 5 reboots: WiFi available after reboot each time! Much better than before!
I will observe it now for a while regarding wifi-off after sleep or sporadical wifi-off.
Btw. for the random reboots of the unmodified linageos17.1 (ripee) I'm pinging my DNS-server all 2mins using Tasker. Fixed reboots since 2 month at least on my system.
Yogi555 said:
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible.
Click to expand...
Click to collapse
The above might be due to you not having adb root enabled in developer options. I will update the instructions to make sure that's enabled.
Strangely the setting seems not there in my system. But I remember that in some system its available. Can the installed Magisk be the reason?
Yogi555 said:
Strangely the setting seems not there in my system.
Click to expand...
Click to collapse
It's there.
Short update: The S2 wifi blobs are a huge improvement. With S6 blobs I had reliable dropoffs at medium router-signal combined with heavy wifi-load (no dropoffs with full router signal). With the S2 blobs no single dropoff even at weak router-signal and heavy wifi-load for several hours now.
Again, to enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Yogi555 said:
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Click to expand...
Click to collapse
Thanks, @Yogi555! It's great to know that replacing the blobs works on one of the other S2 models! We could only test it on gts28wifi (T710).
@Yogi555, about the Rooted debugging option: my T710 doesn't show that option, either, and I think it's because I have Magisk installed (@retiredtab doesn't).
If the device is not rooted, "adb root" temporarily restarts the adbd daemon on the device as root (there's a timeout period after which it will remove root access again).
I'm guessing that if the device is rooted, that isn't necessary - because adbd is probably already running as root . The Rooted debugging option is therefore unnecessary, and isn't shown.
In either case, when you do "adb root" on the PC, there should be a prompt on the device asking you if you want to allow access. Did you see the prompt? If you don't explicitly allow it, root access won't be given.
Also, "adb root" works on Windows (for an account that's in the Administrators group) without needing to be Run As Administrator, but I think Linux requires the command to be run as root (eg, sudo adb root).
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device. After "adb remount" next, an error is displayed:
Not running as root. Try "adb root" first.
remount failed
Maybe my adb is too old (version 1.0.40)
However "adb reboot recovery" works and "adb root" then in TWRP as well. So strange, but no problem
Yogi555 said:
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device.
Click to expand...
Click to collapse
Did you check the device to see if it's prompting you to allow this access? The prompt times out fairly quickly, so you might not see it if you don't check straight away. It does give a notification sound.
The prompting came yesterday at the very beginning of the activity and I allowed it (including the always checkbox). "adb device" shows the device id.
I don't understand why you'd see anything different from what I see. I use a Windows PC, I have Magisk (version 23.0) installed on the T710, and have previously allowed adb root access "always".
What I see is this:
Code:
> adb version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
> adb root
adbd is already running as root
> adb remount
remount succeeded
> adb root
gts28wifi:/ #
I think there could be something wrong with your Magisk configuration. What version is it?
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Yogi555 said:
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Click to expand...
Click to collapse
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
If you uninstall Magisk, I think you will find that your "Rooted debugging" is OFF. If so, turn it on, then try "adb root" etc. You don't need to root the device in order to use adb root functions. If you want the device to be rooted, by all means re-install Magisk - but with that setting still ON.
I'll be very interested to hear what happens.
The simplest way to check that adb root has actually given you root access is to "adb shell". The prompt will end in a "#" if the shell's running as root. As mentioned in an earlier post.
Want to also quickly confirm in here that the S2 Blobs are working real fine for me as well.
lpedia said:
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
Click to expand...
Click to collapse
I've just re-installed Magisk and proved to myself that Magisk 23 is hiding the setting. I found that Magisk 22 didn't hide it - I re-installed using a version 22 zip that I had on hand, checked the "Rooted debugging" setting, which was still visible, then updated to Magisk 23 via the app. After the reboot, the setting had disappeared again.