I already made logs with adb but as the reboot happens randomly, it’s difficult to have the phone connected all the time to my desktop.
My question was about other methods to have logs. Bug report, maybe ?
Is it usefull for this kind of problem ?
I generated one. But what is interesting to look in these files generated ? It talks about a lot of things…
And I suppose some errors are “normal”…
Maybe, I will reinstall from scratch and not install any soft, to see if the problem is present with defaut installation. (to bad, I really wanted to have at least Signal and Blokada…)
Bonjour (I’m French and I used DeepL for the translation)
I have encountered this problem with a redmi note 8. Untimely restarts, but I had managed to understand when the restart was happening. Indeed, my phone would restart when I lost the mobile network.
I tried several rom :
E = KO
Lineageos = KO
CRdroid = KO
CarbonRom = OK
Today, I use Carbonrom on which I installed NanoDroid.
It’s working and I don’t have any reboot.
Christian
I have indeed noticed that the reboot happens often when leaving my home. I thought it was the loss of wifi, but not necessarily the loss of the mobile network.
Our experiences seem to confirm a problem specific to the Redmi Note 8…
I decided to connect the phone to a laptop and make the rest of the day like that.
Fortunately, I’m travelling by car… so I made a logcat file like this.
The log stops abruptly when the phone rebooted after connected to my wifi when arrived at home…
I hope someone will find a solution to this bloking problem.
One or two devices have had an issue of crashing when connecting to some routers. You might be able to do some research combining the ideas of switching off WiFi as you leave and enter your home. In this testing report Testing Samsung A3 (2016) a3xelte January 2021 Oreo "dev" build, I did such experiments and found a “soft” technique for starting WiFi.
Not very practical in daily use, but might allow more organised collection of logcat.
Very interesting input from @christianrablay. If mobile connection might be the issue - is there any evidence that mobile data, is the issue. So, in this case, is the phone capable of running and working for extended periods if mobile data is off. One could further extend this research using no SIM card or a different SIM card. Just testing ideas to think about adding to the bug report!
The other approach is to think of the install method - was the phone fully “Xiaomi” updated before the /e/ install?
Following Christian’s advice, I tried CarbonROM. Indeed, no more reboot problems.
I still tried to switch the phone back to MIUI (last version, Q) to be fully “Xiaomi” updated. No problem with MIUI, but as soon as I reinstalled /e/, the reboots came back…
As the phone must be available quickly for the person for whom it is intended, I had to resign myself to install CarbonROM.
Too bad for /e/, a phone that is supposed to be supported and that reboots regularly, it’s not possible…
Hello,
I bought a new Redmi 8T as I want to leave Google android…
I success in instaling /e/ but, as others, it reboot randomly and relatively frequently (from 1 time/3 days to many times the same day).
The installaion was new, no other apps than the one of the installer.
Everything seems ok except th reboot. After weeks of try, wait for update in /e/ etc… I finally desisted.Very sorry for that, I hope you can solve this issue as I was very happy with /e/ and didn’t find any cellphone with characteristic as good as the Redmi 8T (autonomy, sd card, jack, nfc, b28 band for french Free operator…).
Hope to come back when an equivalent phone is available in /e/
Hi everyone, thanks to the e-OS team.
Just to report too that I own a Redmi Note 8T and that I have random reboots too.
It doesn’t really bother me, so I am not going to swap ROMs or do any work on it. I’ll just let it reboot.
If it gets sorted out in future updates, all the better. If not, not a problem.
Hi,
I have an issue like @xlbt describes.
I identified that my Redmi Note 8 (Ginko) crash and reboot when there is no GSM network (for example in train…)
When the phone is in plane mode it does not crash.
This bug is very problematic and the phone is almost unusable…
Have you tried to upgrade firmware of your device? You had to be carefully though and select right variant from:
First select ginkgo for Redmi Note 8 or willow for Redmi Note 8T, and then it’s up to you to select right variant for your device. After downloaded right variant zip file, flash it from twrp.
If that right variant for your device, it should be usable at twrp => install => select that zip etc.
That’s what I’ve done to my Rermi Note 8T (willow, which uses same unified ginkho build). Last time had to update after /e/ OS V1 R ginkgo, to get camera fully working (for that obviously fw for A11). But there’s always risk when updating fw, so double check everything.
And I haven’t ever even tried Firmware creator or stock MIUI ROM from there. Placed my RN8T to queue to open bootloader at day 1 and have updated fw few times.
Just to agree with @huuhaa … check very carefully.
I did use ROMs from the site quoted first by @huuhaa.
I would not use something where i did not fully understand the supporting words!
I had a different Xiaomi, the fastboot flashable ROMs were more like 3-4 GB, other smaller firmwares were just an update. I apologise for introducing a distinction with fastboot, but that was my only experience.
)
