Develop Bugs

[DISCUSSION] RIL Problem in E980/F240

Hi, this is United Oxygen.
We're delaying our kernel/ROM release date because of very unstable RIL.
Too lazy catching signal, often RIL goes off to heaven etc...
When we fix RIL almost, then battery leak happens...
So we're in slump.
We want to ask you, is there any RIL problem in Official CyanogenMod 12.1 in e980.

There is RIL problem in every ROM, even in AOSP based (I'm maintaining unofficial slim build). RIL sometimes picks network up right away, sometimes seems too lazy to pick-up the network for 20-30s and after that is OK.
Our device libs need some serious updating, that's the main reason why this is happening...
In the meantime, I can give you the commits which will fix that for CM based ROMs - you'll need to patch frameworks_opt_telephony and android_device_gproj-common, that will make RIL work for after initial 20-30s of insanity..

If that's the case, that explains why the last pac rom 5.0 seems to never pick up the signal. I thought @emannuel's zip patch does a good job of fixing the problem. Blisspop seems to do a good job of picking up the signal, have any of you consulted @nerdyblond about the RIL issue?

No matter how you patch it (Emmanuel's patch, or Jan's patch I'm using) you'll have to maintain telephony_opt repo because it changes constantly, I had more work updating my fork of telephony repo than porting Slim.
Sent via carrier pigeon.

ShadySquirrel said:
No matter how you patch it (Emmanuel's patch, or Jan's patch I'm using) you'll have to maintain telephony_opt repo because it changes constantly, I had more work updating my fork of telephony repo than porting Slim.
Sent via carrier pigeon.
Click to expand...
Click to collapse
We think 20-30 secs delay may be come from rild problem.
And, we've also found that when rild crash is happening, Force Stopping com.android.phone process restores the signal according to log.
So, we're really looking foward to e980 developers to make this scripts : when rild crash happens, force stop com.android.phone process, then signal will be restored.

Genie's said:
We think 20-30 secs delay may be come from rild problem.
And, we've also found that when rild crash is happening, Force Stopping com.android.phone process restores the signal according to log.
So, we're really looking foward to e980 developers to make this scripts : when rild crash happens, force stop com.android.phone process, then signal will be restored.
Click to expand...
Click to collapse
For me, RILD crashes after telephony tries to set subID, and quickly recovers, and it all quckly happens while phone is still booting. After boot, phone has network connection on primary (and only slot), but after that it just keeps searching for additional slots/IDs - possibly connected to dual-sim support introduced earlier this year.
Only way to fix this without workarounds is to fix device's ril and libs, other stuff is just simple workarounds to make it somehow work...

ShadySquirrel said:
For me, RILD crashes after telephony tries to set subID, and quickly recovers, and it all quckly happens while phone is still booting. After boot, phone has network connection on primary (and only slot), but after that it just keeps searching for additional slots/IDs - possibly connected to dual-sim support introduced earlier this year.
Only way to fix this without workarounds is to fix device's ril and libs, other stuff is just simple workarounds to make it somehow work...
Click to expand...
Click to collapse
It is hard for us to fix ril and libs, so we've thought about workarounds, and found that closing com.android.phone process forcely makes RIL recovered.
If you test this method on your E980?

Genie's said:
It is hard for us to fix ril and libs, so we've thought about workarounds, and found that closing com.android.phone process forcely makes RIL recovered.
If you test this method on your E980?
Click to expand...
Click to collapse
I'm using this one: http://review.cyanogenmod.org/#/c/108153/ on CM-based ROMs, Slim doesn't need any kind of those fixes - it simply works, takes some extra time but it simply works, logs don't even show any crashes/segfaults (at least not for me). I can't even enter my PIN fast enough after boot, I'm already connected to the network so killing com.android.phone will just make some mess for me. E988 variant, flashed from stock Jellybean.
I'm trying different approach: I've extracted my old KitKat backup and I'm hunting down libs needed for RIL to work. If I manage do make it work faster that way, I'll post the (flashable) zip and push changes to my git.
Update on that: pushed all needed libs, rild seems to be starting but it continuously restarts with "memory violation" from audit. Gah. Maybe something more is missing?

Android marshmallows in ROM does not change my Internet connection speed

My network connection speed never change only h or only edge Pls help me :crying: :crying:

+++ I also have no LTE, 30B (Bump), different modem (hybrid or 21A). what to do ?

if you flashed the kdz you should be fine

For me, I have to wait for the next build... The first build is not always the best build... 21A modem makes at least the signal working...

Signal drop on CM13

Hi, i'm using Temasek's CM13 and i noticed the cellular network lost its signal every day. Is there any way to fix/prevent it? Or solve it when it drops signal. I'm fixing it by turn on airplane mode, restart, turn off airplane mode, restart, turn on airplane mode, then off again (long procedure), so if there is any way to fix it faster, plz tell me.
My phone: Z008, Temasek CM13, OctoDex kernel 5.0

Please dont open new threads for old bugs.
Qick search on Temasek (or CM13) ROM thread.

C-Ph87 said:
Please dont open new threads for old bugs.
Qick search on Temasek (or CM13) ROM thread.
Click to expand...
Click to collapse
I know my question have been asked for hundreds times, but i see the changelog of the rom says "on 9th July fixed signal lost issue", but i'm on the newest build (10th July, Z008), so it have to be fixed, but i'm still have that issue

HungNgocPhat said:
I know my question have been asked for hundreds times, but i see the changelog of the rom says "on 9th July fixed signal lost issue", but i'm on the newest build (10th July, Z008), so it have to be fixed, but i'm still have that issue
Click to expand...
Click to collapse
Understand.
But the right thing to do is to report on apropriated thread - the official CM thread - and, in this case, the issue will only be solved when the asus blobs are fully merged into CM kernel.

HungNgocPhat said:
I know my question have been asked for hundreds times, but i see the changelog of the rom says "on 9th July fixed signal lost issue", but i'm on the newest build (10th July, Z008), so it have to be fixed, but i'm still have that issue
Click to expand...
Click to collapse
just flash Octodex kernel. no more signal drop issues

Siddk007 said:
just flash Octodex kernel. no more signal drop issues
Click to expand...
Click to collapse
Yes, I'm making this thread on Z008, CM13, and Octodex kernel

Siddk007 said:
just flash Octodex kernel. no more signal drop issues
Click to expand...
Click to collapse
It only solves signal drop issues for several people. For me, flashing or not doesn't have any impact if Indosat SIM card is active: Signal could suddenly loss and I need to take a full reboot to recover.
Sent from my ASUS_Z00A using XDA Labs

Volte loosing issue in oreo roms

i have tried each and every oreo rom available for lenovo p2 and using jio roaming
i am facing volte loosing issue after certain reboots in every rom,
i tried swapping sim cards, flashing stock rom using fastboot and did all the ota updates, tried adding ims to apn type, adding some build prop lines and also tried vreating new apn ! still no success
not facing same issue in los by code elixir but dont want to use it as it has less customizations.
any other solution available for this problem ?
i know most of the developers dont use volte so dont care much about volte but most of the indians are using Jio som cards for calling and internet accessing purpose
So devs i humbly request you to find solution for this issue...

Ya its a big issue in using Oreo rom. I am back to Lineage os 14.1 .

Flash the modem of the stock ROM when you lose the connectivity. It worked for me.

appy.79 said:
Flash the modem of the stock ROM when you lose the connectivity. It worked for me.
Click to expand...
Click to collapse
I don't have backup of stock ROM. Did u download it??

bhupeshbb said:
i have tried each and every oreo rom available for lenovo p2 and using jio roaming
i am facing volte loosing issue after certain reboots in every rom,
i tried swapping sim cards, flashing stock rom using fastboot and did all the ota updates, tried adding ims to apn type, adding some build prop lines and also tried vreating new apn ! still no success
not facing same issue in los by code elixir but dont want to use it as it has less customizations.
any other solution available for this problem ?
i know most of the developers dont use volte so dont care much about volte but most of the indians are using Jio som cards for calling and internet accessing purpose
So devs i humbly request you to find solution for this issue...
Click to expand...
Click to collapse
I got the same problem.

any solutions?

Please can somebody post the modem for the S251 stock ROM.

Sutcliffe9 said:
Please can somebody post the modem for the S251 stock ROM.
Click to expand...
Click to collapse
Here is the file https://drive.google.com/file/d/1O42-tqX7StyScOuKRpakEH44-xt9tBri/view?usp=drivesdk

[email protected] said:
Ya its a big issue in using Oreo rom. I am back to Lineage os 14.1 .
Click to expand...
Click to collapse
VoLTE is a PIA for developer's. not just because the code is proprietary (meaning no access to the source code).
the Dev's so far have not focused to fix VoLTE for Oreo hence the issues. they focus on other major more important fixes first.
Oreo is a major re-write to C++ compared to Nougat.
VoLTE on 14.1 is stable because the Dev's have figured out a proper way to make it work. Which is not yet the case with Oreo. so if you want stable VoLTE stick with Official LOS 14.1.

celoxocis said:
VoLTE is a PIA for developer's. not just because the code is proprietary (meaning no access to the source code).
the Dev's so far have not focused to fix VoLTE for Oreo hence the issues. they focus on other major more important fixes first.
Oreo is a major re-write to C++ compared to Nougat.
VoLTE on 14.1 is stable because the Dev's have figured out a proper way to make it work. Which is not yet the case with Oreo. so if you want stable VoLTE stick with Official LOS 14.1.
Click to expand...
Click to collapse
Okay. Thankyou for info btw

appy.79 said:
Flash the modem of the stock ROM when you lose the connectivity. It worked for me.
Click to expand...
Click to collapse
How to flash stock modem .
I am on AEX.
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
I think AOSP roms have volte problems.
When I am on AOKP os volte working fine..
Yesterday I flashed AEX which is based on AOSP.
Volte gone.

One way to get back the volte is by changing the sim card from 1 to 2 or vice versa. This will get you volte. And then if you want to change the sim cards back to original then do so. The volte will stick.
Other one is, flash the stock ROM modem or an LOS modem. It worked for me with stock and RR modem.

appy.79 said:
One way to get back the volte is by changing the sim card from 1 to 2 or vice versa. This will get you volte. And then if you want to change the sim cards back to original then do so. The volte will stick.
Other one is, flash the stock ROM modem or an LOS modem. It worked for me with stock and RR modem.
Click to expand...
Click to collapse
How to flash modem. Can u please explain

Flash the modem backup file using TWRP.

fix signal issues on pie roms ?

How to fix fluctuating signals of 4g as well as 3g signal on pie ROM specifically crdroid pie ROM

You have to ask this in respective thread... Being a custom ROM user you have to deal with all the unexpected bugs.. if possible take logs and post it on crDroid thread so that developer can look into that issue.