yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] grandmagoblin:
So I do see that there is not an option for VoLTE, and it is disabled. I changed providers to test whether it was a provider issue, and it is.. mostly. I am using Mint Mobile right now, and there is a significant delay in the calling which is to be expected since I have read that it because VoLTE is not supported. I am still able to make calls, just takes a bit to make them like ~30-60 seconds delay. As far as getting this working, what can I do to help? I have both an Atom L and Atom XL that I am willing to brick if necessary.
[Miscellaneous Android Development] a-dead-trousers:
The next release should include a fix for vtservice and hopefully that fixes the VoLTE issue.

https://github.com/ADeadTrousers/an...mmit/1953275ee7939a97ed90d6956f62e681500214f3

What I'd need is someone who is willing to do a little bit of research on the VoLTE front, test things out on their own (e.g. forking, tinkering, building, testing) and in the end providing merge requests/commits to fix VoLTE for good.

The same goes for the DMR on the Atom XL.
[Miscellaneous Android Development] grandmagoblin:
I resolved my own issue with rerunning the patches. So false alarm.
[Miscellaneous Android Development] a-dead-trousers:
I know, I've a heavy reliance on patches ;)

If someone knows a better solution (besides forking the original repos) I'm all ears.
[Miscellaneous Android Development] grandmagoblin:
So I have some interesting results from testing. I was able to call on wifi, but only outward. I suspect it is because my IMS is not registered, but it will not allow me because the phone does not "support" it. I added a couple more parameters to the /device/Unihertz/Atom_LXL/product.prop. I have included the file below and the results. I am going to do some more testing and see what happens, but I will keep you updated.

# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1

# Data Options
persist.data.iwlan.enable=true
persist.data.iwlan=1
persist.data.iwlan.ipsec.ap=1

# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1

#IMS Options
persist.ims.disable=0
persist.ims.reg=true
persist.ims.volte=true
persist.ims.vt=true
persist.ims_support=1

# Other Options
persist.sys.cust.lte_config=true
persist.rcs.supported=1
telephony.lteOnCdmaDevice=1

#Instant Ring
ro.telephony.call_ring.delay=0
ring.delay=0

#LED Settings
ro.LED_KEYLIGHT_TEST=yes
ro.agui.single.mic=yes
ro.LED_COLOR_TEST=yes
ro.low_battery_led=yes
ro.battery_charging_led=yes
ro.miss_call_ledcolor=Red
ro.other_notifi_ledcolor=Green
ro.unread_notifi_ledcolor=Red
ro.incoming_ledcolor=Blue
ro.scridle_ledcolor=None

#Bluetooth Settings
persist.bluetooth.a2dp_offload.disabled=true
persist.bluetooth.bluetooth_audio_hal.disabled=true

Phone B is the Atom XL that I am using.

Inbound​

Calling from Phone A to Phone B​

Wifi​

Straight to Voicemail​

No Audio​

Inbound​

Calling from Phone A to Phone B​

LTE​

Straight to Voicemail​

No Audio​

Outbound​

Calling from Phone B to Phone A​

Wifi​

Call was placed​

Two-Way Audio; Able to place call with just wifi enabled, and with LTE enabled.​

Outbound​

Calling from Phone B to Phone A​

LTE​

Call was placed​

Two-Way Audio; When call was established LTE disappeared​
[Miscellaneous Android Development] grandmagoblin:
Forgot to include results of texting:

Inbound​

Text from Phone A to Phone B​

Wifi​

Never received​

​

Inbound​

Text from Phone A to Phone B​

LTE​

Never recieved​

​

Outbound​

Text from Phone B to Phone A​

Wifi​

Sent successfully​

​

Outbound​

Text from Phone B to Phone A​

LTE​

Sent successfully​

​
[Miscellaneous Android Development] SPHM900:
hi guys, i saw that the rom has been updated to android 11! thats awesome! is the DMR still broken with the fully flashed rooted rom?
[Miscellaneous Android Development] grandmagoblin:
I haven't had a chance to try it since I don't have anyone to try it with. I can say that the app boots up and is stable, and I have not had it crash or anything, but I have not been able to try the call quality or routing. I am working on getting another Atom XL to test with, so I will let you know when I test it.
[Miscellaneous Android Development] SPHM900:
if you live in the NY area i could help
[Miscellaneous Android Development] The_Anomalist:
where are the kernel sources?
[Miscellaneous Android Development] a-dead-trousers:
In a vault at meditek headquaters.

No, seriously, mtk doesn't want their source code to be public and therefore developers like unihertz aren't allowed to publish them (or need to pay extra to do so; I don't really know the details)

There are some source code pieces in the official android kernel repository but they are way too old and not being actively maintained:

https://android.googlesource.com/kernel/mediatek/

If you want to have sources of a kernel that is compatibel with some (many?) mtk devices, there are some to be found in the various GSI builds but I doubt those will support the DMR of the Atom XL or the FM radio chipset among other things.
[Miscellaneous Android Development] The_Anomalist:
Couple more questions. The link you provided. Could you find the source that works with or for your device and the 2nd question is how many people have been trying to decide for device?
[Miscellaneous Android Development] grandmagoblin:
I don't mind helping to figure out if another one works as well. As for the second question, what do you mean?
[Miscellaneous Android Development] The_Anomalist:
Is the community active? Any other ppl working on the devices?
[Miscellaneous Android Development] grandmagoblin:
I bet we could get more people involved. I am at least active. I have Atom XL and Atom L to test with. I plan to get another Atom XL to test DRM.
[Miscellaneous Android Development] The_Anomalist:
Well I'm down to help as well. I currently am building for many misc devices along with my OnePlus 8T. Check those source for me and see if they got something that might work. I'm currently at work myself so it will be a few hours before I can do anything
[Miscellaneous Android Development] grandmagoblin:
I will check when I get home or have free time. I am currently at work. I will let you know what I come up with.
[Miscellaneous Android Development] grandmagoblin:
Okay so, the kernel version currently running is 4.14.186. There is a 4.4 version. The only issue that we would be downgrading, and I don't know how the software will take to that or if this even the right choice. How would using a Android Common Kernel work? I assume there will be some feature unavailable, but what is the general impact of that? I am willing to custom design apps to tailor to an updated kernel, if necessary.
[Miscellaneous Android Development] The_Anomalist:
you got telegram?
[Miscellaneous Android Development] grandmagoblin:
So I tested, and you are able to message, but not use voice. I am still working on determining what could be the issue.
[Miscellaneous Android Development] a-dead-trousers:
As far as I know it should have something to do with USB and/or audio.

On A10 I was able to get it to work when "deactivating USB audio routing" in the developer settings. But it wasn't stable. Now on A11 I even had to tinker with A2DP and deactivate it to get bluetooth audio to work.

https://github.com/ADeadTrousers/an...mmit/c7a73e4dc7e55b12555c117634966a0834018eb5

I was only able to get this far and am not that good in system analysis especially what to look for. There are quite some errors and repeating warnings in the logs but nothing I tried seem to fix those (like selinux denies that I'm pretty sure to have added a corresponding allow for).

So every help is much appreciated.

Maybe you could also open up an issue on my github to keep track on your work.

https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL/issues
[Miscellaneous Android Development] grandmagoblin:
I submitted an issue on the GitHub to track it. Do you also want me to take a look into the camera issue? I also forgot to mention that the GApps Google Cam does not work and instantly crashes (it is something with the software itself not your build from the troubleshooting I have done). I am wondering if maybe some settings could be added to fix it.
[Miscellaneous Android Development] a-dead-trousers:
Thanks for your help.

I've only included google camera on my private builds and I don't think this could be fixed at all. As far as I know it's only useable on a Pixel phone. The only official version that should be working on other phones is 2.7.010 but that cannot be specifically included in A11 builds as it is only for max. A9. So no need for digging into that. Also as openGapps seems to be vacant I'm considering removing it anyway.

The other thing with the wrong resolution needs some help though

https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL/issues/13
[Miscellaneous Android Development] agarwaen163:
@a-dead-trousers I have been able to acquire a log from the time it boots to when it crashes. I think I see a good deal of permission errors. Honestly I see so many errors / warnings I'm not sure which is which so I'm just attaching the entire log. Please let me know if you'd like me to record with any different logcat options or anything. This is on the TEE versions following the steps I've mentioned in my previous posts.

Edit: I don't think this forum is allowing me to post the file? It attaches but never shows afterwards.
[Miscellaneous Android Development] a-dead-trousers:
As far as I know you need at least 10 or so posts in order to be able to upload files.

EDIT: You could use services like https://gist.github.com/ for uploading files in the meantime.
[Miscellaneous Android Development] a-dead-trousers:
Despite my first assumptions DMR is working great with the Atom XL and Lineage OS 18.1.

Only thing that needs to be done is deactivating "USB audio routing" in the developer settings.

My bad.
[Miscellaneous Android Development] clewis.it:
Awesome. Now that this is basically resolved, I would like to redirect things a bit. I for one don't want to be stuck on android 11. I have (finally) got the right process to upgrade to newer android GSI's. No patching kernels or disabling things you aren't already disabling (except I do use Magisk for some stuff, so root may be a deal-breaker for some users). I will document the process next time I upgrade.

Negatives:

1) the 2021-11 (Android 11) version of Intercom won't load. I have signed the app with the appropriate key (public keys for GSI's unless you build your own), and set the selinux tag for the app. Intercom will start, but continuously cycles through initializing and failed to initialize.

2) IR blaster doesn't work after the first boot.

3) FM radio is not supported.

4) TWRP doesn't decrypt with newer android versions, last time I checked. I don't know if this is still an issue since I restored the stock firmware last week.

5) Something is wrong with LineageOS based GSI's that breaks DNS services, so no internet access. AOSP ROMs that are not derived from LineageOS seem to work fine.

6) headset jack isn't detected correctly. There are some settings in the GSI that help this, though.

Positives:

1) the 2021-05 (Android 10) version of intercom does work. The only issue here is that you might get audio stuttering while the record PTT option is turned on. This is an intermittent problem I'm not sure how to resolve other than turning off the record feature.

2) VoLTE works, and I believe VoWifi also works.

3) Fingerprint works for app authentication (if you so wish).

4) Android 12 and 13 features. Possibly 14 soon.

If anyone has any ideas how to fix the negatives above, I would appreciate some assistance.
[Miscellaneous Android Development] a-dead-trousers:
@clewis.it

Most of the problems you describe for kernel 2021-11 come from the fact that it doesn't feature the "permissive" mode for selinux which many GSIs require to be present (at least in the beginning). According to official docs the "permissive" mode is a debugging feature and should not be included into official kernels. That might be the reason for unihertz to remove it.

You need to study your logcat to find missing rules.

Alternatively you could try to use the selinux rules from my repos. They were taken straight from the stock rom and should reflect everything needed (the resulting cil-files were almost identical).

I also did a little bit of tinkering though and was able to patch "permissive" back into the kernel. Four of five functions needed for this I was able to modify. The last one is only for status reports which should be irrelevant. If you want I can send you a guide to reproduce this.

Higher TWRP variants cannot decrypt lower encryptions. At least that's what I was told from the devs. Therefore I didn't bother to tinker with the variants for A12 and onwards.
[Miscellaneous Android Development] ljonkat:
Hi @a-dead-trousers, as always, thanks for the recent update. However, it seems that TEE ROM with June upates is in EEA folder and vice versa.
[Miscellaneous Android Development] grandmagoblin:
What GSIs are you using? I have found a lot of luck in TrebleDroid. I am working on seeing if I can get the Intercom App working. One of my Atom's is currently running Android 13. So far, I have not had any issues with internet access. I do agree with the other things, and I am willing to lend a hand with testing and experimenting.
[Miscellaneous Android Development] clewis.it:
Thanks for the reply. I have also modded the kernel to enable permissive mode as you mentioned, and I can confirm this allows the IR blaster to work, but that's the only thing it fixes, so hopefully that and the android 11 intercom can be fixed with your selinux rules. I will attempt to go through that, but I have only a 1% grasp on selinux.
[Miscellaneous Android Development] clewis.it:
I have used LineageOS (both the TD and legacy versions), crDroid, Derpfest, TrebleDroid AOSP, ArrowOS, basically anything that will flash. TrebleDroid AOSP, Derpfest and I think ArrowOS had no problems with internet. LineageOS, crDroid and a bunch of others all had DNS issues.

If you don't mind using Magisk and a slightly modified version of the Android 10 Intercom app, I can provide you the files that I use on mine.
[Miscellaneous Android Development] grandmagoblin:
I am open to anything. I have a couple of Atoms so I can test anything that will possibly brick too.
[Miscellaneous Android Development] clewis.it:
Ok, here you go then. 2 Magisk Modules.

Magisk-PhoneIcom_AtomXL_a10_03.zip: this one contains the Intercom app, the necessary libraries, the extmodule program, and some scripts to start extmodule on boot and enable or disable the necessary settings. Intercom has been modified to

- allow transmit up to 120 seconds

- allow longer contact, channel, and zone names

- extended frequency range (This is for the Armor 3WT, it causes a initialization loop on the Atom XL so stay between 400MHz and 480Mhz.)

- added 3rd digit in the channel number so it doesn't crash when you go past channel 99

- corrected frequencies in the US FRS/GMRS default zone.

Magisk_AtomXL_PTT.zip: This just has some scripts to handle the PTT button (even when the screen is locked) and send the appropriate broadcast to the Intercom app. Scripts are started on boot. Only if you want it, it's not necessary for Intercom to work.
[Miscellaneous Android Development] a-dead-trousers:
:oops:

Will be fixed in the comming days.
[Miscellaneous Android Development] a-dead-trousers:
Is now fixed.

:cool:
[Miscellaneous Android Development] agarwaen163:
@a-dead-trousers thank you for the link. Also congrats on the DMR sound!

I have been able to upload my boot loop logs here: https://gist.github.com/chancecardona/e10fbfe2f01048f582fd198c0b017ed2

Please let me know if there are any log settings I should apply. Also, if there is something that I may not have been wiping on installs (I followed the instructions in the wiki afaik).
[Miscellaneous Android Development] a-dead-trousers:
Can't see anything too suspicious.

Although there are some lines that might give a hint:

1) You seem to be using an older revision. "linker : CANNOT LINK EXECUTABLE "/system/bin/vtservice": cannot locate symbol ..." should be fixed by https://github.com/ADeadTrousers/an...mmit/1953275ee7939a97ed90d6956f62e681500214f3

As VoLTE seems to be initiating later on (but fails) this could a reason. Do you use a VoLTE enabled SIM? Try to boot without it inserted.

2) The repetiting errors regarding "MtkOmxVenc" could also hint a problem but I don't know what this is needed for exactly. It seems that this particular service is being started several times but always fails.

The data partition seems not to be the problem like I originally thought. Vold is running fine and also all of the lines in the log indicating the initialization of the encryption keys are there.

Did you by any chance include openGAPPS? If so, try to build the Rom without it. The binaries are rather old (feb. 2022) and might be not compatible anymore.
[Miscellaneous Android Development] agarwaen163:
Thank you so much for checking that out for me. Interesting. I have been running with no openGAPPs and no magisk for all of this (I figured I would add complexity when I got a baseline working). But notably I wanted to mention this process is with the official builds on your github too. I've been trying all of this using your official builds which is how I got that log output. I have also done it with my custom builds, but they had the exact same result. My last attempt was probably 2-3 weeks ago using the latest builds at the time. I will try again with the latest and report if it fixes the issue, but this has been pretty consistent so far.
[Miscellaneous Android Development] omairi:
Hello,

Does this rom works on the original atom ? The smallest one ?
[Miscellaneous Android Development] a-dead-trousers:
Nope.

Differnet kernel (drivers and so on) and binary blobs (vendor and system)
[Miscellaneous Android Development] agarwaen163:
@a-dead-trousers I have redone all of the install steps again (including reflashing stock too in another attempt), yet am still greeted with the same problem. Here is a github gist of my bootloop log using the 6/15 updated files (this log is from the locally built source code that was updated on 6/15, but I also tried with the prebuilt 6/12 binaries and they gave the exact same result). (No magisk, no GAPPs).

https://gist.github.com/chancecardona/f9428e5a8c1e2c78091536050f3ba2f9

I'm not sure what it could be at this point. Perhaps something isn't happening quiiiite right with linux reflashing the Stock ROM (that doesn't occur with windows?). It seems to flash correctly though.

Anyways, here's the gist, hopefully it can point us in a right direction.
[Miscellaneous Android Development] a-dead-trousers:
The last (repeating) errors seem to be centered around telephony. Have you tried to boot without a sim card inserted?
[Miscellaneous Android Development] clewis.it:
Hey all. I thought I would do a little something different today. I just discovered DSU Sideloader and thought I would document which GSIs work and which ones have issues. Interesting note, some GSIs behave differently when installed on the system vs. when they are installed as DSU. I will come back and update this post every do often as new GSIs are released.

DSU installations

crDroid: boots, but can't access the internet.

Derpfest: boots and works fine.

Evolution X: boots and works fine.

LineageOS "Light": didn't boot, reboots to recovery.

Pixel Extended: boots internet works, capacitive buttons do not work.

SuperiorOS: boots and works fine.

YAAP: didn't boot, stays on boot animation.

System installations

crDroid: boots, but can't access the internet.

YAAP: boots and works fine.
[Miscellaneous Android Development] agarwaen163:
I tried that (Edit: "that" being actually inserting a sim card) and it worked!

I have been running the 06/12 official build as my daily for ~1 week now, and it is running very well. The sim card error experienced earlier is an interesting edge case though for the install. I will experiment more and report on if the crash is only during initial bootup or what. Anyways, nice work!

Next will be experimenting with the upgrade/restore process as they come and maybe getting magisk in too to experiment if needed.

I tried Intercom with another DMR and the PTT definitely... did something (modulated it very loudly, nothing else came through). Still figuring out if user error or current limitations of development. Getting more app dev/debug stuff setup.
[Miscellaneous Android Development] kingbeandip:
My wife recently bought an Atom XL to install Lineage on. She got it installed, carefully following the github instructions, but the right half of the touchscreen doesn't work. She went back to the stock OS, hoping it would fix it, but it didn't. We've been working in our free time for a few weeks trying to figure out how to fix the touchscreen. As far as I can find, it has something to do with the super.img file. Anyone know how to fix it?
[Miscellaneous Android Development] a-dead-trousers:
nope, never had that happen.

Maybe a newer hardware model which requires updated drivers in the kernel?

What stock OS version was on the phone when you bought it?

If it was 20221215 (L EEA), 20221214 (L TEE) or 20230110 (XL EEA & TEE) that means it was indead using the latest stock rom.

If you're willing to try you could use my branches to build LOS with the newest stock rom

https://github.com/ADeadTrousers/android_device_Unihertz_Atom_XL_TEE/tree/stock-2023-01

https://github.com/ADeadTrousers/android_device_Unihertz_Atom_XL_EEA/tree/stock-2023-01

(Simply change the contents of roomservice.xml accordingly)

In conjunction with the latest stock rom for the file extraction of course. But be aware that the Intercom app won't work with this one. Also you might need to create a suitable super.img yourself.

Everything you'd need should be part of my documentations

Other than that you could try an older stock rom release instead and see if the touchscreen is working or not.
[Miscellaneous Android Development] PaulMoore24:
Hi folks

Sorry to jump over the thread, but I'm hearing some people claiming they're running A13/A14 on the Atom L with various GSI/AOSP roms.

Can I ask... how? I can't find any guides (apart from a-dead's L18.1).

From what I can see, it should be as simple as replacing the system.img with a custom rom and flashing with Mediatek's flasher. Is that right?

Any help would be much appreciated.
[Miscellaneous Android Development] feanor_twh:
I tried to install the system and ended up with a bootloop. Then I tried to reinstall the original firmware (downloaded from XDA Firmware) with SP Flash Tool and I got the brick. At this point I don't know what else to do, can you think of anything? I almost think I've lost the device.