we can use this thread for discussion about xposed for lollipop (when we get it) on our device, rather than spamming numerous other threads with it.
i will try to keep useful links updated below, as i find them, or you guys/gals send them to me.
official thread http://forum.xda-developers.com/showthread.php?t=3034811
work around for stock lollipop http://forum.xda-developers.com/lg-g3/general/how-to-xposed-running-properly-stock-t3030261
flashable zip to make selinux permissive http://forum.xda-developers.com/showpost.php?p=59056954&postcount=36
fix crashing apps http://forum.xda-developers.com/lg-g3/general/how-to-xposed-running-properly-stock-t3030261
installed fine on illusion. only activated amplify so far to test basic functionality. amplify says all is good on the exposed end, too early to tell if the module is actually working properly though.
Thank you for making this thread !!
Kris Nelson said:
Thank you for making this thread !!
Click to expand...
Click to collapse
np
as far as amplify, the module will need an update i believe. it should have pulled some wakelocks by now, and still shows none. these issues are to be expected with some modules as described by rovo89.
g3 tweaksbox is not compatible with L, fyi
I agree about amplify incompatibility - it runs but no wakelocks are registering. I'm at about 50%(4 of 8) of module functionality. I'm sure things will work better in time when devs push updates out, but 50% is still a good start. :good:
Anyone here happen to be running a CM12 nightly? No luck here getting xposed to work on mine so far....flashed the zip and installed the apk, then modules and reboots, and the modules and app still give errors saying it's not installed. Even succeeded in getting the app to prompt me for root which I granted, and refreshed the zip in recovery immediately afterwards and still nothing. Same error as a bunch of people posted on the main thread, esp. in the first few pages that I saw.
bweN diorD said:
np
as far as amplify, the module will need an update i believe. it should have pulled some wakelocks by now, and still shows none. these issues are to be expected with some modules as described by rovo89.
g3 tweaksbox is not compatible with L, fyi
Click to expand...
Click to collapse
running greenify and amplify and "unspecififed music-mod" module on cm12 dated 1/15/2015. (as a secondary rom in multi rom... if that makes a difference)
woking like a champ with no sign of errors.
Updated: amplify not working. no errors but also no wakelocks
ohlin5 said:
Anyone here happen to be running a CM12 nightly? No luck here getting xposed to work on mine so far....flashed the zip and installed the apk, then modules and reboots, and the modules and app still give errors saying it's not installed. Even succeeded in getting the app to prompt me for root which I granted, and refreshed the zip in recovery immediately afterwards and still nothing. Same error as a bunch of people posted on the main thread, esp. in the first few pages that I saw.
Click to expand...
Click to collapse
I ended up changing my selinux status(not sure if I had to but saw it in a post), installing the apk, rebooting into recovery and flashing the zip, then once it booted up I opened the xposed installer and under 'framework' choose soft reboot. The error message went away after it rebooted and my modules installed after that, but only if I did a soft reboot. Anytime I did a full reboot my modules stopped functioning until I soft rebooted again. Error messages still appear but the modules do actually work.
I'm on blisspop so hopefully cm has the same solution for you. Good luck.
startswithPendswithOOH said:
I ended up changing my selinux status(not sure if I had to but saw it in a post), installing the apk, rebooting into recovery and flashing the zip, then once it booted up I opened the xposed installer and under 'framework' choose soft reboot. The error message went away after it rebooted and my modules installed after that, but only if I did a soft reboot. Anytime I did a full reboot my modules stopped functioning until I soft rebooted again. Error messages still appear but the modules do actually work.
I'm on blisspop so hopefully cm has the same solution for you. Good luck.
Click to expand...
Click to collapse
Very interesting, well thanks for the heads up! I'll have to try this out.
If you read rovo's comments, you will find him saying there are some false errors that will get fixed eventually. This is an alpha build to get all the issues that need to be fixed reported so he can work them out before he releases the stable build.
Startswith is correct, here is the link to the post with the work around (http://forum.xda-developers.com/showpost.php?p=58839832&postcount=854)
It has been confirmed by other G3 users to be working. :good:
I didn't have to do anything with SELinux. Just installed a module, activated it, and rebooted.
spotmark said:
I didn't have to do anything with SELinux. Just installed a module, activated it, and rebooted.
Click to expand...
Click to collapse
That is good to know, I'm just glad it works. I have not yet been able to try this (stuck at work and we can not bring phones in) so I will be taking care of this when I get home.
spotmark said:
I didn't have to do anything with SELinux. Just installed a module, activated it, and rebooted.
Click to expand...
Click to collapse
Which ROM? I just downloaded illusion 5.5 and it has selinux set at permissive as default...
{
"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"
}
Blisspop is enforcing by default.
startswithPendswithOOH said:
Which ROM? I just downloaded illusion 5.5 and it has selinux set at permissive as default...
View attachment 3165336
Blisspop is enforcing by default.
Click to expand...
Click to collapse
I originally installed it on 5.0, but redid it this morning, on 5.5.
spotmark said:
I originally installed it on 5.0, but redid it this morning, on 5.5.
Click to expand...
Click to collapse
Either way...as long as one of these methods works its all good
For sh*ts and giggles I downloaded illusion 5.5 which is permissive by default, set it to enforcing, and xposed will not work...
Once I set it back to permissive it worked again.
yep
op updated with a stock (when we get L) workaround if not fixed by then.
Amplify has been updated to work with LP now. If that was mentioned already I do apologize.
Related
{
"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"
}
I DID NOT MAKE THIS ROM! I just compiled it from the beanstalk and CM sources
-Data is having trouble keeping a connection after some time (present in 275. build 270 still ok)
-ALL CM bugs will be present. This build uses the CM jewel device tree and kernel.
http://forum.xda-developers.com/showthread.php?t=2397942
http://d-h.st/bTn
BeanStalk Build 4.4.249_OLD_FORMAT
http://d-h.st/bTn
-Updated CM/Beanstalk sources to 2/18/14.
THE FOLLOWING BUILD IS FOR THOSE WHO UPGRADED TO THE NEW HBOOT 2.10 SENSE 5 ROM...IF YOU ARE ON HBOOT 2.09 THIS IS NOT THE BUILD FOR YOU!!!
YOU MUST PERFORM THE ENTIRE UPGRADE PROCESS INCLUDING BOOTING THE ROM HERE
Captain_Throwback said:
DISCLAIMERS:
Instructions for installation:
Download firmware file, and install via HBOOT or fastboot. This will update your HBOOT (2.10) your radio (1.13.11.1105), and some other important firmware bits. Make sure you remove or rename any PJ75IMG files from your external SD card after this step.
Download recovery file (TWRP 2.6.3.1b) and flash via fastboot. This version of TWRP has been modified to accommodate the updated partition layout for this update.
Download ROM (either version), and flash via TWRP. If the TWRP gives an error and reboots, hold the volume down button to get back to the bootloader, boot back into recovery, and flash again. It *should* flash fine on the second attempt.
Click to expand...
Click to collapse
Once you have booted into the Sense 5 rom successfuly you may proceed in flashing the NEW_FORMAT version of this rom after a full wipe in the new recovery.
BeanStalk Build 4.4.285_NEW_FORMAT
http://d-h.st/gtg
-updated sources to 4.4.285 from beanstalk
BeanStalk Build 4.4.270_NEW_FORMAT
http://d-h.st/9sI
-updated sources to 4.4.270 from beanstalk
1. Download the latest build
2. Download the latest Slim GAPPS or other 4.4 specific gapps
3. In recovery, full wipe, and manually format /system
4. Flash ROM and the gapps you want, reboot
SlimROM source can be found HERE
BeanStalk source can be found HERE
CM sources HERE
For Changelog/Features
http://www.scotthartbti.com/index.php/beanstalkbuilds/
Thanks:
deck's tireless work made the CM kernel and device tree that this and many other roms for this device are based on.
scotthartbti for posting creation, updates, and keeping github up to date.
insaneo1488, tearaz, Haus_, shortyishere, NaterTots, CaptainThrowback, and everyone in the #htc-dev channel for all of their support and info along the way.
Please dont hesitate to let me know if someone was missed here, send a PM or catch me in freenode and ill get you in there
Reserved
Reserved
First... and you've been pretty busy lately GoblinZ ... get some sleep. :laugh:
Awesome... Downloading now Thanks!!!!
This is very nice.
Thanks a ton!
Holy shiiiiiii! Beanstalk is back! You rock man!
Dirty Dirty EVO
Figured out xposed location.... but can't get DPI to change.
Also, for Pie control, not seeing how to change background on lock screen.
Nice work man thank you for bring us such a lovely Rom. I hope you have as much fun as I did building and maintaining this Rom. :thumbup:
Sent from my EVO using Tapatalk
mcwups1 said:
Figured out xposed location.... but can't get DPI to change.
Also, for Pie control, not seeing how to change background on lock screen.
Click to expand...
Click to collapse
So I pulled the feature list directly from the lead developer's thread with the assumption that he had kept up the feature list...appears he doesnt keep his thread up.
http://forum.xda-developers.com/showthread.php?t=2091900
So I will edit out all the features from the OP and instead just put a link to the kitkat changelog.
Copy that, but I don't see why DPI settings aren't working. Xposed is there, as well as app settings, so it should work.
I installed and enabled, then rebooted.
I'll keep trying.
mcwups1 said:
Copy that, but I don't see why DPI settings aren't working. Xposed is there, as well as app settings, so it should work.
I installed and enabled, then rebooted.
I'll keep trying.
Click to expand...
Click to collapse
open xposed back up on the top where it says "Framework" change to "Modules" put a check in the app settings module...reboot
GoblinZ said:
open xposed back up on the top where it says "Framework" change to "Modules" put a check in the app settings module...reboot
Click to expand...
Click to collapse
I did that. I've used Xposed in almost every ROM I've installed. I'm familiar with it.
Attached pictures, and I've granted SU permissions and rebooted twice.
mcwups1 said:
I did that. I've used Xposed in almost every ROM I've installed. I'm familiar with it.
Attached pictures, and I've granted SU permissions and rebooted twice.
Click to expand...
Click to collapse
I did not test dpi, I set an app to "landscape only" and that worked after enabling in the modules.
Message app is awesome!
Sent from my EVO using Tapatalk
Anyone get DPI settings to work?
So right after I say message app is awesome it's force closing when I attach and try to send a picture. Any ideas
Sent from my EVO using Tapatalk
thewind730 said:
So right after I say message app is awesome it's force closing when I attach and try to send a picture. Any ideas
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I flashed the Full Modular GAPPS from the 0-day PA so my messaging app didnt look any different. I was able to attach a picture and send without issue.
Edit: so, I wiped flashed Just this rom and the PA Gapps, and sure enough force close...google is clearly forcing us to use hangouts...but in all seriousness it seems to be affecting CM nightly as well
http://forum.xda-developers.com/showpost.php?p=50141180&postcount=1184
So, I will recompile and post to OP as soon as CM has the code cleaned up with a fresh build. Sorry for the trouble.
Ok cool cause I was having the same issues with decks irc build with the messaging app ill try this out once you get it fixed
Sent from my EVO using XDA Premium 4 mobile app
GoblinZ said:
I flashed the Full Modular GAPPS from the 0-day PA so my messaging app didnt look any different. I was able to attach a picture and send without issue.
Edit: so, I wiped flashed Just this rom and the PA Gapps, and sure enough force close...google is clearly forcing us to use hangouts...but in all seriousness it seems to be affecting CM nightly as well
http://forum.xda-developers.com/showpost.php?p=50141180&postcount=1184
So, I will recompile and post to OP as soon as CM has the code cleaned up with a fresh build. Sorry for the trouble.
Click to expand...
Click to collapse
Thanks man! For looking into this and bringing these builds back your time is greatly appreciated
Sent from my EVO using Tapatalk
{
"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"
}
This firmware:
- Does not include root management (I suggest flashing SuperSU from recovery)
- Installs TWRP as device recovery
- 5.0.x Tested using PA Pico GApps
- 5.1 Tested using BaNkS Gapps via euroskank
or these other minimal GApps (untested)
Known issues:
- No sound during calls until toggle speaker phone
- Time zone bug
Installation notes:
- Do not use Mr.Cook's rom-wipe script; [ here's why ]
- I do NOT recommend dirty-flashing over other i777 firmwares
**Downloads**
I am not a developer, just a builder.
Credit to the Omni team, and to @asimovi, for the i9100/exynos4 source modifications, from which these builds are based.
Happy flashing,
-Cyril
**Source Details**
So what are the bugs in this rom. Is it same as cyandel?
On this firmware, WIFI works, and mobile data works.
I have not been running this firmware long, so I don't know all of the bugs yet. I am still testing the firmware myself.
I will keep the OP updated as I learn more.
virajjjj said:
So what are the bugs in this rom. Is it same as cyandel?
Click to expand...
Click to collapse
Can you shoot videos??
Is sdcard detected?
It looks like there's no multi-user support. Or maybe I'm blind and I just can't find it. The other problem I found is that ES File Explorer doesn't work; it crashes and causes the phone to restart. Updating from the Play store doesn't fix it.
Otherwise, it seems to run alright. Wifi is fine, but I don't have a SIM for it.
mmystere68 said:
Can you shoot videos??
Is sdcard detected?
Click to expand...
Click to collapse
Sdcard is fully functional. When shooting video, the stock camera freezes.
sciguy125 said:
It looks like there's no multi-user support. Or maybe I'm blind and I just can't find it. The other problem I found is that ES File Explorer doesn't work; it crashes and causes the phone to restart. Updating from the Play store doesn't fix it.
Otherwise, it seems to run alright. Wifi is fine, but I don't have a SIM for it.
Click to expand...
Click to collapse
I intentionally disabled multiuser support. If that's something that you use, I can enable it.
The stock file browser, and solid Explorer both work well on this firmware. I therefore suspect that ES crashes are an app compatibility issue.
SIM card works, I'm daily driving it right now.
I appreciate the feedback.
-Cyril
it works
thank you for sharing this with us, i have been trying to just see/try android 5.0 on my device and with your rom its working . i didnt fully test everything but overall seems fine to me
coolerboyj said:
I heard there was a bug of the wifi, and that if you power your phone off with the wifi off, it will be stuck in a boot loop.
Is this true?
And secondly, I wanted to know if I could flash another kernel, like Shift....
Click to expand...
Click to collapse
@coolerboyj, I just tried it. I turned off the wifi, then rebooted, and the device booted into android as expected.
I have not tried shift with Omni 5.0, but it should work well.
i have had some random reboots and the call bug as you mentioned but other than that all is good. just wondering about any future fixes for the call bug ?
MONSTERELLEVEN said:
[...] just wondering about any future fixes for the call bug ?
Click to expand...
Click to collapse
...I sure hope so. This is where you can all help me out. If you notice that another 5.0 firmware (for i777 or i9100) doesn't have the call bug, let me know, and I will look into what fixes they applied, and attempt to apply them to OMNI.
-Cyril
cyril279 said:
...I sure hope so. This is where you can all help me out. If you notice that another 5.0 firmware (for i777 or i9100) doesn't have the call bug, let me know, and I will look into what fixes they applied, and attempt to apply them to OMNI.
-Cyril
Click to expand...
Click to collapse
yeah, absolutely hope soon it would be fixed as its pretty hard to go back to kk after trying lollipop
**2015/02/10 build posted**
multiuser enabled
ambient display enabled (settings > display > ambient display)
a few other fixes
yeah, absolutely hope soon it would be fixed as its pretty hard to go back to kk after trying lollipop
Click to expand...
Click to collapse
Can you give specifics? Just curious as to what you like best about it.
When trying to flash Gapps from here, I keep getting "Error Code: 70". I tried it with both Stock and Micro versions and it sayd "Error executing updater binary in zip". Does this mean it's just a bad zip? Or is there another issue I'm missing?
squiglybob13 said:
When trying to flash Gapps from here, I keep getting "Error Code: 70". I tried it with both Stock and Micro versions and it sayd "Error executing updater binary in zip". Does this mean it's just a bad zip? Or is there another issue I'm missing?
Click to expand...
Click to collapse
Tried Pico? I've only tested with Pico.
desteele said:
Can you give specifics? Just curious as to what you like best about it.
Click to expand...
Click to collapse
I like the refreshing nature of the interface. I'm eager to see what the big three add as customization.
This device doesn't handle the animations very well yet though. Maybe device tree refinements will improve it, maybe succeeding versions of Android, or both. Either way, only time will tell.
cyril279 said:
Tried Pico? I've only tested with Pico.
Click to expand...
Click to collapse
Ah I didn't realize pico was one of the packages [emoji14] I'll give that a shot thank you
EDIT: Success!
good job!!!)))
Big thanks for LoliPop In our device!)
Does this have cm12 theme engine ??
mmystere68 said:
Does this have cm12 theme engine ??
Click to expand...
Click to collapse
No, does not have the engine СМ12, but without it everything is just perfect
Hello!!
The #HYPE is correct.
OPT devs are on the job for creating the best base of CM12.1
Meanwhile here is my guide to install the Xposed Framework on Stock Oxygen OS after Root.
1) YOU NEED PERFECT ROOT WITH SU. Follow THIS awesome simple guide.Before Starting to Unlock Your Boot Loader
Backup Every Bit of Your Data
Perform fill wipe op your mobile
Don't use encrypted mobile. REMOVE Encryption
Have patience, After OEM Unlock, Don't Reboot.
(Hold Volume Down + Power) to open the TWRP else you will end up in STOCK Recovery.
2) Make a NANDROID
Click to expand...
Click to collapse
Since OPT is based on ARM64, Get the following from Official Xposed Thread Here
You should get these two files
1)
{
"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"
}
xposed-v73-sdk22-arm64.zip - (5.62 MB)
2)
XposedInstaller_3.0_alpha4.apk - (611.8 KB)
Once You are ready with all the above quoted prerequisites, start
Step 1:
Download the above said two files in a folder of your OPT Internal Memory
Step 2:
Boot to recovery
Step 3:
Flash 1st file which is a Zip File
Step 4:
Reboot your Mobile after flashing normally.
Step 5:
Open the Second File (.apk) from your file browser and install.
Step 6:
Open the Exposed Installer from you app Menu.
Step7:
If everything goes well, You should find this..
Hope From this you can take off downloading the modules you would like to and enjoy tweaking the Stock ROM...
This is Youtube PopUp Module (Second one from the list) Working on my OPT
This is the Lockscreen Mod
Enjoy Guzy.. Hit Like if this guide Helped
are there any bugs? will we get OTA if we install this? can we uninstall this ? will warranty be affected? please confirm
---------- Post added at 10:10 PM ---------- Previous post was at 09:35 PM ----------
Can you tell us which are the modules that are safe and working here? so that we can test and confirm ?
Hi Bharat
OTA have no issues so far.
See my screens below running Latest of Oxygen OS
Will be certain if any more updates are out. As of now, no issues.
All modules which are for lollipop are working absolutely fine. No issues if you go through the description of each module before installing. However device specific modules which are developed for Xperia.. Samsung.. HTC.. Etc.. Can't work.
Hope this helps.
No SU for Xposed Installer
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
fpavoncelli said:
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
Click to expand...
Click to collapse
Open Xposed Installer->Framework->Reboot Grant SU permission.
Tapped from my ①+②=❸
vaisakh7 said:
Open Xposed Installer->Framework->Reboot Grant SU permission.
Tapped from my ①+②=❸
Click to expand...
Click to collapse
That didn't work, that's why I posted the question.
With only Greenfy and Bootmanager modules installed, I rebooted a dozen times but it didn't get SU permissions.
The problem was solved later on when I installed the "true silent mode" module (it doesn't work in case you want to know), wich I guess needed the permission.
Anyway, problem solved, now it has SU permissions. Thank for the help anyway.
fpavoncelli said:
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
Click to expand...
Click to collapse
Hi there..
Its because of improper rooting.
I Suggest you to re-start the rooting process from the guide above.
After OEM Unlock and recovery flashing.. DO NOT REBOOT
Then Reboot to recovery and then Don't forget to slide (RECOVERY IMAGE STABILIZING)
Then after rebooting to system..
Reset your Phone (Prefer to take a NANDROID after this)
Then Flash SU and check with Rootaccess Checker
If everything Goes well
Then Flash the Xposed Framework given above an then Install and REBOOT before opening.
Then when you open the Xposed application, then SU should popup for permission..
Hope this helps...
Did you suggest some interesting modules for Xposed on OPT ?
ps000000 said:
Did you suggest some interesting modules for Xposed on OPT ?
Click to expand...
Click to collapse
No, I just got it, and I'm trying to figure out Oxygen OS lack of funcions compared with Cyanogen wich is what sold me on the OPO.
Maybe in the next few days I will.
Just my 2 cents:
Download xposed-uninstaller-20150831-arm64.zip and keep it on your internal sd card!
In case of a bootloop caused of a trouble making Xposed mod you just flash the uninstaller to get rid of the bootloop.
Then uninstall or deactivate the mod in Xposed Installer app and reinstall Xposed again.
So when i checked the official thread for xposed it showed a newer file version than what is mentioned here. However in that v74 there are 2 versions again
xposed-v74-sdk21-arm64.zip -
xposed-v74-sdk22-arm64.zip -
not sure which one to use with my Oxygen OS 2.1
Anyone has any information on the above.
Edit : Never mind mound it.
Dude_Virus said:
So when i checked the official thread for xposed it showed a newer file version than what is mentioned here. However in that v74 there are 2 versions again
xposed-v74-sdk21-arm64.zip -
xposed-v74-sdk22-arm64.zip -
not sure which one to use with my Oxygen OS 2.1
Anyone has any information on the above.
Edit : Never mind mound it.
Click to expand...
Click to collapse
so which did you use? the 22?
I used v74sdk22
Sdk 22 is the right one.
Sdk 21 was for Android 5.0
Oxygen OS 2 is based on Android 5.1
Full list of SDK versions and corresponding Android version:
http://developer.android.com/reference/android/os/Build.VERSION_CODES.html
does whole xposed module work well on OPT? any bugs or app that isn't working or so?
22vlaja said:
does whole xposed module work well on OPT? any bugs or app that isn't working or so?
Click to expand...
Click to collapse
No issues so far!I'm running Amplify, Gravitybox,Greenify,Powernap,Notification Counter,AppOpsXposed.
Tapped from my ❶+❷
vaisakh7 said:
No issues so far!I'm running Amplify, Gravitybox,Greenify,Powernap,Notification Counter,AppOpsXposed.
Tapped from my ❶+❷
Click to expand...
Click to collapse
Did u notice some strange behavior after installing Xposed? and did u follow tutorial flash from first site?
22vlaja said:
Did u notice some strange behavior after installing Xposed? and did u follow tutorial flash from first site?
Click to expand...
Click to collapse
1.Flash the Xposed V74-arm64-SDK22 from here.
2.Wipe cache and dalvik cache after flashing.
3.Reboot and install the XposedInstaller-alpha4.apk
4.Open the app->Framework->Reboot.
5.Grand SuperSU access.
Done!
You might have missed the second step.That's not mentioned in the OP.
Tapped from my ❶+❷
allready installed Xposed, just wanted to be sure that this steps is ok!
one more thing, why did you installed AppOpsXposed? its implemented in Oxygene.
22vlaja said:
allready installed Xposed, just wanted to be sure that this steps is ok!
one more thing, why did you installed AppOpsXposed? its implemented in Oxygene.
Click to expand...
Click to collapse
AppOpsXposed is needed to handle GooglePlayServices.
Tapped from my ❶+❷
Download:
The module is available in the Xposed Repo.
Compatible Apps
Gallery3D (Cyanogenmod 11+)
Google Photos
QuickPik (4.5.2)
Description:
Ever hate when you show a friend a single photo/video and they start swiping away through your photos and videos? This module aims to help solve this issue by allowing you to lock an image. If the user attempts to swipe to another image/video they can be greeted by the application crashing, returning to the home screen, or a custom message.
Example Usage:
Example Video
Instructions:
- Enable Module
- Open Don't Swipe Module (App Drawer or Xposed -> Modules -> Don't Swipe)
- Update Hooks (Gallery3D and QuickPic excluded)
- Choose Desired Swipe Action (Optional)
- Open Desired Gallery App
- Find Desired Image/Video
- Click Three Dot Icon and Click Lock
Please make to do the step detailed above before posting for help.
To Do List (Request/Bugs):
None At The Moment
Screenshots:
{
"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"
}
Source Code:
GitHub - Link
Looks nice. I'll download it and try it.
Very buggy, needs work.
grawkiller73 said:
Very buggy, needs work.
Click to expand...
Click to collapse
Can you explain the issues you are facing? Thank you.
just what I've been looking for for ages, but causes bootloop on my nexus 5 running 5.1.1 Dirty Unicorns
DrRuckingFetard said:
just what I've been looking for for ages, but causes bootloop on my nexus 5 running 5.1.1 Dirty Unicorns
Click to expand...
Click to collapse
That is rather strange. I have a Nexus 5, so I will look into this issue immediately. I apologize for this issue you have encountered.
DrRuckingFetard said:
just what I've been looking for for ages, but causes bootloop on my nexus 5 running 5.1.1 Dirty Unicorns
Click to expand...
Click to collapse
I just tested Dirty Unicorn's Weekly 9.6 on my Nexus 5. I didn't experience any bootloop. Is you signature still current about you using version 9.5 or are you currently using another version? I want to see if I can replicate this issue.
Edit:
Tested Weekly 9.6, Official 9.6, and Official 9.5 with no issues. All done with full wipes, re-installation of Xposed, and installation of module.
iHelp101 said:
I just tested Dirty Unicorn's Weekly 9.6 on my Nexus 5. I didn't experience any bootloop. Is you signature still current about you using version 9.5 or are you currently using another version? I want to see if I can replicate this issue.
Edit:
Tested Weekly 9.6, Official 9.6, and Official 9.5 with no issues. All done with full wipes, re-installation of Xposed, and installation of module.
Click to expand...
Click to collapse
signature is outdated, I'm running weekly 9.6 (Aug 18th build i think). Had to boot into twrp and delete the app manually to get the phone to boot again
Excellent. Works with quick pic but can you make it work with stock samsung gallery app? Quickpic was sold to cm and dont want to use it now ?.
DrRuckingFetard said:
signature is outdated, I'm running weekly 9.6 (Aug 18th build i think). Had to boot into twrp and delete the app manually to get the phone to boot again
Click to expand...
Click to collapse
I can confirm this, phone was stuck at boot animation for nearly 20 mins then went to recovery and deleted apk and it booted fine, running AICP on Note 4, latest build.
I'm guessing this module doesn't work on Touchwiz ROMs either. I am using a TW 5.0.0 ROM and it bootloops when I enable this module too.
Doesn't work on my Oneplus running Blisspop 4.0 using Quickpik 4.5.2. The lock option doesn't appear inside the 3 dot menu.
Same as above but with the stock LG G3 rom.
Quickpic v4.5.2 doesn't shows the option to lock.
I apologize for the issues users are facing. I have set the module as experimental at the moment since individuals are reporting bootloops. I have tested four personal devices (Moto G, Nexus 5, Blaze 4G, and OPO) to have no issues. I am trying to nail down what may be causing issues for some, but sadly have been unable to reproduce the bootloops some are facing.
Nexus 5 latest Cataclysm. Bootloop. Does it matter if FIRST I started and configured the module (updated hooks) and THEN restart the device?
@iHelp101 Idk if I should call myself a idiot or whatever, but after failing on 1st attempt and reading your post that you tested it on 4 devices, I just out of curiosity thought to give it another try, this time reading the instructions properly. I realized that I updated hooks for Cyanogen gallery before (thinking the default gallery on my CM ROM would be Cyanogen gallery though it was Gallery3D upon checking my nick does tell that ) and maybe that caused me to stuck in a bootloop. This time tho I just installed the module and activated (read that hooks ain't required for Gallery3D n Quickpik so dint do anything other than activating) and it works like a charm now! :good: Thank you very much for this awesome module! :highfive::highfive:
AndroidNoob22 said:
@iHelp101 Idk if I should call myself a idiot or whatever, but after failing on 1st attempt and reading your post that you tested it on 4 devices, I just out of curiosity thought to give it another try, this time reading the instructions properly. I realized that I updated hooks for Cyanogen gallery before (thinking the default gallery on my CM ROM would be Cyanogen gallery though it was Gallery3D upon checking my nick does tell that ) and maybe that caused me to stuck in a bootloop. This time tho I just installed the module and activated (read that hooks ain't required for Gallery3D n Quickpik so dint do anything other than activating) and it works like a charm now! :good: Thank you very much for this awesome module! :highfive::highfive:
Click to expand...
Click to collapse
Thank you for the positive message. I will try to reproduce these steps to see if the module causes a bootloop for me. If you are able to, once again updating your hooks for Cyanogen Gallery. Reboot and see if you get a boot loop again. If so I can nail it down to the way the hooks are stored (Via SharedPreferences).
dniwe1337 said:
Nexus 5 latest Cataclysm. Bootloop. Does it matter if FIRST I started and configured the module (updated hooks) and THEN restart the device?
Click to expand...
Click to collapse
I am trying to find the correlation currently. I apologize about this and promise I will find a resolution. If you are still in a bootloop use TWRP to delete the module located under /data/app/com.ihelp101.dontswipe.apk.
iHelp101 said:
Thank you for the positive message. I will try to reproduce these steps to see if the module causes a bootloop for me. If you are able to, once again updating your hooks for Cyanogen Gallery. Reboot and see if you get a boot loop again. If so I can nail it down to the way the hooks are stored (Via SharedPreferences).
Click to expand...
Click to collapse
Bootloops.
AndroidNoob22 said:
Bootloops.
Click to expand...
Click to collapse
Found the issue. The fix should be pushed out soon.
So recently I've rooted my galaxy s5 tmobile sm-g900t and install viper4andriod. I have Busybox installed through google play and installed on both my xu and system folder. I also made sure there was enough space. Around 30mb of space. I then installed SeLinuxMode Changer and Universal init.d so that i can force the SeLinixmode changer to stay on permissive. There is a bug where restarting and exiting out the app would reset SeLinux mode you have selected. Now that that SeLinusMode restarts on permissive, i was able to install Viper4Andriod. I then continued and installed the driver, but after installation, i checked to see if anything changed in the sound. Nothing changed so i checked the driver status. It turns out to be Abnormal and unsupported. I'm running 2.3.40, and have also tried the latest version of Viper4Andriod, but both doesn't seem to work. I have stock touchwiz rom and completely disabled and removed Knox. I checked my root with Root Checker, and it passed. But for some reason going into recovery mode, it asks me to install supersu because it was missing. But at the same time, i am running PhilzTouch, which is outdated. I have tried other methods, but it doesn't seem to work. I just need to get pass the driver status problem.
If anyone know the solution to this, I'd very much appreciate it if you help us all out.
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
maximumentropy said:
...
Install the APK in the standard way (not in priv-app or most convolvers won't work).
Install the highest quality drivers and reboot to recovery
Flash the update here from recovery to allow V4A execution with SELinux Enforcing: http://forum.xda-developers.com/showthread.php?p=61242973#post61242973
Flash the Viper4A-[Soundfix-LibFiles]-CWM.zip from this message (but not the others) to replace the system sound libraries in /system/lib/soundfx with V4A-compatible versions: http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609
Reboot
In Viper settings, use Normal mode, not Compatible.
Enable V4A-FX in the desired profile (it is not necessary to use Force Enable V4A)
...
Click to expand...
Click to collapse
alexbelgium said:
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
Click to expand...
Click to collapse
It says its only for kitkat rom? Do you knw if it works for gs5 sm-g900t?
Frankie_Xenon said:
It says its only for kitkat rom? Do you knw if it works for gs5 sm-g900t?
Click to expand...
Click to collapse
Well I am sure that it works both for SM-G900F on 5.0 and 6.0.1 roms. The best for you is to make a backup of your system before trying. As it only impacts the system and not the kernel, it should work whether it is g900f or g900t...
alexbelgium said:
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
Click to expand...
Click to collapse
Do you know if this works for lollipop 5.1.1? It said for kitkat rom?
Frankie_Xenon said:
Do you know if this works for lollipop 5.1.1? It said for kitkat rom?
Click to expand...
Click to collapse
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
alexbelgium said:
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
Click to expand...
Click to collapse
My apologies lol. My phone lagged and i ended up replying twice. Thanks ill give it a shot!
alexbelgium said:
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
Click to expand...
Click to collapse
For some reason the driver keeps asking me to install it after flashing 2 the zips.
Guys, can you check this ROM(lollipop 5.1.1) for geiti94 which have all ready included this app. Very stable and battery friendly.
https://mega.nz/#!HdggTITL!C9bVqBlPwh8Kg8R7eeJQ_NokENEBwqmhkXBMNjwOZUs
Frankie_Xenon said:
For some reason the driver keeps asking me to install it after flashing 2 the zips.
Click to expand...
Click to collapse
Is your kernel still permissive? If not you can also try to flash the supolicy fix.
You can also try to remove completly the viper4android app and reinstall it.
Lastly there are some identified issues with some supersu versions. I am sure that the driver installation works with supersu 2.52 (my main one when I was on lollipop) and 2.68 (the one I use on marshmallow). Changing your supersu to 2.52 could perhaps help you. This is identified in the main viper4android thread here "If you see V4A installation pop-up loop, its probably due to incomplete root."
Hi. I have a G900H with stock rom, just rooted and Selinux enforcing and Viper works just fine. I just installed it and also installed busybox and flashed a file I got somewhere on xda to permit Viper on enforcing. I also had to verify my settings on supersu to uncheck the entry for namespaces. Hope it helps
Enviado desde mi SM-G900H mediante Tapatalk
So op, did you manage to make viper4android work?
alexbelgium said:
So op, did you manage to make viper4android work?
Click to expand...
Click to collapse
read the reply above you it gives you the solution
---------- Post added at 12:09 AM ---------- Previous post was at 12:04 AM ----------
alexbelgium said:
So op, did you manage to make viper4android work?
Click to expand...
Click to collapse
mannyvzla said:
Hi. I have a G900H with stock rom, just rooted and Selinux enforcing and Viper works just fine. I just installed it and also installed busybox and flashed a file I got somewhere on xda to permit Viper on enforcing. I also had to verify my settings on supersu to uncheck the entry for namespaces. Hope it helps
Enviado desde mi SM-G900H mediante Tapatalk
Click to expand...
Click to collapse
works like a charm thank you! lets spread this so more people will enjoy it
Also make sure "Mount Namespace Separation" is off in SuperSU.
{
"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"
}