Related
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk
I have rarely had any bootloop on my previous devices, so I'm not sure if this even counts as bootloop:
An hour ago I found my Pixel 2 (stock 8.1, Magisk 14.5 unmodified, TWRP 3.1.1) restarted itself (with the internal error message it's hard to miss). So I hit OK and enter the pattern to unlock. Upon unlock it reboots and arrives at lock screen again. Another unlock would trigger another reboot, over and over.
Luckily, I had Magisk uninstaller stored on SD card so I went in recovery to flash that, which seems to have restored the backed up boot image, and the phone is properly functional again. Then I flashed Magisk and it's all fine now.
I'm not attributing this issue to Magisk but just wonder if anyone else has seen this issue before. With lock screen being properly loaded, I'm not sure if this even counts as a bootloop.
Another factor to consider is, about two hours before all this happened, I installed AdAway to modify the host file. Don't know if that could be the reason, but now I've modified the host file again, will see if this issue comes back.
I just started having the same problem about the same time. I did a complete shutdown from the lock screen and when it fully booted, it was fine overnight, but it started acting up again this morning, so I did a complete shutdown again. It hung on the shutdown screen, so I had to do the hard reboot. Doing fine again, for now. I also have Magisk and AdAway, but I'd had both of those active for a few days before this started up.
I has something similar but different happen. After updating to 8.1 with magisk, I updated my hosts with adaway. I then had it hang on shutdown (this was the first time this had happened). Hard reset and rebooted and everything seemed to be fine. I then put it on the charger overnight, only to wake up the next morning and find it in the recovery menu saying there was an error booting the system and recommending a factory reset. I ignored that and rebooted, and haven't had any other issues since, but that one was weird.
It's something to do with magisk 14.5 456 beta. I've had the same boot loops, reverted to stock boot.img and problems went away
I haven't has this issue since I posted. To be clear, the problem I had could not be solved by a hard reset - it actually reboots itself every time I try to get past the lock screen for the first time after the previous (self) reboot. It's exactly a bootloop except that the phone makes it into the OS instead of failing to boot.
It can be Magisk or Adaway, no worries. I just pray it's not a hardware issue.
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
I'm still using Magisk 14.3 on 8.1, "Flash" kernel, no issues.
I've not had this issue since I posted about it. I uninstalled one live wallpaper app, which I'm not sure did the trick or not.
froader said:
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
Click to expand...
Click to collapse
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
cswithxda said:
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
Click to expand...
Click to collapse
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
froader said:
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
Click to expand...
Click to collapse
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
cswithxda said:
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
Click to expand...
Click to collapse
Thanks for confirming. I wasn't sure if that was present flashing via TWRP, but makes sense that it would.
Same exact "Internal error" warning and occasional boot loop after upgrading the Pixel 2 (not XL) to 8.1 from Magisk 14.5.1456 using TWRP 3.2.1.0. Also an AdAway user. Glad to hear I didn't mess it up and it's just a quirk of the method and the alpha/beta stages. Hopefully this resolves soon as I hate guessing whether my device will go belly up at random. Seems like Flash kernel with Magisk 14.3 may be ideal - any other confirmations that this is a stable method?
I'm having this same issue as well! Using Magisk 14.5 1456, with the latest TWRP non-beta, and the Unified Hosts Adblock module. Randomly my phone goes into a soft reboot loop like your describing. If I hard reboot using power + volume up it seems to fix it for a time, then it happens again at a, seemingly, random time. It's crazily frustrating. The only other things I have that involve root are a terminal app, Drives roid, and CoSy to sync Facebook contacts. I also had Substratum using the root method, but I uninstalled that today wondering if that was the cause.
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
cswithxda said:
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
Click to expand...
Click to collapse
Were you able to recover from the bootloop at all without uninstalling? For me I was able to force restart it, it would be fine for a few hours then it would bootloop again.
Additionally, I uninstalled Magisk and flashed the stock boot image as well and so far it hasn't come back. I still have TWRP.
Not at all, hard reset still sees the same reboots over and over, so I had to try something. And the only thing I found was the Magisk uninstaller on the SD card lol. I then uninstalled the Magisk and reinstalled it, and the issue has not come back so far.
I'm having that boot loop. I'll try uninstalling magisk
Sent from my [device_name] using XDA-Developers Legacy app
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Interesting about removing AdAway. I had a hosts adblocker as well, I wonder if that has something to do with it.
Not sure how I got here.
Yesterday, went to pay at a Grocery Story with Google Pay, got a message that said "You can no longer pay in stores with Google Pay." Magisk seemed okay, seemed like I was passing SafetyNet (tried two different apps, including Magisk's built-in checker). No big deal, paid the old-fashioned way.
Today, I decided since Magisk or Google Pay was going to be that way, I might as well update EMUI—I've put it off for a good six months or so, because everything was working fine. Now that it wasn't, why not do the whole shebang?
Update went smoothly. Now on B376 (I think).
Updated Magisk. Patched boot.img, all that.
Now, however, I'm getting this screen, and I think somewhere I must have flashed the wrong Magisk. I'm still rooted (Adaway works), but MagiskManager won't get past this screen.
Any ideas on how to do this properly so Magisk and MagiskManager are on the same page?
Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]
Haluter said:
Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]
Click to expand...
Click to collapse
Thanks for this.
Just downloaded Magisk 18.1.zip from Github. It's currently on my computer.
My question is... how do I install it at this point? I don't have TWRP on my Mate 9, since it's so finicky to use. Yesterday, after I updated EMUI, I installed Magisk Manager, and had it sort of install/do its thing. I assume it downloaded its own Magisk, though which version, I have no idea. I used the custom channel found here.
However, now that I'm retracing my steps, I just noticed the verbiage in @Wirmpolter's guide, that says
Latest Magisk Manager and magisk work now so no longer need to setup and flash the specific version found in the original post from topjhnwu.
Click to expand...
Click to collapse
So... no need to use the custom channel URL from Magisk Manager. Got it.
Any advice on how to proceed? Currently... I have Magisk and Magisk Manager installed. Magisk Manager is 7.0, but Magisk itself, I suspect, is not 18+.
If I had to lay it out, I might try:
Uninstall Magisk (uninstall.zip, or whatever it's called)
Reinstall Magisk Manager 7.0
Use @Wirmpolter's instructions, pulling, patching, and re-pushing boot image (again!) in fastboot.
Is there an easier way to do this? Just curious.
EDIT: Another quick question to the big bad XDA world out there: do I flash the Magisk uninstall zip in fastboot, as well?
So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?
daina said:
So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?
Click to expand...
Click to collapse
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).
ante0 said:
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).
Click to expand...
Click to collapse
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...
daina said:
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/showpost.php?p=79029481&postcount=9
Its a temporary fix as well... But beats calling the bank I guess
Hi Daina,
after a short-lived success I ended with the same problems the next day. Afterwards I tried all suggestions from various forums but nothing worked.
After a short period of frustration I decided for a radical solution and installed a new OS on my HTC U11. (Lineage unofficial)
And... surprise! GPay works without any flaws.
Hi Folks,
I've been away for a long time on XDA but I'm back trying to root my S8+ and ofcourse with success.
I made what I believe is my own version wich works for me on to one little detail...Youtube Vanced.
Installed some APK packages, nothing worked with MicroAMG for logging on. After two days (and I don't really know what I did)
I just saw after the 100th boot my Youtube was gone and instead it was Vanced. So no two applications but just the one. It worked for
like three days and know Youtube is back. Like it has overwritten Vanced.
Google Play is not on automatic updates.
Is there a solution, a tool, a workaroud that I can do to make this permanent?
Thanks in advance,
Fabian1985
Really nobody has a solution?
Fabian1985 said:
Really nobody has a solution?
Click to expand...
Click to collapse
Try to use the YouTube Vanced Magisk module. Uninstall the vanced apk u installed before flashing the Magisk module.
Thanks for the reply.
I already tried that but it does not install. It does something...maby need trying to flash it with tgwp?
Turn off auto update on your Play Store, don't update the YouTube app. Detach YouTube from market using Titanium Backup.
If it still doesn't work, install the standalone no root version of the app via XDA Labs and install MicroG.
Yeah I didn't know you could detach it thru Titanium Backup.
Now I've got the non rooted version but no MicroG is working. When signing in it keeps trying but with no success. Gonna trie to detach it thanks!!!
Thanks bro it did the trick!!
Hi guys, so I didnt know that you had to unhide magisk in order to update, this morning I got the notification to update it, clicked on it, and boom, doesnt open anymore, opens for a split second and crashes.
uninstalled the shortcut, installed the apk again, but still same, won't open. Root and everything works as usualy, but It won't open the app.
I run stock OS with just magisk for rooting and some modules.
is there a way to uninstall it completely? I imagine being hidden its still installed under another package name, I tried searching for it but can't find anything....
I hope there is a solution that doesnt require wiping and starting over......
Thanks!!
FIXED, I had version 25206 installed, and when updating to 25207, it wouldnt open, found another apk of 25206, reinstalled, it works now!
For some reason, can't seem to update it, I unhide magisk, update the app, its back to not opening, something is wrong here and I cant figure out what exactly.
I've never unhidden Magisk before updating fwiw...
krakout said:
I've never unhidden Magisk before updating fwiw...
Click to expand...
Click to collapse
me neither, but I read somewhere you had to unhide it before updating just in case, thing is now it wont update, doesnt matter if its hidden or unhidden, after installing, it just crashes on opening.
EDIT: seems like its a common issue with canary builds. will wait for a fix.
iTudorS said:
me neither, but I read somewhere you had to unhide it before updating just in case, thing is now it wont update, doesnt matter if its hidden or unhidden, after installing, it just crashes on opening.
EDIT: seems like its a common issue with canary builds. will wait for a fix.
Click to expand...
Click to collapse
The exact reason I use stable. I had the same issue in the past
iTudorS said:
Hi guys, so I didnt know that you had to unhide magisk in order to update, this morning I got the notification to update it, clicked on it, and boom, doesnt open anymore, opens for a split second and crashes.
uninstalled the shortcut, installed the apk again, but still same, won't open. Root and everything works as usualy, but It won't open the app.
I run stock OS with just magisk for rooting and some modules.
is there a way to uninstall it completely? I imagine being hidden its still installed under another package name, I tried searching for it but can't find anything....
I hope there is a solution that doesnt require wiping and starting over......
Thanks!!
Click to expand...
Click to collapse
Canary Magisk 25207 had a bug in it which prevented the app from opening. It has been fixed so hopefully a new build will be released soon.
Fix release build by yujincheng08 · Pull Request #6638 · topjohnwu/Magisk
Fix #6637
github.com
Lughnasadh said:
Canary Magisk 25207 had a bug in it which prevented the app from opening. It has been fixed so hopefully a new build will be released soon.
Fix release build by yujincheng08 · Pull Request #6638 · topjohnwu/Magisk
Fix #6637
github.com
Click to expand...
Click to collapse
yep, updated this morning to the new build, all is OK!
iTudorS said:
yep, updated this morning to the new build, all is OK!
Click to expand...
Click to collapse
canary? and how do you update it? unhide first then update or just update while hidden?
amders said:
canary? and how do you update it? unhide first then update or just update while hidden?
Click to expand...
Click to collapse
yes, canary, this time I didnt do anything, left it hidden and updated, everything worked out just fine.
iTudorS said:
yes, canary, this time I didnt do anything, left it hidden and updated, everything worked out just fine.
Click to expand...
Click to collapse
ah.. ok... just got the magisk update notification.. btw do you use google wallet? if yes can it use? i'm stuck on adding card step..
amders said:
ah.. ok... just got the magisk update notification.. btw do you use google wallet? if yes can it use? i'm stuck on adding card step..
Click to expand...
Click to collapse
yes, wallet working perfectly with safetynet-fix by displax. no issues whatsoever