Database Users

RIL disapperaring sometimes

Hi guys, I have to clear my mind on a problem:
I have a XT1562 european mono-SIM Moto X Play, and I've upgraded it to Marshmallow (the indian dual-SIM firmware) after unlocking the bootloader and flashed Squid kernel some weeks ago (and then updated to the last build, of course).
Sometimes I'm experiencing an annoying thing: after a reboot RIL dies, and on the best, on the next reboot it reappears; on the worst, after multiple reboots with no luck, I have to do a wipe cache to see it again.
I have root and Xposed (and so, also busybox).
Is anyone experiencing something similar?
There's a way to fix it that maybe I didn't find here on XDA?

Nobody?

have u tried flashing the modem for ur rom?

anks095 said:
have u tried flashing the modem for ur rom?
Click to expand...
Click to collapse
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.

nplezka said:
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
Click to expand...
Click to collapse
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.

anks095 said:
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
Click to expand...
Click to collapse
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...

nplezka said:
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
Click to expand...
Click to collapse
I don't know if this is the same thing as you but I had "Emergency Calls Only" sporadically as well but it would come back either after a short period of time or after a reboot. I also had random reboots too (didn't matter which ROM I was on at the time).
I lived with this for a bit but then upgraded my SD card (it was old) and I haven't had either problem since.
My guess is that my SIM card might not've been seated properly in the little carrier and/or the SD card I had was mucking things up somehow. I wasn't using it as internal storage either.
Anyways, if you haven't tried this already, might be worth taking out your SIM card and re-seating it (and maybe give the contact part a careful wipe). If you still have the problem and you have an SD card remove it and see what happens. Good luck!

Hi guys! I'm here with news:
after several tests in these days, I discovered the problem was every module that can modify the systemUI.
I tried activating and disabling those modules one by one (I'm talking about GravityBox first, then little modules like Advanced Power Menu or a newer one called NeoPowerMenu), and I saw that without them, I had network at every reboot. The only exception in systemUI is SignalIconsAOSP (I really hate that big "4G" icon next to the signal indicator) and it works at every reboot I did. The other modules (like Xposed GEL Settings, Lolistat, YouTube AdAway) don't annoy the system.
So, I don't know, Moto seems dislike too much modifications on the UI or it's a strange bug. Maybe a bug.

Kernel wakelock and no deep sleep since CM13.0

Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!

Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk

CoinCoin88 said:
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Click to expand...
Click to collapse
looks like you are having weak or no signal. this is likely to cause this issue!

Bac0nator said:
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
hellcat50 said:
looks like you are having weak or no signal. this is likely to cause this issue!
Click to expand...
Click to collapse
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.

CoinCoin88 said:
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
Click to expand...
Click to collapse
sultan's rom is cm13 with caf kernel. it is known to be very battery friendly.
Here is the link: http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700

and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...

Sultan's builds are optimized for battery on the one plus one. They tend to be better than official cm13 builds, most of the time.
Another option is downloading an app called nap time on the play store, which forces your phone to go into deep sleep the moment the screen shuts off.

CoinCoin88 said:
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Click to expand...
Click to collapse
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.

I have the same issue on Sultan's Rom. First 20 days battery life was awesome and now all the time phone is awake. I am reflashing sulatn build again

Thanks for this info, this is going in the same direction I observed and somewhat reassuring. Are you talking about CM nightlies then ?
edit: that was inteded for @tiny4579
Sent from my A0001 using XDA Free mobile app

tiny4579 said:
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
Click to expand...
Click to collapse
By any chance, would you happen to have SuoerSU as root binary/manager? I recall it patches boot.img which prevented encryption from being run in the first place (to encrypt, I had to reflash the stock boot.img, encrypt, then reflash SuoerSU). I'm wondering if the altered boot.img couldn't be part of the problem.
Sent from my A0001 using XDA Free mobile app

Some heads up: there was indeed a wakelock issue that has been fixed by a commit on the 4th of June.
See associated bug on JIRA: https://jira.cyanogenmod.org/browse/BACON-4987 (and appreciate how it's easier to blame the user than to try to replicate a bug). Hopefully we'll have a 'future OTA' before the end of the year...

I still have this wakelocks issues right now...

Can't turn wifi on...

Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"

Prob a bug. My n5 had similar issue.... Turned out board was bad. I think the wifi chip had a broken solder joint. Because it would say "turning on" and never complete. I reflashed a hundred ROMs, and other recoveries including CAF. I think this happens to a lot of devices after they've been dropped 30 or 40 times there are small micro fractures each time until it causes a break in the connection somewhere.
But you just gave me a good idea I think I'm going to try to Reflow the board in the old oven

Etheralrealm said:
Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"
Click to expand...
Click to collapse
Did you have the problem before flashing Lineage? If not its almost certainly a bug in the rom. If they have a support thread you could try getting help there or you could flash a different rom and see if the problem persists.

jhs39 said:
Did you have the problem before flashing Lineage? If not its almost certainly a bug in the rom. If they have a support thread you could try getting help there or you could flash a different rom and see if the problem persists.
Click to expand...
Click to collapse
sorry it took me so long, still having the problem, and no, it was perfectly fine until lineage.

This has happened to me about 7 or 8 times running 7.1.1 lineage. Look and see what your mac address is under configure wifi, mine changes to 02:00:00:00:00:00 when this happens to me. I have found posts about the problem but no real solution. The only way I have gotten it working again is by wiping the data partition and doing a clean flash, or flashing a backup I made while it was working. It drives me mad, I thought it might be a hardware problem at first because it started with a replacement device, but I feel like it must be software as I can fix it with a clean flash.
Sent from my Nexus 6P using Tapatalk

Etheralrealm said:
Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"
Click to expand...
Click to collapse
I doubt this is a bug. Are you on the latest nightly? If you are running TWRP, start by wiping both dalvik and cache and reboot. There are LOS dedicated forums here, and this type of Wi-Fi issue would be a complete bust and I just don't see it. It could also be with how you installed LOS. The instructions are clear about fully wiping the device beforehand. I have been running LOS on my N7 for months, updating with weeklies and have never had a WiFi issue. Reddit has some decent forums you could ask around in as well.

ive been running it on my device since about november, worked until about a month ago, just been using data, tried wiping and i did a full wipe when i installed it. I went back to my january 30th build (oldest build i still had on my pc), running fine. No problems.

Here is the January 30th build, ready to flash with TWRP. Hope you have the same luck as me.
https://drive.google.com/file/d/0B9cTDZV2zbsvelUyMHJSXzlSU3c/view?usp=sharing
Cause I'm not taking chances I'm NOT responsible for any damages.

[ROM] New official ROM Global V8.5.4.0.MAGMIED released

Hi all
I just received a new OTA update on official Global ROM. New version is V8.5.4.0.MAGMIED.
Release notes only state one entry.
other
Fixed bugs
OTA is 128 MB.

I've got the update now since around 1 hour and everthing is still working. I believe, but maybe that's because of the reboot, that the finger print sensor is a bit faster now. The update fixes various security issues, but based on the date in the About Phone, the WPA2 issue isn't yet fixed.

I updated my girlfriend's phone. The fingerprint sensor is MUCH faster. Previously it failed a lot of times, too. The one issue she encountered was, that there were a lot of ghost touches, but after restart, they were gone and came back one more time. Will report if this repeats.

8.5.4.0 is really outdated now. It still have Marshmallow base.

It's not outdated, on the contrary. It's a very stable and good system now.
Which features of the newer Androids do you miss?

For me is the same software. Same bugs, i don't know what is change. Maybe the new interface when open a system app

Snow24 said:
For me is the same software. Same bugs, i don't know what is change. Maybe the new interface when open a system app
Click to expand...
Click to collapse
I guess/hope they probably didn't introduce new bugs... so why are you complaining? It's nice that they updated the security patch level...

OJK said:
I guess/hope they probably didn't introduce new bugs... so why are you complaining? It's nice that they updated the security patch level...
Click to expand...
Click to collapse
I love Xiaomi philosophy, but the Mi 5s was updated 3 times in one year. I dislike this situation, because I already have Android MM and i can't istall or use some apps. It's not a huge problem, but now there is Android Oreo and I have Marshmallow, with Miui 8, because Miui 9 isn't ready. There are some bugs, and a lot of things that Miui don't fix and i don't understand why. I'm very sad for that, and the only thing that I appreciate is the new security patch, but Miui is too slow with development, for me

Snow24 said:
I love Xiaomi philosophy, but the Mi 5s was updated 3 times in one year. I dislike this situation, because I already have Android MM and i can't istall or use some apps. It's not a huge problem, but now there is Android Oreo and I have Marshmallow, with Miui 8, because Miui 9 isn't ready. There are some bugs, and a lot of things that Miui don't fix and i don't understand why. I'm very sad for that, and the only thing that I appreciate is the new security patch, but Miui is too slow with development, for me
Click to expand...
Click to collapse
But that's a little bit how all the companies do, no? My experiences with HTC, Motorola and now Xiaomi are all similar - in the end, the custom roms were always the best, strangely also in terms of stability, but mostly in terms of safety (security patches). It is kind of a ****ty situation but it's well in line with our economic system, I'd say...

OJK said:
But that's a little bit how all the companies do, no? My experiences with HTC, Motorola and now Xiaomi are all similar - in the end, the custom roms were always the best, strangely also in terms of stability, but mostly in terms of safety (security patches). It is kind of a ****ty situation but it's well in line with our economic system, I'd say...
Click to expand...
Click to collapse
Yes, it's real. My experience is with a Nexus 5, so I was in a perfect situation and now i can't appreciate no one smartphone without pure Android

does anyone else have more problems after the update?
I really regret updating!
Now I have problems with Bluetooth - keep disconnecting or having interference. My multimedia system in car gone crazy. stops playing music, lost wheel buttons commands.
Even with apps that rely on Wifi I have problems I didn't have before.
GPS isn't connecting automatically after I turn it off, until I reboot the device

No problems here, but I clean flashed it via Fastboot. Try to wipe cache/dalvik or factory reset. I need my opinion clean flashing is not a big problem because setting everything up again is quite fast thanks to the build in backup.
Edit: I clean flashed the 8.5.3.0 then updated immediately via OTA. Got that mixed up.

Leni_YO said:
No problems here, but I clean flashed it via Fastboot. Try to wipe cache/dalvik or factory reset. I need my opinion clean flashing is not a big problem because setting everything up again is quite fast thanks to the build in backup.
Edit: I clean flashed the 8.5.3.0 then updated immediately via OTA. Got that mixed up.
Click to expand...
Click to collapse
Thank you.
Does wiping cache delete the device content?
The build in backup cannot handle all my content

wiping cache is totally safe here is a short manual (DONT delete user data or anything else):
1. Switch off your phone.
2. Power on your phone while pressing Volume up button + power button
3. A menu appears on the screen. choose Mi Recovery option.
4. choose your language.(select via volume +/- buttons,and choose via Power button)
5. Now choose Wipe and Reset option.
6. Now choose Clear Wipe cache data option.
7. All Set, done. Reboot your Phone.
Click to expand...
Click to collapse

Leni_YO said:
wiping cache is totally safe here is a short manual (DONT delete user data or anything else):
Click to expand...
Click to collapse
Thank you very much.
I tried to do it now
I get the following options:
Reboot
Wipe Data
Connect with MiAssist
When I choose Wipe Data, The only option on the next menu is Wipe All Data
which doesn't sound so good....
It shows me that it's version 3.0 of Mi-Recovery

flipperx said:
Thank you very much.
I tried to do it now
I get the following options:
Reboot
Wipe Data
Connect with MiAssist
When I choose Wipe Data, The only option on the next menu is Wipe All Data
which doesn't sound so good....
It shows me that it's version 3.0 of Mi-Recovery
Click to expand...
Click to collapse
Hmm okay. Maybe someone else can help you. I come from motorola and at the moment with my mi5s im using twrp recovery. You can also clear the cache from inside miui. In my experience clearing the cache never fixed such big system problems. Factory reset is always the way to go imo even if it's quite annoying.

Leni_YO said:
Hmm okay. Maybe someone else can help you. I come from motorola and at the moment with my mi5s im using twrp recovery. You can also clear the cache from inside miui. In my experience clearing the cache never fixed such big system problems. Factory reset is always the way to go imo even if it's quite annoying.
Click to expand...
Click to collapse
Thank you,
If I won't be able to live with it I'll do a factory reset

OnePlus 5 Slowy, Lags..

Hi, I'm here to ask for your help because I don't know what to do.
Since the update to xXx 9.6 no limits my Oneplus 5 runs in slow motion, the applications take a lot of time to open it is unusable. Even the startup animation is slow.
I've already reformatted everything, flash with unbrick tool but it's the same.
I have the impression that only when I format in F2FS it works normally but I can't find a compatible Rom. Thank for your help.

Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues

Thesuprememonkey said:
Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues
Click to expand...
Click to collapse
I have try xXx, Stock Rom and Lineage OS

mrsachou said:
I have try xXx, Stock Rom and Lineage OS
Click to expand...
Click to collapse
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom

Thesuprememonkey said:
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom
Click to expand...
Click to collapse
I start notice when i install the new Snapchat.
I'm gonna try thanks

You formatted the data (which wipes everything on your device ) or just wiped the partitions? If you completely formatted and are experiencing the exact same issue on LOS and xXx there are several possibilities -- 1) You have a hardware issue; 2) You are using corrupt or mismatched firmware; 3) A third party app is causing the issue. The last one is very easy to check--just boot your OP5 into Safe Mode and see if the issue persists. If you encountered the issue on stock OOS and did a clean install after formatting your data then it shouldn't be a firmware issue.
It's very important that you completely format all the data on your phone--not wipe the partitions or format them individually because you need a fresh start in case it's just an issue with corrupted data. My guess based on everything you wrote is that you have a hardware problem and need to have your phone serviced.