Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RIL sometimes doesn't start on boot or on RIL restart #6

Open
ThePiGuy0 opened this issue May 27, 2018 · 2 comments
Open

RIL sometimes doesn't start on boot or on RIL restart #6

ThePiGuy0 opened this issue May 27, 2018 · 2 comments
Labels
AOSCP / CypherOS bug Something isn't working LOS / Lineage RR / Resurrection Remix workaround-available

Comments

@ThePiGuy0
Copy link

ThePiGuy0 commented May 27, 2018 •
edited by steadfasterX
Loading

Temporary fix applied - it repeatedly restarts RIL until it works. A better solution is needed though.

current workaround:
https://github.com/Suicide-Squirrel/android_device_lge_g4-common-LOS/blob/lineage-15.1/rootdir/etc/init.qcom.post_boot.sh#L205-L223
@steadfasterX
Copy link
Contributor

difference between working and nonworking:

working: RILC : setRadioPower: serial -890895263 on 0
notworking: RILC : setRadioPower: serial 1 on 0

only when not working:

RILJ : [3648]< GET_HARDWARE_CONFIG error 2 [SUB0]
RILJ : [3649]< RADIO_POWER error 1 [SUB0]

so it can't power on the radio

steadfasterX added a commit to Suicide-Squirrel/android_device_lge_g4-common that referenced this issue Jul 17, 2018
@steadfasterX
g4: init: init.qcom.post_boot.sh RIL workaround
5df7195 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common that referenced this issue Jul 17, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
c59fd39 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
steadfasterX added a commit to Suicide-Squirrel/android_device_lge_g4-common that referenced this issue Jul 18, 2018
@steadfasterX
g4: init: init.qcom.post_boot.sh RIL workaround
782e59a 
Enhanced the workaround:

- decrease the wait time for RIL initialization from 30 to 20

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I3ef41183b7ec103422f94faf1408219abf4a4d78
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common that referenced this issue Sep 24, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
53c4185 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common that referenced this issue Sep 25, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
981ebef 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common-OUTDATED that referenced this issue Sep 28, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
5b2ad19 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common-OUTDATED that referenced this issue Sep 28, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
2bbb863 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common-OUTDATED that referenced this issue Sep 28, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
15eb2da 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common-OUTDATED that referenced this issue Sep 28, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
30ffbbb 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common-OUTDATED that referenced this issue Sep 30, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
b517b1d 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common-OUTDATED that referenced this issue Sep 30, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
f6c8bca 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
pavlaras pushed a commit to Suicide-Squirrel/android_device_lge_g4-common-OUTDATED that referenced this issue Oct 1, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
88354a0 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
Sirhc95 pushed a commit to CypherOS/device_lge_g4-common that referenced this issue Oct 3, 2018
@steadfasterX @pavlaras
g4: init: init.qcom.post_boot.sh RIL workaround
81c0665 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: Ife3cc5be251ef5872331379b4a6ce12107757b6c
@breversa
Copy link

breversa commented Oct 31, 2018 •
edited
Loading

I have a spare H815 for LineageOS testing purposes. Is there anything I can do to help ? :)

aoleary pushed a commit to aoleary/android_device_lge_g4-common-LOS that referenced this issue Nov 25, 2018
@steadfasterX @aoleary
g4: init: init.qcom.post_boot.sh RIL workaround
8389db9 
Enhanced the workaround:

- catch all other states (e.g. UNKNOWN)
- special handler for PIN_REQUIRED:
   sometimes this state is set but no prompt happens.
   a trigger will be set + reset which ensures a RIL restart on every second run.
   handler will wait 30s for user input between each run/test
- increase the number of tries to 20 (10 is too less - especially when 3 are
   happen almost always directly on boot due to the date/time corrections!)
- increase the wait time for RIL initialization from 10 to 30 (makes no sense to
   kill too fast)
- logging

example run:

> RIL restart - try 1 of 20
> restarted RIL daemon as gsm.sim.state was ><
> RIL restart - try 2 of 20
> restarted RIL daemon as gsm.sim.state was ><
> PIN_REQUIRED detected. waiting 30s for user input..
> RIL restart - try 4 of 20
> restarted RIL daemon as gsm.sim.state was >PIN_REQUIRED<
> PIN_REQUIRED detected. waiting 30s for user input..
>
> [USER ENTERS THE PIN]
>
> gsm.sim.state >READY<
> ended

(related issue Suicide-Squirrel/issues_oreo#6 )

Change-Id: I1f6a1aeb2eaff0432a8b0d1082522def1ddcd69a
(cherry picked from commit 53c4185)
@steadfasterX steadfasterX mentioned this issue May 16, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
AOSCP / CypherOS bug Something isn't working LOS / Lineage RR / Resurrection Remix workaround-available
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@breversa @steadfasterX @ThePiGuy0