[ROM][10.0][UNOFFICIAL] LineageOS 17.1 for Unihertz Atom L and XL [Alpha] [2022-04-21]

Should the OTA update feature be enabled in the next build?

  • Yes, I'll overlook the montly updates otherwise.

    Votes: 1 100.0%
  • No, I don't have enough mobile data for a montly update cycle.

    Votes: 0 0.0%

  • Total voters
    1
  • Poll closed .
Search This thread

a-dead-trousers

Senior Member
Jul 28, 2016
404
1
177
Samsung Galaxy S5 Mini
It still thinks it is 170 when it's supposed to have changed to 410. It's just still using the data from the original APN entry rather than the new one, and I don't know where else it's getting that from.
It's getting theese infos from the sim card. apns-conf.xml is then used to determine the additional settings. But there is also a signed app that interacts with the sim card in a certain way which produces alternative values and that's what prevents it_unihertz_when_i_pee's phone from working correctly. Sadly I don't know how to fix this cause I don't know an operator with this kind of "registration" in my area to be able to run some tests and figuring this **** out.
 

SepticFuddy

Member
Oct 3, 2019
33
3
It's getting theese infos from the sim card. apns-conf.xml is then used to determine the additional settings. But there is also a signed app that interacts with the sim card in a certain way which produces alternative values and that's what prevents it_unihertz_when_i_pee's phone from working correctly. Sadly I don't know how to fix this cause I don't know an operator with this kind of "registration" in my area to be able to run some tests and figuring this **** out.
Seems like my best bet then is to try rebooting next time I'm in town, and if that doesn't work maybe ask them for a new SIM. Not sure if they'll have any because the VOIP-only service is sort of a legacy product, but also possibly the only reason it works where I live. I'll update if I learn anything else
 

SepticFuddy

Member
Oct 3, 2019
33
3

a-dead-trousers

Senior Member
Jul 28, 2016
404
1
177
Samsung Galaxy S5 Mini
Same result. Rebooting in town didn't work either. I guess I should note I have not been wiping anything during installation to avoid the pain of the restore process. I figured a changed system file should do the trick on its own, but is it possible I need to be wiping something to make this work?
Nope, normally no wipe is needed.
So, you're saying that there is no ERESELLER entry in the APN List?
 

SepticFuddy

Member
Oct 3, 2019
33
3
Nope, normally no wipe is needed.
So, you're saying that there is no ERESELLER entry in the APN List?
Nope. This is what I've got. Pretty sure one or two of those weren't there before the first custom build but I don't remember which.
 

Attachments

  • image_2022-04-04_093159.png
    image_2022-04-04_093159.png
    57.5 KB · Views: 11

SepticFuddy

Member
Oct 3, 2019
33
3
@SepticFuddy
Another day, another test build
https://github.com/ADeadTrousers/an...04-UNOFFICIAL-Atom_XL_TEE-signed-apn_test.zip
In this one I fixed the ordering of my "stock apn overwrite" feature. Apparently it was overwriting my overwrites with stock entries and not the other way round :poop:
This should also slightly reduce the amount of entries.
Progress! All the settings have updated to the ERESELLER entry, except the MNC is still 170 instead of 410, so now I can't connect to LTE. I think fixing that should solve the problem
 

a-dead-trousers

Senior Member
Jul 28, 2016
404
1
177
Samsung Galaxy S5 Mini
Progress! All the settings have updated to the ERESELLER entry, except the MNC is still 170 instead of 410, so now I can't connect to LTE. I think fixing that should solve the problem
And that's what I don't know how to do. See problem of it_unihertz_when_i_pee. The 170 is from the sim/carrier and can't be changed (or at least shouldn't be needed to be changed)
 

talmid01

New member
Nov 19, 2021
4
0
I following the guide, but I'm not able to flash the recovery. I tried different versions of it from other threads. Every time I try to get into the recovery I get a chinese menu, not the TWRP one. I know that going to Android will overwrite the recovery, but doesn't matter how I try it doesn't get into the TWRP. The command "fastboot boot recovery.img" fails.

I was also doing research if there is a Treble Vanilla version, that is easy to flash from fastboot, but doesn't look like there is one developed.

Any ideas how to continue on installing Lineage on this?
 

SepticFuddy

Member
Oct 3, 2019
33
3
I following the guide, but I'm not able to flash the recovery. I tried different versions of it from other threads. Every time I try to get into the recovery I get a chinese menu, not the TWRP one. I know that going to Android will overwrite the recovery, but doesn't matter how I try it doesn't get into the TWRP. The command "fastboot boot recovery.img" fails.

I was also doing research if there is a Treble Vanilla version, that is easy to flash from fastboot, but doesn't look like there is one developed.

Any ideas how to continue on installing Lineage on this?
Sounds to me like you are holding volume down instead of volume up. I did the same thing at one point without realizing, bringing me to the Chinese menu instead of TWRP
 

dr-dude

Member
May 18, 2022
7
0
Sorry to be 'that guy', but any assistance? I'm DESPERATELY trying to get lineage running on my Atom L and have run into yet another wall.
Anybody know why TWRP keeps "failing to mount 'system_root' (permission denied)" and ends updater process ERROR: 7?

Unihertz stock rom dated: 202105
unlocked boot loader
magisk and rooted image (magisk says root is good)
I can recover into TWRP 3.5.2_10-0
Trying either as ADB sideload or install from SD card gives the ERROR 7 message (see attached screen shot)
I've even gone so far as to use a text editor to remove the first few lines of text in the 'updater script', but that doesn't seem to make a difference

Again, sorry to be an idiot. I'm sure it's something super easy that I'm screwing up
BTW HUGE THANKS to @ADeadTrousers for boss level work on this project

THANKS!!
 

Attachments

  • IMG_20220517_215308611_HDR.jpg
    IMG_20220517_215308611_HDR.jpg
    1.6 MB · Views: 14

a-dead-trousers

Senior Member
Jul 28, 2016
404
1
177
Samsung Galaxy S5 Mini
Anybody know why TWRP keeps "failing to mount 'system_root' (permission denied)" and ends updater process ERROR: 7?
Unihertz stock rom dated: 202105
unlocked boot loader
magisk and rooted image (magisk says root is good)
I can recover into TWRP 3.5.2_10-0
Trying either as ADB sideload or install from SD card gives the ERROR 7 message (see attached screen shot)
I've even gone so far as to use a text editor to remove the first few lines of text in the 'updater script', but that doesn't seem to make a difference
The "system_root" error can be ignored. Some parts need it but others complain about it, I don't know why.
The "Error 7" (updating_dynamic_partition) and what to do is described in the install guide under "Troubleshooting".
 

dr-dude

Member
May 18, 2022
7
0
The "system_root" error can be ignored. Some parts need it but others complain about it, I don't know why.
The "Error 7" (updating_dynamic_partition) and what to do is described in the install guide under "Troubleshooting".
HA! This is a great reminder about the quote, 'when all else fails - read the instructions'

I'm on it. Thanks again!!!!
 

dr-dude

Member
May 18, 2022
7
0
I'm now sooooo excited to be up and running on lineage with my Atom L. Thanks!
By chance, has anyone got Google Fi running? I'd previously read that it also needs 'carrier services' and 'google connective services', so i installed them. I've also allowed all service permissions for both apps and google fi.
When i try to credential phone with a fi SIM, i get error B042. Anybody else run into this? Any recommendations?
Thanks again!
 

dr-dude

Member
May 18, 2022
7
0
Yet another noob question. Sorry. I'm successfully up and running 17.1-20220421 But ...

Having difficulty getting my virtual network operator SIM to function. I can't seem to find the configuration section of the settings. Any help? Where I usually look (network & internet / mobile network / advanced setting) doesn't have the usual spot to config the APN. The only option there is "carrier video calling". When i search for "APN" in settings, nuthin comes up.

Help, as always, is very much appreciated.
 

a-dead-trousers

Senior Member
Jul 28, 2016
404
1
177
Samsung Galaxy S5 Mini
Yet another noob question. Sorry. I'm successfully up and running 17.1-20220421 But ...

Having difficulty getting my virtual network operator SIM to function. I can't seem to find the configuration section of the settings. Any help? Where I usually look (network & internet / mobile network / advanced setting) doesn't have the usual spot to config the APN. The only option there is "carrier video calling". When i search for "APN" in settings, nuthin comes up.

Help, as always, is very much appreciated.
Here is the thing:
On my device and ISP/contract/SIM the setting is there and editable.
Others reported they have the option but it's not editable. For them I tried to provide the settings directly via apn-conf.xml which isn't always working.
And now you, with no options at all. Sorry but I'm at my wits end.
You can send me your mcn/mcc from your phone and the settings provided by your operator and I'l try to integrate it in my next build.
https://forum.xda-developers.com/t/...and-xl-alpha-2022-04-21.4171407/post-86671635
But I also don't know when that will be cause I'm kneedeep in 18.1 and that ****er won't boot :mad:
Another option would be to try it with a sim from a friend who has a more "common" phone operator and see if it works then. This way we can at least rule out an error in the ROM/device.
 

dr-dude

Member
May 18, 2022
7
0
Here is the thing:
On my device and ISP/contract/SIM the setting is there and editable.
Others reported they have the option but it's not editable. For them I tried to provide the settings directly via apn-conf.xml which isn't always working.
And now you, with no options at all. Sorry but I'm at my wits end.
You can send me your mcn/mcc from your phone and the settings provided by your operator and I'l try to integrate it in my next build.
https://forum.xda-developers.com/t/...and-xl-alpha-2022-04-21.4171407/post-86671635
But I also don't know when that will be cause I'm kneedeep in 18.1 and that ****er won't boot :mad:
Another option would be to try it with a sim from a friend who has a more "common" phone operator and see if it works then. This way we can at least rule out an error in the ROM/device.
You, sir, are a gentleman and a scholar. Thanks for your continued diligence with this project.
1) I'm happy to standby for 18.1 to see if that fixes the issue
2) Looks like the t-mobile connection for google fi is 310/260. Fi won't carrier switch unless the phone is designed for it, so this code should be the only one needed
3) I tried to find the mentioned package to see if that'd fix it, but couldn't find the 'signed-test_apn' package over on github. Am I doing something wrong?
4) great idea to try a traditional carrier SIM to eliminate problems. I'll work that angle as well

Thank you !
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    500px-Lineage_OS_logo.svg.png


    Code:
    * Your warranty is now void.
    *
    * I am 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 me for messing up your device, I will laugh at you.

    This is a LineageOS 17.1 ROM for the Helios P60 based Atom L (Atom_L) and Atom XL (Atom_XL), two rugged Android phones released by Unihertz in July 2020.

    This ROM supports both devices as well as both regional variants!
    You need to make sure which device and variant you need!


    LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0 (Q), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.

    Not Working
    • VoLTE is working but has some issus with SELinux in enforcing mode
    • LiveDisplay is not working (and probably never will)
    • DMR (Atom XL) is working but only with a headset
    • Face Unlock isn't available
    • You tell me

    Releases
    Atom L EEA (european union)
    Atom XL EEA (european union)
    Atom L TEE (non-european union)
    Atom XL TEE (non-european union)

    How to install
    How to update
    How to upgrade

    Links
    TWRP
    Common device tree
    Device tree Atom L (model)
    Device tree Atom XL (model)
    Device tree Atom L EEA (european union)
    Device tree Atom XL EEA (european union)
    Device tree Atom L TEE (non-european union)
    Device tree Atom XL TEE (non-european union)
    Bug reporting

    2022-04-21
    * April security updates included
    * Extended apn list included
    2022-03-27
    * March security updates included
    2022-02-16
    * February security updates included
    * Updated apns-conf.xml with stock entries
    2022-01-31 (Only for Atom L TEE)
    * Fixing a mixup of the prebuilt kernel
    2022-01-22
    * January security updates included
    2021-12-16
    * December security updates included
    2021-11-14
    * November security updates included
    2021-10-10
    * October security updates included
    2021-09-16
    * New icon for NavButtonRemap
    * LineageOS OTA updates enabled
    * September security updates included
    2021-08-10
    * August security updates included
    2021-07-14
    * July security updates included
    2021-06-16
    * May vendor updates included (needs vendor to be upgraded manually)
    * June security updates included
    * FMRadio is working now
    * Nav Button Remap included
    2021-05-10
    * May security updates included
    2021-04-15 2021-04-21
    * April security updates included
    * FMRadio is working now, without sound
    * Raised the size of the system and product partition to support bigger gapps installs
    * Combining the work for the Atom L and XL
    2021-03-09
    * March security patches included
    * Built for the first time using a combined Atom L/XL device tree
    2021-02-11
    * February security patches included
    * Notification LED is working now
    * Included FMRadio app (but not working)
    2021-01-24
    * Intercom DMR is working now
    * Audio Jack fixed
    * Wifi Hotspot and USB Tethering are enabled
    2021-01-16
    * January security patches included
    * Switched to TWRP recovery
    2020-12-19
    * December security patches included
    * Updated for stock release 2020-11-04 (announced 2020-12-03), needs vendor to be updated separately
    * !!! untested (for now) !!!
    2020-11-10
    * Rom build variant is "user" and is signed with release keys
    * Recovery is still build variant "userdebug" and signed with test keys
    * November security patches included
    * Intercom doesn't crash anymore (but still doesn't work either)
    * Some apps and sepolicies included from stock rom
    2020-10-01
    * Initial Alpha build released

    Help from other developers is certainly welcome. Currently only myself is working on this ROM.

    Credit and Thanks

    • LineageOS team
    • @PeterCxy for starting the work on the Atom L

    Enjoy! (y)

    XDA:DevDB Information
    LineageOS 17.1 for Unihertz Atom L and XL, ROM for the Android General

    Contributors
    a-dead-trousers
    Source Code: https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    Based On: LineageOS

    Version Information
    Status:
    Alpha

    Created 2020-10-02
    Last Updated 2022-04-21
    2
    Good news my fellow Atom XL Users: DMR is working (kind of) even in the current release! :)

    BUT

    only with a freeset :confused:

    During my struggles to get the mediatek code integrated into LOS I encountered many problems. One was that I muted the phone entirely. So with every step I took I did a full sound check including audio jack and headphones. That's how I found out that the sound of the DMR was working all along even without any modifications. It's just not able to "access" the built in microphone and speaker.
    This feels quite familiar as I had some issues with the audio jack in the beginning but the other way round. So maybe some settings I changed to get the audio jack to work were counteracting this.

    Just to let you all know, that there is still some progress on my part.
    2
    Hi everyone!

    I am not sure whether I have ever posted on these forums at all, but this one got me seriously intrigued and for the first time I felt the sudden urge to jump in and assist if I can.

    Just received my Atom XL yesterday afternoon (which seems to be just the best phone I have ever owned), and I have started to look for options to replace the stock ROM or at least root it so I can remove the bloat and Google crap before I actually start using the phone as a phone.

    I am really happy to see we already have a working Lineage build for this - so huge thanks to everyone for the efforts so far!

    My other phone is a Blackview BV9100 for which there was not much to be found in terms of customization, and since the manufacturer software updates are non-existent I had to figure out everything by myself - which means I have some experience, so if there is anything I can provide to help fixing the current issues, just let me know. I will give a shot at rooting the XL tonight but keep the OS otherwise untouched for a while if needed. I see flashing a Magisk patched boot.img caused a bootloop for someone, so I will see if I can get it to work somehow.

    In the meantime I will have a look at the issue updates on Github as well to see what is the actual status.
    2
    First impressions: install went smoothly, I'm so happy to have a Google apps free install. I'll try features, but so far, no show stopper, it feels good!
    2
    Thanks for all the help above on flashing with the sdtool. I've been using the 11/10 build for the past couple months and have recently updated to the 1/24 build. Already noticed a few fixes for things that I use.

    Here is a list of things I encountered in the 11/10 build with notes as to what I've seen in the 1/24 build so far.


    Wifi/bluetooth randomly turning off - For some reason, wifi/bluetooth would just turn off after about 1-2 days of uptime. Toggling it back on through the menu brought it back up. Unsure if resolved, need more time to test.

    Bluetooth failing to connect to anything after days of uptime - After a few days, bluetooth would just die and require a restart of the phone to fix. Toggling bluetooth off/on again had no effect. Unsure if resolved, need more time to test.

    Wifi calling would only work on the first wifi network connected to - A quick test of toggling off wifi and reconnecting seems to allow wifi calling to still work. Will continue to see if it continues.

    Disconnecting wifi - Phone disconnects from 5GHz wifi every 30 minutes and reconnects, even with strong signal. Will disable 5GHz on the AP to see if it continues to do this tonight on 2.4GHz. This might be an issue with my AP.

    UHF radio not working - Tested with my ham radio, able to broadcast and receive now.

    Magisk unable to display the root access dialogue - Works now and apps can be granted root

    ADB over usb sometimes not working - Haven't seen this issue yet, but it was random before. Will continue to watch for this.