Related
hi sorry about my english
Have anyone tried the module of Dual touch for Cypress touchpad on
GingerDX | v004??????????????
please help me i cant to build the multi touch in rom
GingerDX | v004 what can i do?
tam3xx said:
hi sorry about my english
Have anyone tried the module of Dual touch for Cypress touchpad on
GingerDX | v004??????????????
please help me i cant to build the multi touch in rom
GingerDX | v004 what can i do?
Click to expand...
Click to collapse
At least, post what You´ve been done already. Pushed the modules to /system/lib/modules and tried to insmod it??? Or you don´t know how to start it?
I've done this. Works.
Put modul .ko in system where to have to be (system/lib/modules), execute command in terminal emulator (can't remeber this command, search this topic), check with multitouch visualiser 2, if ok check with internet app or google maps, should be ok.
Then u can add line with this modul to startup the system in hw_config.sh (as topis says) and that's all.
mr-tical said:
I've done this. Works.
Put modul .ko in system where to have to be (system/lib/modules), execute command in terminal emulator (can't remeber this command, search this topic), check with multitouch visualiser 2, if ok check with internet app or google maps, should be ok.
Then u can add line with this modul to startup the system in hw_config.sh (as topis says) and that's all.
Click to expand...
Click to collapse
the command is:
Code:
insmod /system/lib/modules/ax8mt.ko
I think
You're right
mr-tical said:
I've done this. Works.
Put modul .ko in system where to have to be (system/lib/modules), execute command in terminal emulator (can't remeber this command, search this topic), check with multitouch visualiser 2, if ok check with internet app or google maps, should be ok.
Then u can add line with this modul to startup the system in hw_config.sh (as topis says) and that's all.
Click to expand...
Click to collapse
thanks for answering but the system/lib/modules not working in this rom
and i change the hw_config.sh and not working again what can i do
perhabs other method are working i dont know any body do this for this rom?
Are you sure you have a cypress digitizer? Read this thread carefully and check: http://forum.xda-developers.com/showthread.php?t=1135965
When you copy the module into /system/lib/modules make sure you actually copy the module, not the .zip file, and check the permissions on the module they should match those of the other modules.
tam3xx said:
thanks for answering but the system/lib/modules not working in this rom
and i change the hw_config.sh and not working again what can i do
perhabs other method are working i dont know any body do this for this rom?
Click to expand...
Click to collapse
This method works on this rom,i've done that and it works
sent from x8 with tapatalk
the GingerDX | v004 is not complate root and the chenge to hw_config is not possibel and not working in this rom and u can do the multi touch whit termillator
but when restart the multi touch terminate and not working
i like the rom with the moulti toch and i like this rom but i cant create stabel
multi touch what can i do????
tam3xx said:
the GingerDX | v004 is not complate root and the chenge to hw_config is not possibel and not working in this rom and u can do the multi touch whit termillator
but when restart the multi touch terminate and not working
i like the rom with the moulti toch and i like this rom but i cant create stabel
multi touch what can i do????
Click to expand...
Click to collapse
I don't understand, what u say is that it is not possible to edit hw_config and save changes etc in this rom to make this works??
Please repeat, slower and give a try to understand u
Basically, paste ax8mt.ko into /system/lib/modules
Then, type in terminal emulator:
su *hit enter button*
insmod /system/lib/modules/ax8mt.ko *hit enter button*
afterwards, check multitouch.
If working, edit /etc/hw_config.sh using a text editor (not notepad). Add these lines:
# Multitouch by AnDyX *hit enter*
insmod /system/lib/modules/ax8mt.ko *hit enter*
Then save files and then reboot and then you're done. Don't forget to make a backup in xRecovery or CWM recovery first in case something happens.
I have ginger dx v013 and i put the ax8mt.ko in the modules folder but there is one ax8mt.ko. I get to the part insmod /system/lib/modules/ax8mt.ko *hit enter button* and i get an answer not permitted....what to do?
try reinstalling superuser
or maybe change some permissions using root explorer
Questioner said:
try reinstalling superuser
or maybe change some permissions using root explorer
Click to expand...
Click to collapse
The problem is that my root explorer keeps crashing when i run it so i used bs explorer to copy that file. :/. I gona try full whipe
maybe install another rom
like gc
Gc? Remind me, gingercruize or somthing like that? Is it better then gingerdx?
gawran1 said:
Gc? Remind me, gingercruize or somthing like that? Is it better then gingerdx?
Click to expand...
Click to collapse
DX rom is still in development so i suggest Kuyadroid, it has great battery life and its smooth. Return to DX later when its fully complete. If you can stay away from it for that long
Sent from my X8 using XDA App
Yea dx is awesome .
Kuyadroid is better? I didint know, i must try it. Ty
One more thing, Kuyadroid is updating every few weeks so its not fully complete eather?
hi..i want to format my phone coz im suspecting a virus. im using floyo 1.0 and tried some other roms,but i usually get random reboot.tried scanning for virus but not working. so i really need any step by step guide or tips on how i can format my phone safely or any of u have tips on how to help me.sorry if im reposting but i cant find any post about this.
any help will be mostly appreciated...
maliceomalice said:
hi..i want to format my phone coz im suspecting a virus. im using floyo 1.0 and tried some other roms,but i usually get random reboot.tried scanning for virus but not working. so i really need any step by step guide or tips on how i can format my phone safely or any of u have tips on how to help me.sorry if im reposting but i cant find any post about this.
any help will be mostly appreciated...
Click to expand...
Click to collapse
Those random reboots can be caused by a number of things, but, in this instance you should put "virus" at the bottom of the list. Since your using customs ROMS, first to check is overclock, you might be pushing your Phone's CPU/GPU too hard.
I would assume you have a rooted phone and using a custom ROM. Reboot to Xrecovery and wipe user data. Next reformat your SDcard. reboot and you'll have a "clean" phone.
ok..i'll try.thanks
viper001 said:
Since your using customs ROMS, first to check is overclock, you might be pushing your Phone's CPU/GPU too hard.
Im using floyo 1.0 so how should i manage to avoid pushing CPU/GPU too hard?
xperia x8 proud owner
Click to expand...
Click to collapse
If you have root explorer. go to system\lib\modules. check and see if you do have the overclock module. also check if you have the undervolt module. Make sure R/W is enable and Move the OC and UV Module to the SDCARD as backup. Reboot and test you phone if its still randomly rebooting.
alternatively, you can check setting >> cyanogenmod settings >>performance >> cpu settings. if there is and you find CPU can be adjusted then reduce the clock to around 691Mhz.
Another option is to install CPUMaster or SETCPU to adjust clock speed.
viper001 said:
If you have root explorer. go to system\lib\modules. check and see if you do have the overclock module. also check if you have the undervolt module. Make sure R/W is enable and Move the OC and UV Module to the SDCARD as backup. Reboot and test you phone if its still randomly rebooting.
i surely have OC no UV module.so must i install UV and then move them to SD..? or i just install UV module and see what happen..?
Click to expand...
Click to collapse
maliceomalice said:
viper001 said:
If you have root explorer. go to system\lib\modules. check and see if you do have the overclock module. also check if you have the undervolt module. Make sure R/W is enable and Move the OC and UV Module to the SDCARD as backup. Reboot and test you phone if its still randomly rebooting.
i surely have OC no UV module.so must i install UV and then move them to SD..? or i just install UV module and see what happen..?
Click to expand...
Click to collapse
try to remove the oc module first. see if that make it stable.
Click to expand...
Click to collapse
i tried benchmark and i get 400+ only. Is that normal?
xperia x8 proud owner
I have been looking through the recent ICS threads and people have had alot of out of memory problems, so I thought I would post this easy to understand tutorial (well I hope it will be easy to understand)
Before starting, on Miroslav's Project Icecream Swift, you need to download busybox installer and install version 1.18.2, busybox included will not correctly determine minfrees.
First download the latest version of V6 at the end of this post, then copy it to your SD card and run it with Script Manager (from the market).
Choose your prefered scrolling speed and in the latest version its pretty much automated, you just have to say yes no a few times but it will auto detect the best settings based on the RAM of the device.
Also do not superclean and reboot, we need to do something else before we reboot.
Ensure you have a file explorer that can view the /system partiton before continuing.
On your phone browse to http://android.mimic.ca
Then click browse and choose your file explorer, and find services.jar in /system/framework then upload it.
After this the site will modify the services.jar and offer a download for it, to make it easy lets just use the update.zip so select that and download it.
Using the stock browser atleast it will go to /sdcard/download.
After this reboot to recovery, scroll to mounts and storage and mount /system manually (when I did not do this it didn't write the modified file) then install the zip.
Wipe dalvik cache and reboot, first boot will take a long time while its upgrading applications then run the V6 supercharger script to confirm you are 100% supercharged and you have your hard to kill or die hard launcher.
Note: On AOKP (atleast this version) because it doesn't have init.d (think its that one) before you first reboot to install services.jar you will need to browse in script manager to /data and find the 99SuperCharger.sh file and make it run on boot to get 100% supercharged.
I don't know if its important but every new rom I use I repatch services.jar just to be safe.
Any questions post here (also if the file doesn't download let me know and I'll upload it and post the link.)
Recovery zips for AOKP and Icecream Swift services.jar can be found below, just mount /system manually and i"nstall zip from sdcard" sorry it took a bit
For me i just use swap works good enough
For me not. Even if i use swap when i try to use gplay and listen music, music app closes itself. (Miro's latest ron)
Sent from my GT540 using xda premium
coto39 said:
For me not. Even if i use swap when i try to use gplay and listen music, music app closes itself. (Miro's latest ron)
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
Thats because swap is not technically used as RAM, what it does is suspends background apps using up RAM, then puts that state in to swap, the apps cannot run from the swap partition, so if you are listening to music and using the browser you will notice this, if you have twitter open, then open a link from a twitter post, the state of twitter gets pushed to the swap partition, to allow the browser to open and run, you then close the browser and it pulls twitter from the swap partition back to RAM giving the illusion of multitasking.
V6 actually gives multitasking by making sure android does not close apps when you have a fair amount of RAM left.
delsus said:
Thats because swap is not technically used as RAM, what it does is suspends background apps using up RAM, then puts that state in to swap, the apps cannot run from the swap partition, so if you are listening to music and using the browser you will notice this, if you have twitter open, then open a link from a twitter post, the state of twitter gets pushed to the swap partition, to allow the browser to open and run, you then close the browser and it pulls twitter from the swap partition back to RAM giving the illusion of multitasking.
V6 actually gives multitasking by making sure android does not close apps when you have a fair amount of RAM left.
Click to expand...
Click to collapse
Thanks for the explanation. I tried to apply supercharger (latest version, Update9RC8.2) to IceCreamSwift second official release bug when it try to apply minfrees the phone reboots.... The version you left works but don't shoy current minfrees, just shows: , , , , ,
coto39 said:
Thanks for the explanation. I tried to apply supercharger (latest version, Update9RC8.2) to IceCreamSwift second official release bug when it try to apply minfrees the phone reboots.... The version you left works but don't shoy current minfrees, just shows: , , , , ,
Click to expand...
Click to collapse
Hmm thats wierd, I have always been able to see them, but if it works it works
delsus said:
Hmm thats wierd, I have always been able to see them, but if it works it works
Click to expand...
Click to collapse
Don't know why but everytime i try to use the script with latest miroslav ICS i got an exception when try to appy supercalculator minfrees then a reboot.
With latest version of the script i can see original minfrees= "1,1,1,1,1,1,1" and when i try to apply new one = Poof! reboot!
Did you installed another busybox or something?... This rom without the script sucks in multitasking matter. (open one app and the others will be closed, is monotasking )
coto39 said:
Don't know why but everytime i try to use the script with latest miroslav ICS i got an exception when try to appy supercalculator minfrees then a reboot.
With latest version of the script i can see original minfrees= "1,1,1,1,1,1,1" and when i try to apply new one = Poof! reboot!
Did you installed another busybox or something?... This rom without the script sucks in multitasking matter. (open one app and the others will be closed, is monotasking )
Click to expand...
Click to collapse
I'll check it on new version of miro's rom tonight when I charge my phone (battery is dead right now) but I normally use the default busybox, it could be that the default has been changed on this rom, download busybox installer from the market and try a version on there, they are all complete so should have no problems on that end, lemme know if it still doesn't work.
delsus said:
I'll check it on new version of miro's rom tonight when I charge my phone (battery is dead right now) but I normally use the default busybox, it could be that the default has been changed on this rom, download busybox installer from the market and try a version on there, they are all complete so should have no problems on that end, lemme know if it still doesn't work.
Click to expand...
Click to collapse
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
coto39 said:
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
Click to expand...
Click to collapse
Hmm, I'll try myself soon, havent noticed the problem before, I'll report back
coto39 said:
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
Click to expand...
Click to collapse
Ok I just resupercharged my phone running miroslav's rom, and I did see your problems, I fixed it downloading busybox installer and using busybox version 1.18.2 and it will detect your minfrees.
Also updated OP with this info and the patched services.jar files.
delsus said:
Ok I just resupercharged my phone running miroslav's rom, and I did see your problems, I fixed it downloading busybox installer and using busybox version 1.18.2 and it will detect your minfrees.
Also updated OP with this info and the patched services.jar files.
Click to expand...
Click to collapse
I did this, but when i run the script for second time to confirm if it worked, it says:
Launcher is DIE-HARD! ie. SUPERCHARGED
but after says:
OOM Grouping Fixes ARE NOT in Effect
...
Current values DON'T MATCH Prior SuperCharge!
this means that didn't worked???
I use miroslav last update 20/05/12
arperalta3 said:
I did this, but when i run the script for second time to confirm if it worked, it says:
Launcher is DIE-HARD! ie. SUPERCHARGED
but after says:
OOM Grouping Fixes ARE NOT in Effect
...
Current values DON'T MATCH Prior SuperCharge!
this means that didn't worked???
I use miroslav last update 20/05/12
Click to expand...
Click to collapse
Did you use busy box installer to install busy box or are you just using the version pre installed? The CM9 one will not work with V6.
Sent from my LG-GT540 using XDA
delsus said:
Did you use busy box installer to install busy box or are you just using the version pre installed? The CM9 one will not work with V6.
Sent from my LG-GT540 using XDA
Click to expand...
Click to collapse
I used busybox installer to get the version 1.18.2
arperalta3 said:
I used busybox installer to get the version 1.18.2
Click to expand...
Click to collapse
Using root explorer check /system/etc/init.d and see if there is a supercharger script in there.
If not try supercharging again, reboot and check, if its still not working find the 99supercharger.sh script and select "run on boot" and reboot, it should work after this.
delsus said:
Using root explorer check /system/etc/init.d and see if there is a supercharger script in there.
If not try supercharging again, reboot and check, if its still not working find the 99supercharger.sh script and select "run on boot" and reboot, it should work after this.
Click to expand...
Click to collapse
thanks, the script is in /system/etc/init.d, i will try to run the script with the option "run on boot" in script manager later
arperalta3 said:
thanks, the script is in /system/etc/init.d, i will try to run the script with the option "run on boot" in script manager later
Click to expand...
Click to collapse
Before you select "run on boot" just try to supercharge again, something could have messed up a little when you applied the minfrees, init.d scripts should run on boot anyway.
delsus said:
Before you select "run on boot" just try to supercharge again, something could have messed up a little when you applied the minfrees, init.d scripts should run on boot anyway.
Click to expand...
Click to collapse
weird weht i run the script in the end it says that everything is ok and active, but when i reboot and clean davilk chache and run again, it says that isnt ok
I have applied V6 Supercharge on this IceCreamSwift ROM. If I do Wipe Data/Factory Reset, do I need to apply V6 again?
Yes
Hi,
Sometimes in Lollipop some module don't work. Then, in my case I reboot to recovery and I touch the file "conf/disabled" for starting without Xposed. After that, I like to disable the module in the UI of the Xposed Installer App... but when the framework is disabled, this option is disabled.
Please, can you change this?
Thank you!
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
manos78 said:
Hi,
Sometimes in Lollipop some module don't work. Then, in my case I reboot to recovery and I touch the file "conf/disabled" for starting without Xposed. After that, I like to disable the module in the UI of the Xposed Installer App... but when the framework is disabled, this option is disabled.
Please, can you change this?
Thank you!
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
Click to expand...
Click to collapse
Why don't you just disable the module, reboot, enable the module again and reboot again? No need to place any files through recovery?
By the way: could you give us more information about your device, the Android version and the Xposed files you use? Those are important information, without them nobody might help you.
orville87 said:
Why don't you just disable the module, reboot, enable the module again and reboot again? No need to place any files through recovery?
Click to expand...
Click to collapse
Because the device don't boot (bootloop on the boot animation)!!!
So, in this case the ONLY solution is: boot to recovery, touch the "disable" file, reboot with Xposed disabled... and then: How to DISABLE the module? The UI is blocking the option of enable/disable modules when the framework is disabled!
Please, remove this arbitrious limitation in the UI.
Thank you!
Why don't you just delete the modules.list inside the
data/data/de.robv.android.xposed.installer/conf/
folder?
corncobman said:
Why don't you just delete the modules.list inside the
data/data/de.robv.android.xposed.installer/conf/
folder?
Click to expand...
Click to collapse
Good alternative, but this disables all modules and you lost the info related to enabled/disabled modules... or not?
manos78 said:
Good alternative, but this disables all modules and you lost the info related to enabled/disabled modules... or not?
Click to expand...
Click to collapse
Yes, this method disables all modules. But what info related to enabled/disabled modules are you talking about? Which modules have been enabled and which not?
... you lost the info related to enabled/disabled modules... or not?
Click to expand...
Click to collapse
Not. The list of which modules are selected and which are not selected are still shown. Just disable the offending module and reboot.
corncobman said:
Not. The list of which modules are selected and which are not selected are still shown. Just disable the offending module and reboot.
Click to expand...
Click to collapse
Then you recommend "delete this file" instead of "touch the disable file" for disable only the loading of the modules but enable the framework? Then, when rebooting the phone the module list will be re-created?
The module list will be created when you change the list, i.e. toggle one module on or off. The changes only apply when you reboot.
manos78 said:
Then you recommend "delete this file" instead of "touch the disable file" for disable only the loading of the modules but enable the framework? Then, when rebooting the phone the module list will be re-created?
Click to expand...
Click to collapse
Do you want to permanently disable the module that causes the issue or do you want to use the module again after reboot?
In the first case, you can delete the corresponding module by using the in-build file manager of your recovery. Just navigate to /data/app and delete the module's folder. Done.
Otherwise, you only have the limited options presented to you (but I don't know why someone would continue using a module that is causing issues again and again).
orville87 said:
Do you want to permanently disable the module that causes the issue or do you want to use the module again after reboot?
In the first case, you can delete the corresponding module by using the in-build file manager of your recovery. Just navigate to /data/app and delete the module's folder. Done.
Otherwise, you only have the limited options presented to you (but I don't know why someone would continue using a module that is causing issues again and again).
Click to expand...
Click to collapse
Hi, I agree!
However, when a module "fails" I don't like to uninstall it... I like only to disable it. Why? Because I like to contact with the author and try fix the bug. Sometimes the problem is an update, o some other times the module is part of an App that has another functionalities. Then the best option is disable the module and not uninstall/remove it.
So, my concern is related to the best option to fix a bootloop when a module is creating some interference. Until now my best option is disable the Xposed framework, but here the recomendation is disable the load of modules. In this last case, I need to know if this file is re-created by the Xposed framework. And however, I feel is a good recomendation to enable the UI of the modules when the framework is disabled... the current behaviour is annoying.
Regards!
manos78 said:
Hi, I agree!
However, when a module "fails" I don't like to uninstall it... I like only to disable it. Why? Because I like to contact with the author and try fix the bug. Sometimes the problem is an update, o some other times the module is part of an App that has another functionalities. Then the best option is disable the module and not uninstall/remove it.
So, my concern is related to the best option to fix a bootloop when a module is creating some interference. Until now my best option is disable the Xposed framework, but here the recomendation is disable the load of modules. In this last case, I need to know if this file is re-created by the Xposed framework. And however, I feel is a good recomendation to enable the UI of the modules when the framework is disabled... the current behaviour is annoying.
Regards!
Click to expand...
Click to collapse
Ah, I see your point there. Well, I have some thoughts about another possibility. I haven't tried it yet, so no guarantee can be given if this will work. But before updating a module, you could backup the folder of the module from /data/app and place it's backup folder somewhere else. Then update the module and reboot. When facing a bootloop, just use the recovery file manager to replace the new files of the module with the old ones and reboot. This way one does not have to disable all modules or even disable/uninstall the entire framework.
orville87 said:
This way one does not have to disable all modules or even disable/uninstall the entire framework.
Click to expand...
Click to collapse
Yes, but I like the most simple option: At time, I do this when bootloop:
a) Reboot to recovery.
b) Open Aroma File Manager.
c) Rename "_disabled" to "disabled" in the xposed/config directory
d) Reboot
And when the device boots, I like to "disable" in the Xposed App... the problem is the UI... it disables interaction when the framework ins't loaded. From my point of view is a mistake! Why force this? Any reason that I don't view?
Another option is remove the file with the list of modules, but I don't know if the Xposed App recreates this file after boot, and if it's maintains the selected/unselected list of modules (normally I have some modules installed but disabled... think on Apps with Xposed add-ons that I don't like to use!).
Any comment?
manos78 said:
Yes, but I like the most simple option: At time, I do this when bootloop:
a) Reboot to recovery.
b) Open Aroma File Manager.
c) Rename "_disabled" to "disabled" in the xposed/config directory
d) Reboot
And when the device boots, I like to "disable" in the Xposed App... the problem is the UI... it disables interaction when the framework ins't loaded. From my point of view is a mistake! Why force this? Any reason that I don't view?
Another option is remove the file with the list of modules, but I don't know if the Xposed App recreates this file after boot, and if it's maintains the selected/unselected list of modules (normally I have some modules installed but disabled... think on Apps with Xposed add-ons that I don't like to use!).
Any comment?
Click to expand...
Click to collapse
When you have deleted the module list from recovery, Xposed will not create a new list after the following boot process. You have to open Xposed Installer and disable/enable a module, then reboot. This time, Xposed will create a new module list (with exactly the modules states they had before deleting the module list file apart from the last modification you have done to trigger this recreation) and you are free to go. Nevertheless, a cumbersome solution.
I have no idea why one isn't able to interact with the checkboxes, but my best bet would be to prevent the user from thinking that Xposed is indeed active and modules are not working despite being enabled.
orville87 said:
I have no idea why one isn't able to interact with the checkboxes, but my best bet would be to prevent the user from thinking that Xposed is indeed active and modules are not working despite being enabled.
Click to expand...
Click to collapse
Ok. I understand this point... with this the user don't be confused.
So, why not add one option menu in the screen of modules for "enable changes" when the framework is disabled? This option implies "the framework is disabled, but you can change the options". This be user friendly and powerful at time.
What you think?
manos78 said:
Ok. I understand this point... with this the user don't be confused.
So, why not add one option menu in the screen of modules for "enable changes" when the framework is disabled? This option implies "the framework is disabled, but you can change the options". This be user friendly and powerful at time.
What you think?
Click to expand...
Click to collapse
Might be a good point, but you have to ask rovo89 for feature requests. But I highly doubt that he will implement such thing.
orville87 said:
Might be a good point, but you have to ask rovo89 for feature requests. But I highly doubt that he will implement such thing.
Click to expand...
Click to collapse
Well, I hope Rovo89 will read this and agree to implement... it's a very simple change in the UI. :fingers-crossed:
manos78 said:
Hi,
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
Click to expand...
Click to collapse
Not really complicated. If you've access to ADB simply do
Code:
adb shell sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/conf/modules.list
adb shell sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/shared_prefs/enabled_modules.xml
Change PACKAGE with the package name of the app.
The first command would disable only the module, not the framework, not the rest of the modules. The second command would make sure that when you open the Xposed app -> Modules, your module shows up as unchecked. The second command is not important but it is good to keep confusion at a distance.
If you don't have access to PC always, you can keep a script inside your sdcard or `/data` as
Code:
#!/bin/sh
sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/conf/modules.list
sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/shared_prefs/enabled_modules.xml
If you've TWRP, you can edit the file to change the package name and run the script without the need of a PC.
nomap_here said:
If you've TWRP, you can edit the file to change the package name and run the script without the need of a PC.
Click to expand...
Click to collapse
Thank you!
But quite complex! I prefer to "touch disable" for disable Xposed (fail safe boot mode) and in the UI of the App (when the Xposed is disabled) then enable/disable the ofending module. I feel is MORE SIMPLE and INTUITIVE!
I hope Tovo read this and change the UI. :fingers-crossed:
So I've been using the LiveBoot module from this post on MM, but today I've updated to Nougat and it does not seems to work. Does anyone knows something about this?
I think the LiveBoot app do work, can anyone confirm?
Thanks.
eXtremeDevil said:
So I've been using the LiveBoot module from this post on MM, but today I've updated to Nougat and it does not seems to work. Does anyone knows something about this?
I think the LiveBoot app do work, can anyone confirm?
Thanks.
Click to expand...
Click to collapse
you can get it working pretty easilyg without a module having to be installed, just install it like a normal app on your phone and then put the file it makes after it installs into the magisk.img (while its mounted) in the post-fs-data folder.
It will look like this:
/magisk/.core/post-fs-data.d/0000liveboot
the contents of my working 0000liveboot script is:
#!/system/bin/sh
/system/bin/sh /data/user_de/0/eu.chainfire.liveboot/files/liveboot &
If for any reason the file called is not in that spot, you'll gave to find it manually and change the script to reflect where it is on your particular phone. Possible locations might be /data/user/0/ or /data/data/
Best case is you can just use the 0000liveboot script exactly like I have it. Try that first. If you have no log overlay next boot, you'll have to did where the I installed liveboot app you have is keeping its data and simply change the script so it reflects wherever you find it, then try rebooting again and it should work!
I should mention I'm using v1.60 of chainfire's app
the attachment here is just the script that I know works, just in case anyone wants it.
Sent from my LG V20 using XDA Labs
Thanks, I'll try and tell you. And nice signature by the way haha
I installed the app but I can't go further if I don't allow the installation of the script in the system partition, and that's what I'm trying to avoid…
Sent from my ONE A2003 using Tapatalk
eXtremeDevil said:
I installed the app but I can't go further if I don't allow the installation of the script in the system partition, and that's what I'm trying to avoid…
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Try the init.d linker module in the Magisk repo (in Downloads in the Manager).
Didgeridoohan said:
Try the init.d linker module in the Magisk repo (in Downloads in the Manager).
Click to expand...
Click to collapse
How? I don't know exactly what you mean
eXtremeDevil said:
How? I don't know exactly what you mean
Click to expand...
Click to collapse
All the LiveBoot app needs is a working init.d. If your ROM doesn't have that already, the easiest way to achieve this with Magisk is to symlink /magisk/.core/post-fs-data.d to /system/etc/init.d.
I haven't tried it myself, but you should simply be able to install the init.d linker module, reboot, install LiveBoot and then let it do it's thing. Nice and systemless.
Reading your previous posts again I see that the app already has asked to install the script, meaning you already have init.d support. Why not just let it install the script? If you have init.d you don't have to worry about official OTAs anyway and it is very unlikely it'll trip SafetyNet (if that's what you're worried about). Or, just use the above mentioned module.
OK, I installed the app, let it do it's thing, then moved the script from init.d folder to post-fs-data.d magisk folder, created a symlink back to init.d folder so the app doesn't complain about script not installed (and also to be able to edit its settings), rebooted and it's working again!
Thanks so much for the help
eXtremeDevil said:
OK, I installed the app, let it do it's thing, then moved the script from init.d folder to post-fs-data.d magisk folder, created a symlink back to init.d folder so the app doesn't complain about script not installed (and also to be able to edit its settings), rebooted and it's working again!
Thanks so much for the help
Click to expand...
Click to collapse
Hi,
I am sorry , I am not able to find the init.d folder and post-fs-data folder.could you please guide me with the full path for these.Thank you.
Rhaegar85 said:
Hi,
I am sorry , I am not able to find the init.d folder and post-fs-data folder.could you please guide me with the full path for these.Thank you.
Click to expand...
Click to collapse
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Sent from my ONE A2003 using Tapatalk
eXtremeDevil said:
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Click to expand...
Click to collapse
Thanks.Yes, I have. Found the path and managed to create a symlink, still not working. I used sdmaid to move files and Mount the partition and terminal to symlink.I am using MI 5 Gemini with ViperOS 3.1. Can this be done on my device?
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
eXtremeDevil said:
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
Click to expand...
Click to collapse
Thanks for your help. Yes, I had the file on that path. It was not working even after moving the 0000liveboot file to magisk/.core/post-data-fs.d. I have now done a clean install of Viper with SuperSU rather than magisk. And now it's working like a charm. I never had the liveboot working with Magisk except for test run. Thanks for your help.
eXtremeDevil said:
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Click to expand...
Click to collapse
Hi,
Yes, sorry, I moved the file to magisk/.core/post-fs-data.d, and created a symlink as well, but it was not working. And I really don't want to leave viper or liveboot either, so I installed SuperSU. But can this be done using Magisk? I am using mi5 Gemini, Viper OS 3.1.1. Thank you again.
eXtremeDevil said:
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
Click to expand...
Click to collapse
Ha! Finally it's working now on magisk . I copied the liveboot file in magisk directory and installed init.d linker on magisk. Instead of creating a symlink using terminal, just moved the initlinker.sh file to the original source and Bingo! Thank you very much mate. I almost lost hope using liveboot with magisk. It was possible for you, THANK YOU?
(Magisk 15.1 / init.d enabler v2.2 , LiveBoot v1.6 )
I can also confirm that the Official Liveboot v1.60 from Playstore in combination with Magisk 15.1 works as soon as it finds a working /system/etc/init.d.
The Linker Modul does its job as expected by Didgeridoohan.
The Test Run works perfect.
When i boot up the phone i can see that Liveboot starts, as the screen is flickering shortly in the transition from Boot-Bootscreen and System-Bootscreen (same logo).
But the scrolling liveboot log itsself just shows up for half a second, when the boot screen switches to "home" respective Lockscreen respective the launcher.
From the previous state (SuperSu/Magisk 12) i know thats it is supposed to appear very soon on the screen.
The liveboot option "overlay on top of the boot animation" changes the appearance of that mentioned half second, but not the timing of the appearance.
Any ideas ? Which Logs ?
Thanks, Greets and a happy 2018
Just put the (liveboot) script in /magisk/.core/service.d, works like a charm.
Confirmed !
Now works like expected. Thank you !
Any way to get this to work on pixel 2 xl ? I tried the above and it fails The closest ive gotten so far is the google logo changed to an android one and the test on the liveboot app works.
Im confused I tried all the steps again but from fromflash fire and it failed, but flash fire itself reboots and scrolls the catlog while its flashing. ( think it reboots twice )