yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] Baryn:
Yes, I've done some more research and have found that the error message is not limited to :MSREMNET.

I searched for other parts of the error message, and have found it in many forms, but the problem that we are experiencing is somewhat rare and goes on unexplained.

What do I believe the problem is? An unfixable bug in the kernel. Why do I believe this? Because when I have this problem, an unskinned version of the phone app opens. If I close this with Magic Button (a common task manager app), the problem goes away!

However, it will soon return until I do a soft reset. Before that, most apps don't work, many parts of the OS crash, and my backlight goes to full brightness.

This problem isn't always caused by web access, either. It goes on when I work on documents in Office for extended periods.

Surely, after further research, I deem this problem unfixable, a flaw in the OS itself that spans across devices - if you are working on your device for an extended period, save often or you will likely lose your work.

Your only other option is to wait 12 months for a 2nd generation iPhone, wait 12 months for a mature Android device, or wait 12 months for the completely rebuilt WM currently dubbed 'Photon'. Until the end of next winter, this problem goes on, a fact of life.
[JASJAR, XDA Exec, MDA Pro General] z0d1ak:
well thats the problem i dont like waiting and i m in love with my fone thou its like a lil brik in ur pocket . still i love it and it gots its karizma wen i b using it in public seriously. anyways thats off topic. the point i m to make is me working on 6.1 as of yet haven faced this yet . u can try downloading wm6.1 of mwang or ranjus and try flashing ur device with it and chek if the problem persists . dude if its a kernel problem then y wud it appear with every rom flash where u upgrade the os n the kernel gets a reprint in the memory location depending on the os u use. it myt b a mother board defect or defect in the gprs or wifi connection reception. but as u said it appears with office as well i need to try that out and c for myself . will keep this posted. m glad i found one guy ales with the same screw up problem. man its one irritating thing ! no matter how sweet the rom is but functionality crash sucks
[JASJAR, XDA Exec, MDA Pro General] Baryn:
Definitely not a motherboard issue, unless the Universal, Apache, and other devices with this glitch have the same one. It's a software issue.

I was shocked to see the problem persist between WM5 and WM6, however. Clearly, there must be a common software component between both bugging out. The two OSs are so very similar, however, that the chances of pinpointing this, or wow, bringing a solution, are slim.

Do keep me posted though, I guess.
[JASJAR, XDA Exec, MDA Pro General] kdskamal:
I had this problem when I had universal. You are talking about this right?

http://xdaforums.com/showthread.php?t=315914
[JASJAR, XDA Exec, MDA Pro General] z0d1ak:
no its not. its a bug in the core or driver i guess that wm5 n wm6 shares for temporary data intrepetation over PIE or OFFICE . i think its a cache controll problem and has to do sumthing with random access memory thou m no certain on that point. the error keeps poping wen u r using the internet or as our other mate said it also occurs in using windows compact edition office. the problem u pointed at is the problem of memory issue. its a memory problem but i dont think the same as u do.my fone shows the same memory and other intact details as a normal fone wud. but its more about remnet protocol that freezes all ur application saying that there .exe files are not digitally sighned as i mentioned in the very 1st post.

ps: baryn can u try using other applications where u have temporary storage b4 main storage like in case of PIE n OFFICE b4 main page storage.
[JASJAR, XDA Exec, MDA Pro General] z0d1ak:
hmmm well can v get the remnet file from wm2003 or older editions and try replacing it and c if it works the other way round . in the meantym m gonna dig up sum dirt on kernel similarities n difference in wm editions till date. i must add in recent ones the main difference lies in jus interface as i have observed n sum drivers here n there. wud dig pinpoint detail on that now
[JASJAR, XDA Exec, MDA Pro General] z0d1ak:
problem still persists with windows mobie 6.1

and problem with pocket office also confirmed .
[JASJAR, XDA Exec, MDA Pro General] fredsmithz:
MSREMNET

I have the MSREMNET pop up and then i Have to reset. Does anybody have a workable solution yet? I have even tried resetting everything back to the factory defaults and still get the problem but eventually it comes back.
[JASJAR, XDA Exec, MDA Pro General] Baryn:
Yes, it has been discovered to be an indescript hardware issue. There is no software- or firmware-based solution, which sucks, but phones released in the past couple of years don't seem to suffer from it at all.
[JASJAR, XDA Exec, MDA Pro General] TFGBD:
This issue isn't directly related to REMNET, Office, IE or any other built in MS app. The errors with MS applications occur because the .lnk shortcuts and APIs that call most of these programs reference the Raiper Shell paths in the registry (HKLM\Software\Microsoft\Shell\Rai) instead of calling the exe directly. I'm pretty sure this issue happens because the user registry and possibly even the disk it resides on is suddenly getting unloaded and dismounted. The screen brightens because it is loading the system defaults from the registry hives in ROM. This is the same reason the skin on WM 6.5 suddenly disappears. At times I get a password prompt when I never set a password. Again, because too many required registry settings disappeared. After it happens, you can sometimes fix it by powering on/off the device but it usually doesn't last long and you eventually need to soft reset.

I have no idea what causes it but it always seems to happen after using the device for a few hours. It also doesn't seem to matter what ROM is used. It may just be me, but I also noticed that the device feels really hot after it's happened and if you leave it charging for awhile. For me, it happens quite often while using Remote Desktop for extended periods of time. I wish I knew what exactly was causing these hive dismounts. It may indeed be a hardware issue. Failing flash disk? Wear from overclocking? Does it even happen on factory ROMs? Also, is there anyone who has an original 64MB device that has the same problem? I wonder if cooking a rom with the registry hives and system databases stored on an SD card or in the extended ROM would fix the issue for people with these problematic devices.
[ZTE Axon 7 Guides, News, & Discussion] Znuf:
Still no work for me. I can install it but when i reboot Magisk disapear. And i don't know why but magisk worked good before i do a factroy reset.
[ZTE Axon 7 Guides, News, & Discussion] Erahgon:
Alright, still working on streamlining my methods, and I've managed to get root, Magisk, and system-less Xposed playing nice together.

The next step was to try to not trip SafetyNet with this setup, and I've made some progress on that front. It involves installing the patched Kali kernel (as I've done so far) and suHIDE from Chainfire (next test, tomorrow).

I'll update the OP tomorrow, with screenshots!
[ZTE Axon 7 Guides, News, & Discussion] Znuf:
Good for you!

Everything I try to install it didn't survive to reboot ðŸ™.

I make a fresh install and same. I don't know why. Last time I tried it worked.

I tried everything ðŸ˜¢
[ZTE Axon 7 Guides, News, & Discussion] Erahgon:
I've just updated the guide. Do you want to give it a shot and see whether it works for you?
[ZTE Axon 7 Guides, News, & Discussion] Znuf:
It's exactly what I do many time, at least 10.

But it's never activated after boot. :sad:

If I found a way I'll post here
[ZTE Axon 7 Guides, News, & Discussion] Znuf:
I found a way.

On unlocked phone.

Install supersu 2.65 from here https://download.chainfire.eu/921/SuperSU

Reboot system.

Update supersu via play store

Download magisk and magisk manager from here. http://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Install magisk manager.

Install magisk v9.

Reboot when it prompt but Boot directly in twrp.

Flash magisk v9.

Reboot system.

This worked for me.
[ZTE Axon 7 Guides, News, & Discussion] Oki:
I have a couple of doubts about your procedure before testing it twice:

1. Are you sure you have to install SU v1.65? Why not SU v2.65?

2. you are referring to the magisk framwork, but I do not find it. Were you referring to Xposed framework maybe?

It would be easier if could provide some links to the download pages, just to match versions.

Thanks
[ZTE Axon 7 Guides, News, & Discussion] Znuf:
I update my post. Sorry for the poor precision. It was late. ?
[ZTE Axon 7 Guides, News, & Discussion] Oki:
Thanks for the clarification, I understand that when you say install Magisk v9, you rever to install within the Magisk manager app, and then later, booting directly to TWRP flashing the Magisk v9 zip file.

I have been experimenting with Safetynet helper and I have found that it doesn't pass when the phone is unlocked. As soon as I unlock the bootloader, the safetynet helper reports a CTS profile doesn't match. Even when using the stock boot and stock system without any root!!!!

Any thought on this???

blue skies :cool:
[ZTE Axon 7 Guides, News, & Discussion] JKSurf:
So Android Pay is working with this method?
[ZTE Axon 7 Guides, News, & Discussion] Oki:
Not for me.

I am still experimenting, there must be a way.

---------- Post added at 17:30 ---------- Previous post was at 17:23 ----------

I have done exactly that with the B29 ROM with stock boot and system. For some reason Magisk manager keep asking for Magisk v9 even after the whole process has been completed. I have root thanks to SuperSU, but safetynet helper test doesn't pass.
[ZTE Axon 7 Guides, News, & Discussion] -Duir-:
A better question is if you can pass the SafetyNet check apps.

I posted this in the thread that started this one, but with the

official

TWRP you can flash recent versions of SuperSU, not just 2.65 anymore (that was a limitation of the unofficial).

I know this thread relates to getting Magisk working, but unless there's a specific module you're looking to use, I don't see a benefit to using it for systemless root over SuperSU. I had tried to install it before using unofficial TWRP and had problems, but I think those, like the inability to install SuperSU past 2.65 we're due to faults with the unofficial TWRP. Official TWRP should install Magisk just fine (haven't cared to try it).

That said, if Android Pay is you're concern SuperSU might be the way to go. I am running SuperSU 2.79, Xposed 86.2, suhide 0.55, and Root Switch 1.3.3.2 and am able to pass both of the popular SN test apps (SafetyNet Helper and SafetyNet Playground). I don't use AP to know if that functions, but Pokémon GO, which also relies on SafetyNet runs just fine.

Also, as far as kernel goes, if you want one that doesn't have all the extra stuff the Kali NetHunter kernel does, there's a stock kernel patched for SafetyNet, kcal, and exFAT in this post of the same thread.

If you don't care about Xposed, SuperSU and Root Switch should be all you need to pass.

And as I mentioned in the other thread, this will likely all be rendered useless by the Nougat update hopefully coming next month.
[ZTE Axon 7 Guides, News, & Discussion] Erahgon:
The method I posted as an update in the OP the other day closely follows [MENTION=1023347]Znuf[/MENTION]'s method, and all the relevant files are linked in the OP. Still a bit busy to experiment more, but this is how far I had gotten with the method I had posted, and, in theory, should work with suHIDE. Even the Kali Kernel I have linked to is the patched one without the extra tools.

With suHIDE my config should be similar to [MENTION=4492889]-Duir-[/MENTION]'s configuration, except that I've installed Xposed through Magisk (Xposed v87) instead.

I'll try this out and update it soon. Screenshots attached is my progress on the last update..
[ZTE Axon 7 Guides, News, & Discussion] H0lmEd:
Has anyone tried to replicate this using a2017g? From what I can tell it should all work but I'm worried about flashing the bootloop fixer script that is designed for a2017u
[ZTE Axon 7 Guides, News, & Discussion] Erahgon:
The bootloop fixer script should work on all devices as it just disables forced encryption in your bootloader. Make backups and try it out. If you experience a problem just restore the backed-up boot partition.
[ZTE Axon 7 Guides, News, & Discussion] Znuf:
I'm on 2017g no bootloop.
[ZTE Axon 7 Guides, News, & Discussion] -Duir-:
suhide will only work with Xposed 86.2 (which is provided in the same post).
[ZTE Axon 7 Guides, News, & Discussion] Oki:
Do those configurations support SafetyNet while Xposed modules are loaded? I don't want to softboot the phone when I am in a store and I have to pay.

Thanks
[ZTE Axon 7 Guides, News, & Discussion] -Duir-:
Yep, Xposed modules still work, all you're toggling is root and no reboot required to disable/enable root. It's worth clarifying that while modules will still work, root apps obviously won't while disabled. Also, while root is disabled, Xposed installer will say Xposed isn't installed - as long as Xposed installer is green when root is enabled you're good.
[Xposed Framework Modules] MrWasdennnoch:
Scoop: Catches a stack trace when an app crashes unexpectedly

This module - as the description says - saves the stack trace of a crashing app and displays all crashes in a list so you don't have to look through a long logcat anymore. Additionally you get a notification on every crash (configurable) which already displays the most important information.

This module is based off the module Cracker which sadly isn't being developed anymore so I made an updated version which catches crashes more reliably (supports custom crash handlers set by apps), features material design and contains more functionality such as:

Search in crashed apps

Search in stack trace

Crash preview in notification

Combination of same crashes / apps to avoid long repetetive lists

Crash blacklist

Quick actions to copy / share a stack trace

Download: http://repo.xposed.info/module/tk.wasdennnoch.scoop

Source: https://github.com/wasdennnoch/Scoop

You can help translate this module on GitHub!

Changelog:

XDA:DevDB Information

Scoop, Xposed for all devices (see above for details)

Contributors

MrWasdennnoch

Source Code: https://github.com/wasdennnoch/Scoop

Xposed Package Name: tk.wasdennnoch.scoop

Version Information

Status: Stable

Current Stable Version: 1.6.4

Stable Release Date: 2017-04-01

Created 2016-12-23

Last Updated 2017-04-01
[Xposed Framework Modules] mauam:
Amazing, thanks for this Christmas gift:cool:
[Xposed Framework Modules] KaMyKaSii:
Could you add line break and search in log? Thank you!
[Xposed Framework Modules] MrWasdennnoch:
Done and available in v1.3.0 :)

(Disabled by default)
[Xposed Framework Modules] KaMyKaSii:
Thank you. I upgraded from version 1.1.0 to 1.3.0 and now it says I do not have Xposed installed. I've restarted, cleaned up data, reinstalled, same thing. Before clearing the data, by clicking on the crash log of another app, Scoop also crash. Attached are the logs logs
[Xposed Framework Modules] MarioUnoDueTre:
Word wrap is very appreciated!

Version 1.2 and 1.3 does't work on n910f (note 4) running marshmallow 6.0.1

Definitely a good upgrade from the good Cracker.

I have an old S3 on 4.1.2 (that i use for debugging) with xposed version 54, could this beatiful tool work on xposed version lower than 81 like Cracker?
[Xposed Framework Modules] MrWasdennnoch:
I fixed the warning (yet have to push it), but I need a logcat to resolve the crash. Your one unfortunately didn't contain any crash info. Make sure to capture it during the crash (because the module doesn't always catch itself :p ).
[Xposed Framework Modules] KaMyKaSii:
I took it with the Logcat Extreme app, I hope to be enough. I configured it as verbose, fresh log, main, brief. Let me know if you have any better. You said that Scoop does not log its own crash logs, but actually once here it happened, before clearing Scoop data
[Xposed Framework Modules] MrWasdennnoch:
I said "not always" :p

I fixed it in v1.3.1. The fault was a misconfigured Proguard which removed more than it should have. I enabled Proguard for debug builds to avoid such issues in the future.
[Xposed Framework Modules] KaMyKaSii:
No more crashes, but the notification that Xposed is not installed persists. I updated the module, cleaned data and rebooted

Edit: Looking at this screenshot I recommend future features like search in the main screen, grouping of same app logs and individual exclusion
[Xposed Framework Modules] MrWasdennnoch:
Now it should be fixed. Problem is I can't test it because I updated to N and thus don't have Xposed anymore, so I had to try different ways. And of course it was Proguard again.

I'll add the search soon, I thought of only searching for different apps though and not searchin the short description. Not sure how I should approach the grouping but it's possible too. With exclusion you basically mean blacklisting?
[Xposed Framework Modules] Fabian Rï¿½ling:
Xposed bridge version

Xposed installer tells me that I need Xposed bridge version 81. There are no updates for the XPosed bridge for me and the current version is 54, so I think that's a bug.
[Xposed Framework Modules] MrWasdennnoch:
The newest available version is 87, but I just remembered: 81 isn't available below LP, right? I'll fix that in the next release.

EDIT: Compatibility down to 52 added in v1.4.0
[Xposed Framework Modules] MarioUnoDueTre:
Compatibility down to 52 is very good, thanks.

The problem is in the image below :(

View attachment 3980424

Only version 1.1 works for me (n910f note 4 running marshmallow 6.0.1)
[Xposed Framework Modules] KaMyKaSii:
The bug of not having Xposed installed continues, but the app continues to intercept the crashes normally
[Xposed Framework Modules] MrWasdennnoch:
That's really weird, it hould be working. I completely disabled the warning and will have a look again when Xposed for N is available.
[Xposed Framework Modules] KaMyKaSii:
I reported with version 1.3.2, although you talk about version 1.4.0, it was not available when I opened the Xposed Installer. I will update now

Edit: The new version is not working, no crash is being logged
[Xposed Framework Modules] MrWasdennnoch:
1.4.2 should fix it... Really bad that I can't test it myself, it could've avoided many issues. But hey, at least I now know how to configure ProGuard properly. At least I hope so.
[Xposed Framework Modules] KaMyKaSii:
Thanks, now it's working. Can you explain to me how the grouping that you implemented works? When I suggested, I wanted to say that after clicking on the crash group of the app, a list of all the crashs with information like date and time appears, and that they expand in the full log when they are clicked. And about the deletion, I'm talking about a button to clear any individual log after a long click on it. At this time it is only possible to clear all logs at once
[Xposed Framework Modules] MarioUnoDueTre:
Yes!

1.4.2 is working; good job, thanks a lot.
[Xposed Framework Modules] MrWasdennnoch:
The grouping that's currently enabled only groups the entries when they have an identical stack trace so that you don't see the item with the same log over and over again, it's not grouped by apps right now, but I can add that too. I'll add the option to delete individual crashes as well.
[Xposed Framework Modules] daoudedy:
Gj mate, you're doing great.
[Xposed Framework Modules] XlAfbk:
I get a lot of stack traces from Google Play Music app at random intervals. These aren't really crashs or anything. Is it possible to ignore these / add a configurable ignore-filter?

java.lang.IllegalStateException: could not connect to GoogleApiClient: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
at com.google.android.wearable.datatransfer.internal.DefaultPeerProvider.blockingConnect(DefaultPeerProvider.java:73)
at com.google.android.wearable.datatransfer.internal.DefaultPeerProvider.getConnectedPeers(DefaultPeerProvider.java:30)
at com.google.android.wearable.datatransfer.internal.DataSyncServiceHelper.processIntent(DataSyncServiceHelper.java:380)
at com.google.android.wearable.datatransfer.internal.DataSyncServiceHelper.access$000(DataSyncServiceHelper.java:49)
at com.google.android.wearable.datatransfer.internal.DataSyncServiceHelper$IntentProcessor.run(DataSyncServiceHelper.java:727)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
[Xposed Framework Modules] ~El Julio~:
Despite having the "Show stack trace in notification" option disabled, each notification I get is already expanded and showing it anyway.

(YotaPhone 2 running 5.0)
[Xposed Framework Modules] MrWasdennnoch:
I just added an option to blacklist apps, there you can blacklist GPM.

I can't reproduce this. Are you sure what you are seeing isn't just the description but the "real" stack trace?
[Xposed Framework Modules] ~El Julio~:
Good question I wouldn't give a bad answer to.

All I can tell is that when opening it, I only see the same thing obviously longer (but not entirely though : there always seem to have more trace collected than displayed since it shows a non-clickable "...10 more" at the end).

And speaking of the description per se, I may not have yet seen one displayed anyway : It displays the same first information in the notification that good old cracker used to display too.

How should it look like ?
[Xposed Framework Modules] MrWasdennnoch:
Looks fine to me.

The description of a typical crash starts with the type of crash (like "java.lang.NullPointerException") followed by an optional message (like "Attempted to invoke virtual method blablabla on a null object reference"). If you disable the stack trace preview that's what gets shown in the notification (same in Cracker). The same text is shown in the overview.

When you click on the notification (or a crash in the overview) you get to the detail view which displays the whole stack trace which includes the description at the beginning followed by the actual stack (like "at package.Class#method(Class.java:38)"). If you enable the stack trace preview you also see those "at..." in the notification.

I'll see if I can get it to display the whole stack trace without the "...12 more"
[Xposed Framework Modules] ~El Julio~:
Well, then I guess disabling the stack trace preview doesn't act as expected because I get some of those first "at.." lines in the notifications.

I had first installed your previous build and enabled the option to see the difference with cracker. After seeing it, I didn't want to use the option so I disabled it. Rebooted once after that, still having the stack trace in notifications. Same after last update.

Description is always shown as expected though.

Great !
[Xposed Framework Modules] MrWasdennnoch:
I'll do some tests but afaik it works fine on my phone and in my emulators.

Edit: Does the module respect other settings such as completely disabling notifications? (you don't actually have to reboot for any setting)

Edit 2: I can't change and won't change the "... x more" because it indicates that the hidden part of the stack trace is the same as the previously shown trace. From the docs:

Also see here.