Thank you for your time and patience Gagan for the TWRP I will also provide a logcat also. I will attempt to try the phone out tomorrow with all my mods and see how it fares. I also noticed i couldn’t play with the frequencies or turn off cores with the kernel manager but i guess that is to be expected with stock kernel.
1 Like
Good morning Gagan,
I have just inserted my sim card and micro sd which was detected and decided i was going to place a call to verify VOLTE in LOS 18 works and upon calling my voicemail it has fallback to 3g throught the call did i miss a setting? (Bands on the rogers network are compatible) is this a known issue being ironed out?
Uhm, that is not intended behaviour. Can you try setting it to LTE only?
→ Go to Phone, type in ##4636##
→ Select Phone Information
→ Set preferred network type to LTE only
→ Additionally, press the three dots at the top and check IMS service status
→ It should say Voice Over LTE: Enabled
→ If it is disabled, please try Googling for your APN, it usually is the issue with Lineage builds since LineageOS ships with a few older APNs.
The ##4636## does not work for lineageos i think stock only. Also here is a screenshot displaying it is set in settings to lte and volte but i am still experiencing no volte. I remember looking over my apn this morning and it looked fine however i will look it over again.
That’s really weird… I’ll have a look, will ship updated APNs with the newer build pretty soon, till then please try the APN thing.
On another note, do you want a Google apps build too?
- Yes
- No
0 voters
I decided to go back to stock and try to see if volte was working only to find that on stock it does go to 3g upon calling and receiving calls APN matches with what is online but i cannot edit it for some reason. Anything you can suggest i try to get volte working? Edit: ##4636## comes back with error connection problem or invalid MMI code. I can confirm Volte works on Stock rom h915 on my lg v20.
I tried following the rooting instructions like i have for lineage for stock rom and I keep getting the error upon using fastboot flash recovery
Writing ‘recovery’ FAILED (remote: ‘This partition doesn’t exist’)
fastboot: error: Command failed
any idea why it cannot find the partition? I used the right boot from the stock image not lineage.
The recovery partition does not exist on emerald, since the partitioning of the device is A/B instead of the regular A on zirconia.
Neither Lineage, nor stock ROM have that partition, you might have downloaded the wrong package.
Hi Gagan, for the stock image the boot file was what I have extracted from the Emerald stock image file. After careful consideration I might just go with the teracube one due to software maturation. How would I go about returning the 2 devices and prepare to order the teracube one?
Guess I didn’t consider the teracube 1 to be not in stock I will continue to tinker with this model in the coming days.
(asterisk)(hash)(asterisk)(hash)4636(hash)(asterisk)(hash)(asterisk)
*#*#4636#*#*
I just realized the community portal uses * for bold.
1 Like
I’ll be unifying everything under a new ROM specific to Teracubes only very soon, so I don’t think it’ll be much of an issue 
1 Like
I just tried it but nothing comes up I suspect the phone might not be provisioned so I will call my phone provider and get back to you with the results. *Edit: seems android 11 is not liked by most of my apps however it works well under lineage 17 (upgraded from 16) when tested under my old lg v20 would it be asking alot to have 1 build to see how well it would play out? If it is alot of work don’t bother just frustrated with the incompatibility I am faced with. Apps: root call sms manger, having magisk call recorder write directly to SD card not possible. 2nd Edit: just noticed th first batch has a lineage 17 build can it easily be placed on emerald somehow?
Android 11 has set a few restrictions in place in order to improve security and overall UX, which neither we nor LineageOS have control over. We can revert those changes, but it will only cost us time and will reduce user security which we do not prefer.
As for your question regarding Lineage 17.1 on the newer units, I’m sorry to say it is not possible due to a newer partition layout and bootloader firmware. It will result in a brick which might be irrecoverable.
1 Like
Thank you Gagan,
I will continue to tinker and await the lineage 18 you will be releasing later this month with upcoming fixes such as double tap to wake and Google apps added to lineage 18 ^-^.
So I just tried the phone out all day and here is what I found out when compared with my lg v20 which also uses lineage.
MMS does not work at all on the teracube 2e emerald with lineage 18.
NFC is absent
All call recording apps do not work with this phone just user side is present.
Root call sms worked once then upon reboot stop working tried using edxposed, lsposed with Riru and zygist mode with no success and many trial and error.
Star number Star number 4636 LTE only works but when calling I loose connection completely
On the bright side the phone doesn’t overheat like my lg v20.
MMS is something I have never used nor tested, so I’ll have to check it up once.
NFC does work fine here though?
As for VoLTE, @jbray had an issue on Cricket that was similar to yours, but it was a carrier side issue.
Can you recheck APNs and try another SIM card in the 2e to test if calls go via 4G?