Have you had any luck since then?I got this the other day, had to flash the factory images to even get it to boot. AFAIK, its a data corruption issue. I'm looking into it, but I dont know wtf is going on honestly
Have you had any luck since then?I got this the other day, had to flash the factory images to even get it to boot. AFAIK, its a data corruption issue. I'm looking into it, but I dont know wtf is going on honestly
Are you planning on making an update with blueborn vulnerability fixed? I know you updated your rom but the issue is kernel side meaning that it won't have any affect on custom kernels like this right? Thanks.
Panic#1 Part1
<3>[ 49.647929] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 49.647942] Fatal error on the modem.
<3>[ 49.647949] modem subsystem failure reason: fs_rmts_pm.c:854:[5, 6] rmts_read_iovec failed.
<6>[ 49.647959] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.
<6>[ 49.649578] IPA received MPSS BEFORE_SHUTDOWN
<6>[ 49.652476] rmnet_ipa started deinitialization
<3>[ 49.652491] ipa ipa_teardown_sys_pipe:1187 bad parm.
...........
<6>[ 52.727405] sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and modem's SSCTL service
<4>[ 52.743496] wl_host_event: Invalid ifidx 0 for wl0
<4>[ 52.744058] dhd_rtt_init : FTM is supported
<4>[ 52.747076] dhd_bus_devreset: WLAN Power On Done
<4>[ 52.748677] wl_host_event: Invalid ifidx 0 for wl0
<4>[ 52.749551] wl_host_event: Invalid ifidx 0 for wl0
<3>[ 52.771349] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 52.771853] Fatal error on the modem.
<3>[ 52.771869] modem subsystem failure reason: fs_rmts_pm.c:854:[5, 6] rmts_read_iovec failed.
<6>[ 52.771881] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.
<0>[ 52.771892] Kernel panic - not syncing: Subsystem modem crashed during SSR!
Forgot to actually post a few things that stood out (also attached the full log):
Code:Panic#1 Part1 <3>[ 49.647929] SMSM: Modem SMSM state changed to SMSM_RESET. <3>[ 49.647942] Fatal error on the modem. <3>[ 49.647949] modem subsystem failure reason: fs_rmts_pm.c:854:[5, 6] rmts_read_iovec failed. <6>[ 49.647959] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED. <6>[ 49.649578] IPA received MPSS BEFORE_SHUTDOWN <6>[ 49.652476] rmnet_ipa started deinitialization <3>[ 49.652491] ipa ipa_teardown_sys_pipe:1187 bad parm. ........... <6>[ 52.727405] sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and modem's SSCTL service <4>[ 52.743496] wl_host_event: Invalid ifidx 0 for wl0 <4>[ 52.744058] dhd_rtt_init : FTM is supported <4>[ 52.747076] dhd_bus_devreset: WLAN Power On Done <4>[ 52.748677] wl_host_event: Invalid ifidx 0 for wl0 <4>[ 52.749551] wl_host_event: Invalid ifidx 0 for wl0 <3>[ 52.771349] SMSM: Modem SMSM state changed to SMSM_RESET. <3>[ 52.771853] Fatal error on the modem. <3>[ 52.771869] modem subsystem failure reason: fs_rmts_pm.c:854:[5, 6] rmts_read_iovec failed. <6>[ 52.771881] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED. <0>[ 52.771892] Kernel panic - not syncing: Subsystem modem crashed during SSR!
EDIT: Sorry if any or all of this is useless, I'm just trying to learn.
Well wait some more and don't bug the Dev.Need that O goodness! Been trying to wait patiently.
What's your problem dude?Well wait some more and don't bug the Dev.
Your post comes across as whining, and/or asking for an update.What's your problem dude?
Use the kernel that comes with NetHunter build as it requires quite many drivers for the features to function well.Does this kernel have Nethunter support?
Hey guys,
Just popping in to this thread to say that I will no longer be updating this. Between college, work, and also trying to manage a social life (hah, funny joke right?), I've made the decision to only maintain my daily driver device. As of now, that's the Pixel 2 XL. I will still be maintaining CarbonROM on all of my devices, but Electron will be limited to my DD. It's been a good run, thanks for all the support, and I hope to see some of you try out my Pixel 2 XL kernel!
Hey guys,
Just popping in to this thread to say that I will no longer be updating this. Between college, work, and also trying to manage a social life (hah, funny joke right?), I've made the decision to only maintain my daily driver device. As of now, that's the Pixel 2 XL. I will still be maintaining CarbonROM on all of my devices, but Electron will be limited to my DD. It's been a good run, thanks for all the support, and I hope to see some of you try out my Pixel 2 XL kernel!
Should be fine just don't use it in oreoIs this compatible with resurrection remix os 7.1.2