Develop Bugs

[App][Root] FolderMount Support for Android 5.0+

For full FolderMount details, Go to this link --> http://forum.xda-developers.com/showthread.php?t=2192122
People who have updated to CM12 or lollipop version are facing several issues regarding FolderMount app is not working, Link2SD etc. (I was one of those) so after taking help from people around, here i present you an easy solution for it.
About CM12 Based Devices (Lollipop 5.0+):
> Since you are on CM12 and we all know it is based on Security-Enhanced Linux (SELinux), you can see this is the basic concept here to make everything work like charm. What you have to do is change the SELinux status to PERMISSIVE MODE from ENFORCING MODE. This will allow the App to Get into with Full Root Access.
> What SELinux does here in ENFORCING MODE is that is limits the root access to be used. It generally stop the access to take all authority rights and moreover concentrating it should not damage your smartphone or tablet.
How to use FolderMount on CM12 Based Devices (Lollipop 5.0+):
1) Go to Play Store and Download SELinux Mode Change App
2) After the App Install, Open the app and allow root access.
3) You will now see ENFORCING MODE already selected.
4) Just click on PERMISSIVE MODE and head to Settings > About Phone.
5) Scroll to the last and see, the mode will be changed (CHECK SCREENSHOTS IN ATTACHMENTS)
6) Now, Open FolderMount and try to turn on the SymLink/FolderMount you wanted to create or already created.
7) Done! Enjoy your FolderMount or any other app that was creating root problems.
You can say thanks by clicking the thanks button ^_^ :good::laugh::fingers-crossed:

sagargulati said:
For full FolderMount details, Go to this link --> http://forum.xda-developers.com/showthread.php?t=2192122
People who have updated to CM12 or lollipop version are facing several issues regarding FolderMount app is not working, Link2SD etc. (I was one of those) so after taking help from people around, here i present you an easy solution for it.
About CM12 Based Devices (Lollipop 5.0+):
> Since you are on CM12 and we all know it is based on Security-Enhanced Linux (SELinux), you can see this is the basic concept here to make everything work like charm. What you have to do is change the SELinux status to PERMISSIVE MODE from ENFORCING MODE. This will allow the App to Get into with Full Root Access.
> What SELinux does here in ENFORCING MODE is that is limits the root access to be used. It generally stop the access to take all authority rights and moreover concentrating it should not damage your smartphone or tablet.
How to use FolderMount on CM12 Based Devices (Lollipop 5.0+):
1) Go to Play Store and Download SELinux Mode Change App
2) After the App Install, Open the app and allow root access.
3) You will now see ENFORCING MODE already selected.
4) Just click on PERMISSIVE MODE and head to Settings > About Phone.
5) Scroll to the last and see, the mode will be changed (CHECK SCREENSHOTS IN ATTACHMENTS)
6) Now, Open FolderMount and try to turn on the SymLink/FolderMount you wanted to create or already created.
7) Done! Enjoy your FolderMount or any other app that was creating root problems.
You can say thanks by clicking the thanks button ^_^ :good::laugh::fingers-crossed:
Click to expand...
Click to collapse
I think this is wrong place to post this thread, really nice work but wrong place bro.

@hemant4409: Yeah the thread is moved

I've tried to change SELinux mode to Permissive and foldermount was worked, but my phone became not responding. I had to enter recovery mode to wipe the application cache and my phone back to normal. I've tried it twice and i got the same result..
Sent from my GT-I9082 using XDA Free mobile app

Abuarsyad said:
I've tried to change SELinux mode to Permissive and foldermount was worked, but my phone became not responding. I had to enter recovery mode to wipe the application cache and my phone back to normal. I've tried it twice and i got the same result..
Sent from my GT-I9082 using XDA Free mobile app
Click to expand...
Click to collapse
Try this:
Unmount everything > change mode to permissive > reboot > install foldermount, clear data, add new link, add the link again and mark
remove duplication, activate the link/mount, reboot and try.
Also check the root and app has full write permission to folders and files and it's not clashing with any other thing.

sagargulati said:
Try this:
Unmount everything > change mode to permissive > reboot > install foldermount, clear data, add new link, add the link again and mark
remove duplication, activate the link/mount, reboot and try.
Also check the root and app has full write permission to folders and files and it's not clashing with any other thing.
Click to expand...
Click to collapse
Thanks for ur reply, since SELinux related to root previledge, then i tried uninstalling some application which need root access. After that i could change SELinux mode to permissive without any problem..
Sent from my GT-I9082

Abuarsyad said:
Thanks for ur reply, since SELinux related to root previledge, then i tried uninstalling some application which need root access. After that i could change SELinux mode to permissive without any problem..
Sent from my GT-I9082
Click to expand...
Click to collapse
Hit the thanks button if it helped I told you to remove some apps thats clashing root. CM12 comes pre-installed root option, so you don't need to install SuperSU or any third party app to manage root access.

Good, great help, thank you

hzikito said:
Good, great help, thank you
Click to expand...
Click to collapse
If it helped. Please click the thanks button
Keep sharing

Works Perfectly.
Thanks , Changing to permissive mode Works perfectly.sometime after reboot i need to change mode again.
Once again Thnx friend.

kiridhruv said:
Thanks , Changing to permissive mode Works perfectly.sometime after reboot i need to change mode again.
Once again Thnx friend.
Click to expand...
Click to collapse
you can set the app to update the status on every reboot just give the app proper permissions.
It that helped, please do click the thanks button :')

hmm .. there was that option and i have already ticked it. after reboot it shows me to change the mode and do it manually.
i was asking any way it happen automatically, nevermind i dnt have problem to do manually. so Its OKAY. Nice app

Solved
Sagargulati, thanks for your help. I was getting nuts finding out a solution to use foldermount. I have lolllirock installed on Google nexus player. Your solution worked flawlessly.
Thanks.

aamsid said:
Sagargulati, thanks for your help. I was getting nuts finding out a solution to use foldermount. I have lolllirock installed on Google nexus player. Your solution worked flawlessly.
Thanks.
Click to expand...
Click to collapse
No issues if that helped, please share with people and click the thanks button ^_^

Hi
There seems to be an issue with FolderMount and Marshmallow, would these steps work for Marshmallow? Looking at the App updates, it doesn't seem MM is supported yet, do we just need to play the waiting game?

Update the SElinux and change the mode to permissive, then update the folder mount to latest version.
Restart your smartphone and you can add the mounted folders easily.
Give it a try!
Thanks!

Hi
My phone is already set to permissive but how would I update the SELinux? is this done as part of the ROM, how would I check which version I am on? I have resurrection ROM 5.6.2 installed on my galaxy S4 i9505 ROM. I have the latest version of Folde mount installed but it looks like it doesnt say that it supports MM. Have you had this working on MM or are you using it on LL?

ranjb said:
Hi
My phone is already set to permissive but how would I update the SELinux? is this done as part of the ROM, how would I check which version I am on? I have resurrection ROM 5.6.2 installed on my galaxy S4 i9505 ROM. I have the latest version of Folde mount installed but it looks like it doesnt say that it supports MM. Have you had this working on MM or are you using it on LL?
Click to expand...
Click to collapse
download the SElinux mode changer. That will help you!

Hi
Is the app available on play store? When I search for SeLinux mode change it doesn't produce any results for that app, only similar sounding ones.
Would a new version of the ROM i am using automatically update this?
Thanks

Is there a Version for MM?

Gravity box running on marshmallow 6.0.1

Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?

cescman said:
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
Click to expand...
Click to collapse
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.

C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot

cescman said:
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
Click to expand...
Click to collapse
Then it's strange. There must be something different about our devices and the way they are set up. I haven't come across any of these issues whether on N5X or N5. My setup is:
- stock 6.0.1
- modified boot.img which allows SuperSU to work (found in Rooting guide thread in 5X forum)
- xposed framework v78
- GravityBox 6.0.2 (the only module I have installed)

I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.

cescman said:
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
Click to expand...
Click to collapse
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.

C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
C3C076 said:
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
Click to expand...
Click to collapse
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?

cescman said:
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
Click to expand...
Click to collapse
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs

C3C076 said:
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
Click to expand...
Click to collapse
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.

cescman said:
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
Click to expand...
Click to collapse
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.

C3C076 said:
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
Click to expand...
Click to collapse
No, I didn't click fix permissions in recovery, although, as I now remember, installing xposed wasn't that smooth. After installation, I got some error messages saying some services is forced to stop, and I needed several reboots, and the system needed to optimise apps each time before the phone is boot up normally at the end

deleted

Android Q beta 3 wont mount /system as rw

Okay I was able to modify /system on android Q beta 2 just fine but on beta 3 I cant do it no matter what I do. Everything I do either results in "invalid argument" or "/dev/block/sda7 is read only" Heres what Ive done so far:
1. Magisk Canary
2. Boot into TWRP and try mounting there
3. Flashing Q again but with -w
4. Custom Kernel
5. Issuing any mount commands I can think of
6. Resetting back to Pie then updating to Q again
7. Relocking the bootloader and then unlocking it again but this time with unlock_critical (for some reason the phone wouldnt let me do unlock_critical before)
Any help would be greatly appreciated, I need access to /system to edit build.prop to get rid of the navbar and to disable carrier provisioning
Also yes I have verified root works, as my kernel manager can modify kernel related settings

I don't have a "fix" for it unfortunately, but I just wanted to let you know you're not alone. I've experienced the same thing. I tried Magisk Stable and Canary, FX Explorer, Root Explorer, ES Explorer, and a couple of other root file explorers, several busy boxes "versions," setting SELinux to permissive, upgrading to beta file explorers in the Play Store, and on and on. Regardless of what I tried, nothing work to make /system read-writable. I can only assume it's a new security "feature" in Q that apps devs are going to have adjust for. I've left a few messages with some of the devs letting them know about the issue.
Unfortunately, in situations like this, most non-XDA, Play Store devs wait until the new version is official before they bother "fixing" their apps. That means it could be several months from now before it works again, unless it's a bug in Q3, which is entirely possible. If that's the case, the maybe we'll get lucky and Q4 will fix it.
In the meantime, coming to that realization was enough for me to go back to Pie. I've got to be able to make manual changes to /system.
I had a really hard time when I tried to Google search this issue. This issue specifically to do with the Android Q beta 3 doesn't seem to be mentioned anywhere that I came across. I'm going to subscribe to this thread. We can use it to post updates on this issue as new betas come out, or if someone actually finds a way to "fix" it.

Yep having the issues,been through the same processes,I have posted up in the q thread yesterday, apart from this issue the ROM is looking great.

all43 said:
Yep having the issues,been through the same processes,I have posted up in the q thread yesterday, apart from this issue the ROM is looking great.
Click to expand...
Click to collapse
Someone mentioned MiX explorer in that thread, did you try that one. I think I looked for it when I was on Q, but couldn't find it. I don't think I checked XDA though. In any event, they posted a link to it. If you're still on Q, try it out and let us know.
Sent from my Moto G6 using XDA Labs

Mixplorer silver sees system and confirms it's deleted files until you refresh,sadly not working for me

all43 said:
Mixplorer silver sees system and confirms it's deleted files until you refresh,sadly not working for me
Click to expand...
Click to collapse
Someone in the MiX thread said something that makes it's seem like it's a Magisk issue and not a file explorer issue. I've asked them to clarify.
Sent from my Moto G6 using XDA Labs

nice one sharkie, would be a bonus!

Same goes for A10 OTA. There is a updated Magisk 19.4 but still didn't fix /system problem yet.

MiXplorer doesn't mount system rw on android 10. Anyone knows any other method. It has been quite time since we are facing this problem...?

adeelsmatrix said:
MiXplorer doesn't mount system rw on android 10. Anyone knows any other method. It has been quite time since we are facing this problem...?
Click to expand...
Click to collapse
It's due to a fundamental change in Android Q. Topjohnwu had an article explaining it in more detail somewhere. I wouldn't hold your breath for it to be worked around any time soon. You'll have to make due with Magisk modules to accomplish whatever it is you want to do.
I can try and help you out with whatever it is you want to do, either by giving you a link to a module that already exists, or helping you create your own.
Sent from my moto g(6) using XDA Labs

[ROM][FIREOS 5.6.4.0 FOR HD10][Magisk][Gapps][busybox]

Here we are folks latest fireos release for the HD10(Suez) (actual 5.6.4.0) MAY 2019
Deodexed
Removed Kindle special offers aka lock screen ad's
pre-rooted with Magisk 19.1
Disabled OTA
Busybox
changelog V2 5/16/19
fix some wonky dhcp related permissions because amazon doesn't know what the fk they are doing
recommend you guys update asap to avoid wonky wifi
/System increased to 1.6GB to accommodate Gapps
there should be no issue upgrading from previous versions but I have not extensively tested that so if you encounter issues do a factory reset
*Gapps Please do not use hacky tools like fire toolbox. Instead, Install Gapps via TWRP as it is the 'right' way to install Gapps (something reinvent wheel.... )
https://opengapps.org/ 5.1 ARM nano package has been tested and confirmed working **
*it may crash once or twice during account setup but it works just fine once you get logged in
please note that play store version of Amazon apps are NOT Compatible with fireOS exercise caution when allowing apps to update it is highly
recommended you turn auto update OFF, or flash a market detatch script failure todo so will result in you losing amazon stock apps!
if you encounter issues with flashing/updating magisk or do not want root flash the stockboot zip there seems to be a wee bit of jank when flashing over an unclean boot image (an example is if you are updating and already have magisk installed)
the same warning as other stock roms apply do not update magisk from magisk manager use TWRP, flashing modules should be fine
DL:
Rom V2: https://www.androidfilehost.com/?fid=1395089523397966787
Magisk https://github.com/topjohnwu/Magisk/releases/download/v19.1/Magisk-v19.1.zip
Gapps: https://androidfilehost.com/?fid=1395089523397966611
stock boot https://www.androidfilehost.com/?fid=1395089523397965517

Tested this and It's working !

Just a correction your GAPPS link is to an ARM64 package that is not compatible with this tablet. Thankfully the ARM ones work just fine. Thanks for making this great ROM! Running great on my Fire 10 right now!

AngryManMLS said:
Just a correction your GAPPS link is to an ARM64 package that is not compatible with this tablet. Thankfully the ARM ones work just fine. Thanks for making this great ROM! Running great on my Fire 10 right now!
Click to expand...
Click to collapse
this is what I get for uploading at 3am
should be fixed momentarily
edit: link corrected

Just curious, what's the benefit of flashing GAPPS vs other install methods?
Also what's the benefit of having them as system apps? Thanks.

Kctucka said:
Just curious, what's the benefit of flashing GAPPS vs other install methods?
Also what's the benefit of having them as system apps? Thanks.
Click to expand...
Click to collapse
because play services are meant to be installed as a /system app
it will also survive a factory reset
sideloading the apk's can also lead to weird bugs

WiFi? How did you avoid dhcp errors?

DragonFire1024 said:
WiFi? How did you avoid dhcp errors?
Click to expand...
Click to collapse
that was _fixed_ in like 5.6.3 ?
edit apparently it was not fixed
but even this still doesn't like my deco mesh wifi I need to static it to get it through setup and it still randomly disconnects sigh ...
I guess it better look into seeing why its doing that
edit fixed rom updated

Legitsu said:
that was _fixed_ in like 5.6.3 ?
but even this still doesn't like my deco mesh wifi I need to static it to get it through setup
you can also just chmod 755 the configs
i may experiment with replacing the dhcp binaries with ones built from source at a later date
Click to expand...
Click to collapse
I'll have to make a test build and seeif that's what the case was. If so I could kick myself repeatedly. I have a 64 bit build built for this thing, built from AOSP. I have yet to test it. But if you need any of the bins for it, I have them.

deleted see next post for fix to all wifi problems
attached is example updater script

ok so mystery solved once again permission errors
****ing A amazon get it right
@DragonFire1024
boot to recovery
mount system
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
enjoy no more wifi problems
probly could update the updater-script to set_perm and fix it
logcat and grep are your friends use them
you see things *****ing about permission denied its a dead give away

Legitsu said:
ok so mystery solved once again permission errors
****ing A amazon get it right
@DragonFire1024
boot to recovery
mount system
chmod 555 /system/etc/dhcpcd-run-hooks
enjoy no more wifi problems
probly could update the updater-script to set_perm and fix it
logcat and grep are your friends use them
you see things *****ing about permission denied its a dead give away
Click to expand...
Click to collapse
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.

DragonFire1024 said:
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
Click to expand...
Click to collapse
fixxed a typeo lol woops
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
and
chmod 555 /system/etc/wifi_log_levels.sh
I am updating the installer script todo this for you reuploading rom gimme a few

Legitsu said:
fixxed a typeo lol woops
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
I am updating the installer script todo this for you reuploading rom gimme a few
Click to expand...
Click to collapse
I think it's time we checked the permissions in other files this might be worth a shot at fixing the rest of the problems these things have with Wi-Fi.
Edit: has anyone uninstalled the wifi locker app yet? The only thing it has permissions to do is upload and store credentials or something to that nature but I don't think it has anything to do with storing Android credentials.

DragonFire1024 said:
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
Click to expand...
Click to collapse
you can confirm its the issue with
logcat | grep dhcp
and
locat | grep wifi
look for the permission errors
some of these daemons are executed under a different group which leads to issues
this occurs even on a virgin untouched tablet
I should have posted this a long time ago I have known about it for a year just have not had time lol

Legitsu said:
you can confirm its the issue with
logcat | grep dhcp
and
locat | grep wifi
look for the permission errors
Click to expand...
Click to collapse
I don't doubt you for a second because I figured the Wi-Fi log levels script was causing the issues and though it didn't fix it it seems to have stopped a lot of the reconnect disconnect issues the things seem to have with jumping back and forth to different Wi-Fi networks so I deleted it, at least on other builds but none that I put out to you guys. So it does make a lot of sense however I still kick myself in the ass for not checking permissions first.

DragonFire1024 said:
I don't doubt you for a second because I figured the Wi-Fi log levels script was causing the issues and though it didn't fix it it seems to have stopped a lot of the reconnect disconnect issues the things seem to have with jumping back and forth to different Wi-Fi networks so I deleted it, at least on other builds but none that I put out to you guys. So it does make a lot of sense however I still kick myself in the ass for not checking permissions first.
Click to expand...
Click to collapse
the major problem was the dhcp hooks without that dhcp does not work properly
it also for whatever reason needs to be 555 775/660 will not do it don't ask me why I tried it both ways it only works 0 2000 0555
I blame amazon

rom updated op updated
amazon made aware of the problem hopefully will get fixed so you don't need to root your device to have wifi that works

Legitsu said:
the major problem was the dhcp hooks without that dhcp does not work properly
it also for whatever reason needs to be 555 775/660 will not do it don't ask me why I tried it both ways it only works 0 2000 0555
I blame amazon
Click to expand...
Click to collapse
It would make sense if they wanted to throw off whoever could successfully pull off deodexing. It wasn't easy pre twrp. I had to do it piece by piece, and only some of the manually replaced ones worked. But you are right I've never seen those files with 555 before.
Sent from my Droid Razr M using XDA Labs

DragonFire1024 said:
It would make sense if they wanted to throw off whoever could successfully pull off deodexing.
Click to expand...
Click to collapse
Lol. Do you seriously think some engineer at Amazon (or whomever they contract with) is charged with scheming up bizarre ways to throw off the miniscule community of deodexers? Too much daytime TV.

Question LE2123_11_F.75

Has been released and distributed by Oxygen Updater

Already installed

What do you think about it?

Phone on .74 version was eating 3% of battery overnight, now on .75 version 11% overnight.

neotion said:
Phone on .74 version was eating 3% of battery overnight, now on .75 version 11% overnight.
Click to expand...
Click to collapse
Oof

neotion said:
Phone on .74 version was eating 3% of battery overnight, now on .75 version 11% overnight.
Click to expand...
Click to collapse
Try to force the app optimization with the command below if u have root.
su -c "cmd package bg-dexopt-job"

davyleggend said:
Try to force the app optimization with the command below if u have root.
su -c "cmd package bg-dexopt-job"
Click to expand...
Click to collapse
after the update i didn't change any settings and i didn't add any new apps. Won't this optimization close my apps that need to run in the background?

neotion said:
after the update i didn't change any settings and i didn't add any new apps. Won't this optimization close my apps that need to run in the background?
Click to expand...
Click to collapse
After any firmware update u need to do the app optimization, if u don't have root u need to keep the phone on charging for a while after reach 100% and it do automatically

thank you very much, it's interesting what you write - I'm still learning new things.. Yes, I have root. I will do this command through ADB on the phone connected to the PC?

neotion said:
thank you very much, it's interesting what you write - I'm still learning new things.. Yes, I have root. I will do this command through ADB on the phone connected to the PC?
Click to expand...
Click to collapse
U can download material terminal app from the play store. Give it the root access with the "su" command (without the "") and next do the command i wrote. Wait until it says "done". If u do the command and it finish in a couple of seconds probably your apps it's already optimized, if not it take a while.

davyleggend said:
U can download material terminal app from the play store. Give it the root access with the "su" command (without the "") and next do the command i wrote. Wait until it says "done". If u do the command and it finish in a couple of seconds probably your apps it's already optimized, if not it take a while.
Click to expand...
Click to collapse
Thx! I'll check it

Hi guys, I'm looking for some information. I'm on f.73 with root and unlocked bootloader. Can I update to f.74 of f.75 without a computer and retain root and not loose any data? If so, how do I go about this? I don't want to wipe any of my data

cybrid3 said:
Hi guys, I'm looking for some information. I'm on f.73 with root and unlocked bootloader. Can I update to f.74 of f.75 without a computer and retain root and not loose any data? If so, how do I go about this? I don't want to wipe any of my data
Click to expand...
Click to collapse
Use Oxygen Updater app and follow the instructions

Upgraded from f.72 to f.75. However, I now have no AOD, ambient display setting. I can't find such a menu item in Settings.

Always on display and ambient display are there for me ( le2123 )
The attached pictures will show you where it should be.

AndyC76 said:
Always on display and ambient display are there for me ( le2123 )
The attached pictures will show you where it should be.
Click to expand...
Click to collapse
Interesting that I did a local update and then got AOD and ambient display setting. Then I rooted it and then no again.

klasszsrac said:
Interesting that I did a local update and then got AOD and ambient display setting. Then I rooted it and then no again.
Click to expand...
Click to collapse
Is your phone 100% stock with no modifications?

I think there may be a solution. I used the installer suggested by Steve0007 in this forum. https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-13-f21-f75.4252373/
The a/b partition caused the update to be installed on one of the partitions, but I think incorrectly. Since you showed that there is an AOD setting, I thought I would update again, but I used the system's own installer. In this case it switches partitions and then the new installation starts, which was fine. But then I didn't root it straight away. I had AOD set. Then I rooted and I think it switched partition again, which started with the wrong installation. Again, no AOD. Then today the new v26.0 magisk came out. I did a magisk update. I think it will start with a different partition again. Then the partition installed correctly started with a working root.
So now I have root and I have working AOD and ambient display. I think I will leave it like this until there is another update

davyleggend said:
Try to force the app optimization with the command below if u have root.
su -c "cmd package bg-dexopt-job"
Click to expand...
Click to collapse
I got "failure* after this command. I have a root with magisk and the last update of oos13.

Sergykm said:
I got "failure* after this command. I have a root with magisk and the last update of oos13.
Click to expand...
Click to collapse
I noticed it too, it's a problem of oos13. I don't find any working command. Now I'm on Nameless and the command work.