yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] JoeRifle:
Yes. That can be an issue here. BUT one thing amazes me: none of the Samsung devices have these issues. They seem to handle the "always on and connected" LTE / 5G thing very well - even under bad reception. So I still need to investigate further here...my next point of investigation will probably be the firewall. I might be blocking sth there...not 100% sure atm since apart from energy issues everything seems configured just fine in there. It blocks all these peske PID 1000 things that phone to Tencent etc.

That **** reminds me of Windows' svchost.exe btw. Holy moly, that is another pest right there

;)
[Miscellaneous Android Development] GilouXDAD:
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!
[Miscellaneous Android Development] SepticFuddy:
So I decided to try out the build finally. Not sure what I'm doing wrong, but when trying to run `fastboot flashing unlock`, nothing happens. CMD just says "<waiting for any device>", the device unplugged sound keeps looping, and the phone screen says "=>FASTBOOT mode...". Fortunately I'm stuck just BEFORE wiping data, but I clearly could use a tip.
[Miscellaneous Android Development] GilouXDAD:
I ran into the same issue, though I didn't notice as I was doing something else… Ending up switching the cable from a USB hub to a direct port, as dmesg was complaining about a "bad cable", and … it worked (fastboot devices should list your phone, if it hangs or doesn't display anything, it can't see the phone!).
[Miscellaneous Android Development] GilouXDAD:
OK, so… everything seems quite smooth. I indeed don't have the FM radio (« unavailable »), and will be able to test that.

I'm not sure what I should/can use to test the talkie-walkie feature, but I think it was mentionned earlier, so I'll read on ;)

Camera, dual SIM, GPS

Also, it might be me being dumb, but I can't find some customizations that I like, like showing the battery level, and the current bitrate in the notification bar, but I'll dig further, I doubt that is something to set in the ROM…

Next step, setting up the build environment, I never did that, so I can fiddle a bit with a-dead-trousers' work, and maybe simply do my own settings there…

Thanks again for working on this and releasing it, it is appreciated, I feel like Unihertz could benefit from having this around, but I'm sure every phone owner says that once they can boot lineage OS ;)
[Miscellaneous Android Development] SepticFuddy:
Doesn't seem to matter what cable I'm using (2 are brand new and 1 came with the XL) or what port (one front USB3, one rear USB3, one powered USB2 hub), I still get the same results. The connection is maintained fine with any of those cables up until it's in fastboot mode, where it no longer can see the device.
[Miscellaneous Android Development] a-dead-trousers:
Are you using windows?

One other member on the Atom L Forum mentioned the same thing happening to him.

I recommended that he uses Linux to rule out a driver/OS issue but he never replied if he was able to get it to work or not.
[Miscellaneous Android Development] a-dead-trousers:
I was offered a solution for the FM radio but it requires some tinkering (patching) of source code only to get the stock FM radio to work. It's currently in a pull request on my github if you like to give it a shot. But according to the author it's still missing the actual audio (you can't hear anything neither from the speakers nor from the headphones/audio jack)

You're welcome. The more the merrier ;)

Thanks.
[Miscellaneous Android Development] SepticFuddy:
Ah ok, I'll try it out on my Debian box soon. I don't have it configured for Android stuff yet, so I'll report back with the results.
[Miscellaneous Android Development] a-dead-trousers:
I just got word and can confirm that adb sideload isn't working from either windows or linux with my latest TWRP.

So the only way to install the rom is to transfer the zip file to the SD card beforehand (e.g. with MTP from a working OS) or by using `adb push`.

My guess is that the partial decryption of `/data` is messing up the connection (as it is the same with MTP). I'm working on this but it may take some time because I don't know what's missing:

https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_XL/issues/1

I've already updated the install guide accordingly.

Sorry for the inconvenience.
[Miscellaneous Android Development] GilouXDAD:
Ah, yup, I had the issue as well, and I indeed used push ;)
[Miscellaneous Android Development] GilouXDAD:
Not sure if it's ROM related, but I don't seem to be able to set the volume for the speaker when I'm on the phone, might always have been the case though, as sound was always quite loud on the speaker.
[Miscellaneous Android Development] SepticFuddy:
So I finally tried out the LOS ROM. I wasn't able to make any phone calls at all, whether with VoLTE/VoWIFI enabled or disabled. It seemed to trigger resets in the service connection. Also, LiveDisplay didn't seem to be working at all.

Because of the calling issue, I tried to revert to stock. Problem is, TWRP won't let me flash the stock ROM over LOS build because it's older ("Can't install this package over newer build"). Having already wiped the LOS install, I can't get into the OS for ADB (I was going to try disabling AVB again in case that let me install the older ROM). Re-flashing LOS leaves it broken for some reason. TWRP isn't being replaced by factory recovery, so I'm out of ideas.

If anyone can help, I'm a little desperate. Thanks.
[Miscellaneous Android Development] a-dead-trousers:
That is ... unfortunate. May I ask what steps you did on installation?

I tried to get it to work but I can't find any decent configuration options. All that I found don't seem to match the devices kernel services.

LiveDisplay is not working · Issue #8 · ADeadTrousers/android_device_Unihertz_Atom_LXL

I just got word that LiveDisplay isn't working at all. The settings are there but it cannot be activated.

github.com

If you just want to get rid of LOS without wiping "/data" you could try to flash the "super.img" from stock rom. This could be done from inside TWRP or from bootloader with fastboot.

If nothing helps you could always do a factory reset with SPFlash tool. Here you can also select which partitions to overwrite. So it's possible to leave out "/data" allthough I won't get my hopes up that you could save your data as they are encrypted.
[Miscellaneous Android Development] SepticFuddy:
I did everything as the instructions state, until I got to the "adb push" command. It was giving me an I/O error, and for the life of me I couldn't find any of my microSD adapters, so I had to enter into the stock OS, set up the SD card as portable, transfer the ROM, and then go back to TWRP and wipe/flash as instructed. Oddly enough I was able to push something later on when trying to recover. I flashed Magisk but not GAPPS. My plan was to stick to MicroG but I don't think I had it fully working yet before I noticed the call issue.

Another weird thing is that after swapping to my OG Atom as a backup, I did experience a similar calling issue at one point, and it always says "T-MOBILE - NO SERVICE". But when I first put the SIM in and toggled airplane mode, I was able to call, and I've been able to call just fine today. I was having some weird behavior previously where I live on the stock XL, some outages and persistent call quality problems, but not that particular issue where I have signal but can't place a call. Makes me wonder if it was a matter of bad timing or something on LOS. May be worth trying it out again just to see now that I have the Atom all ready as backup.

The ship has long sailed on trying to saving data thanks to some minor oversight on my part. I'll probably try factory resetting with SPFlash tool when I get the chance
[Miscellaneous Android Development] a-dead-trousers:
My sdcard is set up as "portable" to begin with. So maybe that's the reason why it wasn't working for you but I'm not sure why though because this setting only affects the ROM and the recovery is different from that. Maybe it has something to do with the file system (ext4 vs. fat) in the fstab or elsewhere. I'll look into this.

I sometimes too have a similar problem with the mobile network: Full reception but no connection.

Then I go into the settings do a manual search and select my "home network". After that I can switch back to automatic and everything works fine again. I had these problems mostly when I was actively trying out new settings in the build process. So while flashing nearly 4 - 5 times daily I thought it was connected to that and not a problem within the kernel/ROM itself.

My guess was that you were desperately trying to keep your /data but that triggers the most bizarre errors. And if that would have been the case you would be able to switch back to stock by simply flashing super as that is the only thing affected by a "dirty flashed" LOS installation.
[Miscellaneous Android Development] SepticFuddy:
Anyone have a scatter file I can use? I had forgotten all about this SP Flash Tool business until a-dead-trousers mentioned it. Now I don't have ADB access and thus no way to generate one. Thanks in advance.

I had a similar problem again this morning on the old Atom. Had signal, tried calling, suddenly no signal and call wouldn't place. Went into settings and manually selected the network and it started working (probably just by resetting the connection, who knows). It's really puzzling me that I didn't have this problem on the stock XL but I get some variant of it on LOS and the stock (rooted) Atom.

Nope, no attempts at keeping data were made. Only attempts at migrating backups from key apps.
[Miscellaneous Android Development] a-dead-trousers:
It's part of the official rom releases:

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

Also I made an updated guide which uses the latest release of the SPFlash Tool:

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

(The screenshot is missing though)
[Miscellaneous Android Development] SepticFuddy:
Ah, thanks. I'm getting an "ERROR : STATUS_SCATTER_FILE_INVALID (0xC0030001) The scatter file format is invalid!" though. The solutions I've found don't apply in this case or don't work.
[Miscellaneous Android Development] a-dead-trousers:
That's ... never happend to me.

Honestly I don't know how to help you with that. The scatter file is a simple TXT-File with no CRC/Checksum whatsoever. Only possible cause I can think of is a different codepage or an error during the unpacking from the ZIP or a currupt ZIP archive but that would have triggered an error during the unpacking.
[Miscellaneous Android Development] SepticFuddy:
The file opens just fine for me in notepad. Would you mind uploading/pastebinning yours so I can compare and make sure it's not actually the scatter file?
[Miscellaneous Android Development] SepticFuddy:
Oh wow. Way different. Turns out I was using an OTA-specific ROM from a different drive link sent to me by Unihertz a while back, and it's significantly different internally from the one in the drive page you posted. Good to know. Using the non-OTA version worked fine, thanks for helping me sort that out. I wonder if it would have flashed when I was stuck previously.

Since I've got my old Atom up and running again, I ended up flashing the XL back to the LOS ROM again to see if I could get calling to work. Still can't so far, despite manually choosing the network, but data and SMS work fine. I had T-Mobile push me updates to try to fix it, but no dice. Of course I told them I reset the phone, not that I flashed it ;) . They're supposed to get back to me tomorrow with an update on the issue, so hopefully we can figure out what's going on. In the mean time, I think I'll tinker with getting things set up the way I want in LOS. Worst case is the issue ends up being somewhere in your device tree or something and I'll have an LOS backup to try later after it hypothetically gets sorted.

Meanwhile, does anyone have a good suggestion for swapping the back/task view buttons in LOS? I found something that has to be built manually, but I figured I'd ask first in case there's something more convenient.
[Miscellaneous Android Development] a-dead-trousers:
Glad you got that sorted out.

When data and SMS are working there could indeed be a problem with VoLTE. My guess is that as soon as the carrier promotes VoLTE it gets activated and because of an unknown error it gets stuck that way and cannot be turned off. Problem is, like I wrote earlier, that I don't have an VoLTE option on my mobile contract to test that.

You mean like settings -> system -> keys ?
[Miscellaneous Android Development] a-dead-trousers:
I have a very bad feeling about this (at least for me).

Since I'm from europe I used the SEEA variant of the stock rom for building mine. For non europe there is the STEE variant. I always thought the only differences are the bundled apps/libraries because of legal issues. But the more I think about it the more I believe it's not that simple. You having problems with your carrier and others don't, the kernel being a different size and so on. If my hunch is correct that means I need to build 8 roms in total:

SEEA Lineage for Atom XL

SEEA TWRP for Atom XL

EEA Lineage for Atom L

EEA TWRP for Atom L

STEE Lineage for Atom XL

STEE TWRP for Atom XL

TEE Lineage for Atom L

TEE TWRP for Atom L

For that I need to restructure my build environment drastically. So I will do one more (S)EEA release with the latest security updates for Lineage and TWRP with my old environment and then begin the changing.
[Miscellaneous Android Development] SepticFuddy:
The thought crossed my mind when the volume level warning popped up while using it to play music in the car. The stock STEE ROM doesn't do that... which was a nice breath of fresh air compared to every other phone I've used for that purpose in recent memory. I remember reading years ago that the warning is for compliance with EU laws while researching how to get rid of it (invariably requiring root). Apparently, most manufacturers just don't bother not including it (and who knows what else) in their non-EU devices.

Additionally, I would think that disabling VoLTE and/or using Wi-Fi calling would make it work, but they don't. The former is more understandable because I've also read that US carriers tend to try to force you into VoLTE where available, but Wi-Fi calling not working makes no sense to me. I've used it in foreign countries without cell service, so I don't see why an inability to connect to the local cell network properly should affect anything. Of course, TMobile hasn't come back with an update despite saying they would within 24 hrs. Shocker. Hadn't had the chance to bother them again but now I'm wondering if it's even worth trying before getting to test your TEE release.

Also, out of curiosity, what is the difference between the S and non-S variants? I only see S variants in their drive.

I only saw options for the "home", "recents" and non-existent "search" buttons there, and no options that would allow swapping the recents and back keys around. I got sick of the mind games so I did eventually go ahead and build and install this: NavButtonRemap. Works perfectly. It shows up as an accessibility service and has options based on screen orientation. Might even be worth including just because the stock ROM also includes a key switching option, also under accessibility IIRC.
[Miscellaneous Android Development] a-dead-trousers:
S = Atom XL

non-S = Atom L

Now I understand what you meant: "back" is no option for key assigment and therefore also no configurable key.

This is set in keyboard-layout in the device tree. I'll look and see if there is a setting in LOS to get this key as assignment too.

btw. "search" is the big read button on the side of the phone (LOS doesn't offer a better "named" option for this assignment)
[Miscellaneous Android Development] a-dead-trousers:
Now Atom L and Atom XL are supported as well as both regional variants EEA (european union) and TEE (non-european union)

(Please bear with me as I'm now just in the process of building all four variants. This will take some time)
[Miscellaneous Android Development] SepticFuddy:
So I've downloaded all the STEE assets. When I tried to flash over the previous LOS install (including the wipe steps), I got the black screen issue again. So I reflashed stock with SP and followed through the first-time install steps. For whatever reason, it boots into the Chinese menu instead of TWRP, even if I don't let it boot back to stock first. Maybe the STEE recovery image file is accidentally the wrong file?

Would it be possible to add in options like flashlight activation for key assignments? In stock I had it set up for long press on red to toggle flashlight, double press on red for screenshot. They also had the option to make it the PTT key for Intercom (even if a bit silly to have to change back and forth manually).
[Miscellaneous Android Development] a-dead-trousers:
I just checked (downloaded) and it's the same file as in the OUT-Folder of TWRP. So no accidental mix-up.

The only time I had the chinieese menu was when I accidentially pressed vol-down instead of vol-up.

(Nearly gave me a heartattack)

I can't do anything until monday because I'm not at my place anymore. That's why I had to rush to get everything done yesterday. Maybe there are some mix-ups but the TWRP STEE is none of it. Next week I'll have time to test the TWRP recoveries individually but I fear that everything will be working fine as I never had any issues on that front. As with the LOS variants I don't want to go through the struggle of setting up four different installs as it's my only device and daily driver. So I'm depending on others to test and give me feedback.

So anyway, one step at a time, first we need to figure out why TWRP is refusing to work on your device.

I haven't forgotton about this. As soon as we figured out the other issue I'll look into this.
[Miscellaneous Android Development] SepticFuddy:
Turns out I was doing the same thing, down instead of up. Big relief there.

On the other hand, the LOS install is failing. I'll take it to GitHub.
[Miscellaneous Android Development] a-dead-trousers:
Already attended to ;)
[Miscellaneous Android Development] a-dead-trousers:
I just updated the install guide for troubleshooting a problem that might occour on partition resizing during the installation as I recently raised the size of "system" partition to support bigger gapps variants. In the case of this error the "super" partition needs to be resized beforhand. To make it easier for everyone I provided an already resized copy of "super.img" for all four device variants including the latest stock "vendor" partition.

Bonus:

In the future this could also be used to update "vendor" if unihertz ever decides to do another update without the need to flash stock rom beforehand.
[Miscellaneous Android Development] SepticFuddy:
I've got the STEE version installed and running, so the super.img file works.

Still have the same issue with calling though. I actually don't even see the wi-fi calling and VoLTE options this time, though from looking around I think that may be a consequence of not being able to connect to the network properly? In any case, the bright, young team at T-Mobile is going to send me a new SIM for some reason, despite knowing that the one I have works in my backup and did work on this phone :rolleyes:. Really wish I could just tell them it's a custom ROM and to put an engineer on the line...
[Miscellaneous Android Development] a-dead-trousers:
I think I know now what I did wrong. Will do an updated release ASAP.
[Miscellaneous Android Development] a-dead-trousers:
I just deleted v20210415 from my releases and replaced it with v20210421.

I forgot to extract the vendor blobs in the previous build. Now everything is included as it should have been in the first place. Sorry for the inconvenience.
[Miscellaneous Android Development] SepticFuddy:
Calling works. Thanks for sorting that out! The signal seems to be a bit wonky so far but it was enough to get everything activated and enable wi-fi calling. Not sure that that is an issue with the ROM though. EDIT: After rebooting while in town yesterday, the intermittence issues seem to be sorted out. Despite nominally having 3-4 bars out in the mountains where I live, there seems to be an issue with being able to update the profile out here. So if anyone else has issues with calling/texting being real finnicky in a low pop area, you may want to try a reboot in a nearby population center. Everything seems to be stable for me since last night.

Also seems to have fixed the issue I had in stock where nobody could hear me on speakerphone during a normal phone call (but it worked just fine on Signal calls). So that's a nice bonus.
[Miscellaneous Android Development] landsome:
Has anyone here compared this LOS with GSI versions (LOS, AOSP etc.)?
[Miscellaneous Android Development] a-dead-trousers:
Not really. In the beginning I looked into project treble but I didn't understand the structure of the project itself so I set up my own device tree... with black jack and hookers ;)

But it shouldn't be that hard to get everything treble ready as I'm not tinkering with "vendor". You're welcome to give it a try, I don't see any benefit though.
[Miscellaneous Android Development] landsome:
Thanks. I have just flashed the v305 of the phh AOSP, mostly out of frustration because I cannot either boot to fastboot(d) with TWRP (reboots back to recovery) or start ADB from recovery (ADB starts but hangs and does not even cancel). (Tried several versions of TWRP, including the latest.)

I was encouraged by PeterCxy over on the Jelly 2 reddit forum. AOSP seems to work well, with minor glitches known from other MTK devices (e.g., echo during calls, cured by v305 except on BT; no audio volume change during calls). Unfortunately, it does not cure my main problem with stock, which is annoying BT cuts and interruptions when there is any sustained activity on wifi 2.4 (works fine on 5ghz).

Unihertz told me the issue will be solved on their coming Android 11 release, but apparently not on AOSP 11.