Problems with xposed lately - Redmi Note 2 Q&A, Help & Troubleshooting

Hi,
I have some issues with xposed lately. I cannot open the modules in the download section and i neither receive updates for my modules since one week.
When i start the module i receive a error message saying that the download of a dll file (see screenshot) failed. What might be the problem? Xposed worked fine all the time
I use 7.5.1 stable rom from xiaomi.eu.
The xposed i used till today was the version 85 arm64 by solarwarez. After that error i updated to v86 but the result is the same

"The repository (repo.xposed.info) is currently down because my provider is temporarily moving it to a different server. They said the load is too high, but unfortunately failed to provide any details so far. It's also been six hours since they have started the move, no idea why it's taking that long and when it will be finished.
Unfortunately, there's nothing I can do at the moment, so please be patient."
http://forum.xda-developers.com/showthread.php?t=3034811&page=4

Ok no problem. Today everything works normally

Related

[Q] Help, getting a 923 error.

Ever since I came back from the android m preview I have been having difficulty with Google apps. I have gotten error 923.
Timeline:
Flash M preview, have fun
Go back to 5.1.1
- this where I first got the 923 error and nothing would update it the Google play store. Also had WiFi connection issues.
Went all the way to 5.0.1 didn't see any issues
Tried uploading DU and its minimal gapps package.
- got a lot of Google apps error not working or something
- I think this is also where I got an error on initial setup saying "there's an internal problem with your device. Contact your manufacturer for details.
Back to 5.1.1 same issue error 923
Try the steps listed in this post:
http://forum.xda-developers.com/showthread.php?p=61433504
You only need to go up to step 5. The steps after that are just for installing DU.
(Oh, and you can ignore that warning message you get on boot. It's not important)
Sent from my Nexus 9

Moto E 1st Generation (4.4.4) gives random system app stopped notifications

i installed marshmellow in moto e first generation.. however after some days it started giving random notifications of various system apps have been stopped (sometimes google play... sometimes google plus... sometimes some services etc) ... further.. i downgraded again to 4.4.4..... It worked well for couple of months and started again same problem. i reflashed again with 4.4.4. and now almost everyday I have to reflash the 4.4.4 ROM as it gives me random app has been stopped error.
To flash 4.4.4. I follow this post
https://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
I have already tried with Cynogen Mod 13 (in this ROM my IMEI nomber becomes blank for both sim)
I have already tried with Linage 14 (nougat) but this also works for few days and gives same app/service stopped error
I do not install any app outside playstore. Also I do not have much apps installed in my phone. Only Whatsapp and 2-3 other apps are installed. Also I do not play any games in mobile.
Pls help.

Confuzzled by results of fulmics install LG G3 US990

I started this before but I don't think I finished it nor hit submit.
I have an lg-g3 us990 that came stock with lollipop that I flashed with fulmics 7.6 following the pdf linked in the fulmics thread here. It's running, but with a 90 second delay on boot where it's first frozen on "secure boot error 1003" before it runs the animated lg start up screen
Im not development savvy in Android, I usually find idiot friendly walk through guides to follow. I needed to be able to stream seminars to YouTube on mobile and thought I'd install 6.0 to enable that (before I heard about the 1k subscribers requirement)
I had difficulty finding an effective root solution but finally found the thread here for lollipop that linked the download for the "newest root version 03" that worked with a "root.bat" file that was packaged in with everything. Then I tried installing twrp via the official app, doing the latest version and ended up with the "secure boot error 1003" looping every 7 seconds if I tried to boot into recovery, and I'd have to remove batter to get out of the loop, but could boot normally into stock with no problems. I found the bump'd twrp 2.8 for my phone and loaded via flashify and that seemed to work but with one catch, when booting into recovery it would display the "secure boot error 1003" for 7 seconds then go into recovery. Since the guide said use latest version but was written using version 3.0.2 I downloaded that one for my phone from twrp and loaded via flashify and it worked the same as the bumo'd twrp
so I backed up all my personal files then the system via twrp & xferred to flash drive and laptop for redundancy and installed fulmics 7.6 according to the instructions. On reboot it showed the "secure boot error 1003" frozen (no looping) for more than a minute with no flashing led or anything. So I pulled the battery and retried several times while researching possible causes and looking for solutions. I tried one last time, leaving it frozen as I started to ask on here and suddenly heard it chiming and looked over and saw the screen that it was starting apps. I finished the post installation steps and tested thoroughly and it worked but with the caveat of each boot freezes for about 90 seconds on "secure boot error 1003", and I still have not found a decent solution that seems to fit my model.
Should I be worried? Does anyone have any suggestions or ideas? The only other problem I have is that I found out that I need 1000 subscribers to my YouTube channel in addition to the marshmallow or above to use the mobile streaming feature and unless someone has a way to get 1k subscribers in 2 days, then that's just an "oh well" moment.
Any solid suggestions on this "secure boot error 1003" frozen for 90 seconds before boot is greatly appreciated

Methods to find out crash reasons

Hello,
on my Ray Adrian's 'lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-urushi.zip' ROM runs not that stable.
In a time frame of about 5 to 8 hours there always is a sudden crash even when you don't touch the phone. It restarts after the crash automatically.
My question:
How can I find the log files and what else can I do to find out the reason for this crash?
Or did you make the same experiences with this version cm14 so that I have to accept it to be 'normal'?
I have GAPPS installed as well.
I presently assume that it should be caused by any background service of my ~35 downloaded apps...
Thank you for your help.

AOKP Osprey 2019-04-18 / 2019-04-11 - Moto G 2015

Hi all!
I have already commented on a opened thread about this problem but, as it was a similar, not exactly the same problem, I decided to make a new one, and delete the comment. I tried to install AOKP osprey nougat on my Moto G 2015. It installed with no problem at all, I installed it with Magisk and OpenGapps micro. But, as soon as the phone turned on and I started to go through google registration stuff, I started get a "advanced settings has stopped" with a close button. It was happening forever. I could fast click close and do one click on the phone but the error message was popping up every second. It was unusable, forcing me to not use aokp custom rom. I'm waiting for a new release. U guys do an awesome job and I would love to be able to use it on my phone...
Ty.
:crying:
Hello again guys! A new aokp Osprey version has been released in 05/23. I tried it in my Moto G 2015 that was running LineageOs with no problems. Just like the older ones it installed fine with gapps. But the further problems that I had with the older versions happened again. In the first boot, after installation, the popup error, that I talked about in the previous post appeared, but, this time I managed to get rid of it by just closing it some times (approx. 20x), so then I could login to my google account. In this first boot the phone was working fine, I installed some apps, changed some configs, and it seemed to be working ok. I decided to reboot my phone for testing purposes and here is where stuff broke again. The same error popup that I talked about, but now even with me closing it for at least a hundred times the popup was showing everytime. So, saddly, I just had to return to LineageOS.
That's it, bugs are still happening... But keep up with ur good work and, hopefully we will have some amazing Osprey ROM in te future.
Same bugs...
New ROM (aokp_osprey_nougat_nightly_2019-06-06_ota.zip), same bugs...
I'm giving up on AOKP for now...

Categories

Resources