yashsingh1/xdaforums huggingface dataset:
[Xposed General] .corrupt.:
I saw your post earlier. My phone is rock-stable, however. Just drains lots of energy now.

Here's what I'm running in detail. Maybe we can find something on your device that causes this:

32.1.A.1.185 Customized DE

AndroPlus Kernel v24

Xposed arm64 v83 sdk23

Xposed Installer v3.0 alpha 4

SuperSU v2.65-20151226

Xposed Modules:

BootManager 3.7.1

BubbleUPNP 2.6.2 (currently deactivated)

Disable Charging LED 1.0.2

GravityBox 6.1.1

Xprivacy 3.6.19

Did a full wipe and clean reinstall for the update.

---------- Post added at 02:42 PM ---------- Previous post was at 02:32 PM ----------

Judging from your log - and I'm not an expert on this - your are running modules incompatible to recent versions of Android. rovo89 posted about that here: http://xdaforums.com/showpost.php?p=58840569&postcount=7

Looking at your log I'd say you have to deactivate XLED and Force Touch Detector at least, and Hide Sim Icon Label just to make sure.
[Xposed General] magnamentis:
very good reply except that i don't agree with your solution ( smiling of course )

i would recommend to revert and stick to v80 as long as we can see that many module devs don't test and update their modules again v81 and above. like this he can keep his functionality and for those who's device setup was perfectly fine with v80 there is not benefit from updating.

the newer versions took care of a few issues on specific setups and only for those folks an update is somehow mandatory or recommended.

as we see, also in the rom and kernel threads, too many people have issues with incompatible modules without even recognizin the reason.

that said if everyone would properly read [MENTION=4419114]rovo89[/MENTION] 's release notes they would know, it was clearly mentioned in v81 release note.
[Xposed General] .corrupt.:
I see your point, thanks for clearing that up. On Sony devices, v83 is a big bonus, though. Many of Sony's core apps like the camera crashed in certain reproducible cases (like trying to record a panorama). Since Soheil_rf is running a Z5, I guess it's up to him whether he'd rather use the camera to full extent or keep all his xposed modules. I have to say that, so far, v83 is the best MM xposed I have used. Except for the battery drain.
[Xposed General] Rombena:
Closed for Marshmallow

Will this work if I have CM13 installed on my S5?I am looking for a CM13 custom Kernel.
[Xposed General] Renegade1504:
Test 2 zip for LG G4

Hello all together,

I found the discussion on Github about the issues and saw that there were some test zip files but Dropbox shows 404 error.

[MENTION=4419114]rovo89[/MENTION]: Can you please refresh the link?

Thank you very much
[Xposed General] magnamentis:
sure, certainly true, which is what i meant with "specific setups" hence we're in full agreement here, thanks for pointing out on of those exceptions, this will certainly help sony users to avoid lot's of unnecessary trouble :good:
[Xposed General] Soheil_rf:
Thanks for replay

I flashed on clean Rom .185

for now i disabled XLED and Force Touch for testing also install original Xposed Installer v3.0 alpha 4 from rovo89 , at befor i used material designed version

Till now works normal
[Xposed General] rovo89:
You mean this one? https://github.com/rovo89/Xposed/issues/100

I have justed added a comment there that the issue is fixed in v83 (except for the weather app).

I always remove test versions once I have released the final version.
[Xposed General] AreOh:
If you update and find issues and want to revert back to a lower version like v80, is it as simple as flashing the zip, wiping cache and rebooting?
[Xposed General] Fif_:
Yes. Please wipe the Dalvik cache. Wiping the regular cache is recommended but not essential, but the Dalvik wipe is.
[Xposed General] Portgas D. Ace:
Yes, Xposed will work on your S5 with CM13 installed.

If you are looking for a custom kernel, you should search for one in the Galaxy S5 section here on XDA as Xposed is not a kernel.
[Xposed General] yoahmad1995:
I have 6.0.1 based ROM installed. Whenever I install xposed, Facebook Messenger calls not work.

What happens is I can hear them but they can't hear me.

Mic works in all other VoIP apps.

Logcat attached bellow.
[Xposed General] Renegade1504:
Hello rovo89,

thanks for the clarification. Flashed v83 on LG G4 H815 V20D and working awesome.

Donation is on its way ;)).

Greetings

15Reno04
[Xposed General] MichDroid:
I want to install the X86 on my ZenFone 2 but I'm not sure about the files available. I'm running CM13 so I went to the 23 X86 folder and there is both a .zip and a .sdc, which do I flash with my TWRP? Thank you in advance!
[Xposed General] tanpro260196:
The zip file...
[Xposed General] MichDroid:
Thank you for the quick reply!
[Xposed General] Augustin79:
I updated my custom ROM today and after that whenever I try to flash Xposed I get a "There's not enough internal storage space" warning after rebooting. It says I don't have enough storage for the system, but I have 2 Gb of free system storage which I think should be sufficient. To me it seems the phone thinks it doesn't have enough storage but it seems like it does in fact have enough... Never had this problem on my Nexus 6P before. I have tried removing xposed and that removes the low system storage warning, but I desperately want to have xposed installed.

Can anyone help with a fix or does anyone have any thoughts as to why this is happening?
[Xposed General] Portgas D. Ace:
system partition =/= internal storage

The /system partition is only a small part of your internal storage, therefore it might be absolutely reasonable that such a warning occurs. Try to delete some system apps (for example Google apps such as Gmail, Youtube, Google app itself), those apps can be installed from the Play Store later on as user apps, so they won't be part of the system partition. Afterwards, try to re-flash Xposed again.

If you flash GApps after flashing your ROM, I would recommend to flash minimal GApps (for example Open GApps Pico) and install all other apps later on from Play Store.
[Xposed General] Augustin79:
I have 2gb of free system storage and coming from a clean install of new ROM there aren't any more system apps to remove afaik. Isn't 2 gb of system storage supposed to be more than enough?
[Xposed General] magnamentis:
the greatest default system partition i'm aware of (i've seen) was 2GB so i simply don't believe you that you have 2GB left.

further you did not read carefully, of course you have system apps that you could remove and re-install from playstore to internal storage instead of system partition.

i never understand why people ask for advice and then argue back and forth. just do as advised and your issue will be gone. easy as that.

and only if that wouldn't work, (it will) come back and ask for more help, too many "buts" and "justs" around IMO

EDIT: has nothing to do with clean or not clean, the opposite is the case, google stock for example is filling system partition to capacity on a number of devices as with marshmallow.

then it came to my mind that i dunno your ROM, probably or perhaps stock but why not mention that stuff so that everyone can see immediately what we're dealing with?

and last but not least, this problem has been mentioned and answered at least several dozen if not hundred times, hence a bit of reading and searching would be nice.
[Xposed General] Augustin79:
Sorry if I have offended you. I'm aware that similar issues have been mentioned but I don't feel my issue is answered. That's why I dared to ask for help in here.

My system folder shows 1.98 GB free space and I can't find any more system apps to remove. Did as mentioned and flashed with pico-Gapps. On a Nexus 6P running BenzoRom and AK63 kernel. You might not believe me but I did indeed search and read before posting here.
[Xposed General] .corrupt.:
What magnamentis is saying is that /system isn't a folder but a partition. You can install an app like DiskInfo and look at the size of that partition. The "internal storage" view that settings shows you is just the amount of flash memory your phone has. That memory is partitioned, however. And you can only flash things into /system until that partition fills up. Hence the recommendation to uninstall system apps and reinstall them in user space.
[Xposed General] drewski_1:
While i agree with much of your post i did want to say huge /system partitions are out there. :silly:

My Moto X 2014 is close to 3GB (screenshot), and my Pixel C /system is 3.61GB :(

Annoying because there's a ton of wasted space and it cuts into the '32GB' advertised capacity (total, including /system)
[Xposed General] Augustin79:
Thanks! If I use DiskInfo is the storage listed under System the one I should pay attention to? Not familiar with this app... (a long with a lot of other things apparantly ;) )
[Xposed General] .corrupt.:
DiskInfo by default only displays a few partitions. "System" is where your ROM is installed, "Data" is where your apps and, as the name says, userdata are stored. If System is close to full, there's not much you can do to install xposed except trying to free up space by uninstalling big system apps.
[Xposed General] Augustin79:
Thanks for your assistance. This app tells me I have 1.98GB free out of 3GB under system. This is why I was wondering if close to 2GB of free space shouldn't be enough for xposed. Guess I'll have to revert back from the latest ROM build if I want to keep using xposed. Again, thanks for your patience!
[Xposed General] teddy0209:
Apps like root uninstaller will make it easier for you to free up space on system partition...
[Xposed General] drewski_1:
select "[root required]" when it launches and then View->/system
[Xposed General] steveo17:
so it appears that there is still the compatibility issue with v83 and supersu 2.71?

TiBu still does not stay open for me
[Xposed General] grep_i:
You're talking about titanium backup ?

On my setup titanium backup is just working with Xposed framework v83 and Supersu 2.71

See screenshot
[Xposed General] steveo17:
yes thats correct. TiBu just closes on its own when i have v83 installed.

you're on a 6P?
[Xposed General] grep_i:
Nope sent from my Nexus 5

And this doesn't happen when you are on a lower version like v82 or lower like v80 ?
[Xposed General] steveo17:
it is fine on v80. started on v81 and higher
[Xposed General] grep_i:
For now I would stick to v80.

You have a Nexus device there is no special reason to update to v83.

Notify developer of titanium backup and maybe they will fix it very soon
[Xposed General] steveo17:
yes. that is what i have been doing. it is not a TiBu problem. its related to xposed
[Xposed General] RandomPooka:
Running nexus 6 and 2.71 with v83 and Titanium Backup is just fine here.
[Xposed General] pakom8:
Does anyone know if there a Xposed Module that allow to add transition animation to MM roms, CM Base?
[Xposed General] magnamentis:
thanks for clarification, yep there are even moore devices with huge system partitions, i just don't have one of them, hence the therm "that i've seen" that was misleading from me, i should have said "that i own" good and important find and correction :good:

---------- Post added at 12:34 AM ---------- Previous post was at 12:25 AM ----------

for all those who don't have to (n-preview and certain devices) i recommend strongly to stay with v80 and SSU 2.68

both have compatibility issues with some apps and some modules.

to be clear, it's the app dev's fault because they did not update to latest standards but that does not help us users if things don't work

so SSU2.68 and Xposed v80 work across the board with very few exceptions

SSU 2.71 was originally developed and is mandatory for N-Preview for Nexus devices. i have that on my nexus 6 which is why i know

all the issues as to permissive mode, TiBu, Secure Settings and many other valuable root apps, but again it's neither the fault of xposed v83

nor the fault of SSU 2.71, the apps have to keep up with standards and those new standards will be enforced i android N, again a notch

stricter than under marshmallow for those who remember the first days with all the patches and stuff :)
[Xposed General] deklica:
I have OnePlus One, with COS 13, SSU 2.71 and I think xposed v83 restart my phone from time to time, because when I uninstalled him, no more random restarts...
[Xposed General] Nergal di Cuthah:
Read the post directly above yours
[Xposed General] elesbb:
Hey zelendel. Sorry to pest you.

But do we have any idea how Snapchat is doing this? Can you give me some names of other apps that detect Xposed?

I first thought they were using Thread.currentThread().getStackTrace() and going through that to detect xposedBridge. But using xposed, I successfully removed the xposed classes from the stack trace, yet I am still denied log in.

My next thought is they are doing it via native code. Once I have more time, I will go through the .so files in IDA and see if that is what they are doing.

But I was just wondering what other people's thoughts/discoveries are.

Thanks.
[Xposed General] zelendel:
To be honest I am not sure. As my rom doesn't support xposed I stopped using it before 6.0 came out.

It could be as simple as them doing a query on the framework as it differs from stock.

I don't recall other apps names but if you search for it I'm sure you will find it. Sorry this is the only xposed thread I read. (every once in a while) and it has been awhile since it was mentioned.
[Xposed General] elesbb:
Thanks boss. I found this. So I may go through the methods mentioned in there to see if Snapchat adopted any of them. They are definitely doing the check either server side or through native code. When grepping through the decompiled smali files, there is not one mention of xposed. So I think they send some kind of string value to their native code, do the check there, then either deny or allow the log in.

Thanks for getting back to me. I just feel like this issue would be something we could remove. Plus the challenge is quite fun lol. Was just wondering if you knew any more about it than I already had an idea of. Thanks again boss!
[Xposed General] deklica:
Yes, thanks... SSU 2.68 and Xposed v80 seams to working good...
[Xposed General] Snah:
I had problems with the screen being all black with previous versions of 83. Now it's working here too! G4 H815 MM 20D as well.

Thanks so much [MENTION=4419114]rovo89[/MENTION].

EDIT: Sadly, Bluetooth does not work on v83 for LG G4. It goes on shortly, then turns off. Reverting to v80 it's working like it should.

[Written by my thumbs on a state-of-the-art Nokia 3110.]
[Xposed General] ky200028:
I flashed this on my Samsung Galaxy S6 Edge (Sprint) (Deodexed), and I heard that reboot can take a while, but its been almost two hours. How long before I should assume its a soft brick?
[Xposed General] grep_i:
I guess right about now.

Try to uninstall the framework and see if everything works fine than.

Also take a look at following thread it's especially for Samsung devices

http://xdaforums.com/showthread.php?t=3180960
[Xposed General] payne_307:
Hello all.. I'm trying to use this module (http://xdaforums.com/showthread.php?t=2040163) on Stock Omni ROM and it doesn't work as its unable to get the needed hooks. However the same module works with other Marshmallow ROMs like SlimSaber, CM13 and COS13 (for OnePlus One). I really wish to use the Omni ROM for its camera and but I need that module to work so that I can run my official email app (from which root needs to be hidden). Other Xposed modules work like GravityBox, Amplify, Greenify, etc. I have attempted using both SuperSU 2.68 and SuperSU 2.71. In fact on SlimSaber (which is based on Omni ROM) runs the module fine and works with SuperSU 2.71. Any suggestions, advice, solution ?
[Xposed General] grep_i:
Try asking the rom developer
[Xposed General] gianboy:
Does anyone have camera problems with the last version of xposed (v83) with v82 i didnt have that issue

Moto X 2014 MM stock

Log

http://pastebin.com/VZtv4KsF
[Xposed General] Oswald Boelcke:
Hi Snah. I also experienced a very annoying "black screen" issue: http://xdaforums.com/showpost.php?p=66639443&postcount=1071

It occured while I still was on Xposed v81 but only together with the AGNi v4.5.3 kernel. Since I migrated to Xposed v83, no black screens anymore.:D

For me, no Bluetooth issues on my SGS3LTE. However, this statement is limited to the usage of a headset, as I don't use any other tools.
[Xposed General] bottswana:
Has anyone heard of an app being listed as 'Incompatible' in google play store when xposed is installed?

When xposed is installed on my phone, I can't install the new Philips Hue gen2 app (com.philips.lighting.hue2). When its removed, it shows up as compatible.
[Xposed General] Flowah123:
I don't know where to bug-report, so I'm writing here.

With latest may patch update + Xposed (I tried with v81 and v83) Google Apps go in crash loop ("Messenger has stopped", "Google Play Services has stopped", "Google App has stopped", etc...).

I first flashed the factory image, then TWRP, then SuperSU and then v83.

I tried again flashing the factory image + TWRP + SuperSU and everything was working. Then, I tried again v83 and I got crashes.

Tried again with flashing factory image + blablabla and no crashes. Flashed Xposed v81 and I got crashes.

So, I'm sure the problem is Xposed.

Device: Nexus 5

P.S.: the problem is only with the Google Apps crashing in loop, but Xposed works anyway.
[Xposed General] magnamentis:
yes there are many, snapchat for one but there are many more, you'd have to go to the app threads or forums or communities to verify on a per app basis and to learn about eventual workarounds
[Xposed General] dreinulldrei:
I don't think that Google Play would do such checks. I assume there is some Xposed module installed which alters the device ID. Check in some benchmark or e.g. AIDA64.
[Xposed General] dreinulldrei:
Just tested... works for me. You must have a mod installed in Xposed that messes with the device ID...
[Xposed General] Nergal di Cuthah:
Up and running

Nexus 6 Vanilla 6.0'1 (April's First)

Hellscore Kernel
[Xposed General] DaveImagery:
Noob question: Can I just flash v84 over 83?
[Xposed General] Nergal di Cuthah:
Yes but I always wipe dalvik after, and have never had any issue (78-through-84)
[Xposed General] DaveImagery:
Okay, thank you.
[Xposed General] Yogesh_Dude:
Guys how to survive from bootloops???thnx in advnce
[Xposed General] Nergal di Cuthah:
What? In general?
[Xposed General] Yogesh_Dude:
No. After installing non working module byMistake...
[Xposed General] Portgas D. Ace:
You can either uninstall Xposed framework by flashing the uninstaller.zip or use the file manager of your recovery to delete the module within /data/data and /data/apps.
[Xposed General] magnamentis:
you can:

a) use the uninstaller zip in recovery

b) delete xposed manually

c) dirty flash the rom and other mods over (this is probably the easiest way for most users)
[Xposed General] monleylord:
Even easier, boot to twrp, file manager, delete the files in /data/data/de.robv.android.xposed.installer/conf. After this boot to system, start xposed installer, go to modules and deactivate the addon who causes the bootloops
[Xposed General] grep_i:
I guess you're quite right for most users this is the simplest set of actions to do, but this is quite much for just one module not working.

If one uses the uninstaller for the framework and reboot one can than remove the not working module from within the Xposed installer apk app.

After that you can choose to reinstall the Xposed framework by flashing it again or do nothing at all
[Xposed General] Vincenzo91x:
Version 81 and above are unusable for me. I think because I use modules builded before the 81's optimization for developers. Not sure but I have to stay on v80. Thanks for your hard work dev :good:
[Xposed General] rovo89:
How about trying to confirm this theory by disabling all modules, flashing v84 and then enabling one module after another? Once you have identified the failing modules, you could check in the module's thread (or even here) if others have the same issue. Then you can report it to the module author. He can hopefully fix it and everyone profits.

I have seen quite a few of such suggestions to stay on older versions, but that's not really helpful. I would expect that people in a developer forum at least try a little bit to help improving the software that they get for free.

I have seen the complaints, but I don't think I have seen clear bug reports saying that module X doesn't work, here's the logcat. I can't exclude that I have removed too much or made more incompatible changes than I thought I did, but I think I found only like five (not so well-known) modules that use APIs that are no longer public. And I think none of those changes should even cause bootloops, at most the module might not work.

So please do as I said, or at least post a logcat of the issue you're facing. Then I can have a look to see if there are general issues - I'm quite busy with analyzing properly reported issues on GitHub though, so I can't check everyone's logs.
[Xposed General] mutahharbashir:
tried V84 on mate7 tl10 with marshmallow stockrom (rooted)

installed but not active

nothing in error log,

anyone can help?
[Xposed General] dreinulldrei:
Which version? 32 or 64bits? Which API?
[Xposed General] Psipherious:
I just attempted to install v84 on a Nexus 5, no modules installed yet only flashed xposed zip onto a completely clean/fresh install fully wiped of the latest Android that was just released yesterday: MOB30H and getting SystemUI crashes on initial bootup (unable to setup the phone).

Tried again: wipe, verified all md5 hashes of rom, etc, same problem. haven't tried any older versions of framework yet.
[Xposed General] nevernat_theoriginal:
Weather 4.70.7

Weather Service 4.70.7

Weather Theme 4.70.7

LG G4 H815 stock v20e on TIM Italy

Xposed 84

Weather works fine

Menu works fine.

Tnx a lot Rovo!
[Xposed General] mutahharbashir:
Solved it by myself, need build.prop edit then works
[Xposed General] grep_i:
I guess you need to be more precise I have v84 working on Nexus 5 with 3 modules enabled no problem at all
[Xposed General] rovo89:
Can you post a logcat please?
[Xposed General] Oswald Boelcke:
Concise, very clear and simply true statement! Excellent.

Running v84 without any problems; however, I only use one module (Xprivacy).
[Xposed General] HorstiG:
V84 Works without any problems. (Stock mod M) Thank you [MENTION=4419114]rovo89[/MENTION]
[Xposed General] LoverBoy2415:
v84 Works Fine In My RR 5.6.7 ..
[Xposed General] Psipherious:
I shall post a logcat soon as I give it another go (bit later today).

All the rest of you that are saying it's working (specifically those on Nexus 5), you are running the very latest security revision build just released by Google a few days ago?

Release: MOB30H
[Xposed General] Rapper_skull:
No problems with v84 on my Nexus 5, with a lot of modules installed

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Xposed General] pranik:
Someone else, as well as [MENTION=4615215]Psipherious[/MENTION], tried v84 with the latest version MOB30H for Nexus 5?
[Xposed General] Rapper_skull:
I'm on MMB29Q
[Xposed General] Psipherious:
I just tried downgrading to v80 and I have no issues (no systemUI crashes) on same MOB30H release (will try 81-83 later today) and then I'll get that logcat for 84.

Edit: Further updates - I have now tested v81, 82 - both working on MOB30H, v83 & 84 both crashing SystemUI.

LogCat incoming shortly.
[Xposed General] Psipherious:
Logcat for v84 bootup/crash of SystemUI attached as text file.

I've cropped out a bit of data with personally identifying infos.

Additional infos:

Nexus 5

MOB30H (May 1st security update)

Running latest radio/baseband & bootloaders that came with this May 1st release:

BB: M8974A-2.0.50.2.29

BL: HHZ20f

If you need anything else or anything missing from logcat that you need, let me know.