yashsingh1/xdaforums huggingface dataset:
[Motorola Moto G100 / Edge S] ew:
I see that the official upgrade instructions https://wiki.lineageos.org/devices/nio/upgrade/variant2/ state:

WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.

How do I tell if I am on that firmware, and if not, what do I do to upgrade.

I am currently running V20 and would like to just upgrade at some point.

I am also interested in hearing any recommendations from those that did a dirty upgrade from V20.
[Motorola Moto G100 / Edge S] dianlujitao:
Firmware requirements for 20 and 21 are the same. You can directly dirty flash 21 if 20 runs fine on your device.
[Motorola Moto G100 / Edge S] Niobium62:
I did a direct upgrade from 20 to 21 and I'm happy to report it went smoothly. I kept all my data and apps too
[Motorola Moto G100 / Edge S] Moto-J:
@dianlujitao; as you had enclosed the boot.img in your builds also, when upgrading to the official one is it wise to upgrade boot.img also? I don't know if you made any changes as of compression and if I can expect any issues on that part. I can try of course, though better to know in front ;-)
[Motorola Moto G100 / Edge S] dianlujitao:
It will be overridden by the upgrade
[Motorola Moto G100 / Edge S] dianlujitao:
my 0220 build integrates a potential fix for the freeze issue. please test and report if it makes a difference

any experimental fixes (including this one) won't be applied to the official build until they're verified.
[Motorola Moto G100 / Edge S] Byscu:
I am in 0220 for 3 hours.

And... Sadly, that freeze issue happened again. I don't know how to report. Provide /data/tombstones to you?
[Motorola Moto G100 / Edge S] dianlujitao:
/sys/fs/pstore and /data/tombstones
[Motorola Moto G100 / Edge S] Byscu:
Here it is.

Additional information: this time, the power button worked in turning off & on the screen when freeze happened, but only the screen, not the system.

Additional information 2: My batter was in 52% when that happened.

Addition information 3: fastboot boot twrp.img —— This command not worked in 0220 rom. I use 尘封之泪's twrp.
[Motorola Moto G100 / Edge S] dianlujitao:
The cause of your freeze is Zygote not response, which is completely different from @Moto-J and potentially other users. I suggest to disable random magisk/xposed modules, especially Thanox.
[Motorola Moto G100 / Edge S] Moto-J:
@dianlujitao are you sure you have all patches included in your build? In other words; that you synced with latest source? Asking as I still see the clock is not aligned in the taskbar, where it is in the latest LOS builds (a change of about a week ago?).

Anyway, installed your build and will see if I get a better result as with LOS build from the 17th. Had freezes several times with that one. I will let you know in a few days.
[Motorola Moto G100 / Edge S] dianlujitao:
yes it is, and it's also possible for newer changes to break it
[Motorola Moto G100 / Edge S] 4396316:
This is what I have found so far, although they do not have a significant impact on daily use :

1. It seems that the statistical information in battery - battery usage will clear on its own after a period of time (without undergoing a complete charging process).

2. After a clean flash, the display shows that although the maximum refresh rate is displayed as 60Hz, the actual refresh rate seems to be 90Hz, and it needs to be manually clicked once to return to 60Hz.

3. The issue of volume adjustment has been present since 20, and it occurs when the volume is increased or decreased, although it has no significant impact. It seems that the actual volume does not match the display of the volume bar. Sometimes, pressing the volume+ button may even reduce the volume bar, and it will only start to increase after one or two reductions. The same goes for the volume- button.

Thank you for bringing lineage 21 !
[Motorola Moto G100 / Edge S] tmpusr1:
Freeze seems caused by Fullscreen/Immersive Gestures (Q-U) module.
[Motorola Moto G100 / Edge S] Moto-J:
No freezes so far... Will keep you updated as last time it took 5 days before first freeze but also used profiles, switched on/off wifi etc..., no issues seen.

Further it seems my data connection is coming up faster then before and without any issues. Don't know if it has something to do with your last modifications though switching off/on data/synchronisation etc... is just taking a second now, where it was a few seconds before. The same when switching from Wifi to mobile data.
[Motorola Moto G100 / Edge S] Byscu:
I met a freeze again. And here is the logs.

I've already unmounted the thanox module,

and I will uninstall lawnchair&quickswitch to see will the situation be better.
[Motorola Moto G100 / Edge S] Human_0824:
When I pressed the power button to turn on the screen after I hadn't lit it up for a long time, the screen didn't light up. It should have been frozen, and this is the log after restarting. It has been running for at least 48 hours without freezing before this.

News:

After experiencing the first freeze last night, the second one happened now. It happened when I turned on the screen and activated the flashlight from the dropdown menu when I still had 1% battery. Unfortunately, although I copied the log file to /sdcard after restarting and saw its contents through the file browser, my phone suddenly shut down when I was about to upload. When I restarted, the log file miraculously disappeared on its own.
[Motorola Moto G100 / Edge S] Stanzer:
Hi folks,

I really would like to help (and enjoy a phone without freezes) so I tried to install the latest build lineage-21.0-20240220-UNOFFICIAL-nio.zip. I'm already running lineage-21.0-20240217-nightly-nio-signed.zip.

But when using

adb -d reboot sideload
adb -d sideload lineage-21.0-20240220-UNOFFICIAL-nio.zip

I get this:

serving: 'lineage-21.0-20240220-UNOFFICIAL-nio.zip' (~0%) adb: failed to read command: Success

So I tried the push_update.sh script:

./push-update.sh lineage-21.0-20240220-UNOFFICIAL-nio.zip
adbd is already running as root
lineage-21.0-20240220-UNOFFICIAL-nio.zip: 1 file pushed, 0 skipped. 36.2 MB/s (365965312 bytes in 9.639s)
Error: unable to open database "/data/data/org.lineageos.updater/databases/updates.db": unable to open database file
restarting adbd as non root

What did I forget? How to install this build?

Thanks in advance.
[Motorola Moto G100 / Edge S] Human_0824:
After experiencing the previous freeze for a few hours, I encountered it again. This freeze occurred when I tried to swipe and unlock the screen while it was lit up. I noticed that during this freeze, the SIM card position in the upper right corner displayed "No service".
[Motorola Moto G100 / Edge S] IntinteDAO:
@Deivid Soltoski @dianlujitao Desktop Mode on LineageOS 21 works great :) I mean not maybe like Motorola's, but there is no notch, so you can play games and normal apps
[Motorola Moto G100 / Edge S] HandyE:
Same here...

Before December and with Lineage 20 no crashes or freezes at all. After December phone crashed once or twice a week.

Since Lineage 20.0-20240212 at least one crash or freeze every day.

My hope was Lineage 21. I installed it last Saturday. Since then, there have been five crashes/freezes to date, including two today.
[Motorola Moto G100 / Edge S] Human_0824:
It is highly likely that the problem is caused by the replacement of the kernel and other source code. At least in December 2023, the kernel version of lineage 20 is 4.19.157, but the current kernel version of lineage 21 is 4.19.306. I suspect that similar modifications were made to lineage 20 in January. I haven't encountered any bugs on the lineage 20 of the 157 kernel, but currently it can be said that it frequently freezes.
[Motorola Moto G100 / Edge S] Byscu:
Since lawnchair & quickswitch were uninstalled, I haven't met a freeze crash again👍.
[Motorola Moto G100 / Edge S] dianlujitao:
The 0227 build integrates another potential fix for the freeze issue (the fix in 0220 has been proven ineffective)
[Motorola Moto G100 / Edge S] Moto-J:
Where can we find the code of the potential fixes @dianlujitao ?

I can't find them in github or code review LOS?
[Motorola Moto G100 / Edge S] dianlujitao:
not pushed yet
[Motorola Moto G100 / Edge S] Moto-J:
@dianlujitao, just had a freeze, though adb shell ls /sys/fs/pstore/ with adb root enabled in dev.settings gave nothing after long pressing the on/off button and reboot.

So seems not solved, though can not give you any logs (latest 240227 build).
[Motorola Moto G100 / Edge S] Moto-J:
And to be more specific;

I could unlock the screen, then tried to open K9, though only opened and freezed screen.

I could swipe it to top to close, though starting again gave only the K9 logo, nothing more.

Screen freezed and reboot was the only way.

Was after about 17 hours of running stable.

Update 03:38;

After situation above I tried to open K9 again and again a screen freeze and so a reboot to solve.

After reboot everything okay again, though again no logs.

Though... wat may be can help/ point into the right direction;

I am in another country then normal again after travelling with car. Where I normally have no issues with crossing the border, it took I think about 15-30 mins to get a data connection again and I had to set APN entrypoints to default for that. More then once at home I also had to enable wifi first to get my data connection back with all builds starting from januar 2024.

Another thing about the APN entry points; I am on KPN (Dutch), though default it is always taking Ortel (the fourth in the list) now. Data is working with that, though I can set it to the first entrypoint (KPN 4G LTE) by hand also and is also working.
[Motorola Moto G100 / Edge S] dianlujitao:
Thanks for the report.
[Motorola Moto G100 / Edge S] erimah64:
@dianlujitao Have you seen ticket https://gitlab.com/LineageOS/issues/android/-/issues/6694 on Gitlab? Other (Motorola?) devices also appear to be affected. The same ticket was also available for LOS20.
[Motorola Moto G100 / Edge S] Human_0824:
I may have some insight into the freezing issue. I noticed that since mid December last year, Los 20 has updated some things including blobs, and since then, some people have reported freezing issues in Los 20. And Los21 seems to be using these updated things as well. After the official Android 12 (baseband version 9x and above), it seems that people have not encountered the issue of system firmware getting stuck, while the firmware will encounter it in the official Android 11 (baseband version 9x and below). I myself am the official firmware for Android 11. After pulling the Los20 source code, I replaced the source code in device, kernel, system/qcom, hardware/motorola with one before December 2023. The compiled firmware did not encounter any further lag issues. If this conjecture can be confirmed, it proves that the update violates support for Android 11 firmware and must be updated to Android 12 firmware in order to use it.
[Motorola Moto G100 / Edge S] ew:
I (thankfully) have not been having the freezing issues - none since upgrading to LOS21. I may have had a few in the last few weeks before my upgrade (1-2/week during January) but nothing major.

I hope that those that are encountering the issue can find a quick solution. If there is any helpful information that I can provide, I will be happy to do so.
[Motorola Moto G100 / Edge S] patwwh:
Hi @dianlujitao , since more and more phone like this don't allow downgrading ROM (stock and LOS), but allow flashed with the same minor version. Therefore, in this new LOS 21, may I suggest to store the minor version number in an unofficial place, and let the original official place to store the same minor version always, in order to cheat the above mechanism.
[Motorola Moto G100 / Edge S] Moto-J:
@Human_0824 or @dianlujitao, would it be possible to share the latest LOS21 based on downgraded firmware as Human_0824 is using now if I understand it right?

I think this would be a good option to test for further builds as the Nio builds are temporarely stopped: https://review.lineageos.org/c/LineageOS/lineage_wiki/+/384193.
[Motorola Moto G100 / Edge S] Moto-J:
I know this is may be not the place to report bugs, though I do not have an account at github or other platforms; the reason I do it here.

Although positioning of the statusbar icon's is aligned in one of the "bugfixes" in the last weeks, I noticed the alignment is not updated when you are changing screen resolution. You have to restart the phone to get them aligned again at the new resoltion (for example change in dev. settings from default 360px to 350 or 340).

When I enable Bluetooth and my phone is connected to the BT of my car, the statusbar BT icon seems messed up? I have added 3 screenshots; nr. 1 BT disabled, nr. 2 BT enabled with taskbar pull down, nr. 3 BT enabled with taskbar and the BT "dot". Is this normal behaviour??
[Motorola Moto G100 / Edge S] Human_0824:
(It seems that the translator is not good at batch translation 😶) I have currently compiled firmware based on the latest lineage 20 source code (in addition to the kernel, devices, etc. I mentioned earlier).

I have been running continuously for 48 hours and have not encountered any problems, just like the lineage 20 before December 2023.

If my hypothesis holds, then it is also easy to compile lineage 21 that won't get stuck. (You can check the baseband version in your phone settings to determine if you are the official Android 11 underlying firmware.)

I would be happy to share the latest lineage 20 source code compilation that I am currently using (with kernel, device, system/qcom, and hardware/motorola based on the December 2023 source code). Its current Android security update is February 2024. But I made some modifications to adapt to it, including but not limited to kernelsu, disabling full disk encryption, disguised as the user version, kernel support for Docker, and so on. If you want to use it, you may have to format the data.

I am also willing to use a similar method to compile a lineage 21 that may solve the problem of lag.

Unfortunately, I used a private server to compile the source code. Currently, I have unpacked and boxed it for relocation together. Its earliest re online date was March 5th. At that time, if needed, I would be happy to help.
[Motorola Moto G100 / Edge S] Moto-J:
Hi @Human_0824 , thanks for the response.

I hope your explanation can help for example @dianlujitao to come to a solution for the officials, but based on all modifications you did it and the extra work of fresh install etc.., your build is not a build I can test for now as I simply do not have the spare time. Good luck with the relocation btw!
[Motorola Moto G100 / Edge S] dianlujitao:
disallow major system downgrade (e.g. from android 14 to 13) is the result of app database and/or disk encryption algorithm update, which is impossible to undo. there is not a mechanism to trivially check and reject older system version number as you thought of.
[Motorola Moto G100 / Edge S] dianlujitao:
downgrading everything isn't the right approach to take. we need to find the minimal breaking change and fix or revert it.
[Motorola Moto G100 / Edge S] dianlujitao:
@Moto-J @Human_0824 what are your baseband versions?
[Motorola Moto G100 / Edge S] Moto-J:
@dianlujitao

M55_HI20_209.334.01.99R

Edit:

Just updated to latest firmware from CN version:

M55_HI20_209.334.01.101R

As I am using my phone continously coming weekend, I will let you know the results based on latest CN firmware.
[Motorola Moto G100 / Edge S] Human_0824:
M55_HI20_209.334.01.86R

I have not upgraded to the official Android 12 because the underlying firmware cannot be downgraded.

I crossed nearly a thousand kilometers using the firmware I compiled today with data traffic enabled, but there was no signal freeze. But it seems that his baseband version is the official Android 12. It seems that my hypothesis has been refuted.

If you know how to quickly trigger a freeze(modem crash?), I may be able to provide some help.
[Motorola Moto G100 / Edge S] dianlujitao:
idk, I experienced the crash only once or twice a week

my baseband is M55_HI20_209.334.01.97R, which is even older than @Moto-J
[Motorola Moto G100 / Edge S] HandyE:
I am also on M55_HI20_209.334.01.99R and having a lot of crashes, sometimes multiple crashes a day.

Where to get 101R? Hope this version helps, because phone is sometimes unusable atm.
[Motorola Moto G100 / Edge S] Human_0824:
because of I have noticed that some people on the Moto Edge S section of "酷安" claim not to have encountered a crash, and one of them shows that their baseband version is 101R and system version is 0217.
[Motorola Moto G100 / Edge S] Moto-J:
Please be careful and no guarantees... ;-)

You can take the latest CN firmware from here:

https://mirrors.lolinet.com/firmware/lenomola/nio_retcn/official/RETCN/

And then update using these commands in fastboot:

fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot erase carrier
fastboot erase ddr
fastboot reboot

This is the way I did it today and before with previous firmware updates without any issues.

After flashing and booting up, you have to reboot once again and after that everything should work again (mobile connection, data etc..).
[Motorola Moto G100 / Edge S] ew:
I am on 99 and not experiencing crashes. Maybe it is something else.
[Motorola Moto G100 / Edge S] HandyE:
Thanks a lot. Mine is RETEU. Don't know if it's a good idea to mix that with China Retailer??

I see that @ew is on 99R, too, without having any problems. So it seems that it's not the baseband causing the problems? I think I will wait a bit for now before upgrading baseband ;-)

But, please report back if your crashes/freezes are fixed with 101R.
[Motorola Moto G100 / Edge S] Moto-J:
Mine is also RETEU and am running the CN firmware 101R now without any issues. 5G and Wifi working, all network types available, bluetooth working fine... so till now fully stable, up and running.

If freezes/ crashes are solved by upgrading.... in a few days we will know.

And to be honoust; upgrading the firmware is that easy that I see no reason not to do it when the phone is running fine with it. But give it some time... ;-)

@Human_0824; what about system version? Baseband version I know, though what do you mean by system version related to LOS in this case?
[Motorola Moto G100 / Edge S] Human_0824:
There is a Lineageos version on the same level page as the baseband version.

It is usually a string like "21-20240217-NIGHTLY nio". What I mean by "0217" is the firmware date after "2024".

But I don't think you need to worry about this, because his version seems to have been downloaded from the official website and does not include frozen patches.
[Motorola Moto G100 / Edge S] tmpusr1:
Freeze again on 0227 build.
[Motorola Moto G100 / Edge S] patwwh:
@dianlujitao , I was talking about downgrading to minor version, not major version.
[Motorola Moto G100 / Edge S] dianlujitao:
I guess you can downgrade via adb sideload in recovery, no?
[Motorola Moto G100 / Edge S] dianlujitao:
one thing worth trying is clearing the modem cache: run "fastboot erase" commands in @Moto-J 's post
[Motorola Moto G100 / Edge S] HandyE:
Thanks again! Did that some minutes ago. I will report back if this does any better.
[Motorola Moto G100 / Edge S] Moto-J:
Stable for 24 hours now with travelling, bluetooth, wifi and 5G usage, as sleeping overnight with updated firmware and clearing the modem caches. Using the latest LOS nightly official from Feb.26th. (21-20240226-NIGHTLY-nio).

EDIT 03-03-24:

Overnight after about 30hours unfortunately also this config freezed. So also firmware update and clearing cache is not the solution.
[Motorola Moto G100 / Edge S] patwwh:
@dianlujitao , unfortunately, NO! (I am using LOS' Official Version)
[Motorola Moto G100 / Edge S] :
Hi,

Installation guide is incomplete, command:

fastboot devices

emits no output

what other driver to try on windows 10?
[Motorola Moto G100 / Edge S] :
Ok, I now managed to Install LineageOS 21 but Google Play Store is missing. How am I supposed to install Apps now?
[Motorola Moto G100 / Edge S] IntinteDAO:
Install Google Apps

Google apps | LineageOS Wiki

wiki.lineageos.org

If you want to be more open source, you can install F-Droid store
[Motorola Moto G100 / Edge S] tmpusr1:
Freeze again.

ps: my device with latest china firmware 101R since lineageos 20.
[Motorola Moto G100 / Edge S] dianlujitao:
modem crash this time, same as other users
[Motorola Moto G100 / Edge S] dianlujitao:
The 0303 build reverted some major kernel changes, please test if it helps.
[Motorola Moto G100 / Edge S] Moto-J:
Just downloaded and installed your 0303 build.

Fingers crossed ;-)
[Motorola Moto G100 / Edge S] :
Guys, has 5G started working after installing LineageOS 21? Was it really like for Google Pixel phones when Google blocked 5G service for phone models for countries they don't sell them in? Now prefered network type list is the same cryptic as in secret menu *#*#4636#*#*
[Motorola Moto G100 / Edge S] Moto-J:
5G worked on my Nio with LOS 20 and 21.

VoLTE can be enabled with a simple build.prop change in previous builds, though is enabled also in the latest builds, so I don't see any issue to use 5G/VoLTE with LOS.
[Motorola Moto G100 / Edge S] :
OK. It's interesting if 5G worked with original Motorola ROM? Some users claim 5G option disappeared from Prefered Network Type list after Motorola Android 12 update.

Also I just noticed that LineageOS 21 ROM is buggy:

Tried to wake phone up then suddenly it stopped responding to touch and power button presses, then restarted itself. On the freezed screen saw No service No SIM card messages but it does have a SIM card inside.
[Motorola Moto G100 / Edge S] :
I can confirm, this ROM is unusable, the No Service and freezing+restart bug happened again.

How do I restore everything that was changed? Motorola original ROM and bootloader?
[Motorola Moto G100 / Edge S] Moto-J:
@dianlujitao, seems promising, after 35 hours still no crashes.

I would recommend others to test the 0303 test build from Dianlujitao also to be sure ;)

EDIT 06/03/24:

Till now (45hrs+) no crashes.

Just curious if other users do have issues, as for me it seems that this build is solving the freezes/ crashes?
[Motorola Moto G100 / Edge S] Smaehtin:
Just crashed/froze here on the 20240304 build.
[Motorola Moto G100 / Edge S] :
/*

* Your warranty is now void.

*

* We are not responsible for bricked devices, dead SD cards,

* thermonuclear war, or you getting fired because the alarm app failed. Please

* do some research if you have any concerns about features included in this ROM

* before flashing it! YOU are choosing to make these modifications, and if

* you point the finger at us for messing up your device, we will laugh at you.

*

*/

They are laughing at us now.
[Motorola Moto G100 / Edge S] Moto-J:
@dianlujitao , one thing I notice with the latest build is that my mobile data is not coming up anymore after switching this off and on with profiles, something which seemed to be solved in the previous build(s).

I have to go to the SIM card settings and change the preferred network type once, or I have to enable and connect to my WiFi and switch it off again, then is my 4G/5G connection coming up immediately.

This is a behaviour I noticed somewhere between dec. and later builds, though can not fingerpoint the exact moment anymore.

Further build is still up and running!
[Motorola Moto G100 / Edge S] Moto-J:
Did you already test the unofficial build from 03-03 in the first post?

This one is not freezing/ crashing for me till now, so you can may be help Dianlujitao to find the issue... ;-)

The more testers the better.
[Motorola Moto G100 / Edge S] Smaehtin:
Ah, my bad, didn't realize it was a different build!
[Motorola Moto G100 / Edge S] :
Hotspot app stopped responding, when turned it on, no Internet connection. Restart impossible. Just keep laughing at us.