<Danct12[m]>
does anyone here have any information on S88536AA2 and S88536BA2 xiaomi redmi 4x?
<M0xCAFEBABE[m]>
<Danct12[m]> "does anyone here have any..." <- I have the S88536AA2 variant iirc
<Danct12[m]>
<M0xCAFEBABE[m]> "I have the S88536AA2 variant..." <- which country did you bought the phone in? i heard there's china version of redmi 4x
<Danct12[m]>
i have global redmi 4x
<M0xCAFEBABE[m]>
Danct12[m]: mine is second hand, and yes r4x is available in china too
<Danct12[m]>
M0xCAFEBABE[m]: hmm, second hand, did it come from china?
<M0xCAFEBABE[m]>
Danct12[m]: yes it seems
<Danct12[m]>
probably AA2 = china, BA2 = global
<Danct12[m]>
there's india and indonesia version of redmi 4x too but so far i havent heard about it yet
<dr_shui[m]>
very popular here for 3D printers controller
<dr_shui[m]>
many old batteries died
<dr_shui[m]>
there's a huge amount of this phone on the second-hand market here, very cheap, about 10$.
<barni2000[m]>
i have bought my 4x-s about 30 usd/per each
<dr_shui[m]>
10 usd/per each here for redmi 4-prime. i got my 4x cost 6 usd.
<dr_shui[m]>
And we have an enterprise here that can provide free PCB processing services. Yes, it's completely free, and you don't even need to pay for postage. Each student has the opportunity to process 10 PCBs every month.
<dr_shui[m]>
We can use this to make a modified DC power supply device.
<Danct12[m]>
<dr_shui[m]> "611ee5dc4f80950c3e3556740fe6bfc..." <- so it's still a phone but a different one?
<Danct12[m]>
because there's still camera and sim slots
<Danct12[m]>
0xCAFEBABE: hmm, i think the battery is very much on it's way out :\
<Danct12[m]>
before the replacmeent i noticed sound on android are a bit laggy
<Danct12[m]>
now it's laggy but also random shuts off (like someone pulling the cord)
<Danct12[m]>
thanks for everything, BM47 ❤️
<Danct12[m]>
BTW, MFG date: 2019/09/25
<Danct12[m]>
s/2019/2017/
<dr_shui[m]>
<Danct12[m]> "because there's still camera and..." <- The battery was replaced by the PCB, provide DCDC 24V -> 4.2V , Battery encryption chips onboard and usb 1 -> 4 expand 😀
<dr_shui[m]>
connecting 3D printer motherboard, u2oc_canbus, and usb-camera
<dr_shui[m]>
<barni2000[m]> "msm-firmware-loader just an..." <- should i use it in an chroot envirment ?
<barni2000[m]>
It only works on device
<barni2000[m]>
It is mounting every useful partition
<dr_shui[m]>
oh, first make simple rootfs and flash it into phone, then exec msm-firmware-loader in phone?
<barni2000[m]>
Yes
<barni2000[m]>
You should put it in the init process
<dr_shui[m]>
<dr_shui[m]> "image.png" <- [*] Enable loadable module support ---> maybe this causes this error
<Danct12[m]>
i wonder if the redmi 4x supports sdio 🤔
<Danct12[m]>
it says 4-bit sdio
<Danct12[m]>
man if i had a sdio device on an sd card i'd try it out
<Danct12[m]>
can anyone here with a redmi 4x on downstream run cat /sys/class/power_supply/battery/current_max
<Danct12[m]>
i'm thinking 500mA may be the issue
<Danct12[m]>
possible that i managed to somehow corrupted BMS data
<M0xCAFEBABE[m]>
Danct12[m]: u can boot downstream kernel easily in any state, by `fastboot boot recovery.img`
<Danct12[m]>
i already did
<Danct12[m]>
it says 500000
<Danct12[m]>
ah, this explains why santoni on postmarketos doesn't boot properly..
<Danct12[m]>
* boot properly on some devices..
<Danct12[m]>
as in stuck at MI splash
<Danct12[m]>
the kernel that i was using probably does not support the panel i have
<barni2000[m]>
you can use the panel-driver-generator and define panels in lk2nd
<dr_shui[m]>
Mine stuck at pmos loading， is this because not supported panel ?
<dr_shui[m]>
but rndis and ssh works, wifi can scan but can’t connect
<barni2000[m]>
you can use simpledrm also
<Danct12[m]>
im talking about stuck at Mi.com splash when it boots
<Danct12[m]>
<dr_shui[m]> "Mine stuck at pmos loading， is..." <- no, that's a different issue
<M0xCAFEBABE[m]>
<Danct12[m]> "that's linux, lk2nd uses..." <- regarding board_id cmdline... today i've got a santoni which has `board_id=!!BAD!!!:board_vol=1783600`
<M0xCAFEBABE[m]>
i'm buying second hand santoni again, the seller said he broke it by flashing ROM
<Danct12[m]>
wow i haven't seen that one
<M0xCAFEBABE[m]>
M0xCAFEBABE[m]: the device's condition looks great, the eMMC is still writeable, booting into recovery and charger mode works, but it's unable to boot into ROM
<Danct12[m]>
i'm gonna guess nothing the official EDL flashing tool can fix?
<Danct12[m]>
IIRC xiaomi official flashing tool provides a firehose as well as it's rawprogram and patch
<M0xCAFEBABE[m]>
M0xCAFEBABE[m]: i've tried stock rom (k3.18), custom rom (k4.9 & k4.19), when it reaches to boot animation some random pixels appears immediately and then crashes and restarts, interesting (it crashes when GPU is being used?)
<M0xCAFEBABE[m]>
M0xCAFEBABE[m]: reflashing stock firmware through fastboot doesn't fix it, so... I'm deciding to use that new santoni's board as a playground, moved that new santoni's perfect screen to my old santoni, and I'm planning to solder UART wire onto that new santoni on tomorrow
<Danct12[m]>
M0xCAFEBABE[m]: what about the stock firmware with the official edl tool?
<M0xCAFEBABE[m]>
Danct12[m]: uh I've never tried flashing via EDL, no experience with that
<M0xCAFEBABE[m]>
* via EDL, have no experience
<M0xCAFEBABE[m]>
<M0xCAFEBABE[m]> "i'm buying second hand santoni..." <- tho the seller sounds like a noob so I guess he haven't touched any low level stuff on that device, also I saw that the "MI" sticker still presents on one screw
<Danct12[m]>
M0xCAFEBABE[m]: it's the tool called "XiaoMiFlash"
<Danct12[m]>
M0xCAFEBABE[m]: sounds like untapped device to me then
<Danct12[m]>
probably a good thing because you pretty much got a redmi with original display
<Danct12[m]>
this is how the tool looks like (1:36) if you never seen it
<Danct12[m]>
given that you're currently working on lineageos for this device chances are you already seen this stuff
<M0xCAFEBABE[m]>
Danct12[m]: ok i'll try, thx
<Danct12[m]>
last time i used it was like many years ago when i tried to fix sensors on my redmi 4x because of a bad persist
<M0xCAFEBABE[m]>
<M0xCAFEBABE[m]> "i've tried stock rom (k3.18..." <- one more interesting thing, all of *-adc thermal zones have negative value
<M0xCAFEBABE[m]>
> <@me_cafebabe:matrix.org> i've tried stock rom (k3.18), custom rom (k4.9 & k4.19), when it reaches to boot animation some random pixels appears immediately and then crashes and restarts, interesting (it crashes when GPU is being used?)
<M0xCAFEBABE[m]>
* one more interesting thing, all of \*-adc thermal zones reports negative value on that device (not kernel issue, it works fine on normal devices)
<Danct12[m]>
huh, that's even weirder
<Danct12[m]>
did you ask which rom he tried to flash
<Danct12[m]>
could give us an idea how did he fuck up that bad
<M0xCAFEBABE[m]>
Danct12[m]: not yet, i'll try to ask what he have done on tomorrow
<Danct12[m]>
because to be fair, i have not seen anything like this before, but to me it sounds like he also fucked up calibration values
<Danct12[m]>
the first game i had to test after i got everything back in
<Danct12[m]>
didn't fix my battery issue though :\ so it has to be plugged in if i want to do anything
<Danct12[m]>
this battery is probably beyond dead or i did something to it while i was replacing battery
<Danct12[m]>
s/battery/screen/
<Danct12[m]>
* this battery is probably dead or i did something bad to it while i was replacing screen
<Danct12[m]>
not sure if it's possible to ruin bms calibration by removing it
<M0xCAFEBABE[m]>
Danct12[m]: have you tried booting into downstream android rom for once? maybe it does some sort of recalibration
<M0xCAFEBABE[m]>
i've replugged the battery for a lot of times and haven't got such issue
<Danct12[m]>
M0xCAFEBABE[m]: this is downstream, lineageos 16
<Danct12[m]>
this was actually my own build after santoni is no longer supported on upstream
<M0xCAFEBABE[m]>
Danct12[m]: ah oh, I haven't read it carefully, my bad
<M0xCAFEBABE[m]>
weird then
<Danct12[m]>
also noticed that the sound gets stuttery
<Danct12[m]>
M0xCAFEBABE[m]: kernel 3.18 btw
<Danct12[m]>
a classic :)
<M0xCAFEBABE[m]>
Danct12[m]: in android world we'd rather call it a ultra legacy kernel XD
<M0xCAFEBABE[m]>
santoni have got k4.9 in 2018~2019, and in 2023 I finally made k4.19 usable
<M0xCAFEBABE[m]>
* in 2018~2019 (by other people), and
<Danct12[m]>
M0xCAFEBABE[m]: lol everyone likes the largest number :)
<Danct12[m]>
msm-5.10 santoni when
<M0xCAFEBABE[m]>
Danct12[m]: not just that... android kills EOL kernels on every new versions, those kernels would require some hacks to boot up newer android versions
<Danct12[m]>
i guess by the time lineageos 16 came out for santoni there's already more hacks done to get it running?
<Danct12[m]>
iirc santoni only has marsh and nougat
<Danct12[m]>
no oreo or pie
<M0xCAFEBABE[m]>
Danct12[m]: no, k3.18 officially supported by Google till Android 10
<M0xCAFEBABE[m]>
* no, k3.18 is officially supported
<M0xCAFEBABE[m]>
at los16 times k3.18 is still working well
<M0xCAFEBABE[m]>
* working well without hacks
<M0xCAFEBABE[m]>
it's just that the kernel needs to be upstreamed to newer Android Common Kernel tags, stock nougat kernel wouldn't boot pie for sure
<M0xCAFEBABE[m]>
<Danct12[m]> "msm-5.10 santoni when" <- no clue, it'd be pain... on the one hand we need to forward port some downstream drivers by ourselves and take care of proprietary blobs compatibility, on the other hand msm-5.x stuff is probably too much ahead of msm89xx
<M0xCAFEBABE[m]>
there's no msm89xx/sdm target getting migrated to msm-5.x by qcom
<Danct12[m]>
i guess things will have to go then :P
<Danct12[m]>
but msm-4.19 is gonna be supported for a long time so yeah
<Danct12[m]>
actually.. till next year.
<Danct12[m]>
but linux kernel lts can increase whenever there's a demand so not entirely the EOL date
<Danct12[m]>
* but linux kernel lts can increase whenever there's a demand so not entirely an accurate EOL date
<M0xCAFEBABE[m]>
Danct12[m]: yeah, at the end of the next year
<M0xCAFEBABE[m]>
hopefully that phone would have Android 15 as the last decent android version at least
<Danct12[m]>
hah
<Danct12[m]>
:P
<Danct12[m]>
the things that people won't let go
<Danct12[m]>
gotta be honest, if it wasnt for the broken screen i would still be using the redmi 4x as a daily driver phone
<Danct12[m]>
i was using it until the charging port decided to die, then i replaced it and used it until i dropped it and the screen cracked
<Danct12[m]>
then the touch screen dies
<Danct12[m]>
i was the type of person preferring small phones at the time
<M0xCAFEBABE[m]>
o..
<Danct12[m]>
now even after the screen has been replaced, i still wouldn't use it because i'm currently using a redmi note 7
<Danct12[m]>
both are good phones though
<Danct12[m]>
still no one looked at the redmi note 7 and gave it an official lineageos release after a year, maybe i'll have to step up and maintain my own for myself
<Danct12[m]>
(there was official lineageos for redmi note 7 but it was unmaintained and then dropped)
<jojo_autoboy[m]>
id say my land was my favourite phone too
<jojo_autoboy[m]>
got replaced by my mi a2 just kinda by chance
<Danct12[m]>
did the same for my redmi 4x back then too
<M0xCAFEBABE[m]>
my Redmi Note 5A Prime (MSM8940)... I'm using it from 2018 to this day, have always been along with me even when I was in foreign, at the beginning it's my primary phone now I'm using it as a secondary phone
<Danct12[m]>
using my redmi 4x since sometime in 2017 or 2018..
<Danct12[m]>
yep, probably sometime late 2017 because battery was manufactured in sep 2017
<Danct12[m]>
how did android security update not being the latest
<M0xCAFEBABE[m]>
Danct12[m]: ah no it's glitch XD
<M0xCAFEBABE[m]>
M0xCAFEBABE[m]: because of the spoofs for SafetyNet
<Danct12[m]>
safetynet pass check?
<M0xCAFEBABE[m]>
Danct12[m]: yes
<Danct12[m]>
lol :P
<Danct12[m]>
oh i see
<Danct12[m]>
OH
<Danct12[m]>
the latest update for redmi 4x was in 2019
<M0xCAFEBABE[m]>
* glitch XD, happens after you restart android framework
<M0xCAFEBABE[m]>
Danct12[m]: in official lineageos?
<Danct12[m]>
that make sense
<Danct12[m]>
s/update/MIUI/
<Danct12[m]>
edited ^
<M0xCAFEBABE[m]>
Danct12[m]: tho that's not related with the security patch date on my screenshot... that latest MIUI update have 2018 security patch level, and I'm actually stealing OnePlus7Pro's build fingerprint
<M0xCAFEBABE[m]>
<M0xCAFEBABE[m]> "Screenshot_20231214-031857_Eleme..." <- when I was taking that screenshot, I was trying to open the Element app as a window, UI freezed, I soft restarted android and that 2019 security patch date has appeared...
<M0xCAFEBABE[m]>
* that's what it should display in normal cases
<M0xCAFEBABE[m]>
* a window, unexpectly UI freezed,
<Danct12[m]>
heh
<Danct12[m]>
yeah im thinking that there's something with the BMS calibration data or whatever
<Danct12[m]>
which only allow limited current
<Danct12[m]>
because when i opened the camera while in the charger, it works fine
<Danct12[m]>
but when i unplug it, it takes like half a second then power cut
<M0xCAFEBABE[m]>
is it just the battery connector being loosen, or you haven't plugged it properly..?
<Danct12[m]>
M0xCAFEBABE[m]: i plugged it in properly, and it shouldn't be loose
<Danct12[m]>
because i pushed it to make sure it fully clicked in
<Danct12[m]>
actually it may not be the BMS after all, since now it shuts off instantly after i unplug in camera
<Danct12[m]>
i remember having this issue on redmi note 7, gave it to someone to fix it and it was the battery
<jojo_autoboy[m]>
heh i never updated the miui version on my land since like 2017
<jojo_autoboy[m]>
sucks how i screwed up backing it up and lost that install
<Danct12[m]>
speaking of updates
<Danct12[m]>
i wonder if i should upgrade the firmware on my 4x
<Danct12[m]>
maybe not since it's still working as is
<M0xCAFEBABE[m]>
Danct12[m]: why not... it's not dangerous, you can even do downgrade later if you want
<M0xCAFEBABE[m]>
and, newer firmware does make some difference
<M0xCAFEBABE[m]>
for example, the CPU DAI that used for voice call is CS-Voice on Marshmallow firmware, which got changed to VoiceMMode1 on Nougat firmware
<Danct12[m]>
seems to be on the latest i think
<M0xCAFEBABE[m]>
Danct12[m]: u can check by reading /sys/devices/soc0/images on downstream kernel, here's the result of mine (running latest global fw, V11.0.2.0.NAMMIXM)
<Danct12[m]>
for qcom, no docs, nothing at all, just a kernel and you figure out everything on your own
<Danct12[m]>
Danct12[m]: i know it says "Rockchip Confidential" but they release docs with that on purpose
<M0xCAFEBABE[m]>
Danct12[m]: now even the dts is proprietary since msm-4.19 lol, thanks to some vendors like moto/xiaomi/google which discloses it due to device kernel opensource
<Danct12[m]>
yeah the device tree can be BSD licensed now, last time i upstreamed a device tree i had to relicense it under BSD just so vendors can put it in bootloaders and stuff
<Danct12[m]>
GPL-2.0+ OR BSD-3-Clause
<Danct12[m]>
so now pretty much you can have a kernel with all the drivers.. just without the device tree :P
<M0xCAFEBABE[m]>
yeah lol, but usually not that bad, normal vendors opensource the dts too
<M0xCAFEBABE[m]>
s/opensource/releases/
<Danct12[m]>
update on the screen earpiece issue: asked the seller, the seller say "this is the lcd, we'll look into it"
<Danct12[m]>
and for the whole noon/afternoon i havent heard anything back..
<Danct12[m]>
hmm
<Danct12[m]>
even if it's a loss, probably can be easily fixed by using paper knife and try to cut the plastic around it