Since january 8.1 update i no longer able to create a wireless hotspot using 5Ghz band,
Saying that its not available in my country,
The option for 5Ghz still there though, only it (tethering) cant be toggled on if i choose 5Ghz
What a *bs* by google, a lot of AP i my country use 5Ghz just fine
Any idea how to get through this limitation ? In december patch it work btw
otonieru said:
Since january 8.1 update i no longer able to create a wireless hotspot using 5Ghz band,
Saying that its not available in my country,
The option for 5Ghz still there though, only it (tethering) cant be toggled on if i choose 5Ghz
What a *bs* by google, a lot of AP i my country use 5Ghz just fine
Any idea how to get through this limitation ? In december patch it work btw
Click to expand...
Click to collapse
I know it *was* working just fine on Telkomsel, Pak ...and I see you are on Telkomsel. Maybe try the build.prop mod people are using to bypass tethering restrictions. Couldn't hurt to try it. Semoga beruntung!
v12xke said:
I know it *was* working just fine on Telkomsel, Pak ...and I see you are on Telkomsel. Maybe try the build.prop mod people are using to bypass tethering restrictions. Couldn't hurt to try it. Semoga beruntung!
Click to expand...
Click to collapse
Yes, thank you pak for the heads up,
Benar benar lupa ada modif itu, since last time i need that kind of mod is back in htc one M7 era
Sudah berhasil skrg aktifkan 5Ghz
Just in case butuh juga, ini saya ada buat module magisknya, supaya tidak usah edit build.prop manual. Resiko kena SN. Nanti e-money isi ulang mandiri ga jalan. Hahaha
Still need to manually do "settings put global tether_dun_required 0" from adb shell or terminal though (one time only)
Forget to attach the module
otonieru said:
Forget to attach the module
Click to expand...
Click to collapse
What is it? Is it something in the Build_Prop that I can edit? I'm trying not to break systemless root so I've installed everything via Magistk.
Aircraft800 said:
What is it? Is it something in the Build_Prop that I can edit? I'm trying not to break systemless root so I've installed everything via Magistk.
Click to expand...
Click to collapse
No, thats a magisk module.
otonieru said:
No, thats a magisk module.
Click to expand...
Click to collapse
Do you know if there is an updated Magisk module? I flashed the one you posted, no luck for me.
Aircraft800 said:
Do you know if there is an updated Magisk module? I flashed the one you posted, no luck for me.
Click to expand...
Click to collapse
After installing the module, you still need to run this command from terminal :
"settings put global tether_dun_required 0"
Sorry to dig out this old thread.
Were do i have time write this command?
Tried it in twrp. It said there is no command like this.
edit:
i receive this message:
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:1798)
at com.android.providers.settings.SettingsProvider.mutateGlobalSetting(SettingsProvider.java:979)
at com.android.providers.settings.SettingsProvider.insertGlobalSetting(SettingsProvider.java:953)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:359)
at android.content.ContentProvider$Transport.call(Unknown Source:12)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:387)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:285)
at android.os.ShellCommand.exec(Unknown Source:35)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:51)
at android.os.Binder.shellCommand(Unknown Source:0)
at android.os.Binder.onTransact(Unknown Source:111)
at android.os.Binder.execTransact(Unknown Source:51)
ermission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
any idea whats wrong here?
schlubbi said:
Sorry to dig out this old thread.
Were do i have time write this command?
Tried it in twrp. It said there is no command like this.
edit:
i receive this message:
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:1798)
at com.android.providers.settings.SettingsProvider.mutateGlobalSetting(SettingsProvider.java:979)
at com.android.providers.settings.SettingsProvider.insertGlobalSetting(SettingsProvider.java:953)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:359)
at android.content.ContentProvider$Transport.call(Unknown Source:12)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:387)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:285)
at android.os.ShellCommand.exec(Unknown Source:35)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:51)
at android.os.Binder.shellCommand(Unknown Source:0)
at android.os.Binder.onTransact(Unknown Source:111)
at android.os.Binder.execTransact(Unknown Source:51)
ermission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
any idea whats wrong here?
Click to expand...
Click to collapse
You need to do it from terminal emulator after boot into system
Don't forget to type "su" first to grant superuser,
Else, you will face permission denied error like above
otonieru said:
You need to do it from terminal emulator after boot into system
Don't forget to type "su" first to grant superuser,
Else, you will face permission denied error like above
Click to expand...
Click to collapse
I downloaded a emulator from playstore and also tried it from cmd in Windows
wrote:
su settings put global tether_dun_required 0
i also tried:
su
settings put global tether_dun_required 0
and nothing happend.
5ghz hotspot is still not working and i still cant use my MiMover to send data from my MiNote 2 to my Mi8 Pro.
Related
It does not prompts and automatically denied the request
Plz help
Sujeet111 said:
It does not prompts and automatically denied the request
Plz help
Click to expand...
Click to collapse
I suggest that you post this on the magisk forum and make sure that you include logcats and other magisk logs required (read first post)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hi, my tbm happens this way sometimes. When this happens I open the magisk, pull the sidebar and go in SuperUsuario, and activate the box that is not activated and ready. I do not know if it helped you, it's worth trying.
Hi folks,
I got my RN5 AI Global a couple of days ago and I want to give Lineage OS a spin. Then I read about this dreaded feature of Google called "ARB" - a developer's nightmare!
My current version is 9.5.17 on my phone. When I change into settings I can see that 9.5.19 has been downloaded and is ready for installation, the only action I have to do is reboot. Since 9.5.19 carries ARB feature, I do not power down my phone in order not to install this fix.
So guys, here is my question: Is there any way I can prevent this update from installing on my phone?
Best wishes,
DFahren
Don't install it?
Just power down and go straight to fastboot (power+voldown) then use mi unlock to unlock then flash lineage after doing twrp.
Not that it would matter too much having 9.5.19 since you can bypass it blocking fastboot commands with the arbypass.img file
Nice idea. However my Mi account is not (yet) eligible for unlocking .... This will take 14 days, I suppose.
Delete the update from internal storage/downloaded_rom
And also turn off automatic updates so you don't get it again.
"If you are on MIUI 9, then:
- Go to Settings
- About Phone
- System Updates
- Click on 3 dots above right
- Turn Off both "Download Automatically" and "Download using Mobile Data"."
And you should be able to reboot your device.
Ok, what you are basically saying is: open a CMD on Windows, issue an "adb shell" and in this shell do a "cd xxx/storage/downloaded_rom; rm *", right?!
I have to do this because I do not see this folder downloaded_rom when using MIUI's filemanager. Correct?
Cheers, Dfahren
corkiejp said:
Delete the update from internal storage/downloaded_rom
And also turn off automatic updates so you don't get it again.
"If you are on MIUI 9, then:
- Go to Settings
- About Phone
- System Updates
- Click on 3 dots above right
- Turn Off both "Download Automatically" and "Download using Mobile Data"."
And you should be able to reboot your device.
Click to expand...
Click to collapse
@dfahren
Maybe try a different file manager than stock.
Someone else reported on another forum that they deleted the downloaded update.
Not sure how exactly, I will message them and find out how.
dfahren said:
Ok, what you are basically saying is: open a CMD on Windows, issue an "adb shell" and in this shell do a "cd xxx/storage/downloaded_rom; rm *", right?!
I have to do this because I do not see this folder downloaded_rom when using MIUI's filemanager. Correct?
Cheers, Dfahren
Click to expand...
Click to collapse
corkiejp said:
@dfahren
Maybe try a different file manager than stock.
Someone else reported on another forum that they deleted the downloaded update.
Not sure how exactly, I will message them and find out how.
Click to expand...
Click to collapse
I deleted the update zip file using solid explorer.
Sent from my Redmi Note 5 using Tapatalk
....deleted ....
gsmyth said:
I deleted the update zip file using solid explorer.
Click to expand...
Click to collapse
Yeah, that's also a good way to get rid of the update.
I used ADB with installed drivers. However path to the update was ..../sdcard/downloaded_rom , but that's a minor. Just wanted to let you guys know.
So, grabbed the latest OTA, and went through the usual re-root cycle, but was unable to edit the build.prop. While /root is mountable, /root/system is not, which means no tethering for me.
Anyone else running into the same issue?
I have the same issue, I've been fighting with it all day.
I patched the boot.img with Magisk Manager and flashed it, Magisk Manager show's I'm installed and Root Checker says I'm rooted, I was even able to install Adaway. But i cannot use any root app that needs to mount /System
I tried using Root Uninstaller and it says it has root access but cannot mount /system as R/W
It seems Magisk is only able to partially root on Android 10
I tried this with the Canary version and the standard version of Magisk and the same issue both times
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
bbarnes1 said:
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
Click to expand...
Click to collapse
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
This has been a problem since the Q beta came out, with each update I tried to figure something out. With no luck! I tried the Magisk Mod but it didn't seem to work.
suggestions would be most appreciated!!
Thinkin about a clean install....maybe.....
Edit: It was also a problem with the P beta until it was out of beta (That was my hope for this)
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....
Click to expand...
Click to collapse
I'm trying to add a prop, which seems like a different need, but will look into it.
tufyuma said:
Thinkin about a clean install....maybe.....
Click to expand...
Click to collapse
Was thinking about this, but realized a clean install for every update isn't worth a hotspot to me.
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
I gave this a whirl, its doesn't appear to actually be change build.prop
bbarnes1 said:
I gave this a whirl, its doesn't appear to actually be change build.prop
Click to expand...
Click to collapse
It doesn't physically change anything in system. The intent is to offer the same functionality as physically editing the build.prop without modifying that file. It creates the prop and value setting and loads into into memory at boot time.....(similar to the way the build.prop file is read at boot time for those settings.) At least that is my understanding. It works for me on Android 9 for setting the prop for tethering...for example. You can confirm it works by using the getprop command to verify the prop you set is set as you intended.
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
somethingsomethingroot said:
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
Click to expand...
Click to collapse
Can you tell me what the process is that got you tethering capability?
Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it.
I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I couldn't mount anything under system so I still can't edit build.prop.
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
Thanks for posting this, it worked great on my Pixel XL on Sprint. I had about given up on being able to edit the build.prop.
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Your prop
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Are you sure that your screenshot of the props output is correct? Because it looks like you have the value set to "net.tethering.noprovisioning" and the prop name has =true in it. I'm just trying to figure this out because I've tried this and everything else trying to get my hotspot to work. My hotspot will turn on and devices can connect to it, but they don't have internet access. Any ideas at all?
Edit: Nevermind, I had the custom prop set to post fs data when it was supposed to be set at boot stage (default). My hotspot is working now. Thank you all.
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Confirming that this works on rooted pixel 4. Thank you for this btw
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
This seems to have worked for me, though I don't really understand why or what did it.
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
wolvmarine said:
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
Click to expand...
Click to collapse
Why need to turn on Hotspot for build.Prop editing? What's wamo?
truelies1 said:
Why need to turn on Hotspot for build.Prop editing? What's wamo?
Click to expand...
Click to collapse
Does anyone know a way to enable gestures on 3rd party launchers on stock rom
Hi,
I did something wrong with my A2 Lite, i've updated the Magisk boot file from the Magisk app. Caused my phone to stop booting Android.
So i tried reflashing it with Mi Flash in EDL mode. That worked but i don't have any signal when i put a SIM in.
It shows my provider in settings so it recognizes the SIM but doesn't do anything with it.
Tried 10.0.13.0 manually and via Mi Flash = no signal
Tried 10.0.2.0 via Mi Flash = no signal
Loaded TWRP, switch A/B = no effect
Does anyone have a clue what i can do now?
Looks like the IMEI numbers are 0.
terrorsource said:
Looks like the IMEI numbers are 0.
Click to expand...
Click to collapse
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
a1291762 said:
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
Click to expand...
Click to collapse
Is it possible to write back the IMEI's if i have them?
terrorsource said:
Is it possible to write back the IMEI's if i have them?
Click to expand...
Click to collapse
It might be. In theory. You'd need to know the format of whatever was overwritten.
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy ?
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Noam5651 said:
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Click to expand...
Click to collapse
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
terrorsource said:
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works partially!
I cannot install the latest "QPST_2.7.453" due to "Installation errors".
If i try "QPST_2.7.422" i can restore the created QCN but i cannot select "Enable Multi-SIM" and it only restores IMEI-1
nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
terrorsource said:
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
Click to expand...
Click to collapse
We'll I have never had an issue with losing my IMEI , the manual is not mine ,I'm glad that it worked!
Upgraded from C.47 to C.60. The memory expansion function appeared. After getting root access through the patched boot, the function disappeared. Has anyone encountered something like this? Have you found a solution to this problem?
Mi Bodya said:
Upgraded from C.47 to C.60. The memory expansion function appeared. After getting root access through the patched boot, the function disappeared. Has anyone encountered something like this? Have you found a solution to this problem?
Click to expand...
Click to collapse
There is no workaround for this. If you're rooted, RAM expansion is gone. Also, if you have a device with at least 8Gb+ RAM, there are zero reasons to use the RAM expansion.
If you try to find this item through the search, then opening it you can see the message "not enough memory to enable this function"
Mi Bodya said:
View attachment 5629613View attachment 5629615If you try to find this item through the search, then opening it you can see the message "not enough memory to enable this function"
Click to expand...
Click to collapse
Have you found the solution?
handydandy said:
Have you found the solutio
Click to expand...
Click to collapse
No
Taken from telegram;
As we all know, after oos13 and 12 get Magisk on mobile phones, the memory expansion disappears and can't be used.
Then the solution is to enter in the terminal emulator:
su
Then enter：
resetprop persist.sys.oplus.nandswap.condition true
And then enter：
echo 1 >/sys/block/zram0/hybridswap_dev_life
Then the phone has to be restarted twice for it to take effect.
You could also make a module with a service.sh file
```
#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
resetprop persist.sys.oplus.nandswap.condition true
echo 1 >/sys/block/zram0/hybridswap_dev_life
# This script will be executed in late_start service mode
```
install this module and thanks me later
yassine2217 said:
instale este modulo y me agradece mas tarde
Click to expand...
Click to collapse
Perfect, thanks.
yassine2217 said:
install this module and thanks me later
Click to expand...
Click to collapse
Noz working on oos 13 f72 (the tab ram extension is no longer found at all)
ChrisFeiveel84 said:
Noz working on oos 13 f72 (the tab ram extension is no longer found at all)
Click to expand...
Click to collapse
using coloros work perfectly
yassine2217 said:
using coloros work perfectly
Click to expand...
Click to collapse
Never coloros! (For china market )
ChrisFeiveel84 said:
Never coloros! (For china market )
Click to expand...
Click to collapse
I'm not concerned with playstore, I'm concerned with the restrictions that coloros has (e.g. how many apps can be set in the auto start,) that coloros does not speak German, and that coloros does not comply with the data protection laws applicable in the eu holds . and some more
.......
co4 said:
Taken from telegram;
As we all know, after oos13 and 12 get Magisk on mobile phones, the memory expansion disappears and can't be used.
Then the solution is to enter in the terminal emulator:
su
Then enter：
resetprop persist.sys.oplus.nandswap.condition true
And then enter：
echo 1 >/sys/block/zram0/hybridswap_dev_life
Then the phone has to be restarted twice for it to take effect.
You could also make a module with a service.sh file
```
#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
resetprop persist.sys.oplus.nandswap.condition true
echo 1 >/sys/block/zram0/hybridswap_dev_life
# This script will be executed in late_start service mode
```
Click to expand...
Click to collapse
Any solution for us non-rooted phones?
yassine2217 said:
install this module and thanks me later
Click to expand...
Click to collapse
Are you sure you made it correctly like it works when flashing the ram extension pops up but upon reboot I lose it till I flash module again. I think the module doesn't send the command each boot but only when installing . Is that right Yassine? How do I fix this.
cbomb1337 said:
Are you sure you made it correctly like it works when flashing the ram extension pops up but upon reboot I lose it till I flash module again. I think the module doesn't send the command each boot but only when installing . Is that right Yassine? How do I fix this.
Click to expand...
Click to collapse
I didn't say I made it, i just suggested the module because I know it works, as I used it in my Coloros 13.
Oh wait all good I just put the code in 3c tool boxes scripter section and set it to boot using that. And removed module and rebooted with it active in scripter and it worked so all good thanks to .