<clfbbn>
Hi, luk. I am having problems bringing up radio of my phone. It seems that the SIM card is not detected at all. When I pull the card holder out off my phone, all I can get is a kernel message "mmc0: slot status change detected (1 -> 0), GPIO_ACTIVE_HIGH". Since you are maintaining some sony devices, could you provide some hints on what could be missing?
<clfbbn>
.. But I do saw mdm errors in dmesg, which triggers resets: "ext-mdm soc:qcom,mdm0: mdm_errfatal: mdm sent errfatal interrupt". I am wondering if this is kernel/dts related.
<LuK1337>
that mmc0 stuff is likely not relevant
<LuK1337>
you're likely starting something like tad too late
<LuK1337>
or you forgot some magic service
<LuK1337>
which in the end gets modem to die
<clfbbn>
OK. I am comparing with the stock vendor and pushing different services to see if that makes a difference.
<LuK1337>
on kirin there was some stupid logging service e
<LuK1337>
that was required to get modem to stop crashing
<LuK1337>
so really, good luck guessing
<sagematt>
Man, I'm so disappointed about that ColorOS switch, that I am simply waiting for LOS 19 before switching from stock on this OP8T.
<sagematt>
That being said I'm seriously considering buying a second phone for work.
<sagematt>
Due to wanting to tinker with my phone and corporate MFA apps being way too touchy about custom ROM/rooted phones and the like.
<LuK1337>
if you want, you can compile 19.1 on 8T without any changes
<LuK1337>
but i'm waiting for OOS 12 kernel src
<LuK1337>
so that's why it's not official
clfbbn has quit [*.net *.split]
clfbbn has joined #titandev
<clfbbn>
Hi luk. Is the SIM detection part done by the modem? I was not able to find anything in the log when I insert a SIM card...
<LuK1337>
is your modem still crashing?
<LuK1337>
if so, focus on that
<LuK1337>
don't bother with anything else
<clfbbn>
OK
<LuK1337>
mlog_qmi_service
<LuK1337>
i needed that on kirin
<LuK1337>
otherwise modem kept crashing
<LuK1337>
maybe you also forgot about it
<LuK1337>
lol
<clfbbn>
Oh luk you saved my day!
<clfbbn>
I tried to add every services that is in the radio group but left this one
<clfbbn>
Much appreciated!
clfbbn has quit [Quit: WeeChat 3.5]
<sagematt>
<LuK1337> but i'm waiting for OOS 12 kernel src <-- Yeah I decided I would wait for this
<LuK1337>
that might take a while
<LuK1337>
after oppo took over
<LuK1337>
src releases are even slower than before
<LuK1337>
they were pathetic before oppo
<sagematt>
But now there's the matter of whether to demote this phone to a work phone, or buy a secondary one and keep this as my primary driver
<LuK1337>
but now they're unacceptable
<sagematt>
it's a very sad state of affairs
<LuK1337>
but oppo userspace/kernelspace is way nicer
<LuK1337>
for custom rom devs
<sagematt>
I'm just disappointed I decided on the phone right before this happened
<sagematt>
Not that I didn't know this wasn't going to happen, I did
<sagematt>
I just didn't realize how bad it would be
<sagematt>
Oh, since you're around, I was wondering about something.
<sagematt>
There's a phone I have on LOS that I hadn't updated for months
<sagematt>
But after updating, I started getting this on several apps: "APPNAME won't run without google play services which are not supported by your device"
<sagematt>
I had previously used MagiskHide Props Config to give it a confirmed working fingerprint.
<LuK1337>
it's a/b and you forgot to flash gapps?
<sagematt>
it's not a/b
<LuK1337>
and gapps work just fine?
<sagematt>
hmm
<LuK1337>
if gapps work fine
<LuK1337>
then reinstall app that's broken
<sagematt>
gapps like gmail and the like?
<LuK1337>
and if it works
<LuK1337>
then it seems like it forgot what installed it...
<sagematt>
I did reflash the rom and gapps again, however
<sagematt>
<LuK1337> and gapps work just fine? <-- How do I check this?
<LuK1337>
just check if google play works
<LuK1337>
and can install apps
<sagematt>
google play did work
<sagematt>
I'll try installing gmail from it just to make sure
<LuK1337>
gmail fails this way?
<sagematt>
says installing
<sagematt>
installed
<LuK1337>
ah
<sagematt>
it opened just fine
<LuK1337>
weird, /data/system/packages.xml is no longer plaintext
<LuK1337>
why
<sagematt>
lol?
<sagematt>
what's that from?
<LuK1337>
/data/system/packages.xml: Android Binary XML v0
<LuK1337>
oh
<LuK1337>
android binary xml...
<sagematt>
pfft
<LuK1337>
oh well, they made it ass for no reason
<sagematt>
"binary XML" wow
<sagematt>
jesus
<LuK1337>
ehh, if it was still plaintext i'd suggest marking google play as force queryable
<LuK1337>
or actually
<LuK1337>
are you still on android 11?
<sagematt>
I am, this is los 18.1
<LuK1337>
then you can still edit /data/system/packages.xml
<LuK1337>
find com.android.vending there
<LuK1337>
and set forceQueryable="true" for it
<LuK1337>
you can likely see other packages there with same attr
<LuK1337>
and that may fix your apps that can't see google play services
<sagematt>
do you have a quick sed line for it?
<sagematt>
I feel that would be faster, I see lots of lines with com.android.vending
<sagematt>
I don't see any lines with forceQueryable, though
<sagematt>
Am I supposed to just add it to the tag corresponding to the package name?
<LuK1337>
i don't...
<LuK1337>
i don't know what device is on 18.1
<sagematt>
oh, sorry
<sagematt>
this is a le pro3
<LuK1337>
oh no, i don't know what device of mine is still on 18.1