[Moto G 2014 LTE Android Development] Rox5:
[MENTION=9806267]Numberone2022[/MENTION]

You should may be not quote every single message you answer, including even the complete home page of this thread.

Just quote, only if necessary, what you want to answer, it will make the thread more comfortable to read.

Now just "waiting" will not make things happen: this is apparently what has been done since about May 2018, without success.

A bug has been introduced in 15.1 [device_thea + device_motorola_msm8226-common + kernel_motorola_msm8226] repositories which prevents making usable builds since about April 2018 (1 year ago).

It can be a simple mistake made by someone who did not verify/check his modification.

Or, it can be intentional to block 15.1 branch, and now force users to debug 16.0 branch, but this needs to be clarified.

16.0 can only be debugged by titan users for the moment.

I have investigated a bit deeper, and the root cause is may be not the RIL, but the library in charge of SIM detection.

When a SIM is inserted, a signal is sent to start com.android.stk (Stk.apk) which is the SIM toolbox which role is to read the content of the SIM, learn about the mobile operator (MCC/MNC) to automatically setup the right APN.

Inserting a SIM card has absolutely no effect on current 15.1 builds (verified in logcat).

I then wonder if the first "vendor image mismatch" message that I firstly estimated a secondary issue, is not a key one, thinking that if a vendor mismatch is detected, the access to vendor firmware is locked, and then.... nothing can happen.

I've made a build by forcing the requested build name in 'device/motorola/thea/init/init_thea.cpp' file, to avoid a ro.bootimage.build.fingerprint, ro.build.fingerprint, ro.vendor.build.fingerprint parameters mismatch, but got another vendor image mismatch.

Then just making builds again and again and applying "security patches" on non-working builds is close to useless, and is (a little bit more) heating the planet.

What should be done is to analyze what has been modified in the source code around April 2018 which has not been checked, and then blocking the 15.1 branch.

To do that, people who have a write access to the source code should be better identified to understand the root cause of this bug, and people who made the latest 15.1 builds for thea may have the history in mind.

[MENTION=5895297]gothicVI[/MENTION]

Do you have this history in mind since April/May 2018 ?

To solve your SIM card format problem which prevents you testing your builds, some mobile operators provide pre-cutted multi-format SIM, and I have no problem to move my SIM card from a MOTO G to an Archos with a different SIM format (all the SIM cards I have are triple format).

This will save you time to test your builds, the RIL part being an absolute key issue, much more important than having all MMI languages available, or the right icons with the right color.

Just pushing builds without any basic minimum test, and waiting for feedback you don't consider to update your home page is hard to understand.

Just 'repo sync && brunch thea' will not make things happen.

Video crashing issue is a minor one (and understood), and I have identified at least two Camera apps fully compliant with HAL1 => no video crashing.

The priority is SIM detection process (RIL is may be fine..... / we don't know yet because cannot be tested without SIM detected !).

The mobile icon in the status bar is not the one which informs a network connection problem, but a slashed SIM icon informing that NO SIM card has been introduced/detected.

=>>> SIM card detection, vendor image mismatch, and nothing else... for the moment.

------------------------------

EDIT: + investigation of Enable persist.radio.no_wait_for_card to make RIL not wait for card by adding "persist.radio.no_wait_for_card=1" to /system/build.prop

=>> no effect =>> still no SIM card detected.