Hi All,
As with my previous devices I've always looked out for the useless but still cool, screen off animation (remember the CRT animation on the old phones? ) as it has not yet been created for our device our only other option is to use Xposed.
Thanks to @zst123 for creating the Xposed module.
Cheers :good:
I've tested this to work with most ROMs, however it should work on any other ROM running android 6.0.XXX
Requirements
Root Access
A device running Android 6.0.XXX Marshmallow
A custom recovery (TWRP)
1. Go here and download this http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
This is the alpha apk
2. Go here and download this http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v81-sdk23-arm64.zip
This is the framework
3. Go here and download this http://dl-xda.xposed.info/framework/uninstaller/xposed-uninstaller-20150831-arm64.zip
This is the Xposed uninstaller just in case you want to remove it.
You now have everything you'll need for now
4. Install the Alpha APK and reboot to recovery.
5. Once in recovery, flash the Xposed Framework, once installed, reboot system, this may take a while, a few minutes is not uncommon.
Once back in the android system, you'll find that it indexes all your apps, this is normal, allow it to finish.
6. Open the Xposed Alpha app and click download.
7. Search for and download the ScreenOffAnimation module and enable it under modules within the Xposed app.
8. Reboot your device.
9. Open the ScreenOffAnimation app and enable an animation. Reboot, again this may take a few minutes although it should be quicker than the framework reboot, no application indexing should take place.
10. Done and Enjoy
You will need to reboot to fully implement any new changes to this app, it also hasn't been updated for a while so the current version is v1.3, however it is functional and should work as expected.
You might be able to squeeze this whole process with maybe a few less reboots, however this is how I first did it and how it worked for me so it should (if you follow to the letter) work for you
At the time of writing the versions used are as follows.
Alpha APK v3.0alpha4
Framework v80sdk23 for ARM64 devices.
ScreenOffAnimation v 1.3
Any questions, please ask and I'll do what I can to assist.
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Gorgtech said:
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Click to expand...
Click to collapse
exactly the same as me mate, I was avoiding xposed for so long but thought I'd try it, and maybe make a little tutorial to go with it.
up until now, no excessive drain, no issues.
I also haven't installed any other modules either. I'm very sure that this can be done without xposed , however until that time, this will do.
but I do agree with you. if I could get this mod without xposed I would.
there's also an uninstaller too so no need to worry
Xposed has been running great for me on 6.0.1
Gorgtech said:
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Click to expand...
Click to collapse
Any chance you're talking about the storage issue that appeared from ART?
I can't run my device without Xposed, lmfao. I set the apps I need with Xposed to not update unless it's compatible with the Xposed modules I run.
Sent from my Nexus 6P using Tapatalk
Gorgtech said:
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Click to expand...
Click to collapse
Exposed is ruining great on mm
Have to say, after my first day. I've not had a single change in battery, hadn't even dropped by 1% overnight
This doesn't work for me. I'm on stock ROM and kernel with Xposed.
Edit: Although it does work with Cataclysm mod/ROM.
Krunk83 said:
This doesn't work for me. I'm on stock ROM and kernel with Xposed.
Edit: Although it does work with Cataclysm mod/ROM.
Click to expand...
Click to collapse
Had you already had xposed installed ? I can't see why it would make a difference so long as you're rooted, have twrp and can successfully install xposed. Also check your version vs the one I used.
I've never installed xposed on a stock ROM so can't comment but I'd have thought it would have worked.
dladz said:
Had you already had xposed installed ? I can't see why it would make a difference so long as you're rooted, have twrp and can successfully install xposed. Also check your version vs the one I used.
I've never installed xposed on a stock ROM so can't comment but I'd have thought it would have worked.
Click to expand...
Click to collapse
Yeah, everything was installed correctly it just didn't work for some reason. It's all good because I just flashed the Cat mod and it worked.
Krunk83 said:
Yeah, everything was installed correctly it just didn't work for some reason. It's all good because I just flashed the Cat mod and it worked.
Click to expand...
Click to collapse
Cat mod?
Also I'd have to verify if it definitely doesn't work on stock ROMs and find out why to update the OP. Might be the version you've got installed.
FYI, try Franco kernel. Apparently xposed plays nicely with it.
I don't mess with custom kernels anymore. Too buggy. The cat mod is a mod to flash over stock to give you the Cataclysm settings. It's not the full cat ROM. So no system wipe/restore needed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P
Krunk83 said:
I don't mess with custom kernels anymore. Too buggy. The cat mod is a mod to flash over stock to give you the Cataclysm settings. It's not the full cat ROM. So no system wipe/restore needed.
Sent from my Nexus 6P
Click to expand...
Click to collapse
Interesting. So it actually has xposed as part of it. Nice. Will check it out.
Nice module, working fine on Screw'd ROM. I have several xposed mods running & have no issue with battery usage or glitches.
I like the random feature & choosing duration - an excellent find thanks
tweeny80 said:
Nice module, working fine on Screw'd ROM. I have several xposed mods running & have no issue with battery usage or glitches.
I like the random feature & choosing duration - an excellent find thanks
Click to expand...
Click to collapse
Very welcome mate, the vertu one is spot on
The module has not been updated since 2014 or am I looking at the wrong one?
May I ask, if I have all system animations disabled via developer options, will this still work?
EarlZ said:
The module has not been updated since 2014 or am I looking at the wrong one?
Click to expand...
Click to collapse
No you are correct, the thing is it really doesn't matter. It works perfectly.
cd993 said:
May I ask, if I have all system animations disabled via developer options, will this still work?
Click to expand...
Click to collapse
Yes it does, functions as expected whilst everything else is off..just tested now.
dladz said:
Yes it does, functions as expected whilst everything else is off..just tested now.
Click to expand...
Click to collapse
That's great, many thanks for helping out
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
Really like this! Favourite so far would be Fade set at 250ms
Related
Impacted ROM
version 1
Will there be a KitKat update of this ROM?
Read here.
Latest JB Samsung TouchWiz
XXUBNB3 (28th February 2014), Android 4.2.2
Why this ROM?
I was using CM-based ROMs since ever, because of their customisability and poweruser options I required. However, I always missed the better camera quality of the TW rom.
Finally, I decided to quit compromising and so I put this ROM together.
Features:
Knox kicked to the curb, along with its apps
rooted
BusyBox and init.d
Zipaligned
odexed (for better performance)
compatible with modern recoveries (like PhilZ)
Extras included:
Xposed framework + Wanam + XuiMod - enables customization of TouchWiz rom on the level comparable with custom AOSP/CM roms. But make sure you know how to use it!
GPS modified for faster lock and better performance
AdAway
How to flash:
Get into recovery (I use PhilZ, but any should work)
Flash the ROM
Reboot and let it bootloop for a minute. It will not boot, and this is normal.
Force reboot into recovery
Flash Vikinger kernel (for BLN support) or f4ktion kernel (for overclocking/undervolting). Warning: f4ktion kernels has a bug - read here. Let me know if it is not affecting you, should you decide to try f4ktion kernel.
Reboot.
Steps 3 and 4 might not be necessary. See for yourself and report back if skipping them works for you.
First proper boot may take several minutes as the phone comes to grips with how awesome ROM it will now run.
Extra steps for those who want to get max performance out of their phones with f4ktion kernel:
7. Edit file /system/etc/init.d/90hardlimit - change HARDLIMIT_VALUE to 2052000
8. Use program like Trickstermod to overclock and/or undervolt. My i9195 works on 2052 MHz with all voltages lowered by 150mV
In terms of looks, it starts just as regular TouchWiz,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and then you can make it look what you want.
This is mine:
Yes, it has battery bar.
Enjoy and prosper.
ROM DOWNLOAD
****************************************
UPDATE:
ROM usage statistics since publication: http://forum.xda-developers.com/showpost.php?p=56442984&postcount=73
,
flashed it today. looks good so far. thank you for your work.
Awesome to see a new rom
Since I'm more a visual guy - can we have some screenshots just to see how the best of two worlds looks like?
charliebigpot said:
Awesome to see a new rom
Since I'm more a visual guy - can we have some screenshots just to see how the best of two worlds looks like?
Click to expand...
Click to collapse
Done. But as I mentioned - it starts just as regular TouchWiz. It just gives you options to customize the crap out of it.
Reboot isn't working properly. Most of the time when I hit "reboot" the device just shuts down.
junkyde said:
Reboot isn't working properly. Most of the time when I hit "reboot" the device just shuts down.
Click to expand...
Click to collapse
Are you using Xposed 4-way reboot? I noticed it, too, and I think it's the module problem.
But it doesn't bother me. Reboot to recovery and download mode should work fine.
Yes I am using it. But when I used it on ML1 and other versions before, there where no issues. It also happend to me when I hit reboot from inside of other apps where I made some changes and a popup told me I need to reboot.
junkyde said:
Yes I am using it. But when I used it on ML1 and other versions before, there where no issues. It also happend to me when I hit reboot from inside of other apps where I made some changes and a popup told me I need to reboot.
Click to expand...
Click to collapse
Can you try removing the framework and module, and then reinstalling it form Playstore?
seems nice.
after deinstalling wanam xposed reboot worked, but with a huge delay. luckily the lights where off so after hitting the reboot button I could see that the display was still glowing, otherwise I would thought the device has shut down. Then I also deinstalled the framework and xposed installer. Reboot was still working (but with the delay). Afterwards I installed everything as it was before and now reboot doesn't work anymore.
Hmm... Perhaps you should disable the module tweaks before removing the modules. Did you try that?
I think so... but I am not quite sure.
junkyde said:
I think so... but I am not quite sure.
Click to expand...
Click to collapse
You could also try flashing Vikinger kernel. If that doesn't help, then most likely it is the NB3 doing that, OR the ML1 kernel is not 100% compatible with NB3.
I flashed Vikinger Kernel, because BLN didn't work with f4ktions. After flashing Vikinger, BLN started working. Then I flashed f4ktion again und now BLN is working with f4ktion. But I don't remember if the reboot problem persisted with Vikinger... And I am too lazy to test it again, because it's not a huge issue for me :laugh:
Prompt for I9190 fit?
Sent from my GT-I9190 using xda app-developers app
woow ! thank !
removed "bloats" ? all unused Samsung apps and some features completely useless .....and with "XS" google apps
what is the most updated and stable kernel between F4k and wikinger ? (with best ratio "good perf / life battery")
Well,i have to much reboots with this rom.Could be the f4ktion-kernel or the framework (i used the rom-integrated and a new one over the xposeapp update).I deinstalled the updated framework and switched the kernel,but with vikinger i can't activate wifi.
Gesendet von meinem GT-I9195 mit Tapatalk
junkyde said:
I think so... but I am not quite sure.
Click to expand...
Click to collapse
NikePershing said:
Well,i have to much reboots with this rom.Could be the f4ktion-kernel or the framework (i used the rom-integrated and a new one over the xposeapp update).I deinstalled the updated framework and switched the kernel,but with vikinger i can't activate wifi.
Click to expand...
Click to collapse
I haven't experienced any reboots. Perhaps the source is one of your programs, or overclocking, if any.
NikePershing said:
but with vikinger i can't activate wifi
Click to expand...
Click to collapse
that's because the f4ktion kernel changes the wifi modules. if you are going from f4ktion to another kernel, you need to replace them with the ones from stock rom. You can read in the f4ktion kernel thread about that issue and you will find the needed files there
I had to replace 3 files in system/etc/firmwares/wlan/prima folder with stock ones.Now wifi works with vikinger after f4ktion.
Gesendet von meinem GT-I9195 mit Tapatalk
Hi there. I have a Moto X 1st Gen XT1053 running 4.4.4
System Version 213.44.1.ghost_row.Retail.en.US
Build Number KXA21.12-L1.29.1
My problem is that for some reason, checking and unchecking the auto rotate check box under display settings does absolutely nothing.
Is there any way I can have the auto rotate feature turned off?
I have tried several auto rotate apps from the play store to somehow keep my phone locked in portrait or however, but again to no avail.
Any help would be appreciated. Thanks.
P.S.
Phone is rooted, supersu installed but bootloader is still locked and running on stock 4.4.4 ROM.
Rootchecker confirmed that the phone has root access.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url][/IMG]
[/url][/IMG]
Bebebs said:
Hi there. I have a Moto X 1st Gen XT1053 running 4.4.4
System Version 213.44.1.ghost_row.Retail.en.US
Build Number KXA21.12-L1.29.1
My problem is that for some reason, checking and unchecking the auto rotate check box under display settings does absolutely nothing.
Is there any way I can have the auto rotate feature turned off?
I have tried several auto rotate apps from the play store to somehow keep my phone locked in portrait or however, but again to no avail.
Any help would be appreciated. Thanks.
P.S.
Phone is rooted, supersu installed but bootloader is still locked and running on stock 4.4.4 ROM.
Rootchecker confirmed that the phone has root access.
[/url][/IMG]
[/url][/IMG]
Click to expand...
Click to collapse
Do you have Gravity box installed ?
If so check if the "allow all rotations" in the "display tweaks" has been activated .
Do post your findings .
Bhargav4591 said:
Do you have Gravity box installed ?
If so check if the "allow all rotations" in the "display tweaks" has been activated .
Do post your findings .
Click to expand...
Click to collapse
Hi. Thanks for your reply, although i am not familiar with this gravity box. How can i go about it?
Bebebs said:
Hi. Thanks for your reply, although i am not familiar with this gravity box. How can i go about it?
Click to expand...
Click to collapse
Well, if you haven't used xposed modules , then this is worth a shot .
Downloaded the latest version of Xposed framework . Read all the risks and instructions here : Ref :-
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053 ;
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
Once you give root privileges to the app, install the xposed gravity box module from within the download section of the app.
Soft reboot to activate the module
Open display tweaks and look for the " enable all rotations " .
Check it once and see if rotations persist , Un check and see if rotations persist .
Note : Ensure that you've BACKED UP your current rom before attempting any changes .
Also, this is only a crude method to see if the values for auto-rotation are being changed or not . No guarantee that it will work, but it's worth a shot (Considering that xposed modules are awesome and you might find quite a few of them to your liking )
Bhargav4591 said:
Well, if you haven't used xposed modules , then this is worth a shot .
Downloaded the latest version of Xposed framework . Read all the risks and instructions here : Ref :-
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053 ;
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
Once you give root privileges to the app, install the xposed gravity box module from within the download section of the app.
Soft reboot to activate the module
Open display tweaks and look for the " enable all rotations " .
Check it once and see if rotations persist , Un check and see if rotations persist .
Note : Ensure that you've BACKED UP your current rom before attempting any changes .
Also, this is only a crude method to see if the values for auto-rotation are being changed or not . No guarantee that it will work, but it's worth a shot (Considering that xposed modules are awesome and you might find quite a few of them to your liking )
Click to expand...
Click to collapse
Thanks for introducing me to this xposed framework. really like what it does. However, it does not seem to help using the enable/disable all rotations, i still get nothing. my xt1053 just keeps on rotating when i rotate the phone. is there any flashable zip files that can revert this back to normal? i am doubtful that someone might have messed up my phone. tsk. i am totally so annoyed when i'm lying on my bed and when i am about to read a text, the screen just rotates itself.
by the way, i already have the bootloader unlocked, and i have had a soft and hard reset on this one. also booted in safe mode but to no success. everything else is working on this great phone except for this auto rotate. tsk. smh.
But thanks again for this xposed framework!!
Bebebs said:
Thanks for introducing me to this xposed framework. really like what it does. However, it does not seem to help using the enable/disable all rotations, i still get nothing. my xt1053 just keeps on rotating when i rotate the phone. is there any flashable zip files that can revert this back to normal? i am doubtful that someone might have messed up my phone. tsk. i am totally so annoyed when i'm lying on my bed and when i am about to read a text, the screen just rotates itself.
by the way, i already have the bootloader unlocked, and i have had a soft and hard reset on this one. also booted in safe mode but to no success. everything else is working on this great phone except for this auto rotate. tsk. smh.
But thanks again for this xposed framework!!
Click to expand...
Click to collapse
You're welcome man.
Don't lose hope yet , it could still do a few things since your boot loader is unlocked . My guess is that the ROM or Kernel is at fault. So,
1) Change your kernel (for 4.4.4) . Try this one :http://forum.xda-developers.com/moto-x/development/kernel-zwliew-kernel-r1-t2926315 - This is because the kernel affects the way your software interacts with the hardware
2) Change your rom , Try krypton, it's 4.4.4 based so you won't lose out on moto features if you want a custom ROM or flash the stock SBF file for XT1053 4.4.4 using RSD lite. Read the general section on how to revert to stock
Do try .
Bhargav4591 said:
You're welcome man.
Don't lose hope yet , it could still do a few things since your boot loader is unlocked . My guess is that the ROM or Kernel is at fault. So,
1) Change your kernel (for 4.4.4) . Try this one :http://forum.xda-developers.com/moto-x/development/kernel-zwliew-kernel-r1-t2926315 - This is because the kernel affects the way your software interacts with the hardware
2) Change your rom , Try krypton, it's 4.4.4 based so you won't lose out on moto features if you want a custom ROM or flash the stock SBF file for XT1053 4.4.4 using RSD lite. Read the general section on how to revert to stock
Do try .
Click to expand...
Click to collapse
I have downloaded zwliew kernel and i am now downloading the krypton 4.4.4 ROM.
I will just have to flash them in TWRP right?
Is there already a stable and battery friendly lollipop ROM for our Moto X?
Bebebs said:
I have downloaded zwliew kernel and i am now downloading the krypton 4.4.4 ROM.
I will just have to flash them in TWRP right?
Is there already a stable and battery friendly lollipop ROM for our Moto X?
Click to expand...
Click to collapse
First I suggest that you only flash the kernel an check (yes, via TWRP)
only then, change your rom.
IMHO, lollipop in itself is fairly buggy . I'm sticking to KK for now
Thanks again man! I figured that it was a ROM issue. i'm not sure why the stock ROM i have was buggy. But i no longer have the auto rotate issue. I have a different issue now though, all the gapps just stops working and force closes. And i dont have anything on my quick action buttons on my status bar. Everything else is ok though. Do have the link for gapps patch?
Bhargav4591 said:
First I suggest that you only flash the kernel an check (yes, via TWRP)
only then, change your rom.
IMHO, lollipop in itself is fairly buggy . I'm sticking to KK for now
Click to expand...
Click to collapse
I really dont know what's going on now. I did a clean install of the krypton 4.4.4 ROM. Everything went exceptionally fine, no auto rotate issue, no nothing. i did not install the xposed framework, i just have the bare ROM.
and then i backed up the phone and rebooted.
after rebooting, there i have the auto rotate issue again. this is just crazy, i'm running out of hope now.
Bebebs said:
I really dont know what's going on now. I did a clean install of the krypton 4.4.4 ROM. Everything went exceptionally fine, no auto rotate issue, no nothing. i did not install the xposed framework, i just have the bare ROM.
and then i backed up the phone and rebooted.
after rebooting, there i have the auto rotate issue again. this is just crazy, i'm running out of hope now.
Click to expand...
Click to collapse
that is weird ! Ok, last option. Download the SBF file for 4.4.4 xt1053 and return to stock rom (May fix the problem)
Use these links for finding the correct version for your model:
{
http://www.filefactory.com/folder/dd...how=100&page=1
http://motofirmware.center/files/category/9-ghost/
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X
}
USE THIS GUIDE BEFORE ANYTHING ELSE
http://forum.xda-developers.com/moto-x/general/guide-newbies-how-to-revert-to-stock-t3104208
And this
http://forum.xda-developers.com/mot...o-x-return-to-100-stock-using-t2446515/page79
Be careful and follow all steps to return to stock , think twice , flash once .
Hi all
At last working xposed for huawei device
I download and tested this xposed and work that same as before in kitkat.
Here you have pack to download v86
https://mega.nz/#!M4YTFJLY!RcGD_28N_SbbwWZm_rXS5jl_Uzyn31jgp6jgo8BE9E0
How install
Download and extract
Install apk and open
Go to setting and select this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go back and go to twrp
Flash api22 for lp or api23 for mm
When it's finish do it wipe cache, dalvic cache and reboot
First time you be have optimalization that same as you flash stock lp or mm
Now you have working xposed on your mate7
Cheers and all credits to @rovo89
Changelog ---> http://forum.xda-developers.com/showpost.php?p=67658523&postcount=35
Send from
chudy_85 said:
Hi all
At last working xposed for huawei device
I download and tested this xposed and work that same as before in kitkat.
Now you have working xposed on your mate7
If you want change something in them you must edit build.prop in this two line
ro.config.hwtheme=0
ro.config.hw_theme=0
Cheers and all credits to @rovo89
Send from
Click to expand...
Click to collapse
Thanks, i understand it so, that i can nothing change on the Device befor edit build.prop in this two line
ro.config.hwtheme=0
ro.config.hw_theme=0
Thats right?
edited. wrong post
Guys i use Android 4.4.2 Kitkat, and i want to install Xposed on my phone, Can anyone help me? I find old xposed installer, can any give me a link?
KayraINCI said:
Guys i use Android 4.4.2 Kitkat, and i want to install Xposed on my phone, Can anyone help me? I find old xposed installer, can any give me a link?
Click to expand...
Click to collapse
Here you have xposed framework 2.6.1
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v32_de4f0d.apk
Send from ?
chudy_85 said:
Here you have xposed framework 2.6.1
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v32_de4f0d.apk
Send from ?
Click to expand...
Click to collapse
I downloaded already at a other website, but when i go to: framework catagory, and i need to install/update framework, it says in red: "blablabla, you phone can be damaged...", can i ignore?
Siemens Mikrodalga cihazımdan Tapatalk kullanılarak gönderildi.
i Don't have this communication. Yes you can but do you have twrp backup
Send from ?
I can't find "hwtheme" or "hw_theme" in B513 and when i try to use flat style apps it dosen't work
Whta to do ??
I tried this in my oppo and got it working on Lollipop despite ColorOS being used. Didn't need buildprop mods in that. The Mate 7 has the custom navbar which creates problems. Just installed Xposed on the Mate 7. Edit your buildprop first if you want to try it because Xposed framework install stops navbar working if you don't. About to test it, rebooting. System optimising.
I may flash back my TWRP backup as I don't really need Xposed on this phone, but I did need it with the oppo as it's my daily driver now and my music player. If MinMinGaurd works properly it will be worth keeping because the pop up ads here on XDA make me insane! I almost stopped visiting this site because of them and I won't pay every three months to be ad free. That's extortion.
I'd be happy to donate to the cause for better reasons, but ads are one thing I detest and a reason I start to dislike Google. Now XDA follows with this......
EMUI actually replaces a lot of tweaks I used to use Xposed for anyway.
Do not do this without doing a recovery backup first!
Edit:
Installed.
I did the buildprop alteration and it boots ok, no bootloops and navbar still works with hide and pulldown present.
Will install a few modules and test. Gravitybox runs but can't use a lot of the cosmetic alteration settings of course. I do now have my skipping music tracks with volume buttons and changed it to 25 volume steps. YES!!!
installed as per guide. Xposed framework is active but those module i installed told me framework is not active. all module is not working.
any solution? do i need to flash the uninstaller before the apk installation?
Not all moduls work I don't now wy but on my don't work gravitybox
Send from ?
I found most modules won't work but the phone is stable and framework is stable and active.
I have installed ActivityForceNewTask but not sure if it's doing anything yet.
Gravitybox (not many settings activated as some will FC the UI or just not work) which does work for some settings I wanted.
MinMinGaurd (add blocker) which is working.
VolumeSteps+ (only changed number of volume steps for all audio streams as other checkbox settings don't work)
Hi,
Thanks for this tutorial. I would like customize my phone ( battery ect ) but i don't find in BUILD.PROP these two line :
ro.config.hwtheme=0
ro.config.hw_theme=0
i try add these line but apparently that's doesn't work.
Any solution ?!
Thanks a lot for your reply
KoganFR said:
Hi,
Thanks for this tutorial. I would like customize my phone ( battery ect ) but i don't find in BUILD.PROP these two line :
ro.config.hwtheme=0
ro.config.hw_theme=0
i try add these line but apparently that's doesn't work.
Any solution ?!
Thanks a lot for your reply
Click to expand...
Click to collapse
You won't be able to customise cosmetic things in the Mate 7 because of EMUI.
If that's all you want Xposed for, don't install it.
If you fiddle too much trying to make cosmetic changes to the UI, it will force close or bootloop.
You need to have a rooted phone with a decent file manager like ES
That first line is in the buildprop but has a 1 at the end. Change that to 0.
The second line needed to be added in mine, then save the file and reboot.
In buildprop, the 1 or 0 is a digital switch, on or off. Like options of true or false.
RobboW said:
You won't be able to customise cosmetic things in the Mate 7 because of EMUI.
If that's all you want Xposed for, don't install it.
If you fiddle too much trying to make cosmetic changes to the UI, it will force close or bootloop.
You need to have a rooted phone with a decent file manager like ES
That first line is in the buildprop but has a 1 at the end. Change that to 0.
The second line needed to be added in mine, then save the file and reboot.
In buildprop, the 1 or 0 is a digital switch, on or off. Like options of true or false.
Click to expand...
Click to collapse
Thanks for your reply Robbo.
I understand what you say but when a was on Lollipop i use Xposed with module like flat bar indicator and that work fine.
For buildprop i don't find any line with ro.config.hwtheme or ro.config.hw_theme.
Maybe because i'm in B513 still beta in France. If it's not possible to change icon bar or something I think rollback my phone to Lollipop.
Skorpi58 said:
Only for battery icon i must have lucky patched?
Click to expand...
Click to collapse
I think his message got lost in translation somewhat. Lucky Patcher and Xposed are two separate things. Lucky Patcher is used to patch (it's in the name lol) applications to do things like add new features, emulate in app purchases (ie free IAPs) and so on. It also does not require Xposed, only root access.
Xposed is something entirely different, and is also something I do not know much about. I will definitely install this and see if it works.
KoganFR, you're likely to be right about the difference with MM and LP. Mine is on B331 LP. It runs stable, no bugs so didn't want to risk MM and never tried it.
That's right!
I'll try rollback this afternoon for LL and install a custom rom.
I like too much customize my phone first reason to choose android phones.
On b522 its work but change theme automatic. I can use this xposed
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Update in first post. Now it's v83
And added good place where you can modded file ro.config.hwtheme
Send from hell ✌
I recently updated my OP2 to OOS 3.0.2, and I installed xposed on it like i normally would. Everything installed without problems, but none of my modules are working. Can someone help me?
I have checked that I have the correct xposed for marshmallow. I have checked that I have the newest apk, any other suggestions?
By any chance, do you have Xposed Status disabled?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using Tapatalk
If it still doesn't work, you can try to uninstall Xposed Installer > reboot your phone > install Xposed Installer and than do a soft reboot (by function on Xposed Installer app ).
This work for me. I think the problems happen because I flash xposed *.zip file after install Xposed Installer
Goodluck.
Curiousn00b said:
By any chance, do you have Xposed Status disabled?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
What apk is that? When I said latest I ment 3.0 Alpha 4. The apk you use doesnt look one bit like that.
Mark2014 said:
If it still doesn't work, you can try to uninstall Xposed Installer > reboot your phone > install Xposed Installer and than do a soft reboot (by function on Xposed Installer app ).
This work for me. I think the problems happen because I flash xposed *.zip file after install Xposed Installer
Goodluck.
Click to expand...
Click to collapse
Did not change anything, sadly
lauge2000 said:
What apk is that? When I said latest I ment 3.0 Alpha 4. The apk you use doesnt look one bit like that.
Click to expand...
Click to collapse
Material Design Xposed Installer.
Did not change anything, sadly
Click to expand...
Click to collapse
Could you either upload screenshots from your Xposed Installer framework section or upload your Xposed log file? It would be easier to help you without only guessing around based on few information.
You could also try to uninstall your framework by flashing the uninstaller.zip within recovery and flash the systemless Xposed afterwards.
Portgas D. Ace said:
Material Design Xposed Installer.
Could you either upload screenshots from your Xposed Installer framework section or upload your Xposed log file? It would be easier to help you without only guessing around based on few information.
You could also try to uninstall your framework by flashing the uninstaller.zip within recovery and flash the systemless Xposed afterwards.
Click to expand...
Click to collapse
Here is a picture of my Xposed installer section.
https://i.imgur.com/tcqZNH3.png
Here is my Xposed log file: https://www.dropbox.com/s/zibe3nywkxzyqzc/xposed_error_20160615_100528.log?dl=0
lauge2000 said:
Here is a picture of my Xposed installer section.
https://i.imgur.com/tcqZNH3.png
Here is my Xposed log file: https://www.dropbox.com/s/zibe3nywkxzyqzc/xposed_error_20160615_100528.log?dl=0
Click to expand...
Click to collapse
Any specific reason why you are using v83 instead of the latest version?
Also disable all of your modules
Enable one of them; imho, start with snapprefs because it looks, from your log that it is working.
Reboot, open snapchat if it works disable snapprefs and enable another module reboot and check if that module's functions work.
Continue doing this until done.
One of your modules is bad, I am 75% sure it is custom alert slider from nqk. The last comments in its thread seem to point to it not working in Android6.0.1.
http://forum.xda-developers.com/oneplus-2/themes-apps/app-alert-slider-oneplus-2-t3248005/page13
Portgas D. Ace said:
Any specific reason why you are using v83 instead of the latest version?
Click to expand...
Click to collapse
Tried v85 and it didnt work, just thought I would try v83 instead
Nergal di Cuthah said:
Also disable all of your modules
Enable one of them; imho, start with snapprefs because it looks, from your log that it is working.
Reboot, open snapchat if it works disable snapprefs and enable another module reboot and check if that module's functions work.
Continue doing this until done.
One of your modules is bad, I am 75% sure it is custom alert slider from nqk. The last comments in its thread seem to point to it not working in Android6.0.1.
http://forum.xda-developers.com/oneplus-2/themes-apps/app-alert-slider-oneplus-2-t3248005/page13
Click to expand...
Click to collapse
Will try this, thanks!
EDIT: I have now tried this, and it didn't work. Anything else I can try?
Can no one help with this??
lauge2000 said:
Can no one help with this??
Click to expand...
Click to collapse
Having the same problem, tried everything with no luck...
Hi.
We had the same issues on the Elephone P9000, also on the UMI Super.
I've made a MOD (grorkmod http://forum.xda-developers.com/showthread.php?p=67247504 ) that will create a patched sepolicy (thanks again to @Chainfire for his sukernel and supolicy) which will be copied into root on every boot.
On boot the stocksepolicy will stay initially, but in the later bootprocess it will be overwritten with a patched one.
The problem in detail:
We have only stockbased ROMs with an enforcing kernel. If we set selinuxmode to permissive with an initd script lots of apps won't work. EBay, google messenger, runtastics and more will just crash. Xposed modules will work but not the apps.
With the grorkmod you have both and that on an enforcing ROM.
It should work on other devices also, but it has to be tested.
Maybe it could solve your problems, too?
For other devices than the elephone p9000 it is strongly recommend to use the latest v0.94.
Greetings
Vsrookie
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Hi.
We had the same issues on the Elephone P9000, also on the UMI Super.
...[/URL]
Click to expand...
Click to collapse
I have set SElinux to permissive with terminal, but modules still don`t work.
gaich said:
I have set SElinux to permissive with terminal, but modules still don`t work.
Click to expand...
Click to collapse
You have to boot in permissive mode. Create a script in init.d with setenforce 0.
greetings
vsrookie
ps: On our chinese phones that was a problem, thats why i created grorkmod.
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
You have to boot in permissive mode. Create a script in init.d with setenforce 0.
greetings
vsrookie
ps: On our chinese phones that was a problem, thats why i created grorkmod.
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Great!!!! This did the trick! I flashed your mod and my modules began to work!:laugh:
Hi.
Nice to hear. May i ask you what phone you have?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Hi.
Nice to hear. May i ask you what phone you have?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, it`s in my signature - Ulefone Vienna with Marshmallow test build.
i have the same problem and ended up just uninstall xposed and installer.
Lineage OS 14.1 for Moto Razr M JBBL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all!
I'm have ported LineageOS 14 for the xt907_jbbl
lineage-14.1-20170707-port-ilichva-xt907_jbbl
lineage-14.1-20170804-port-ilichva-xt907_jbbl
Enjoy.
XDA:DevDB Information
Lineage OS 14 for Moto Razr M_JBBL, ROM for the Motorola Droid RAZR M
Contributors
ilichva
ROM OS Version: Android 7.1.2 Nougat
Version Information
Status: Nightly
Created 2017-03-23
Last Updated 2017-08-05
Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?
trivialPotato said:
Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?
Click to expand...
Click to collapse
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4
ilichva said:
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4
Click to expand...
Click to collapse
Hm... Interesting... That means that a custom kernel would allow them to boot, right?
The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.
ilichva said:
The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.
Click to expand...
Click to collapse
Hm, I didn't get that, replacing the kernel would not allow them to boot? They'd need to be built from scratch?
Hello ilichva, big thanks. And what about root???
mastnacek said:
Hello ilichva, big thanks. And what about root???
Click to expand...
Click to collapse
Install SuperSU...
ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
I just found this thread. When I flashed this ROM, I installed Magisk for root and haven't noticed anything negative, but have found benefits (e.g. installing/running Viper, work around for failing init.d etc). It also appears to be the choice on other devices, in newer ROMs .
@ilichva is there any specific reason you suggested SuperSU? or is it just that you haven't personally tested Magisk?
Originally I was kind of worried that the vanilla style of Lineage OS would bug me (as I am used to ROM's with a lot of customisations). However, I have Magisk (the apparent latest way to root), V4A, a Linux Swap Partition and have Xposed the...err...heck! out of the ROM (8 Xposed modules), including "Settings Editor" which enables you to add things to the settings menu that makes the additions (eg Viper) appear like they are actually part of the ROM.:good:
ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
Thanks, works. In CM13 was supersu already. Good work.
I'm using supersu2.76 zip and install viperatmos stock5.4 and using exposed too, all working well on enforcing mode
dedik46 said:
all working well on enforcing mode
Click to expand...
Click to collapse
Do you have or are you using any boot scripts? ie init.d
DiamondJohn said:
Do you have or are you using any boot scripts? ie init.d
Click to expand...
Click to collapse
No...i didn't use init d or any script
dedik46 said:
No...i didn't use init d or any script
Click to expand...
Click to collapse
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
DiamondJohn said:
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
Click to expand...
Click to collapse
I've never try to use any script on init.d and i don't know if init.d is working or not, maybe i will try to use magisk for the next update..
dedik46 said:
I've never try to use any script on init.d and i don't know if init.d is working or not
Click to expand...
Click to collapse
And that's what I was checking. init.d does not work in this lineage ROM, nor in another devices (Nexus 5) lineage based ROM; ie Resurection Remix on N5. I am really surprised how little attention this artifact is getting.
dedik46 said:
maybe i will try to use magisk for the next update..
Click to expand...
Click to collapse
Although not an issue for me, it has extra features such as allowing some apps that wont run on rooted phones, to have su hidden from them. I like the fact that is has pre-built modules to support extra's such as V4A. I also liked the fact that it has its own init.d functionality that I use since the ROM's init.d does not work. And it appears to be the direction newer custom ROM's are heading for root.
Really, your already thinking about the next build? I am more thinking about the method/steps I did wrong or could of done better from the flash of the last build.
Wifi issue is not only our device
Some people have noted an issue with Wifi. I too have had the issue with the wifi loosing its connection and not automatically re-connecting. even though the Wifi is available and well within range.
I looked into it a little further (created a quick app that logged numerous broadcast messages, and logged them to a file), and as part of that I also tested the "pass" situation on my spare Nexus 5 phone, also connected top my Wifi. However, it too failed! it was however better in that it didn't randomly loose the wifi.
With the N5, if I was connected to Wifi (very strong signal), went into settings, turned off the wifi. When I turned the wifi back on, it did NOT automatically re-connect.
The N5 is running a MM Resurrection Remix (one of the latest builds, based on Lineage I think)
So, It would appear that this wifi issue is not specific to our devices. I am not sure if thats a good or bad thing.
Anyway, I have my logging test app running, and like a watched kettle, it hasn't lost its Wifi connection
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
DiamondJohn said:
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
Click to expand...
Click to collapse
I got the recents working again.
I tried turning all my xposed modules off (including a couple that affected the navbar), but it was still failing.
Then I noticed that for the first minute or so it would work every boot, but then eventually stop. So I thought it was some installed app/config that only started later in the boot sequence. This "app" must have root to do such damage, so I went down that path. Thought it might be Magisk (since I appear to be one of the only on it). So I uninstalled Magisk, and flashed SuperSU. Still failed.
Anyway, I got it working again by turning off Super User access to all apps individually (after a restore back to my original starting point), then turning it back on (with a few reboots between). I couldn't identify exactly which caused it, but now it all works :highfive:, and I have a technique to hopefully correct it in the future.:good:
and downloading now!
http://4pda.ru/forum/index.php?showtopic=403669&st=21880#entry60269538
Thank you @ilichva:good::good::good:
-------------edit
just noticed the link is in the first post