yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] clewis.it:
I found workarounds for these 2 issues now.

Hardware PTT button

Take a screenshot of the Intercom screen for later use.

Install Key Mapper from either Play Store or F-Droid.

Add a new item.

On the Trigger screen, tap the Record Trigger button then press the PTT button.

Tap the 3-dot button on the new trigger and change the click type to "Long Press".

On the Actions screen, click the plus (+) sign.

Move to the "Tap Screen" option.

Tap "Select Screenshot" and choose the screenshot you took earlier.

Tap the location on the screenshot where the PTT button shows, then tap "Done".

Now, tap the 3-dot menu and check the "Hold Down" box, then tap Save.

On the "Constraints" screen, tap "App in Foreground", then select the "Intercom" app.

Tap the save icon (looks like a floppy disk in the bottom right corner).

Auto Start /system/bin/extmodule

Llamalab Automate can start the extmodule. It does require the separate superuser module.

Install Llamalab Automate from the Play store and also install its superuser module.

Create a new flow.

Add the Receive Broadcast block. Set the action field to "Boot Completed"

Add the Shell command superuser block. Set the comand line to "/system/bin/extmodule"

Optional: Add the Toast show block and set the message to "Extmodule started".

Link those blocks together in order and then loop back around from the bottom block to the Receive broadcast block.

Go to the Automate settings and enable the "Run on system startup" option.

Notes:

Remember to grant the appropriate permissions when asked, otherwise these may fail to run. Also, remember that the PTT workaround requires the screen to be on and the Intercom App in the foreground with the Intercom tab showing. Otherwise, it's just activating that portion of the screen on whichever app is currently showing. You may want to add an item to Key Mapper to start the Intercom app with a short press of the PTT button.

If anyone has a better solution for the PTT button, please feel free to post it here.
[General Questions and Answers] radiomean-uk:
Hi,

I am an active UK Radio Ham and bought this phone around 10 months ago, partly because of its enormous battery but also because it has the two-way FM and DMR radio built into it.

I've been very interested to follow this thread. I have used the phone/radio via a 70cms FM repeater but I was disapointed that the DMR capability was very restricted - not true 2 time slots so you can't use it through a DMR repeater.

So - if it can transmit on 2m as well as 70cms that is great, and I wonder if it actually has 2 TS capability?

I am reasonably familiar with hacking iPhones (jailbreaking etc) but have not hacked or rooted Android. I'd really appreciate pointers or links to tutorials to root this phone (if necessary), get the right OS on this phone and get this modified intercom app on it! I have a couple of handheld FM/DMR radios (and also power meters, antennas etc) so I can easily test if the phone is working...

Advice would be much appreciated. The 3WT is my backup phone and has seen very little use so I don't mind risking it to flash ROMs or whatever!

Many thanks, Bill
[General Questions and Answers] clewis.it:
Well, the time slot issue is something different entirely. The Intercom app obviously supports it since this comes from the Atom XL. There is something else telling it that time slots are not supported. It could be in the /system/bin/extmodule program, or in the radio mcu firmware files in /system/data/mcu/. I have no idea how to do anything with those files. I doubt that it is a hardware function, though I could always be wrong about that.
[General Questions and Answers] radiomean-uk:
Hi again and thanks for the reply...

I have done some searching and found all the programs I need, but I would appreciate a bit of advice...

I have the Androld 10 GSI (generic system image?) lineage etc. I have adb minimal tools etc. I have unlocked bootloader on the phone but when I reboot the phone to fastboot mode I lose connection and in device manage the phone is not recognised... Nothing happens when I issue 'reboot' command or try to flash the new image.

Advice would be appreciated! Sorry if this is a bit of a simple question...
[General Questions and Answers] clewis.it:
I'm guessing you have a Windows computer. You probably need to install the drivers for the phone. You might also try using a different USB port on your computer. USB communication with this phone and windows is a bit touchy.
[General Questions and Answers] radiomean-uk:
Hi and thanks again. I have both Windows and Mac but use Windows for preference.

I am making progress and have flashed the phone to Lineage 17.1 (I bricked it once but reflashed it to stock with SP Flash tool so I am learning!). I am trying to install TWRP but I don't think there is a custom TWRP for the 3WT?

Do I need to root it?
[General Questions and Answers] radiomean-uk:
Hi, final question - what to you use to flash the Magisk-PhoneLcom file (Magisk)?

Have you installed TWRP (as far as I can see there is not a TWRP for this phone?)

Thanks!
[General Questions and Answers] kaziq:
There is an unofficial TWRP. I think it's this: https://www.mediafire.com/file/q7sw9pxob9fadxv/Armor_3W_331.rar/file

This flashing instruction seems fine: https://unofficialtwrp.com/ulefone-armor-3w-root-twrp-3-3-1/
[General Questions and Answers] radiomean-uk:
Many thanks!

I have aslo found the TWRP that is on the first page of this thread, and have sucessfully flashed that to my 3WT. As it says, the touchscreen does not work but a mouse works fine. I plan to root and install other stuff this evening!

The Orange state disabler (in the archive) should also be useful to stop the warning splash on boot!

Cheers, Bill
[General Questions and Answers] radiomean-uk:
Hi, I've got lineage running, rooted sucessfully etc...

I am contemplating putting a copy of HavocOS on it instead, but I'm not sure what the 'a only or a/b' device issue is. Could someone please expalin briefly, and tell me what the 3WT is...

Cheers all again...
[General Questions and Answers] radiomean-uk:
This was caused by a driver... I needed to install another driver when in fastboot mode.
[General Questions and Answers] clewis.it:
I have a new update to the Intercom app. Found the latest firmware for the AtomXL and pulled the intercom app from there, added my mods and dropped it in the magisk file. This version fixes the CTCSS display on the Intercom tab, and keeps the CTCSS code when you edit a channel. In addition, device area has become zones and there is a low power exit option as well as a prompt to exit or put Intercom in the background when you press the back button. (I hope that last one becomes optional.)

As always, this software is experimental and I take no responsibility for any issues. Use at your own risk.
[General Questions and Answers] kaziq:
I'm not an expert in this, but I think some devices have two partitions for system image (A/B): system is always running from one of them, and OTA update is flashed to the other one. On reboot after update the newly flashed one runs, and if it doesn't boot, the bootloader (or recovery?) switches back to the partition with the working system.

"A only" devices are those with only one partition, so if the update does not boot, you're doomed.

3W and 3WT are A/B (ARM64).
[General Questions and Answers] clewis.it:
I found a solution for the PTT button that I'm happy with.

I'm only using Llamalab Automate now. I will upload the flow here. It still requires superuser permission to start the extmodule service, and an accessibility permission to monitor the button press. The button press activates immediately, so it works more like a traditional walkie talkie, too. The only remaining issue is that it won't work when the screen is off. If anyone finds a fix for that, let me know.
[General Questions and Answers] radiomean-uk:
Hi,

a) Many thanks for all the advice (A/B etc) and great work on the Intercom app!

b) I have sucessfully rooted the phone and flashed Lineage, Havoc and Bliss (can't find an Android 10 for Bliss).

(Does anyone have any suggestions for other ROMs please?)

c) However I am having an issue with the intercom that I remember from nearly a year ago when I first got the phone... I launch the app, and after about 20 seconds get the message from the 'init channel' screen - 'init failed - device init failed, please start again'.

I remember having this problem a year ago on the stock firmware but I can't remember how I fixed it! I have tried clearing app data and cache but no change...

d) I should add that the intercom app worked fine once I had sorted this problem out - but I can't remember how I fixed it a year ago!

All suggestions appreciated (I might reflash with stock and see if there is any change...)

Cheers all!
[General Questions and Answers] clewis.it:
There is a program that needs to be running before intercom starts. It is /system/bin/extmodule. It needs to stay running, otherwise intercom will fail like that.

You can do this manually by opening a terminal emulator app and issuing the following command:

su -c /system/bin/extmodule

Grant root permission, then you should see a few lines saying it is listening. Tap the home button, then open Intercom. Now it should work.

You can use Llamalab Automate to do this automatically on each boot and it will also handle the hardware button. Download and unzip the flow file that I posted yesterday. Install Automate. In Automate, tap the 3-lines at the top left corner, go to settings, and check the box that says "Run on system startup". Go back to the main screen and tap the 3-dots in the top right. Go to import, then choose the "Intercom PTT.flo" that you unzipped earlier, then tap the import button. (If the list doesn't update, exit and reopen Automate.) Now, tap the "Intercom PTT" task, then grant the superuser and accessibility permissions. (It will need to download the "Automate superuser permissions" app from the play store.) Now, tap the Start button, and you can exit Automate. The next time you reboot, extmodule should run automatically.
[General Questions and Answers] radiomean-uk:
Hi again,

Many thanks for this again... I have my phone successfully rooted with Lineage and I've installed the latest version of your modified Intercom app. I have a couple of problems...

a) there is no audio. I have other handheld transceivers andthe squelch opens when I TX, but there is no transmitted audio. And there is no received audio either (I have also tested simplex)

a1) however, the CTCSS tone is transmitted because a local 70cms repeater is successfully opened.

b) if I try to put a frequency in the 2m band in (say 145.575) - I am in the UK - this is not accepted.

c) I have remembered to grant microphone and storage permissions...

Any advice gratefully received!

Cheers, Bill
[General Questions and Answers] clewis.it:
Enable developer settings on your phone. Find the option to disable USB audio routing and turn it on. That should fix the speaker output.

Intercom will not let you enter frequencies outside the range of 400-470 MHz. You can use a SQLlite editor to change the frequencies in the database after you have created an entry and the program will not verify it. It is great for listening, but I still don't recommend transmitting with the phone on the 2m band though. The power output is not consistent at those frequencies, it gets lower the longer you transmit. I don't know if this will damage the transceiver or not if transmitting for extended periods of time, but it makes carrying on a conversation nearly impossible.
[General Questions and Answers] radiomean-uk:
Hi again... well. it's all working thanks again. The only minor issue is the Automate does not seem to run the su -c command on my phone. I've used SManager but that also does not seem to run at boot, but it's a minor issue.

I have yet to edit in some 2m channels...

Just out of interest, are you in the US - as you mention 220 MHz?

Cheers again.
[General Questions and Answers] clewis.it:
Did you install the Automate Superuser module? Did you grant superuser permissions in Magisk? Are you using the latest version of magisk? According to the changelog, Magisk 21.4 fixes a problem with su -c commands. Are all the permission boxes checked on the Automate flow?

You are correct, I am in the US.
[General Questions and Answers] radiomean-uk:
Hi again, where in the filing system is the db located, so I can edit the channels please?

Cheers!
[General Questions and Answers] clewis.it:
/data/data/com.agold.intercom/intercom.db
[General Questions and Answers] radiomean-uk:
Hi there, that hit the spot!

After puzzling about permissions, I copy the file, edit it on a PC and save it back to the phone.

Opens a local 2m repeater about 15 miles away. Impressive!

Thanks again...

PS I note in the DB that there are two very interesting columns 'slot send' and 'slot receive' - not had a chance to test them out. There is a local DMR repeater only a couple of miles away on 70 cms...

PPS I will also try measuring the power my 3WT puts out.
[General Questions and Answers] clewis.it:
Yeah, I saw the slot options too. As far as I can tell, they don't do anything for our phone. But, I still haven't received a sample record from anyone on the Atom XL, so I have no idea if I'm using those settings correctly.
[General Questions and Answers] clewis.it:
OK, on to the next project. I'm working on building the latest TWRP so we can hopefully install Android R with Magisk. Any ideas on how to get the touchscreen working?
[General Questions and Answers] radiomean-uk:
Hi again, I have one final question about editing the intercom database... It seems that if I alter the number of lines in the intercom.db file from the original 152, the program hangs and won't initialise the intercom. Is this right? I currently have 148...

Cheers again.
[General Questions and Answers] clewis.it:
I have seen that happen. You should add your channel within intercom first with frequencies in the accepted range. Then you can edit in a separate program. Also, make sure the last area and channel number that you had active in intercom still exists. If you can't get back to the way you had it, you might have to clear cache and data in the app settings and start over.
[General Questions and Answers] radiomean-uk:
Hello again.

I have contacted Uniherz about the Atom XL and they have kindly sent me both a user manual and the 'intercom FAQ'. The FAQ explicitly mentions double slot and repeater modes, and I've also seen in the channel DB a mode setting. I reckon it is at least plausible that the 3WT supports 2 slots and repeater mode - and the FAQ is attached for people to look at, if they are interested!

All the best.
[General Questions and Answers] artarts:
Hello Everyone,

I'm an owner of this model (3WT) for the last month and have come up with some issues I don't know everyone is having and didn't find any metions of it.

GPS gets a fix but looses it. Waze keeps recalculating all the time. GMaps does almost the same but stops, hangs longer, and then does its thing. Lets say a good fix doesn't last more than 5 minutes, may take more than a minute to get back. I have noticed that other GSM and Wifi signals do change its behavior, making it longer to get a fix back when present.

Wifi download is terribly slow. Upload not so bad but also below other devices on the same network. Using SpeedTest app, while on other devices on the same network we get an almost constant speed with a steep rise on the begining but on the Armor it does more like a curve never getting as high as other devices and also doing a slop only at the begining but droping intensivily towads the end. Very strange. I have also noticed that my router running OpenWRT (19.07 on an old Linksys e4200v2) also has trouble to list it as a connected device. Something showing the MAC address as 00:00:00:00:00:00. It appears to kick the Armor out every now and then due to this. I keep a 2.4Ghz network with the same info as the 5Ghz network, it NEVER uses the 5Ghz band, it's prefering the 2.4Ghz for some reason. Scanning apps do show it can see the 5Ghz band.

I have added a Micro SD card as Internal memory and as mentioned on other threads, it doubles it's size and show as if it has been half full already.

I bought this phone willing to use it as a portable radio but as for now none of my efforts have showed benefits for this feature. The APP takes too long to load (Init channel message) and also looses precious microseconds when pressing PTT almost makeing it useless.

Device performance overall is not bad, I enjoy using it, but I now know I will have to relay once and again on this very powerfull group here in XDA if I wish to get best out this unit.

My build number says:

Armor_3WT_RF1_EEA_V02_20200903-1048

My intercom app shows:

MCU: 20181221151755

DMR: ver0.5.4_470_TONE

v2.0

Thanks a lot everyone.
[General Questions and Answers] clewis.it:
Hi again.

Unfortunately, at this point in time, this is just wishful thinking. While the Atom XL does indeed support DMR time slots, and the Intercom software certainly has support for it, our phones do not. I doubt that this is a hardware issue, it's more likely to be a DMR firmware limitation.

Now, thankfully, a dev called ADeadTrousers was able to find the build.prop settings in the Atom XL that tells Intercom that it's an Atom XL. So, I set that on my phone and the time slot settings actually appear and populate. Unfortunately, it also changes the way Intercom talks to the hardware. The radio will not initialize, it just gets stuck in a loop. I have also tried loading the MCU firmware from the Atom XL into the Armor 3WT and it still doesn't work, it continues the initialization loop. And finally, since I was at least able to populate the database entries correctly after setting the build.prop flag, I reloaded the old firmware for the Armor 3WT and removed the build.prop flag. The radio works again, but does not use the time slot settings in the database. Brandmeister Last Heard still shows me transmitting on both time slots.

So, unless Ulefone provides a dual time slot update, or if someone knows how to modify the MCU/DMR firmware on our phones so it acts like the Atom XL, I believe we are stuck with this.
[General Questions and Answers] bYOndo:
hello everyone! I have this funny phone since it was on the market, I love it for its ruggedness, the infinite battery, the loudspeaker and the Intercom feat

Let me summarize this post: we can confirm that now this phone (Ulefone 3WT) can be rooted, upgraded to LOS (I'm fine with that rom) and Magisk and has a working walkie talkie app (thanks @clewis.it ), can we?

I'm not a radio amateur, but I'm using normal walkie talkies along with this phone and I'm perfectly fine with that use.

Thanks to everyone!

Massimo
[General Questions and Answers] energeiakos:
Hi all, I am between buying the ARMOR 3WT and the Armor 9. These are the main differences:

Battery: 10300 - 6600

RAM: 6 - 8

GPS: 3WT does not have the European Galileo

Price: 320 Euros - 500 Euros

What do you suggest? Actually, I am all about the Armor 9 but I am afraid about its battery. I don't want to think about charger or power bank between morning and night. What do you think? 3WT has gps problems in Europe? I often hike, so maybe Galileo will be useful?
[General Questions and Answers] kaziq:
I have 3WT and live in Europe - no GPS problems at all.
[General Questions and Answers] bYOndo:
I live in Italy, GPS works very well. I don't know Armor 9, but 3WT's battery is a big point of strength. You have to deal with a phone not so "stylish" nor lightweight, but OTOH you have 3 days from a single charge 😉 it's a trade-off...
[General Questions and Answers] chacho_2me:
hi guys. does anybody knows how tp detect frequencies on the radios we used? i can only see channels but not the frequencies. maybe any app or a work around?
[General Questions and Answers] Hell-dragonne:
Hello

I am new and I do not know much about it, but I have 2/3 questions.

I have a 3wt.

is it possible to have another application that manages the intercom?

Is there a frequency scan function in development?

sorry for my English
[General Questions and Answers] clewis.it:
Unfortunately, I don't think there is any possibility of a scan function for this phone. Whenever any change to frequency, talk group, squelch tones, etc. are made, it has to write those changes to the transceiver module and verify them. It takes about a second to write those changes and give control back to the intercom app. Scanning would be painfully slow.

I dont know of any other apps that run this transceiver. I can't find any information about what chipset is used here. They say it is DMR007 on the website, but I can't find anything about it.

Perhaps if someone slightly more skilled than I am is willing to disassemble the phone, they might provide more information.
[General Questions and Answers] clewis.it:
Well, I guess it helps to understand how GSI's work. It turns out that most of the Android R GSI's work just fine. The reason I wasn't able to mount system after booting the ROM's is because the system partition needed to be resized after flashing. It seems to work great now.

In any case, I was able to build an updated version of TWRP. This also includes the changes to allow the Magisk APK to be flashed without renaming it to a zip file. This new version of TWRP registers as a new device, though, so your existing backups will have to be moved to the new folder in order to see them.

TWRP device tree is here:

GitHub - clewisit/android_device_ulefone_Armor_3WT

Contribute to clewisit/android_device_ulefone_Armor_3WT development by creating an account on GitHub.

github.com

Additional good news is that the Intercom module still works in Android R. Unfortunately, Magisk does not appear to work on most ROMs. If anyone can assist in converting the magisk module to a flashable zip, that would be appreciated.

The only problem I have seen using Intercom on Android R is some audio stuttering when audio starts playing. This appears to be related to data storage. I was able to minimize this by changing the IO scheduler to noop and increasing the cache size to 256kb for both internal and external storage. I used SmartPack Kernel Manager to do this, but you can probably use any kernel manager. You might also try disabling PTT Record from Intercom Settings.

I have made a couple of extra changes to the Intercom software, also. It will now allow you to enter any frequency between 100Mhz and 470Mhz. I still don't recommend transmitting outside the UHF Amateur radio bands. I have no idea if it will break anything, and take no responsibility for any damages. As for the Magisk Module, I ended up removing a bunch of files that are unnecessary.

Recovery image and Intercom magisk module are attached. Remember, this version of Intercom only works on Android 10 and higher.
[General Questions and Answers] andrey bobylev:
Спасибо.

*************

Mod edit - translated:

Thank you.

-----------------

@andrey bobylev XDA Forum Rules:

Spoiler content hidden.
[General Questions and Answers] clewis.it:
Well, this has been a good run, but the DMR transceiver on my phone has kicked the bucket today. It still receives, but transmit has no power. Anybody got some leads with Ulefone on getting replacement parts?

As an alternative, I am also interested in the AtomXL and Runbo E81 phones.