Related
This is an Xposed module (See http://forum.xda-developers.com/showthread.php?t=1574401 for more on Xposed) that allows Netflix to work on CM10.1 on Exynos4 devices.
Source code is at https://github.com/Entropy512/XposedNetflixWorkaround - Use the Android Developer Tools Eclipse package to build it
To install:
Install the Xposed Installer APK from the thread linked above
Install the Xposed framework using Xposed Installer
Install the APK linked in this post
Reboot your device after enabling the module in Xposed Installer
Enjoy Netflix
How does this work?
For whatever reason, Netflix uses its own player, called JPlayer, if it detects that it is running on Android 4.2. For whatever reason, JPlayer does NOT like the current video subsystem in CM10.1 on Exynos4 devices.
What this module does is make Netflix always think that it is running on ICS, which will make it use what appears to be the system OMX player. (I'm not entirely sure of this, but I am sure that it is NOT JPlayer and it DOES work on all of my devices I've tested).
This is an interim workaround/hack until the root cause of JPlayer failing on Exynos4 devices can be determined. (Edit: From talking with a few people, JPlayer is replacing a number of components of Android's playback framework. This includes components that have been altered for Exynos4 compatibility.)
DO NOT REPORT THIS ISSUE IN CYANOGENMOD JIRA. No affected devices are receiving M or stable builds and this is one of the many reasons.
reserved 2 - probably not needed
Worked perfect thanks
Sent from my GT-N8013 using xda premium
I'm having issues installing Xposed - after I install the apk and hit the install button, it throws the error "cannot read /data/xposed/modules.whitelist".
Netflix still a no go for me!
Sent from my GT-N8013 using Tapatalk 2
Worked on the U2.
Sent from my Nexus 4 using Tapatalk 2
BeardedB said:
Netflix still a no go for me!
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
Working here... More details please?
dpwhitty11 said:
I'm having issues installing Xposed - after I install the apk and hit the install button, it throws the error "cannot read /data/xposed/modules.whitelist".
Click to expand...
Click to collapse
Could you try this installer instead? http://forum.xda-developers.com/showthread.php?p=36436643#post36436643
It's a known problem for some ROMs which fail to update /data/system/packages.list.
rovo89 said:
Could you try this installer instead? http://forum.xda-developers.com/showthread.php?p=36436643#post36436643
It's a known problem for some ROMs which fail to update /data/system/packages.list.
Click to expand...
Click to collapse
Worked perfectly, thanks!
Sent from my GT-N8013 using Tapatalk HD
Andrew, version 1.8.1 of Netflix works on Exynos4 + Jelly Bean. I'm not sure if it's the last known working version but it's an alternative; I took a stab and downloaded the version I thought might be at/around the last Netflix update for ICS.
Edit: arcee indicated that 2.1.1 will work in tomorrow's build, not sure if specific to Odroid only.
CMNein said:
Andrew, version 1.8.1 of Netflix works on Exynos4 + Jelly Bean. I'm not sure if it's the last known working version but it's an alternative; I took a stab and downloaded the version I thought might be at/around the last Netflix update for ICS.
Edit: arcee indicated that 2.1.1 will work in tomorrow's build, not sure if specific to Odroid only.
Click to expand...
Click to collapse
He took a different approach to killing JPlayer:
https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520
So this Xposed mod may become obsolete...
There's no clean way to do this. Either there is app-specific **** in the device tree that is difficult for users to remove if it ever gets derpy, or users have to actively search for a workaround such as this one.
Entropy512 said:
He took a different approach to killing JPlayer:
https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520
So this Xposed mod may become obsolete...
There's no clean way to do this. Either there is app-specific **** in the device tree that is difficult for users to remove if it ever gets derpy, or users have to actively search for a workaround such as this one.
Click to expand...
Click to collapse
Latest working version is 2.0.1, the APK is linked below. It is the last version before they have introduced the newest controls. Works just fine on S2 with CM 10.1.
http://www.mediafire.com/?4ra0wf9h441r1oo
This is the easiest solution for the problem right now. Don't update from Market, but that is I guess quite obvious.
kokesh said:
Latest working version is 2.0.1, the APK is linked below. It is the last version before they have introduced the newest controls. Works just fine on S2 with CM 10.1.
http://www.mediafire.com/?4ra0wf9h441r1oo
This is the easiest solution for the problem right now. Don't update from Market, but that is I guess quite obvious.
Click to expand...
Click to collapse
The Xposed solution allows you to update and install from the Market with no issues.
Arcee's "patch the configuration XML file" approach also works.
Entropy512 said:
The Xposed solution allows you to update and install from the Market with no issues.
Arcee's "patch the configuration XML file" approach also works.
Click to expand...
Click to collapse
I know, but I can't get it to work on my 2013-01-17 CM10.1 nightly S2, this was the best way to fix it.
Xposed can't install.
Entropy512 said:
reserved 2 - probably not needed
Click to expand...
Click to collapse
Is this something that will eventually be rolled into a cm 10.1 nightly update or will it always be something that has to be installed separately on the side? Thanks again for all your awesome work.
mauidiver40 said:
Is this something that will eventually be rolled into a cm 10.1 nightly update or will it always be something that has to be installed separately on the side? Thanks again for all your awesome work.
Click to expand...
Click to collapse
Dependent on the device maintainer I'm sure. My Odroid U2 has a fix merged in last night's nightly. YMMV.
Entropy512 said:
He took a different approach to killing JPlayer:
https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520
So this Xposed mod may become obsolete...
There's no clean way to do this. Either there is app-specific **** in the device tree that is difficult for users to remove if it ever gets derpy, or users have to actively search for a workaround such as this one.
Click to expand...
Click to collapse
Any chance of adding this to Galaxy S2 nightlies?
I've added <int name="nflx_player_type" value="6" /> manually to the config file and it works.
mauidiver40 said:
Is this something that will eventually be rolled into a cm 10.1 nightly update or will it always be something that has to be installed separately on the side? Thanks again for all your awesome work.
Click to expand...
Click to collapse
I'm considering using arcee's approach... I really dislike having app-specific **** in the device tree though...
I can't figure out why people are having issues installing Xposed - it has installed flawlessly on every CM10.1 device I've tried. The fact that it may fail on certain manufacturer-customized firmwares isn't relevant here as this hack is specific to CM10.1
The only thing I can think of might be that Superuser prompts aren't quite working right on some people's devices.
As to eventually including Xposed in CM itself - It is something I would love to see, however as a device maintainer, it's "above my pay grade". Including it directly in CM would require careful consideration and analysis by the project leads.
I'm working on a flashable zip that drops a script in init.d to get the job done. The script is based on https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520 although I had to tweak it a little to get it to work. I can share it once it is finished, if anyone is interested. It will also copy a script to addon.d so that as I update cm10.1, the hack will be persistent.
Hey guys!
These days I've started monitoring my cores on N9005 kitkat firmware (everything stock) and I've found that sometimes cores get stuck online and only a reboot fixes the issue.
EDIT !!! : PROBLEM SOLVED
*THE ISSUE IS CAUSED BY TOUCHWIZZ DVFS(DYNAMIC VOLTAGE AND FREQUENCY SCALING) SO THANK YOU SAMMY FOR THAT !
*THE ONLY WAY TO RESOLVE IT IF YOU ARE NOT ROOTED IS TO REBOOT WHEN YOU SEE THAT YOUR CORES DON'T WANNA GO OFFLINE(CHECK THEM WITH PERMOM OR SYSTEM MONITOR...ETC.)
*ANOTHER WAY IS TO ROOT AND WHEN THE ISSUE HAPPENS YOU CAN FIX IT BY RESETING MP-DECISION OR THE PERMANENT WAY IS TO INSTALL XPOSED FRAMEWORK AND THEN DOWNLOAD(DON'T FORGET TO ENABLE THE MODULE IN XPOSED AFTER YOU DOWNLOAD) FROM PLAYSTORE "SAMSUNG DVFS DISABLER" BY WANAM(JUST SEARCH IN PLAYSTORE THE WORD "DVFS" AND YOU WILL SEE IT - !
*OFC THAT AOSP OR CM BASED ROMS DON'T HAVE THE ISSUE !!!
BIG THANKS TO ALL THE GREAT GUYS ON LEAN KERNEL THREAD FOR CONTRIBUTING TO SOLVING THIS ISSUE
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
I experience the exact same issue, but on completely stock 4.4.2 rom. I posted a thread about it a while back but no one answered it:
http://forum.xda-developers.com/showthread.php?t=2646389
I'm positive this is the reason for people's battery drain on stock roms.. Does the stock rom implement some form of hotplug functionality? It must be bugged somehow.
It still happens, and it has not fixed itself. The only way to fix it for me that I know if is a reboot..
EddieN said:
I experience the exact same issue, but on completely stock 4.4.2 rom. I posted a thread about it a while back but no one answered it:
http://forum.xda-developers.com/showthread.php?t=2646389
I'm positive this is the reason for people's battery drain on stock roms.. Does the stock rom implement some form of hotplug functionality? It must be bugged somehow.
It still happens, and it has not fixed itself. The only way to fix it for me that I know if is a reboot..
Click to expand...
Click to collapse
I've found the issue.See what I've wrote in OP with red text :fingers-crossed:
ciprianruse88 said:
I've found the issue.See what I've wrote in OP with red text :fingers-crossed:
Click to expand...
Click to collapse
Thanks, I figured it would be something along those lines.
However I'm fully stock with no plans to root because of the Knox-debacle.. So I guess I will have to stick to rebooting until Samsung fixes the issue
Sent from my SM-N9005 using Tapatalk
EddieN said:
Thanks, I figured it would be something along those lines.
However I'm fully stock with no plans to root because of the Knox-debacle.. So I guess I will have to stick to rebooting until Samsung fixes the issue
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I don't think they will fix it because some users said that they have this issue since 4.3 and kitkat didn't fix it
ciprianruse88 said:
I don't think they will fix it because some users said that they have this issue since 4.3 and kitkat didn't fix it
Click to expand...
Click to collapse
Unfortunately this is also something I'm afraid will never get fixed. I noticed similar battery drain on 4.3 but never narrowed it down to cores bugging out until kitkat. Maybe I'll root anyway..
Sent from my SM-N9005 using Tapatalk
On stock nc2 deodexed with dvfs disabled via wanam, my powersaving mode no longer brings the frequency down. Only if i disable the module and reboot.
Sent from my SM-N9005 using Tapatalk
celderic said:
On stock nc2 deodexed with dvfs disabled via wanam, my powersaving mode no longer brings the frequency down. Only if i disable the module and reboot.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
For me works fine but I am on latest Omega Rom
ciprianruse88 said:
For me works fine but I am on latest Omega Rom
Click to expand...
Click to collapse
Hmmmm very strange
Sent from my SM-N9005 using Tapatalk
ciprianruse88 said:
For me works fine but I am on latest Omega Rom
Click to expand...
Click to collapse
Works fine for me as well on xnote. Great find bro..
PS- Btw might wanna edit the title to show that you have found a fix.. :thumbup:
Sent From My SM-N9005 To All You Wonder Nobodies!!
Khizar said:
Works fine for me as well on xnote. Great find bro..
PS- Btw might wanna edit the title to show that you have found a fix.. :thumbup:
Sent From My SM-N9005 To All You Wonder Nobodies!!
Click to expand...
Click to collapse
You are right ! Thanks for the suggestion :highfive:
Dont work for me. I disabled DVFS yesterday in newest version of wanam xposed, rebooted and checked settings in wanam again. DVFS was unchecked, so I think it is/was disabled. But today´s morning, i had 2 core stuck online again, almost the same as the few issues before unchecking DVFS. So I think, it doesnt work for me. Note 3 SM-N9005...
I been trying to off dvfs. What I can see. It will always run high frequency. Phone get warm and using phone while charging took longer than usual.
Because I run games and always on screen plus charging. So turning off dvfs not a good idea.
Sent from my SM-N9005
I've been testing different firmwares with DVFS off since I started this thread and not once I have seen again 4 or 2 cores stuck online and battery is better than ever so for me this was definitely the cause of random 4 cores stuck online. Good luck !
I'll be trying this for a while. But yeah I did notice that power-saving CPU limiting option does not work if DVFS is off. Mine reaches maximum frequency
Strangely, the Wanam Xposed module never did its job for DVFS, though the standalone module does work, and both are from Wanam.
Do not settle for Wanam Xposed, it is a useful utility but not all features seem to work in Note 3. I.E, Volume UP while on Deep Sleep wont trigger the flashlight, even though you activated the feature, yet the standalone module just for that (again, from Wanam) works perfectly.
http://repo.xposed.info/module/ma.wanam.dvfs
ardom said:
I'll be trying this for a while. But yeah I did notice that power-saving CPU limiting option does not work if DVFS is off. Mine reaches maximum frequency
Click to expand...
Click to collapse
For me works fine with every firmware I tested. Maybe you need a clean wipe.
PlutoDelic said:
Strangely, the Wanam Xposed module never did its job for DVFS, though the standalone module does work, and both are from Wanam.
Do not settle for Wanam Xposed, it is a useful utility but not all features seem to work in Note 3. I.E, Volume UP while on Deep Sleep wont trigger the flashlight, even though you activated the feature, yet the standalone module just for that (again, from Wanam) works perfectly.
http://repo.xposed.info/module/ma.wanam.dvfs
Click to expand...
Click to collapse
Yes. I too am using the standalone DVSF mofule from playstore but I remember testing wannam xposed on NB2 firmware and worked fine. I am glad that we found a way to fix this Sammy bug but I am disappointed that they didn't and I don't think they will ever do so this is probably my last Sammy device.
ciprianruse88 said:
Hey guys!
These days I've started monitoring my cores on N9005 kitkat firmware (everything stock) and I've found that sometimes cores get stuck online and only a reboot fixes the issue.
EDIT !!! : PROBLEM SOLVED
*THE ISSUE IS CAUSED BY TOUCHWIZZ DVFS(DYNAMIC VOLTAGE AND FREQUENCY SCALING) SO THANK YOU SAMMY FOR THAT !
*THE ONLY WAY TO RESOLVE IT IF YOU ARE NOT ROOTED IS TO REBOOT WHEN YOU SEE THAT YOUR CORES DON'T WANNA GO OFFLINE(CHECK THEM WITH PERMOM OR SYSTEM MONITOR...ETC.)
*ANOTHER WAY IS TO ROOT AND WHEN THE ISSUE HAPPENS YOU CAN FIX IT BY RESETING MP-DECISION OR THE BEST WAY IS TO INSTALL XPOSED FRAMEWORK AND THEN DOWNLOAD(DON'T FORGET TO ENABLE THE MODULE IN XPOSED AFTER YOU DOWNLOAD) FROM PLAYSTORE "SAMSUNG DVFS DISABLER" BY WANAM(JUST SEARCH IN PLAYSTORE THE WORD "DVFS" AND YOU WILL SEE IT - !
*OFC THAT AOSP OR CM BASED ROMS DON'T HAVE THE ISSUE !!!
BIG THANKS TO ALL THE GREAT GUYS ON LEAN KERNEL THREAD FOR CONTRIBUTING TO SOLVING THIS ISSUE
Click to expand...
Click to collapse
galaxy note 3 sm-n9005xxufng2 wanam xposed Touchwiz DVS working perfect
First off, you do this at your own risk and I'm not responsible for any damage to your phone etc etc. Also, thanks to it's ties with Sound Alive, it won't work with the stock music player unfortunately but I have tested it with both Spotify and GoneMad and it works perfectly with both.
I'm using this on AryaMod 3.1, so this should mean the instructions below work on any N9005ZSUGOA5 based Lollipop rom.
1) Download and install DarkQueen Kernel here. Thank @hiepgia.
2) Add the line "setenforce 0" (without the quotes) to the end of the file /sýstem/etc/init.qcom.post_boot.sh. This will ensure a permissive state on boot. Thanks to @hiepgia and @filchi756 for this.
3) Download and install the new Viper4Android 2.3.4.0 here. Run, install the driver.
4) Find and freeze/delete Sound Alive. This being present is bad in particular for Spotify, which will always use Sound Alive in preference to Viper4Android.
Reboot enjoy Viper goodness.
For people who want to use the stock player, see @filchi756 post here
For people running AyraMod V4.0, ignore the above instructions, select DarkQueen kernel via Aroma on install (this will automatically result in permissive SE) and please see @filchi756's modified zip here. Don't forget to thank him.
Awesome
Finally!
Oh I am seeking for that. :good::good::good:
After flashing this kernel, WiFi stopped working... Anybody else has this issue? SM-N9005
slavko17 said:
After flashing this kernel, WiFi stopped working... Anybody else has this issue? SM-N9005
Click to expand...
Click to collapse
it works fine like a charm
Unfortunately, it won't work for me... As soon as I flash stock kernel back - wifi is working like a charm again. Tried to do factory reset after flashing this Dark Queen Kernel - it didn't solve the problem.
Any suggestions would be appreciated.
slavko17 said:
Unfortunately, it won't work for me... As soon as I flash stock kernel back - wifi is working like a charm again. Tried to do factory reset after flashing this Dark Queen Kernel - it didn't solve the problem.
Any suggestions would be appreciated.
Click to expand...
Click to collapse
We have the same situation. .I think we have to wait for google to release the lollipop sources for note3 and wait for someone to make a custom kernel intended for our phone.
OP updated.
You eventually did it. Well done!
Nice one! Could anybody make it work with the stock Samsung Music Player using this tutorial? It seems this app is deeply integrated with SoundAlive, so at least with KK it was impossible to make it work reliably with V4A. But things may have changed with LL...
Yeah, unfortunately it appears to be the same here. I froze Sound Alive to get Viper working with Spotify, but this results in no effects whatsoever with the stock music player. Personally, this doesn't bother me as there are far better players on the market.
slavko17 said:
After flashing this kernel, WiFi stopped working... Anybody else has this issue? SM-N9005
Click to expand...
Click to collapse
What baseband are you on? You have the same phone model as myself and my wifi works fine. I suspect it might be related to your modem/NON-HLOS.
Overall everything works fine except few bugs from the Darkqueen kernel, like brightness changes sometimes when I lock/unlock the phone.
Attachement selinuxpermissive installation failed :crying:
rafik25 said:
Attachement selinuxpermissive installation failed :crying:
Click to expand...
Click to collapse
What fails? Did you give it full permissions?
Try this one instead.
Beefheart said:
What baseband are you on? You have the same phone model as myself and my wifi works fine. I suspect it might be related to your modem/NON-HLOS.
Click to expand...
Click to collapse
I'm on the newest XEO Lollipop available from sammobile, so the modem version I have is BNL8.
Thanks for trying to help me
I'm on GNH1 myself. Might be worth trying another to see if the WIFI works.
Sir please help us too. I'm using galaxy s4 i9500 with official lollipop installed. we don't have any permissive kernel.
jagnik said:
Sir please help us too. I'm using galaxy s4 i9500 with official lollipop installed. we don't have any permissive kernel.
Click to expand...
Click to collapse
If you're correct and there is no kernel which is either permissive or can be made permissive then Viper is currently unusable on the Exynos variant of the S4. It's currently impossible to use Viper on an enforcing TW ROM.
I got a problem. Sometimes, I tap the home button, nothing happen. I need to tap twice to go to home.
This happens randomly and logcat can't catch any log about it.
Tried blisspop and temasek, both give same bug. Sometimes, it happen often but still randomly.
Both nav bar and hardware button have same problem. Anyone got this problem too?
Edit: Video showing the bug https://youtu.be/aUtxP7K3cxE
Bump
Bump
psycholyzern said:
I got a problem. Sometimes, I tap the home button, nothing happen. I need to tap twice to go to home.
This happens randomly and logcat can't catch any log about it.
Tried blisspop and temasek, both give same bug. Sometimes, it happen often but still randomly.
Both nav bar and hardware button have same problem. Anyone got this problem too?
Edit: Video showing the bug https://youtu.be/aUtxP7K3cxE
Click to expand...
Click to collapse
Did you do a clean install or just a dirty flash?
Flatric said:
Did you do a clean install or just a dirty flash?
Click to expand...
Click to collapse
Clean flashed 2 or 3 times.. All wiped except my internal.
psycholyzern said:
Clean flashed 2 or 3 times.. All wiped except my internal.
Click to expand...
Click to collapse
Maybe it has something to do with an app you have installed
Flatric said:
Maybe it has something to do with an app you have installed
Click to expand...
Click to collapse
I can confirm this issue does not exist on mahdi rom 4.4.4
Im using mahdi rom now..
I tried blisspop latest version. Damn!! The problem still exists..
Blisspop, temasek, hazyrom, same issue happened...
Hmmmm..
No one have same problem like me?
Try Euphoria. Double tap home will sleep the device and single tap works fine in which case you can tap to go home. These are all customization .
hp13 said:
Try Euphoria. Double tap home will sleep the device and single tap works fine in which case you can tap to go home. These are all customization .
Click to expand...
Click to collapse
Ok I will try later. Now Im on cm12s official stock rom.. Im happy with it because there is no issue.
psycholyzern said:
Ok I will try later. Now Im on cm12s official stock rom.. Im happy with it because there is no issue.
Click to expand...
Click to collapse
CM12s is good but its code is outdated. Other Cm12.1 roms offer both latest code/androi dversion and more customization. They are fairly stable for daily use. Theme engine in 12.1 is better and also DPI changer which is very useful. But its just my opinion
hp13 said:
CM12s is good but its code is outdated. Other Cm12.1 roms offer both latest code/androi dversion and more customization. They are fairly stable for daily use. Theme engine in 12.1 is better and also DPI changer which is very useful. But its just my opinion
Click to expand...
Click to collapse
You are losing my point actually. As stated in this thread's title, I got an issue where sometimes, I need to tap on home button twice, to go to the home. Tapping once doesnt do anything.
I tried temasek, blisspop, cyanide and hazyrom. All of them are based on android 5.1.1 right?
I have tried mahdi 4.4.4 and this issue doesnt came out. So I am trying cm12s and srill there is no issue. Perhaps, Euphoria may have this issue as well.
Btw, thanks for recommendation.
That's great that its not in present in cm12S
Just flashed latest temasek a few hours ago.
Same bug still exists.
??????
After lots of tries i found there is a problem between Xposed and All other camera mods for our Z3 (i have no info about other phones like Z2). So we cant use Xposed + Pexocam or Cyberian or... in Marshmallow (there is no problem with LP!) and it gives u something like this message: "Camera is in use by another application, please close other apps..."
(Note i tested with both .575 and .570)
Anyone has a workaround or has both Xposed and camera mod without problem??
agent.47 said:
After lots of tries i found there is a problem between Xposed and All other camera mods for our Z3 (i have no info about other phones like Z2). So we cant use Xposed + Pexocam or Cyberian or... in Marshmallow (there is no problem with LP!) and it gives u something like this message: "Camera is in use by another application, please close other apps..."
(Note i tested with both .575 and .570)
Anyone has a workaround or has both Xposed and camera mod without problem??
Click to expand...
Click to collapse
I have xposed v85 and have used both of those mods. Likely it's a module than xposed as a whole as I have no trouble.
Have you confirmed it works without xposed installed? Maybe it's another mod?
Dobsgw said:
I have xposed v85 and have used both of those mods. Likely it's a module than xposed as a whole as I have no trouble.
Have you confirmed it works without xposed installed? Maybe it's another mod?
Click to expand...
Click to collapse
Yeah I confirm its Xposed, Without it everything works fine
I just had gravity box on xposed but i cleared its data so that must be a xposed problem
I confirm again
Tried once again with just xposed installed (all modules except greenify - which is inactive- were uninstalled) and camera mods not working.
I dont know how this could happen since you have both xposed and camera mods!
I did this:
flashed rom --> flashed Pexocam v8 --> Everything working fine --> Flashed latest Xposed --> Pexocam not working!!!
agent.47 said:
I confirm again
Tried once again with just xposed installed (all modules except greenify - which is inactive- were uninstalled) and camera mods not working.
I dont know how this could happen since you have both xposed and camera mods!
I did this:
flashed rom --> flashed Pexocam v8 --> Everything working fine --> Flashed latest Xposed --> Pexocam not working!!!
Click to expand...
Click to collapse
Flash xposed first.
I always flash ROM, Xposed, then mods.
Tbh it shouldn't make much difference but something to try.
I'm on MWA 5.0.0 by Pandemic.
If you use custom ROM perhaps something has been edited that the camera required to function?
There's a lot of variables here :/
Could try another ROM with xposed and camera mod and see if it works?
Troubleshooting is gonna suck on this one as it works for some and not others.
Well i tested flashing xposed then camera, makes no difference
I use stock pre-rooted .575, it mustn't be problem because i had that problem with .570 too but there wasn't any problem with LP roms with same xposed version!
I saw some other people had this problem, i used almost all of their solution like clearing data and cache, completely removing camera then installing new mod, etc, but non of them works. That's a xposed problem and idk what's wrong!
Note that I'm using D6633 variant
agent.47 said:
Well i tested flashing xposed then camera, makes no difference
I use stock pre-rooted .575, it mustn't be problem because i had that problem with .570 too but there wasn't any problem with LP roms with same xposed version!
I saw some other people had this problem, i used almost all of their solution like clearing data and cache, completely removing camera then installing new mod, etc, but non of them works. That's a xposed problem and idk what's wrong!
Note that I'm using D6633 variant
Click to expand...
Click to collapse
Its "not" an xposed problem, its quite easy to blaim xposed but i use it a long time and totally no issues with it, maybe is it just the camera mod or duplicated lines in the end of your build.prop !
Pandemic said:
Its "not" an xposed problem, its quite easy to blaim xposed but i use it a long time and totally no issues with it, maybe is it just the camera mod or duplicated lines in the end of your build.prop !
Click to expand...
Click to collapse
I use xposed for a long time too and I never had any issues with it - thanks to its creator - but whenever i uninstall xposed, camera mods work well. Idk if there is any problem with build.prop but it mustn't be camera mod problem since many users installed it successfully.
Do you have superuser mod?
Are you using the versión of MM?
latest versión?
Logs?
panchuckles said:
Do you have superuser mod?
Are you using the versión of MM?
latest versión?
Logs?
Click to expand...
Click to collapse
1. I had Rajeev's Superusermod for cyberian camera III since it was needed but for PexoCam i didn't flash it.
2. I use MM version
3. Everything is at latest version
4. No logs
Hello, sorry that I've dug out an old post. But yes, my Xposed is also conflicting with camera mods (both Cyberian & Pexocam). Camera mods worked when Xposed framework was not installed but once installed, crashed.
Have you found any workaround?
On stock pre-rooted .575 (D6653) as well.
Thanks!
I haven't found any workaround yet
Maybe professionals could help us if they see this thread