yashsingh1/xdaforums huggingface dataset:
[Xposed General] magnamentis:
you both should read carefully:

a) i recommended to mention the developer so he gets a notice and eventually drops in to have a look

b) eventually means, don't expect any reply soon, he is busy with business and has only little time, as you might have recognized

....there is more or less not one post by him except on page one, he probably follows his threads but does not take part in discussions.

do your logs were the right things to do but now you need patience or keep trying and do what i recommended

"edit your posts by adding a mention!
[Xposed General] sully51:
I wiped and reinstalled with the latest beanstalk. Now I get the NFC fc that won't go away. I tried disabling NFC but still get the error. Trying to find the fix but I seem to not have my google-fu working today... Sigh
[Xposed General] vegetaleb:
[MENTION=4419114]rovo89[/MENTION]

Please take a look at my log
[Xposed General] StonedYoda:
Sorry if this is a stupid question, but would Xposed work on Galaxy Note 3 running CM13?
[Xposed General] magnamentis:
Yes, works, enjoy
[Xposed General] unpause:
Take xposed-v80-sdk23-arm64.zip :)
[Xposed General] Xipe_Totec:
sorry for the dumb question but what zip I have to flash on asus tf300t running android 6?

Thank you in advance.
[Xposed General] rasteck:
Hi, Im trying to install last version of xposed to my phone. Is an HTC One m9, with marshmallow. I flashed the last sdk version, and I installed the alpha4 apk, but when I try to install framework, it tells me that the only way to install framework is on recovery. How can I do this??
[Xposed General] grep_i:
Yeah that's right and is the way to go since Android 5.0 that's what they call flashing.

Don't know what you did but it might be you didn't flash last SDK version.

Also try to tell about version numbers nobody knows what last version to you.

You have to flash a custom recovery on your phone with the use of adb and fastboot.

I use twrp for that.

If your phone is already rooted than you can install flashify from play store to install custom recovery with that app.

After that boot your phone to custom recovery find your last SDK version file location and select it for install.
[Xposed General] siealex:
What CPU does this tablet have? Most probably ARM, try sdk23-arm.
[Xposed General] Xipe_Totec:
ty trying out now.
[Xposed General] rasteck:
Ok, you were right. I installed the wrong apk (alpha 2) hahaha. Sorry, my fault :(.

Anyway, thanks for the help. And I take note about flashify, I didnt know that app ;)
[Xposed General] jojo_on:
I'm using Mi3 with MIUI 6.0.1.

Which Xposed version i can install?
[Xposed General] grep_i:
I'm glad I could help you out
[Xposed General] xdvs23:
So I copied my post from another thread. I would be glad if anyone can help.
[Xposed General] siealex:
I had such bugs occasionally on Lollipop.
[Xposed General] jojo_on:
Any help for me with xiaomi mi3 marshmallow 6.0.1
[Xposed General] magnamentis:
only for the future, sounds perhaps wrong but is well meant and i do the same for myself:

in future watch development of devices under evaluation and don't buy devices with poor developer support.

this start with the fact that best supported devices have qualcomm chipsets and so on. i just fell into that trap with the OP2 which other than the OPO has poor or at least slow developement caused by proprietary features like laser focus and proprietary fingerprint scanner.

my lesson which i learnd ( knew it before but didn't expect that ) is to wait a few months into a device's life cycle and see what happens on the def

front and if strange posts amass that indicate the device is poorly compatible with important and/or common mods i won't buy.

i know that this does not solve your issue but still if you follow that path you won't have the problem in the first place. and xiaomi is a common keyword if one would search for devices where stuff doesn't work as expected. just search this thread for xiaomi or miui and you'll see.
[Xposed General] vedantpro:
Xposed never worked correctly on miui and probably never will...

Xposed usually works well with rom which are closer to stock

So my advice would be, install CM on Mi 3 if you want to use xposed

Or else you can experiment and go through some bootloops
[Xposed General] ToF_Itachi:
So I'm on a lg g3 vs985 using the official CM13 ROM. I installed I believe it was the v80 sdk23arm? And it flashed successfully but I installed the installer app version 3.0alpha4 and after trying to activate my modules it and rebooting it now does nothing but crashes. Any help or advise? The MM version is 6.0.1 if that helps
[Xposed General] magnamentis:
that means that one of your modules is not compatible and it also means that you did that wrong. you should only activate one module after another because then you would already now know which one it is. now you have to unistall/remove the entire thing, xpsosed and all modules from recovery, reboot into system to verify it's working as expected and then repeat the xposed installing process a bit more patiently and carefully.

if you look at the list of you modules and if you have a little bit of experience you should see at a glance the possible culprit/s because standard modules usually don't crash once of a sudden. why i'm saying this is because you can start with those to reduce the extra work.

MOST IMPORTANT: make a nandroid backup of the xpose-less working setup so that in case you have furhter bootloops or othe issues you can simply revert back to that nandroid and repeat the process without the module that made the sh...t hit the fan LOL
[Xposed General] sam008:
Exchange PIN bypass

Folks

Has anybody tested the Exchange PIN bypass module - it basically allows you to bypass any PIN requirements to connect email to corporate exchange and worked wonderfully in Lollipop

Thanks
[Xposed General] grep_i:
Sorry can't say I have tested this module also this thread is about Xposed framework and installer issues.

Not about modules you can ask the developer about these things or find another thread.
[Xposed General] satya64:
[MarshMallow] Install Xpose in 64bit Atom processor

Hi

Can we install xposed installer in Atom x86_64 (64 bit) android devices? I asked this because, I could see the custom recovery files of 64bit processor of atom.

Please find the http://xdaforums.com/showthread.php?t=3034811 .

Please some one help me on this
[Xposed General] adhabe:
Need v79

I need xposed-v79 sdk 23 for unofficial cm13 6.0.1..bcoz v80 is not working for me
[Xposed General] siealex:
ARM 32 bit? Try this one.
[Xposed General] adhabe:
Thanks :)
[Xposed General] tanpro260196:
Anyone try xposed on Zenfone 2, CM13 ROM? Any serious bug?
[Xposed General] panjalgmk1panjalgmk1:
Facing this proplem on my p8000..how to solve it? ?
[Xposed General] Nergal di Cuthah:
provide log (the screen even says that the log will tell you why)
[Xposed General] hhhfdq:
hi..any body flash xpose on android 6.0 m9 sprint?
[Xposed General] Thorge01:
First my device: HTC one M9 HIMA, TWRP 3.0.0, Build 3.35.401.12 CL671758, Kernel 3.10.84, Baseband 01.01_u11440792....., S-off, SuperSU Pro v2.65 (stable), Sense 7, Android 6 Marshmallow

Just installed xposed-v80-sdk23-arm64.zip via TWRP 3.0.0 and right after reboot (takes about five minutes) the XposedInstaller_3.0_alpha4.apk - - - - - > Xposed v80-sdk23-arm64 works fine for me.

IMPORTANT: If you install any module just install one, check out if it works and then try the next one, check if it works and so on - remember, xposed for Marshmallow is brand new and not all modules have been updated for Marshmallow so far - so if you install the modules you want install one after another so if you run into a problem you then you know exactly which module causes the problem!!!

If modules not work or even cause lags, crashes or bootloops the reason for that might not be a problem of the module itself - keep in mind that most of the modules are NOT!!!! created for Marshmallows but for Lollipop or Kitkat!!! Also a reason for not proper working could be that a module collides with a regular app installed via playstore (or contrariwise). So just think about that too.
[Xposed General] Athakuri700:
Can I get xposed installer for arm v7 zip file
[Xposed General] siealex:
Use an ordinary ARM package.
[Xposed General] Athakuri700:
Give me the link
[Xposed General] Ja_som:
Is in OP
[Xposed General] Athakuri700:
OP what does that mean?
[Xposed General] Ja_som:
Original Post, or first post...
[Xposed General] Athakuri700:
Oh hehe... ;)
[Xposed General] xdvs23:
I have done that, at the end everything worked, but after one or two reboots I get a bootloop again and need to disable all modules at once by deleting xposed installers data! Any workaround/fix? I tried disabling/uninstalling some modules but does not work. All modules disabled -> no bootlop, all modules enabled -> bootloop.... Idk, if I wipe dalvik and reinstall xposed some times it finally works fine for one or two reboots but then bootloop again. Logcat doesn't tell me anything, but Zygote seems not to start up, xposed modules are all loaded without problems and then nothing happens anymore, the system seems to sleep.... In liveboot I can see that there's no further output. Nothing from PackageManager, and only regularly something from art saying "Starting explicit GC" and again something with GC that it freed up some space. But nothing more. If I wipe dalvik without uninstalling xposed and let all xposed remain activated, only the modules and the framework are dexopted (dex2oat and stuff) but all the other apps NOT.

Help pls.

Hint: look into my signature to find which rom i am using... Blissmallow
[Xposed General] jokerpoker1:
Good morning at all, There still exists the Xposed module to obtain the tablet ui ?

Thanks
[Xposed General] grep_i:
You quote someone that says enable modules one by one and you are talking about enabling all at once, that's not the same it might be if you have only one module but I guess not because you're talking in plural form.

Just try the suggestion that was given to you.

Install Xposed without any modules enabled.

Install one module, reboot device and see if everything keeps working. In your case as you specifically say after one or two reboots you get bootloop I would boot 2 times after module install.

Now if everything still is working install another module reboot one or two times and see if everything keeps working.

From here I think you will catch the drill if you do it this way you will find out whatever module is giving you the bootloop so you can search for an replacement or completely disable it until it gets updated.
[Xposed General] xdvs23:
I have done that, like already mentioned in my post. I enabled one after another and it worked but after two reboots it didn't work anymore without changing anything.
[Xposed General] grep_i:
So after which module did the bootloop happen than ?

You should just know it if you did exactly what is mentioned.

Or am I missing something you said ?
[Xposed General] mielletseed:
or Opening Post ... :laugh:
[Xposed General] rogers11:
Yes, just read exactly what he wrote.
[Xposed General] Ja_som:
Wrong thread...

Oh, yes, that too :)
[Xposed General] TNSMANI:
He has enabled the modules one by one and all of them work singly and together. But when the phone is rebooted a couple of times, for whatever reason, he gets the bootloops. After that he has to disable Xposed to boot the phone.

Now read his earlier post with this info and help him if possible.
[Xposed General] Thorge01:
There is no regular workaround for every single device and its problems - sorry to say but keep in mind that there are many diffrent reasons for problems. To find out specific problems on every diffrent device each owner need to run logcat to find out what causes the problem. You need to understand that using Xposed and its modules is always a try and error. No developer can create a software which runs on every device 100%....

If (in your case) nothing helps (what`s been posted here already) you should either reinstall just everything and try again or go for an other custom rom till everything workes fine for you!

Let`s take a look what you could do.....

First install the latest TWRP 3.0.0 for your device from here: (find your device in the list) https://twrp.me/Devices/

Second install the latest stable SuperSU from here: http://xdaforums.com/showthread.php?t=1538053

Third after sucsessfully installed and proper working TWRP and SuperSU install "xposed-v80-sdk23" and "Xposed installer 3.0 alpha4 apk" from OP (original post/first page) and after installed the Xposed installer apk check after reboot if "Xposed framework 80 is active" .

Fourth if Xposed framework 80 is active just try ONE!!!! module of your interest, install it and work with it for maybe a day or so and if there are no issues go for the next one.

NEVER!!!! install several modules at once and activate them - not a good idea cause if there is an issue after that you`re not able to tell what module causes the trouble!

Fifth if Xposed framework 80 is NOT!!! active you have two options: First just forget Xposed on your device or second try Xposed with a different custom rom!!!
[Xposed General] grep_i:
OK I step aside I really don't understand that he install a module and reboots 2 times without problems and only if all the modules are activated and he reboots two times he than has the issue.

I could say that by removing the modules in backwards order you maybe can restore your device from bootlooping.

Don't know if you know how to disable modules via adb, fastboot or terminal. Another approach could be reading all the developers sites of the installed modules to see which one is not compatible with Android marshmallow.

Another approach would be to only install one Xposed module and work with that for 2 whole days and after install a second module and work with the two modules enabled for 2 days, etc.
[Xposed General] xdvs23:
I did enable one module after another. When I finished that, no bootloop. But then after 2 reboots the bootloop comes again. I think the problem is LPThemer or Holo Themer. I have disabled both. I will check later if the problem persists.

---------- Post added at 07:26 PM ---------- Previous post was at 07:18 PM ----------

On OxygenOS everything worked just fine.

On Exodus 5.1 I had bootloops too but I was able to fix them by easily uninstalling xposed, rebooting and then installing it again. That was a thing of 4 minutes and quickly done.

On CM13 I had the same problem I have on BlissMallow.

It seems to be that LPThemer and Holo Themer are causing it but I don't know. I have to wait a while and reboot sometimes to see if it actually works.
[Xposed General] Nergal di Cuthah:
As the former does not work with Marshmallow at all, and the latter I think was only updated recently (and maybe just to accommodate the new pro license) it's likely the issue. Plus, don't they conflict with each other :unsure:
[Xposed General] magnamentis:
EDIT: i see others were hinting into the same direction but this should be on each page anyways hence i let it stand LOL ;)

no such issue, same combo, it's one of your modules the way to troublehoot is to disable modules except those 100% known to be save, eventually uninstall xposed entirely, and start testing by installing one component after another until the issues start again, then uninstall last 2 installed modules and repeat until it starts again which tells you which module not to use in the future.

further you don't mention any modules, perhaps someone would know already and one could safe oneself the entire back and forth guessing. always provide maximum and not minimum info and modules in use are first with a working install that is causing trouble way after installation.

and a log would be helpful most probably, helps a lot to replace knowledge with guesswork.
[Xposed General] Thorge01:
But you know that LPThemer and Holo Themer were not written for Marshmallow and were not updated so far?

Just use (and learn how to use) logcat to find and locate a problem. To guess is not the way to solve issues!
[Xposed General] xdvs23:
Well, I used LPThemer only to change the status bar color inside whatsapp. Holo Themer was only to use Material theme in some apps which were still using holo. And I don't think that they conflict each other because holo themer is only changing the theme of single applications and lpthemer is theming other specific stuff. But thx anyways.

---------- Post added at 07:18 AM ---------- Previous post was at 07:17 AM ----------

As I said, I did not find any useful information in logcat. It only loaded the Xposed modules and then nothing happened anymore.
[Xposed General] xdvs23:
Already did that mate, but it didn't work. I keep LPThemer and Holo Themer now disabled. I had no bootloop since then. So one of these modules (probably both) are causing the bootloop. Keep in mind that I have LiveBoot where I can check errors during boot.
[Xposed General] grep_i:
This advice was given to you all along I'm glad you finally followed the advise of disabling non compatible modules and you have no problems anymore.
[Xposed General] xdvs23:
Yeah, you're right, the problem was just that the bootloop only appeared after 1-3 reboots. I did not respect that while trying to find out which was causing the problem. Now it worked and I am glad that I have no bootloops anymore.

---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------

I had already installed TWRP 3.0.0, SuperSU, the latest xposed installer apk and the v80 arm64 xposed framework, so no action would be necessary in that situation. The problem also was there on CM13. But thank you anyways for you good explanation.

Problem solved now.
[Xposed General] deBricker:
Anyone else go into a bootloop running the stock ported Marshmallow ROM for the LG G3(d851)?
[Xposed General] MiroShining:
I had the same issues with my s5 mini with unofficial cm13 yesterday. I got xposed running by using the installer 3.0apk and the v80 SDK 23 flashable file form the unofficial forum. However, it is good or even necessary to wipe all data, make a clean install of cm13 and gapps, boot the system and do your settings-stuff and then first flash the xposed framework and after that install the apk. that worked fine for me for 1 day and then I got some serious heat issues with the phone and I thought it was CM13 itself in the first place. So I installed cm12.1 with xposed.... same issues. Today I installed CM13 again, without xposed and what shall I say, no issues at all. I guess I'll wait for a new cm13 update or another stable xposed for cm13.

update: Another thing came to my mind: I've used xposed only because of the netflix issues in CM12.1 and greenify on cm12.1 and cm13. greenify makes no really sense anymore on cm13 i guess and MAYBE, just maybe, greenify could have been the problem too.
[Xposed General] grep_i:
That's probably the case because greenify is not compatible with Android 6.0.1
[Xposed General] Revan335:
Xposed don't started no more on S5 CM 13.

Xposed Log qoute:

02-15 23:08:39.947 E/Xposed ( 474): Found /data/data/de.robv.android.xposed.installer/conf/disabled, not loading Xposed
[Xposed General] barrelr0ller:
Random crashes I guess?

So I've been having this problem on my rooted stock ROM Nexus 6 for multiple iterations of exposed (on LP and MM). Everything would be working well, until some time randomly throughout the day, xposed module will randomly stop running. Advanced power menu via gravity will be gone, snapprefs get buggy, etc. On a seemingly unrelated note, GPS also gets inaccurate by a few streets. All is solved with a restart, but it's getting cumbersome having to guess everyday when the phone is crapping out. System wipes haven't helped. Any ideas?? Any help would be greatly appreciated!
[Xposed General] Didgeridoohan:
Go to the conf directory and remove "disabled" and you'll be fine.

---------- Post added at 04:59 ---------- Previous post was at 04:56 ----------

Probably one of your modules are messing you up. I've been running Xposed on my stock N6 since Lollipop and rarely had any problems. I only run Amplify, Greenify and GEL settings.
[Xposed General] TNSMANI:
Why do you say that? Can you elaborate?
[Xposed General] grep_i:
Check site for greenify and read it
[Xposed General] TNSMANI:
I regularly read the Greenify sub forum and also participate in it. I have not come across any such info there.

Further, I am using Greenify with MM 6.0.1 without any issues.
[Xposed General] xdvs23:
Yeah. I always flash gapps, xposed and cyanogen apps directly after installing the ROM before first boot.
[Xposed General] grep_i:
Nowhere do I see mentioned that Android 6.0.1 is supported only 6.0 and that something is running is not necessarily means it is supported.

A lot of others are having issues when using greenify and as soon as they remove greenify their problem is solved.

I'm not going to back this up with prove or examples you can find that for yourself on this and other threads.

Also to me it is debatable if greenify is still needed when using Android MM with doze function but that is my personal opinion I think the real benefit of the app is not there anymore with the release of Android MM.

I understand that the developer made new experimental features to try to make Android doze even doze more or deeper but that is still highly experimental and yeah it is possible that can give weird issues to a lot of people we will see in the upcoming versions if these experimental features will stay experimental or become regular features or even disappear.

I'm very glad that it all seems to work for you and hope it does stay that way.
[Xposed General] Magnifik81:
So, i flashed a new rom Pure Nexus 6.0.1 with the latest EX kernel for my Nexus 5... And wiped cache/dalvik, flashed Xposed 80 sdk23, wiped cache/dalvik again.. And it bootlooped, I tried three times.. Here's a log http://www.speedyshare.com/b4bwE/xposed-error-20160216-152115.log
[Xposed General] grep_i:
You sure have a lot of modules enabled already for someone who flashed a new rom, are those included in the rom or did you forgot to mention it.

Gravitybox and greenify are mainly crashing and a lot of other modules too if reading your log.

Can you try and disable all modules and enable only the ones you really need or want.

After flashing Xposed with no modules installed or enabled try first installing gravitybox, reboot and after that try installing greenify, reboot and if everything keeps working install other wanted or needed modules one by one with after every new module a reboot.

If bootloops come back you pretty much know which module gives you problems.
[Xposed General] Magnifik81:
Yup, they were left from the previous one(Backuped the Xposed app via titanium), genius I know..? The problem was some modules were not supported by Marshmallow, so I updated the ones which had an update, and uninstalled the ones who didn't. And it BOOTED!??

XPOSED POWER!

And yup, You were right, but I'm reading this after sorting it out by myself. Thanks!! Cheers!
[Xposed General] Thorge01:
Hey, good to hear that you found the cause of the bootloop.

Thank`s for the clou about "LiveBoot" App - never heard of it before so i`ll give it a try....

Take care bro!

Update "LiveBoot"

This is awesome - now i have the ability to check out what`s going on during bootup and via log to find out any problems (but everything just fine on my device ;o)
[Xposed General] rabbo3:
Hy i have s4 with 6.0 M flashed sdk23.. At reboot starts optimitation but ad the end in app i fan t find xposed... Solution?
[Xposed General] grep_i:
Did you also install Xposed installer 3.0 alpha 4 apk after the reboot
[Xposed General] Enter The Nexus:
Does anyone feel like their phone slows down after using Xposed? I installed the framework, moving fine, then installed 5 modules and proceeds to slow down and jitter. I am on a Nexus 6 with the latest AOSiP.
[Xposed General] Ja_som:
Probably is issue with modules, not Xposed, try to disable them, then enable one by one.