Forgive me if this has been resolved in the past, I have looked high and low for a solution, and no amount of Google-fu has found a solution.
Variant: A2017U
The issue is as follows:
On every Oreo Rom I have tried (Lineage included), I have had this issue where after an hour or so, I will never actually receive calls.
My phone will ring, but I will get no notification from the phone that there was ever a call, neither a missed call notification, nor any entry into the dialer call history.
When I attempt to even attempt to access the dialer in this state, the dialer fails to work. The dialer _does_ open, but it's void of any content at all, and will not make a call, almost as if the entire dialer framework has broken top to bottom.
This has happened in every single Oreo rom tested, AEX, DotOS, Lineage, and AOKP all show the same results.
The process I have used for most attempts has been:
1: Wipe System, Cache, Dalvik, and Data (result is the same with internal storage wiped)
2: Flash Bootstack (Last attempt was with DrakenFX's Universal Bootstack v2, have also attempted with Oki's B12 iEDL, flashed with MiFlash)
3: Flash Modem (A2017U_OreoModem.zip as provided for Lineage 15.1)
4: Run Party (if vendor required by rom)
4: Set dm-verity enforcing
5: Reboot back to recovery, install rom, gapps
6: Initial Setup, reboot to recovery
7: Install Magisk
I have also attempted to do this in varying orders as well, and all result in the same thing.
Every time, I end up limping back to my latest Nougat AEX 4.6 backup.
I have a sneaking suspicion that I'm missing something, like the modem package being bad, but I'm not entirely certain.
Has anyone else encountered this issue?
If so, how did you overcome it?
When you cant get calls try open stock sms messaging. If it hangs then I had the same issue.
The issue is contacts sync. If you force stop it, you should be able to get calls again.
Not sure how I permanently fixed but it was a mix of using Google's messages app, dirty flashing Pico gapps and clearing contacts data
Sorry, I can't remember exactly how it fixed for me
CantRememberOldAcc said:
When you cant get calls try open stock sms messaging. If it hangs then I had the same issue.
The issue is contacts sync. If you force stop it, you should be able to get calls again.
Not sure how I permanently fixed but it was a mix of using Google's messages app, dirty flashing Pico gapps and clearing contacts data
Sorry, I can't remember exactly how it fixed for me
Click to expand...
Click to collapse
Thanks for the response, I'm trying again right now, I'll update when I can confirm or deny success.
Hopefully I can figure out exactly how to fix it with that information.
Related
I am running Cyanogenmod 5.0.8 on a T-Mobile Mytouch3G (I tried upgrading twice to CM 6.0.0 but due to issues (lots of Force Quits due to running out of memory - I did not try swapping), went back to Android 2.1).
After running into the issue where creating a new folder would generate a Force Quit (ACore) message, I followed the advice here of running su -> fix_permissions which did solve that issue. However, it created the issue where the Phone Lock (i.e. slide to unlock) no longer appears. It also reset several passwords but that is manageable and also reset my Android Market list so it thinks my downloads were not installed, which was also manageable.
I have tried other lock programs (Lock 2.0, myLock) from Android Market but they don't always work.
I'd greatly appreciate suggestions on how to fix this problem.
Thank you
You can try reflashing CM without a wipe.
Sent from my HTC Magic using XDA App
I tried that but ended up having lots of issues with my phone so I restored my Nandroid backup. I may try flashing it again sometime in the near future.
I encountered further problems with my phone last week, especially with no missed call messages or flashing LEDs being displayed when I missed several calls one evening.
After using multiple backup utilities (just in case) to backup all of my call logs, SMS, MMS, Applications and Data, I dropped into Nandroid last night and did a full user data wipe along with the Cache and Battery Status. (It was a good thing I had used multiple utilities as the first program I tried couldn't find my backup after the install).
I then updated to CyanogenMod 6.0.0 and Gapps-tiny 09302010 and downloaded fresh copies of my applications (moving them to the SD Card where possible) and restored my backups. After completing that, I was pleased to note that the phone lock was restored along with the missed call LED and title bar notifications.
So out of no where, I'm starting to get this error when I try to log in to my work's guest Wi-Fi. I had no issues this morning accepting the T&C and connecting. It times out after 8 hours and forces you to accept the T&C again to connect.
I'm on build MTC19X
6.0.1
Stock rooted w/ xposed.
I've tried:
- rebooting normally
- rebooting to recovery, wiping cache and rebooting
- navigating to system app for CaptivePortalLogin and clearing data and cache
- manually navigating to http://1.1.1.1/login which doesn't load (not sure if that's even an option, was just something I found on Google)
At this point, I'm trying to avoid having to wipe and reflash but I'll do it if I have to. I want to see if anyone has any possible fixes before I do this.
I reflashed the system.img only and it fixed the problem.
The_LC said:
I reflashed the system.img only and it fixed the problem.
Click to expand...
Click to collapse
If you happened to use a layers theme it may have caused the issue. I had the same error in the past when using a layers theme. Anyway glad to hear your issue has been resolved.
CaptivePortalLogin
"CPL" keeps crashing on me too. Android 7.1.1 Android Beta Program. Same problem when booting in safe mode. Recent update to Google Connectivity Services had no affect. Logging in to home wifi isn't a problem. Issue is only at public wifi such as Starbucks or the library.
Having this issue as well after flashing 7.1.1 Developer preview. Only happens when you have to login/accept terms and conditions for public wifi
Yep. Any solution yet? Or is it an issue with the developer preview that requires rolling back or waiting for stable version in Dec?
7.1.1 dev preview, rooted, same problem as well.
I recently switched from AOSPA after not being particularly impressed and went back to oxygen. However, after attempting to send a message I was unable to send one and noticed that I also am unable to receive. Phone calls and cellular data seems to work perfectly. I have flashed the proper firmware and reflashed the OS several times, but for no avail. I've also tried to clear cache l, but still no luck. I haven't been able to test the SIM card on another phone yet, but as the problem started as I switched OS I doubt that the problem lies there.
Some weird things I've noticed:
- Both Facebook and Google Messenger refuse to even attempt at sending a message, whereas textra pretends nothing is wrong
- In gsam battery monitor the phone line is greyed out
- Right after boot a message saying there is no service appears, but disappears fairly quickly.
Thanks in advance!
And this is after clean flash? Also without trying to restore any data using Titanium backup or other?
Clean flash, but I did use titanium backup. Guess that could be the cause. Seems like I'll have to do another clean flash anyway.
"Google Play services has stopped" on 3 different 7.1.1. ROMs (RR, AICP, Lin.)
Hey guys,
coming from a stock 5.0.2 I wanted to install Lineage Nougat. So first I installed TWRP 3.x and then Lineage and gApps.
After the installation I rebooted into the system and the setup wizard started (albeit this also has been crashing sometimes on all 3 roms), letting me go as far as the Google account login, "Checking info..." which crashed with the message "Google Play services has stopped". I can go through the wizard without doing anything, but it's the same in the system.
Can't open Play Store, can't add Google Account.
I've tried 3 roms, Resurrection Remix, Lineage, and AICP. All Android 7.1.1.
I've tried different builds, different builds for gApps, different versions (nano, micro, stock).
Tried the usual clear cache etc. stuff for Google Play that you find online. Tried installing a new Play Services apk from apkmirror.
Nothing works, it's the same thing every time. Recovery, Wipe, Install Rom+gApps, Reboot, Play Services crash.
It doesn't seem to have to do with the ROMs.
Any ideas are greatly appreciated.
So I found something while looking for answers that seems to be my problem, but I don't really understand what this person did.
https://forum.xda-developers.com/showpost.php?p=58818703&postcount=4
Somehow, after many hours spread over the last week, last night I seem to have fixed it.
I had suspected that it was an issue with a corrupt partition, (or permissions, or something!) on the internal storage, as it was only when I tried to download something that the browser crashed, and Play Store would generally only start crashing after a first time browsing with it. Also sometimes from within Recovery I wouldn't be able to wipe data properly (it would complete almost instantly, sometimes not removing a previous ROM...). Sometimes it did seem to work properly though.
I can't pin down exactly what I did that fixed it though. I tried 2 things at once: I manually wiped each of /system, /cache, etc through fastboot in the bootloader, and I also (from adb in recovery) manually did mkdir /data and mkdir /data/media
Click to expand...
Click to collapse
Can someone help me with this, what exactly did he do? When I go adb reboot-bootloader the phone restarts normally, I'm not going into a fastboot mode. And mkdir says the directory already exists.
Stupid question, are you using TWRP 3.1.0-1 by BlastGator? I remember reading something about the recovery being associated with this issue, I just don't remember where.
http://www.gregtwallace.com/lgg2-projects/twrp/
alarsama said:
Stupid question, are you using TWRP 3.1.0-1 by BlastGator? I remember reading something about the recovery being associated with this issue, I just don't remember where.
http://www.gregtwallace.com/lgg2-projects/twrp/
Click to expand...
Click to collapse
YES!
But I think I tried it with 2.8.xx as well, but I'll try again just in case.
Edit: So I tried it, to no avail.
Boot to Rec, Flash TWRP 2.8, Reboot, Wipe, Flash RR and Gapps, Reboot, Google Play Stopped.
Am I missing a step or anything I should try different?
I installed TWRP and root with SRK Tool 2.1, maybe there's something wrong there?
I have exactly same problem with you. I've tried many flashing methods and it went fail and fail again. Please tell me if your problem have been solved. Anyway I'm at CloudyG2 3.3 right now and using TWRP blastgator 3.1.0-1.
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.