[Advanced Users Only][Teracube 2e 2nd Batch (SN: 2021)] LineageOS 18.1 Beta [emerald]

Teracube 2e
#101

Hi Gagan,

Just an update I have now lost the ability to text and noticed my APN list is lost. Taking a closer look I then located the apns-conf.xml file and it look as though it is at 0 byte. Upon resetting to default from the GUI under the mobile settings it is unable to generate from the sim card the APN needed to send text and mms messages Nor can i edit and enter the APNS manually.I suspect this is due to the partition being locked because as you stated earlier I cannot edit the APN file manually to restore my service. I highly suggest that the root partition is the have some available storage or write access to be edited to avoid scenarioā€™s such as this because with the amount of apps I have it takes me about an hour to be up and running now that it looks as though i will have to reinstall the OS.

Edit: was able to get sms back by calling rogers to reset my line not sure how this happened but for the meantime i will be using my lg v20 until i get another sim card and line to test this device.

#102

Hi, how far is that release? I suffer from missing NFC too and other stuff. Would really like to see an update :slight_smile:

#103

Iā€™m sorry to have delayed it so long. Have been busy with other priorities, such as improving performance on both variants, and such. Iā€™ll release it by end of next week, positively.

#104

June update:

Changelog:

Update package: Google Drive - Virus scan warning

Has to be flashed using fastboot update <packagename>
OTA flashing support is being worked on.

For more technical information regarding fastboot updates, please view my blog post here.

#105

malvi.ml does not exists - are you sure you write a blog there? :wink:

#106

I had changed domains.
Post has been changed accordingly.

1 Like
#107

anybody who has used lineage can confirm if they have volte working and no fall back to 3g? what services are you using?

#108

Development has moved on to Android 12.1 and commonizing both the 2020 and 2021 variants of the Teracube 2e. Iā€™ll be letting you know positively of any improvements.

As for TWRP, it is not possible to have it on the 2021 variant of the Teracube 2e because the recovery now resides in the boot partition and the boot partition is overwritten every update for kernel updates. It doesnā€™t really make sense to maintain TWRP for something that is anyways going to be overwritten and it also breaks OTA upgrades on the 2020 unit as well.

#109

PXL_20220714_095133229
PXL_20220714_0951332291920Ɨ2557 230 KB

Teracube 2e 2021 (emerald)

1 Like
#110

Does this mean LineageOS 18.1 for the 2e can be considered stable? If so, great news!

A potentially dumb question, as I have good familiarity with TWRP and flashing LineageOSā€™ official zip archives, but none with SP Flash and fastboot updates. Are the updates cumulative, i.e. do I just need to flash the base image via your instructions at the start of this thread, then flash the June fastboot update and Iā€™m good to go?

Thanks for all your hard work. Iā€™m very excited to run Lineage on my 2e.

#111

You can directly flash the fastboot update. It will flash all the necessary partitions needed for Lineage.

#112

i understood the instructions to issue:

$ fastboot update lineage_emerald-img-eng.gagan.zip 
--------------------------------------------
Bootloader Version...: unknown
Baseband Version.....: 
Serial Number........: 202111T2E001822
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 FAILED

Device product is 'emerald'.
Update requires 'yk673v6_lwg62_64'.

fastboot: error: requirements not met!

but that did not work. what did i do wrong?

#113

@mdt: Check your version of fastboot and adb using ā€˜fastboot --versionā€™ (and ā€˜adb versionā€™). Gagan was able to diagnose that I had an old version.

Installing fastboot/adb with ā€˜sudo apt installā€™ puts an old version on my system. Download it from android . com, (then add PATH to bashrc).

I saw the particular error youā€™re getting when I started the process from the phoneā€™s fastbootd screen (it looks like a recovery screen) instead of fastboot. Starting the process from the fastboot screen gave me a ā€œFAILED (remote: This partition doesnā€™t exist)ā€ since I had an old version installed. Updating to latest fastboot and starting the process from fastboot, and not fastbootd, should work.

Hope that helped.

#114

oh, ok, there are two fastboot modes! the other works just fine. adb reboot fastboot reboots to the wrong one - weird. but during flashing it reboots to that mode againā€¦

so now the long process went through and reports OKAY (only some ā€œarchive does not contain ā€¦ā€).

after reboot i do not have a new system - it is still android 11. hm, whatā€™s wrong?

btw: funny thing: rebooting does not reset the modem. i do not have to re-enter the pin. it that intended?

and: if you would move the boot splash screen a bit to the top it would look much nicer because the text doesnt destroy the image.

#115

All the builds linked in this thread are LOS 18.1, which is Android 11. The update package should have a more recent Security level (Click on ā€˜About phoneā€™ - Android version - Android security update).

Gagan just posted a picture with LOS 19.1 on Android 12.1, not the build. You can ask him if he has a 19.1 build you can use. Maybe he will start an LOS 19.1 thread at some point (for both T2e).

I donā€™t know about the modem and pin.

#116

with the june update i cannot issue phone calls anymore. i can take calls but not initiate calls.

the dialer app stays in the state ā€œinitiating callā€ (dont know if that is the coreect translation back) for ever it seems to be crashed. i cannot end the app, for some time the status icon for ongoing call is shown but no more. any idea whats wrong?

and here the fact that the modem is not completly reset during reboot or switch off/on (noticable because the PIN has not to be entered) hurts because the dialer app notices that the modem is still in a strange state and you canā€™t even start a call.

#117

And in the app-switcher the icon and preview of the app is gone as wellā€¦

Can someone confirm this behaviour or is it a problem only here?

#118

I had no trouble with the June update at all. Sorry to hear about yours.

#119

can you check if you need to enter the pin if you reboot the phone (by software, not by removing the battery)?

it seems that the modem kind of crashes here due to bad reception if i initiate a call. because it is not completly reset on reboot i need to remove the battery to completly restart the phone including the modem.

the other effect (no icons/preview of app in chooser) disapeared later that dayā€¦

#120

@mdt - I just completed a software reboot. Once it booted, it showed the
lock-screen, where I was able to enter my pin/password to log in. I then
called my voicemail to confirm that calling works. No problems observed.