can confirm internet is slow with this mod. and my internet is 100mb fibre optics. so my net is not slow without this mod. android does a great job of handling things. there is no need for snake oil "mods" that cause issues
elsa:/ $ su
elsa:/ # system/engine/feradroid.sh
chmod: /sdcard/Android/FDE_config.txt: No such file or directory
Syntax error in "allow mediaserver mediaserver_tmpfs:file { read write execute }"
Supported policy statements:
"allow #source-class #target-class permission-class #permission"
"deny #source-class #target-class permission-class #permission"
"auditallow #source-class #target-class permission-class #permission"
"auditdeny #source-class #target-class permission-class #permission"
"typetrans source-class target-class permission-class default-class (optional: object-name)"
"allowxperm #source-class #target-class #permission-class ioctl range"
"auditallowxperm #source-class #target-class #permission-class ioctl range"
"dontauditxperm #source-class #target-class #permission-class ioctl range"
"create #class"
"permissive #class"
"enforcing #class"
"attradd #class #attribute"
source-class and target-class can be attributes (patches the whole group)
All sections (except typetrans) can be replaced with '*' to patch every possible matches
Sections marked with '#' can be replaced with collections in curly brackets
e.g: allow { source1 source2 } { target1 target2 } permission-class { permission1 permission2 }
Will be expanded to:
allow source1 target1 permission-class permission1
allow source1 target1 permission-class permission2
allow source1 target2 permission-class permission1
allow source1 target2 permission-class permission2
allow source2 target1 permission-class permission1
allow source2 target1 permission-class permission2
allow source2 target2 permission-class permission1
allow source2 target2 permission-class permission2
Syntax error in "allow audioserver audioserver_tmpfs:file { read write execute }"
Supported policy statements:
"allow #source-class #target-class permission-class #permission"
"deny #source-class #target-class permission-class #permission"
"auditallow #source-class #target-class permission-class #permission"
"auditdeny #source-class #target-class permission-class #permission"
"typetrans source-class target-class permission-class default-class (optional: object-name)"
"allowxperm #source-class #target-class #permission-class ioctl range"
"auditallowxperm #source-class #target-class #permission-class ioctl range"
"dontauditxperm #source-class #target-class #permission-class ioctl range"
"create #class"
"permissive #class"
"enforcing #class"
"attradd #class #attribute"
source-class and target-class can be attributes (patches the whole group)
All sections (except typetrans) can be replaced with '*' to patch every possible matches
Sections marked with '#' can be replaced with collections in curly brackets
e.g: allow { source1 source2 } { target1 target2 } permission-class { permission1 permission2 }
Will be expanded to:
allow source1 target1 permission-class permission1
allow source1 target1 permission-class permission2
allow source1 target2 permission-class permission1
allow source1 target2 permission-class permission2
allow source2 target1 permission-class permission1
allow source2 target1 permission-class permission2
allow source2 target2 permission-class permission1
allow source2 target2 permission-class permission2
mount: '/dev/block/bootdevice/by-name/userdata'->'/data': Device or resource busy
system/engine/feradroid.sh[97]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[98]: mount: not found
system/engine/feradroid.sh[99]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[100]: mount: not found
system/engine/feradroid.sh[101]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[106]: sync: not found
system/engine/feradroid.sh[107]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[108]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[109]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[110]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[111]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[112]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[113]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[114]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[115]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[116]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[117]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[155]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[155]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[163]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[164]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[167]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[250]: sync: not found
system/engine/feradroid.sh[251]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[252]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[253]: sysctl: not found
system/engine/feradroid.sh[254]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[268]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[269]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[270]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[270]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[271]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[272]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[272]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[273]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[273]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[274]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[274]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[275]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[276]: sync: not found
system/engine/feradroid.sh[277]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[292]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[292]: setenforce: not found
system/engine/feradroid.sh[292]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[292]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[293]: setprop: not found
system/engine/feradroid.sh[294]: setprop: not found
system/engine/feradroid.sh[295]: setprop: not found
system/engine/feradroid.sh[296]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[297]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[298]: service: not found
system/engine/feradroid.sh[299]: setprop: not found
system/engine/feradroid.sh[300]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[301]: svc: not found
system/engine/feradroid.sh[302]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[303]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[304]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[305]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[306]: can't create /system/engine/prop/score: No such file or directory
system/engine/feradroid.sh[307]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[308]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[309]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[310]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[311]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[312]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[313]: msg: not found
system/engine/feradroid.sh[314]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[315]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[316]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[317]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[318]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[319]: msg: not found
system/engine/feradroid.sh[320]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[321]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[322]: msg: not found
system/engine/feradroid.sh[326]: sync: not found
system/engine/feradroid.sh[327]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[328]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[329]: mount: not found
system/engine/feradroid.sh[335]: /system/engine/bin/busybox: not found
system/engine/feradroid.sh[335]: grep: not found
system/engine/feradroid.sh[335]: cut: not found
system/engine/feradroid.sh[358]: sync: not found
system/engine/feradroid.sh[359]: /system/engine/bin/busybox: not found
elsa:/ #
Flashed on my V20 and let it sit 5 minutes without touching it. I never got the toast notification or the vibration. I flashed it 2 more times after I read to mount system in this thread and still nothing, no logs either. Now I do have your boot animation every time I restart my phone.
NAFT MEGAROM v5
Latest magisk with xposed
If xposed is the culprit that will suck because I need xposed lol. The boot animation is cool so it's not bothering me hahaI think Xposed is the problem. Just use your backup to get back.
Lol... Ok. Yeah somethings ya gotta decide one or the other. Did you run the uninstaller? It may take you back to normal in boot.If xposed is the culprit that will suck because I need xposed lol. The boot animation is cool so it's not bothering me haha
I'll keep xposed but I just wanna thank the dev for this!Lol... Ok. Yeah somethings ya gotta decide one or the other. Did you run the uninstaller? It may take you back to normal in boot.
I think Xposed is the problem. Just use your backup to get back.
Well if it is Xposed that's very disappointing and a bit rediculous. Nowhere in the OP is it mentioned that this may conflict with Xposed or anything else for that matter. I'll have t stick with Xposed myself because rely on it for serveral other critical functions (like microg) but it should really be added to the modes description that it is incompatible with Xposed if that indeed the case.
Tried installing feradroid twice so far and both times it installed successfully with no issues and gave me a score inside the log with an ok confirmation but both times it resulted in my V20 becoming extremely sluggish randomly. It was very inconsistent as it would be pretty quick in one app then as soon as I go to next app it would look like a slideshow with how much it was stuttering on certain animations. I would get the toast confirmation and the 3 vibrations as well as the successful installation log
One example was the XDA labs slide out menu. For some reason it would stutter everytime I opened and closed it.
I'm on NATF MEGArom V4. 1st time I was coming off of L Speed so I thought maybe it didn't uninstall properly so I installed a fresh ROM with no other mods and it still did the same thing. Anyone have any troubleshooting tips to try?
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
What's worst than this is that he was making fun of the module author on xda discord. He said "Imagine being this guy, lol" after posting a photo of feravolt's comment (where he said he's depressed)
First of all, I don't even know him personally, he never contacted me or my friends, advising or pointing on mistakes or whatever. And so I don't understand why he publically offends me & my work.
This is what you should know about his personality first. This type of behavior kinda reminds me YaroST.
1. "But FDE.AI also overrides the manufacturer’s values." - I am OK with that. They provide those tunables for tuning. So why not.
3. https://github.com/feravolt/FDE-sc/blob/master/fde.c#L1124 > this code is valid for only for 2.6.x kernels (very old devices), and it realy does improve UX a lot since I personally tested that on my 2011's device. For rest kernels this is simply not applied. I might just add kernel version check.
5.1 "dumbest choices for tuning your I/O device" + https://github.com/feravolt/FDE-sc/blob/master/fde.c#L1217 > This code should fix rare deep-sleep issues on older kernels and as per my tests (I do own 2 UFS & 2 MMC devices), does not impact performance. I might add kernel version check before apply here too and/ro simply remove this string.
5.2 Will change that to single hit merge and/or check for storage type, because on slow MMCs this helps a lot in write speed.
5.3 I did researched about this and know what this option do. With my value it showed a better result in benchmarks which may fooled me up. Will research about this more.
6.2 That's true - I mixed this up with f2fs fsync_mode=nobarrier.
arter97@arter97-x1:/tmp/FeraDroid-Engine$ git log -1 @
commit f05275e7ed01827d34cd8d7947aa17f71796b1a4 (HEAD)
Author: FeraVolt <fera.volt@gmail.com>
Date: Sat Jul 22 17:49:07 2017 +0600
Merge to v.1.1-rel
arter97@arter97-x1:/tmp/FeraDroid-Engine$ git grep nobarrier
system/engine/feradroid.sh: $B mount -o remount,noatime,nodiratime,nobarrier,discard "${x}";
system/engine/gears/io.sh: $B mount -o remount,noatime,nodiratime,nobarrier,discard "${x}";
Also nobarrier (in rare cases) could corrupt FS, not physically destroy block. I believe that none of existing FS mount flags can actually physically destroy a block. (Don't mix up with file system corruption)