yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] lambgx02:
Roger. I fully intended to start ripping into this to try to figure it out but I've done nothing the last 6 weeks but work and boat repairs. I'm running out of steam, so maybe I'll have a chance to get back to it. If there's anything you want me to test or check, lemme know. :)
[Miscellaneous Android Development] Mokhand:
Do I need to follow the upgrade guide if I already updated my stock firmware via air? Or I can just install the latest release?

P.S. Does LOS have automatic phone calls recording feature? Sorry, I've never had LOS before (always on MIUI) so I'm not really familiar with this system, but stock firmware is too glitchy to keep it.

Thank you in advance.
[Miscellaneous Android Development] a-dead-trousers:
My upgrade guide is for pre 2021-05 because the moden portion needs to be upgraded too. If you already got it OTA you are good for the installation guide.

As I don't really need APCR I'm not sure if it is available in LOS.
[Miscellaneous Android Development] WeAreGod:
Thank you! :)
[Miscellaneous Android Development] magnetosphere:
Everything related to data/cellular/texting/calling has been unreliable on my phone since some time in May (stock ROM). Google Fi is utterly useless and doesn't want to fix anything. Any reasons why I shouldn't install LOS?
[Miscellaneous Android Development] a-dead-trousers:
Do you have the L or the XL?

For the XL the DMR currently isn't capable of sound output (needs some proprietary api modifications).

For both devices face unlock (a stock feature) isn't available.

VoLTE might be a little bit unreliable but I'm not able to test/fix that properly as I don't have a suitable phone contract.

Aside from these I'm using LOS without any major drawbacks for more than half a year now.
[Miscellaneous Android Development] landsome:
I guess no, if your issues are so severe.

The irony is I had some annoying issues as well, and they were all solved by a fresh install of stock ROM (same version) via SPFlash.

But LOS has other virtues over stock beyond stability.
[Miscellaneous Android Development] GilouXDAD:
Hey!

Just upgraded to the 202107 version, your upgrade doc made it rather easy, and I don't seem to have lost anything in the process. I'm wondering what's the Linux version of the SP flash tool that could be used, so as to avoid a Windows part in my upgrade process…

Thanks a lot for your work, I still haven't found time to fiddle with the image and the options myself, you're making too easy and the default settings suit me in general … :P
[Miscellaneous Android Development] a-dead-trousers:
Thanks.

I've tried it with the Linux version but wasn't able to get it to work. Before the phone boots there is around 3 to 5 seconds of a pre-bootloader state on which the flashing is possible. Under Windows the phone is recognized under a different USBID/devicename. Under Linux you would need to tinker with the udev-rules which I wasn't able to figure out how. Also the various Linux distros out there in the wild might behave differently to mine. Under WIndows this whole ordeal is managed by the mediatek driver. Maybe there is a special Linux driver out there which I couldn't get my hands on but I doubt it would be easy to integrate into the system/kernel of my distro. So for the sake of simplicity I droped the Linux portion of my SP Flash guide entirely.

But that doesn't mean you or anyone else couldn't try it. If you manage to get it to work I would gladly integrate it into my guides. Because then I wouldn't need to switch between Windows and Linux so often after messing up my phone again (just kidding).
[Miscellaneous Android Development] Shadow Of Leaf:
i have this issue also phone is not recognized in linux (ubuntu) when using adb or fastboot but i use this workaround to fix it

use sudo in every command that you want use your phone it will work

for example

if i use fastboot flash something something.img

the system will not recognize the phone

but if i use

sudo fastboot flash something something.img

it will be recognized

this work with adb and fastboot but i did have not try it with sp flashboot so try it out
[Miscellaneous Android Development] a-dead-trousers:
That's not it.

Already tried it with sudo/gksudo.

The main problem here, I think, is the fact that the phone behaves as a completly different device during the first few seconds of booting. So different that the default linux drivers won't recognize it.

To be able to use adb/fastboot without sudo look here:

fastboot and adb not working with sudo

I have a very weird issue on my Ubuntu machine when trying to run the fastboot command. When I run: fastboot devices I get no permissions fastboot So I run the command with adminidtrator

stackoverflow.com
[Miscellaneous Android Development] a-dead-trousers:
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.
[Miscellaneous Android Development] GilouXDAD:
Yup, it switches the USB ID, like a dual usb key that can switch from storage (to expose, say, drivers) to a wireless card… something like usb device mode, iirc…
[Miscellaneous Android Development] GilouXDAD:
So… Last week, my unihertz screen died, after salt water impacts, and a jacuzzi meeting… this phone is not as robust as it is said to be, I'm disappointed, and I think I'll be off it… It saddens me, the small community feeling we have here started to motivate me hehe… I'll keep you posted, but I'm afraid I won't be trusting them, and I doubt they'll fix my phone…
[Miscellaneous Android Development] GilouXDAD:
What is a freeset ? or are you talking about a headset ? Before my phone died, I tried it with one, and I was almost going to say it works, but I wasn't sure if I was just getting lucky :P
[Miscellaneous Android Development] a-dead-trousers:
A freeset (for me) is a combination of headphone and microphone that share the same wire/connector.

But I just checked and you are right, it's more commonly known as a headset ;)
[Miscellaneous Android Development] SepticFuddy:
I wouldn't be so doubtful. Mine just reached China today to repair a microphone issue it's had since I got it and was I too lazy to get fixed. I'd have tried to myself but I was concerned about any unknown waterproofing measures I would irreversibly damage before knowing it. It ain't like a flagship phone where I can at least look up a guide on what's involved. I had to pay to ship it out, but as long as they determine I didn't screw it up by abusing it, the repair is free and they'll ship it back. Since the phone is advertised as being rugged and waterproof, I imagine they'll do the same for you. Doesn't hurt to ask, anyway.

Sure would be nice if someone was willing to sacrifice one of these to IFIXIT though...
[Miscellaneous Android Development] GilouXDAD:
I sent then an email, thanks for the confidence boost haha ;)

We'll see. The way it is screwed is quite interesting, and it's rather easy to access the inside… But that's off-topic ;)
[Miscellaneous Android Development] Shadow Of Leaf:
thanks for the suggestion

i will into it

for the face unlock , i think you need this cause i fix it in my rom

GitHub - shubhindia/android_external_motorola_faceunlock

Contribute to shubhindia/android_external_motorola_faceunlock development by creating an account on GitHub.

github.com

copy this folder to external and

apply the patches to framework_base and packages_settings

and add ro.face.moto_unlock_service=true to system.prop

and enable face unlock in boardconfig

TARGET_FACE_UNLOCK_SUPPORTED := true
[Miscellaneous Android Development] Risitia:
Hello there.

Just wanted to share my experience with installing LineageOS on my Atom L.

Everything went just fine using github instructions.

Very well detailed even for errors that have occured.

The device works well with your ROM, and i really appreciate it, more than the stock ROM !
[Miscellaneous Android Development] WeAreGod:
Are there any good guides on how to root the XL TEE from here? Like what is the most effective & easy way to root after completing the LOS Install?
[Miscellaneous Android Development] a-dead-trousers:
If you already have LOS (and TWRP I guess) it's rather simple:

Just "Install" Magisk the same way you installed LOS.

After that you might need to seperately install the full apk from within LOS too if the stub apk is missing.
[Miscellaneous Android Development] WeAreGod:
Thank you.

Also, I tried switching to TEE after I installed EEA..

Using ADB Sideload method in TWRP Recovery brought me to this message " this package is for device Atom_XL_TEE; this device is Atom_XL_EEA"

As a side note, root permission is still denied whenever I try to wipe the drive..
[Miscellaneous Android Development] a-dead-trousers:
You need to change TWRP to TEE first.

You don't need root to wipe.

Just do that from inside TWRP and you are good.
[Miscellaneous Android Development] landsome:
Any chance to get SafetyNet to work with LOS?
[Miscellaneous Android Development] a-dead-trousers:
Sorry, but I don't know how. There is nearly zero information on how to achieve this nor are there any hints or tricks. Whenever I tried to find anything useful it's always something about how to mimicing or hiding from safety net. Never ever something about how to get it to work from a custom rom standpoint.

At least by enabling selinux and signing the build I was able to grant "basic integrity" but for the "cts profile" portion of SN I don't know any possible solution.

Anyway, for most "security" apps I use magisk does a fine job on hiding the fact that I'm not using a fully approved device.
[Miscellaneous Android Development] nobbyjesus:
Looks like I'm still out of luck for trying that, as I think I gronked my headset socket - dropped it with headphones plugged in.

On the other hand, it may show some chance of integrating other things into the UHF access - I'd love to see a version of the Android FLMsg/FLDigi app that could use it.
[Miscellaneous Android Development] SepticFuddy:
So uh, just out of curiosity, now that they've announced the big surprise of calling for Android 11 beta testing on the L/XL... how much work is that going to be to upgrade the LOS build accordingly after they put out a public release?

As a side note, they've sent my device back from repair with a USPS tracking number, but it hasn't hit stateside yet. No charge (other than my cost to ship it to them).
[Miscellaneous Android Development] a-dead-trousers:
Hopefully not that much *fingers crossed*

(y)
[Miscellaneous Android Development] SepticFuddy:
My device made it back from repair, microphone issue appears to be fixed. Not certain if it's actually mine or not, since it came back with no screen protector and bootloader locked, and there were and are no scratches to compare.

Installed the latest STEE release no problem, DMR confirmed working with headset only.
[Miscellaneous Android Development] landsome:
Tried to update from previous version to latest version (09). First reboot was to recovery. Then the Lineage booting logo appears for a minute or so, the reboots to recovery, then logo, the recovery a.s.o. Followed update instructions. Anyone experienced this? (LOS with gapps, no magisk.)
[Miscellaneous Android Development] a-dead-trousers:
From my experience this mostly happens if the vendor and system partition don't match.

Did you do the "vendor" upgrade (2020-11 > 2021-05)?

Another posibility could be an error/bug in gapps.

Had that with my old phone where from a certain point onward I couldn't upgrade the rom without upgrading gapps at the same time. Later on when there was the switch to 18.1 and no suitable gapps package available I tried to use an alpha built which worked on a fresh install but not in an "update" situation.

On all these occations I couldn't boot into LOS (Logo never "finished") and the phone restarted into recovery after some time.

Sometimes a "downgrade" to the previously installed release helped to get back into the system to be able to "backup" my data. Almost all of the time I forgot to do that :oops:

But to be finally able to "update" to the latest release I always had to do a clean install :cry:
[Miscellaneous Android Development] landsome:
Thanks!

Yep, I had installed the stock 2021/05 via SPFlash.

Possible. I did not reinstall gapps and I have had this experience with LOS upgrades on other phones (Sony XZ1c and XZ2c both had this issue and it was solvable by reinstalling gapps together with the new ROM version).

BTW, I have heard official Unihertz Android 11 is in the works (a few Reddit beta testers got it already).
[Miscellaneous Android Development] a-dead-trousers:
I got an email from unihertz about that a few weeks back.

Hopefully they didn't change too much so it's possible for me to lift the update to 18.1 without too many changes.
[Miscellaneous Android Development] a-dead-trousers:
For those who haven't already checked their LineagOS updater (yes, that's working since 2021-09-16):

I've released 2021-10-10. I just forgot to update this thread.

From now on you should be able to use the built-in LineagOS updater to get the latest version of this ROM.

I just need someone else (besides myself) who can confirm that it's working.
[Miscellaneous Android Development] Risitia:
I tried to update using System>Update and nothing :(.

I have the build QQ3A.200805.001

Maybe i should manually update to 10-10 first :p ?
[Miscellaneous Android Development] a-dead-trousers:
Right above the "build number" is the "build date" which is more meaningful.

The updater was activated in the previous build (Sep 16 2021 or 2021-09-16). So the first update where it should actually work is from 2021-09-16 to 2021-10-10.
[Miscellaneous Android Development] Risitia:
Oh Ok ! Thanks, didn't see the number like that.

So if I understand well too, if I update manually to the last build, I should also reload Gapps and other things right ?
[Miscellaneous Android Development] a-dead-trousers:
Yes. If you happen to have GAPPS installed, you need to install it alongside the ROM updates.

(As mentioned in my install/update guide)

I cannot integrate it and provide an additional line of ROMs because It will rise from a moderate 580 MB to a whooping 1.3 GB (custom build I use which replaces all of the LOS apps with their proprietary Google counterparts ommiting all of the additional "bloatware" like "Duo", "Drive" & many more).
[Miscellaneous Android Development] GameHunter1:
Atom L TEE: there is still old version 20210916 in github.

(The other versions of the phone and the region have already the new version 20211010)
[Miscellaneous Android Development] a-dead-trousers:
No, it's there. Just not in first place but I don't know why.

Edit: oh, now I see it. I used a wrong tag therefore the sorting is off.
[Miscellaneous Android Development] GameHunter1:
I've tried to install LOS using the "How to install" guide.

Not successfully.

After flushing TWRP and rebooting holding the "volume up" button, the TWRP doesn't load. If the TWRP was flashing over the official build 202005xxx or 202011xxx, the phone hangs with a thin green line at the top of the screen (exactly the same line was appeared at the very first tries when people tries to flash LOS recovery - you probably remember this sympthome in the supplementary thread). If the TWRP is flashed over the last ROM 202105xxx, the phone goes to bootloop.

Atom L, TEE, all the ROMS and the TWRP (the last version) are correctly downloaded, the "How to install" guide is accurately executed.
[Miscellaneous Android Development] a-dead-trousers:
Over which stock version you're installing LOS?

The green line tells me that the bootloader doesn't recognize / is incomaptible to the kernel.

The latest ROM and TWRP are built against stock 20210520.

For the bootloop my best guess is, that you either haven't wiped data (problem with encrypting) or you have the wrong model.

Best you start with reflashing the latest stock rom for your model and then retry to install LOS.

EDIT:

Best way to "wipe" data if you cannot boot into your phone is to only flash "data" with SPFlash tool.
[Miscellaneous Android Development] GameHunter1:
I was not able to install TWRP in the TEE version, but I've successfully installed it in the EU version (so, I've used everything for EU: stock rom, vbmeta, TWRP).

(I didn't proceed to the LOS yet)
[Miscellaneous Android Development] GameHunter1:
I've successfully installed LOS.

Is there a more flexible way to use the big red button (aka "search" button in the settings)? I can assign a limited number of actions for a short press. Although there are actions for a long press in the settings, the long press is virtually not working. Actually I want a flash light at the long press.
[Miscellaneous Android Development] a-dead-trousers:
Glad to hear that.

Some time ago I bought another Atom XL to test the various variants. The only impossible switch I encountered was if I changed from Atom L to XL and vice versa. Everytime I tried that I got the "green line"-error. So a full stock rom flash was in order. Switching between TEE and EEA was possible but I had to wipe data otherwise the encryption (best guess is that it includes the device name into the encryption key) would prevent TWRP from booting.

None that I know of. A quick search for "lineage custom actions for button" didn't bring up any useful information on that topic either.

Sadly Unihertz didn't utilize the long press feature as they only made the button available in their proprietary/modified system extension.
[Miscellaneous Android Development] a-dead-trousers:
Bad news:

The workstation I used for my builds decided to just give up and is not booting anymore. According to the onboard LED the CPU seems to be defect. My only hope is that the PSU is the cause (EPS +12V not working). So anyway I'll need some time to get everything sorted out and working again (it's a custom watercooled setup so don't expect a quick recovery especially with the current corona "shortage" of spare parts)

Therefore I cannot promise a november update for my ROM but will try to get it in time of december. Maybe even with LOS 18.1 (looking at you unihertz).
[Miscellaneous Android Development] landsome:
Sorry, I imagine it's terribly annoying.
[Miscellaneous Android Development] a-dead-trousers:
Luckily I was able to find someone who was selling an used CPU near my hometown.

Otherwise a refurbished China import would have cost me the same without a guaranteed delivery date.

So the "beast" is back up and did good already: The November updates are available for download now.
[Miscellaneous Android Development] McHoffi:
Hi, will there also be LOS 19 or even further support, does it depend on Unihertz how long this ROM can be updated? I would love the phone, but want also the possibility of updates. It seems to be a good little android phone with a decent price, something rare to get your handy on. But also do I like security, which includes getting regular updates.

One good thing is that from next year on the seller will be responsible to update the phone for at least two years in the EU. Maybe this will help to keep it updated for longer time and also faster. Because if there is a security risk the seller/manufacturer is also obliged to update fast.
[Miscellaneous Android Development] a-dead-trousers:
Unihertz announced that they'll release an Android 11 (= LOS 18) upgrade of the rom.

Jundging by their previous phones there will be no further upgrade (Android 12) just minor (irregular) updates.

And then *peng* it's July 2022, two years after their launch, so they are not further obligated to do any more updates.

On paper this two year responsibility sounds good but in reality it's not even comming close to being enough. It must be five years ore more to do any good in saving the environment. Companies like Apple and Samsung are releaseing phone after phone and therefore so many people are using theirs no longer than a year. They should be restricted to only being allowed to release a new phone per year tops.

That said, I'll try to support this phone as long as possible but bear with me that I'm rather limited on what I can do as long as there is no source code release of the kernel. So it can be possible to use LOS 19 with the upcomming A11 kernel from Unihertz but it's also possible that it's not gonna work at all.
[Miscellaneous Android Development] McHoffi:
I know its Off topic, but want to warn others and hope someone could help me:

Tried updating today to Android 11 and wanted to install magisk patched boot. Messed the whole day around, just got into a bootloop.

Then tried to go back to old Android 10 with SP Flash Tool v5.1820, but am just getting an error, which means, that I am not using a verified version of the firmware, but it is downloaded from the g drive.

Unfortunately Unihertz did not upload the Android 11 firmware to gdrive.

Now the phone wont even boot. Does anybody of you know what to do?
[Miscellaneous Android Development] a-dead-trousers:
Hi.

I would recommend you use the LATEST device driver and SPFlash Tool.

Here is my guide on how to install and use them

android_device_Unihertz_Atom_LXL/docs/HOW-TO-FLASH-STOCK.md at master · ADeadTrousers/android_device_Unihertz_Atom_LXL

Common device tree for the Unihertz Atom L and XL - ADeadTrousers/android_device_Unihertz_Atom_LXL

github.com

(I just checked the links in my guide and there is now a V6 of SPFlash which I haven't tested yet so I recommend you stick to V5 for now)
[Miscellaneous Android Development] McHoffi:
If someone else encounters problems with rooting Android 11 on the Unihertz Atom XL / L i made it now with this, I dont know what of this guide has had to be done and what was unneccessary, but now it worked:

Got it now working with Virtualbox. Had to make multiple retries.

The final way was:

Install magisk canary build

patch boot.img

Copy everything to virtual machine

Changed the commands for disabling verity from this guide

twrp_device_Unihertz_Atom_LXL/HOW-TO-INSTALL.md at master · ADeadTrousers/twrp_device_Unihertz_Atom_LXL

Common device tree for the Unihertz Atom L and XL - twrp_device_Unihertz_Atom_LXL/HOW-TO-INSTALL.md at master · ADeadTrousers/twrp_device_Unihertz_Atom_LXL

github.com

to the format of this guide

ROOT GAINED !!!!

THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...

xdaforums.com

-> this means: instead of

fastboot flash --disable-verification --disable-verity vbmeta vbmeta.img

changed it to

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot flash boot "patchedbootimgname".img

fastboot reboot

I dont know what then really was the problem, because yesterday I also tried with the virual Linux, but it did not work, maybe it needs the command from the linked guide for disabling verity.