crazy-marvin / morse Goto Github PK

This issue is for getting an overview of uploads from third parties to Google Play and similar platfroms.

• https://play.google.com/store/apps/details?id=com.morsecodealphabet.englishtomorsedecoder
• https://play.google.com/store/apps/details?id=com.appntox.morse
• https://play.google.com/store/apps/details?id=com.translatingmorsecodealphabet.englishtomorsedecoder

Hi There,

Would you like to add "id" folder in /fastlane/metadata/android so I can help you to translate it into Indonesian.

Like the title says. Play did a security update an hour ago, 1800UTC. No updates pending in F-Droid or Play Store. Wouldn't have caught except I was about to use my phone when I saw the update notification. For whatever reason, Play Store update notifications aren't persistent like the other apps.
What's really going on with this app?

java.lang.RuntimeException: Unable to start activity ComponentInfo{rocks.poopjournal.morse/rocks.poopjournal.morse.MainActivity}: java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.

This feedback came in:

Hi,

Some feedback on the excellent Morse app.

Everything is fine apart from the torch flashing. If I type in 'SOS', for example, the app flashes 6 long dashes with no discernable difference between supposed dats and dits, i.e. no dits.

The front screen flashing is perfect.

This app could literally be a life saver in a rescue situation if stranded in remote territory. The torch flashing would be a great way of attracting attention and sending a help message to say a rescue aircraft. Or at sea at night. Great idea.

I am using a Samsung Galaxy S7 edge. Android 8.
Regards

The torch flashing seems to be working correctly on other devices though, for example the Galaxy Tab of the same user:

I just tried the v 1.5 app on my Samsung Galaxy Tab A 10.05 (2018) and the torch is working OK

If anyone experiences the same issue (or not) please comment here.

Android 13 introduced the option for users to set a per-app language preference. It would be nice if we could support this too.

I try to convert digits to Morse code in this app, but the app doesn’t responce them. I used your Morse app v1.4 from F-Droid.

Here is the Morse code for mumbers:

0 -----
1 ·---- 
2 ··---
3 ···--
4 ····-
5 ·····
6 -····
7 --···
8 ---··
9 ----·

See: https://en.wikipedia.org/wiki/Morse_code#Letters,_numbers,_punctuation,_prosigns_for_Morse_code_and_non-English_variants

The user can mark (clicking on the ⭐) phrases and they get saved in the Phrasebook (something like the history in Google Translate)

I updated from 1.5 to 1.6 today and the flashlight button just flashes one long flash without doing anything more. But I thought the previous version 1.5 functioned correctly on off on off, etc, etc. I think my android version is 9.1.

The app highlights the features of the app at the first startup.

Possible third-party libraries:

• https://github.com/Senth/MaterialShowcaseView
• https://github.com/deano2390/MaterialShowcaseView
• https://github.com/ECLaboratorio/BubbleShowCase-Android
• https://github.com/TakuSemba/Spotlight
• https://github.com/erkutaras/ShowcaseView
• https://github.com/canopas/Intro-showcase-view

No use of a third-party library is preferred

Description

When the output reaches a space (represented in the program as a slash) it makes the screen become white indefinitely. You can only solve it by manually closing the program and opening it again, but then your message is lost and you have to recreate one without spaces.

Steps to reproduce

1. Type any message that contains a space (such as "a a"; or even something as simple as a single space " ")
2. Click the screen flash button
3. Observe that the screen is white indefinitely.

Expected behavior

According to Wikipedia and the various other Issues raised, there is a mandatory gap between dots and dashes as follows:

1. The length of signal absence (gap) between dots/dashes is the length of a dot. (In the code, I think this should be structured as a separate variable not linked to the length of the dot's flash)
2. The gap between letters is equal to a dash (meaning 3 dots). (Once again, this variable should probably not be scaled based on the previous item's variable)
3. The gap between words (AKA a space) is equal to 7 dots.

Therefore, the space (represented as "/" in the program) must be a mandatory pause that does not activate the screen and should have the same time as seven dots.

Ideally, the user should be able to control the length of signal absence between ditdah, letter, and word.

Tech info

Device: Any Android device or emulator

Additional context

I think it would also be nice if we could change the color that gets projected through the screen using a color picker, so I could set it to red RGB (255,0,0) and it wouldn't be so hard on the eyes. I had to use the screen flash mode because the flashlight mode is buggy and doesn't have a gap between dots and dashes, causing every letter and every word to be one long dash.

It is possible to paste something from the clipboard into the text field but pasting something into the Morse field is not available.

Pasting possible:

Pasting not active:

https://en.wikipedia.org/wiki/Russian_Morse_code#Table_&_Melody

Every UI element should be described for TalkBack users

First, thanks for this useful and open source application. 🙂

Maybe it would be interesting to add the possibility of translating into Morse thanks to the smartphone's flashlight, in addition to the sound translation, if possible.

Direct audio input of Morse signals via microphone leads to a transcription

Link collection:

• https://gerolfziegenhain.wordpress.com/2013/05/20/morse-decoder-test-iphone-ipad/
• https://www.qsl.net/ah6rh/am-radio/morse/itouch-morse-decoder.html
• https://github.com/drid/morse-audio-decoder
• https://morsecode.scphillips.com/labs/audio-decoder-adaptive/

https://www.quora.com/What-are-some-of-the-most-famous-Morse-code-messages

• App crashes when switching to landscape mode.
• Video:

The font size is very tiny, this makes it hard to read text or Morse code.
Please make the font size bigger or include an option for choosing the font size.

This passage in your readme is totally incorrect:

Since people rarely communicate via telegraph, nowadays there are very few people who can memorize Morse codes. Instead, it has become a way to encode something or special characters for special purposes. Of course, these special characters are still widely used in many situations, you don’t know when you are going to really need it. 

Excuse me? Where is this known? Cite your source. As an amateur radio operator (my call sign is my username), I find that the developer is either totally ignorant of CW (NOT the broadcast TV network) and its current use today, or 2, not a licensed ham.

I am concerned regarding this as a licensed ham, where ham radio is a dying art... but we need to keep the hobby alive. What would happen if the cell towers went down? Hams provide help. Please, I extend a plea to find a ham radio club and get your license. You can start with http://www.arrl.org/find-an-amateur-radio-license-exam-session and it's $15. Morse code is not required for any test now, but still is alive and well. Morse code is still used on QRP (low power) HF communication.

CW (Morse code) is not cryptography! FCC Part 97 prohibits any cipher or other obfuscation to hide the meaning of your transmission.

Please fix your README.MD. The information is totally wrong regarding Morse code.

73, W9JYD

It may be nice to have some sort of CI/CD for Morse, maybe using GitHub Actions, Fastlane, Gradle Play Publisher or something else.

The last sound on a sequence is not played. E.g. SOS shows . . . _ _ _ . . . but only plays back . . . _ _ _ . .

In the meantime I add an extra E to the end

✍️ Describe the bug

Tablet has haptic feedback, no torch…
Crash result inconsistent. Closes by itself but sometimes android has "not responding" even with screen flashing behind message, a "mistaken" crash?

💣 Steps to reproduce

Perhaps selecting both options screen/torch can trigger it.

🔧 Expected behavior

It does pause a bit if I hit torch while screen flashing

📱 Tech info

• Device: Lenovo TB-X505F
• OS: android 10
• Version: v2

📄 Additional context

Screen and torch buttons are close together, can hit wrong one

This feedback came in:

The dats and dits are clearly of different lengths. Maybe the dits could be a bit shorter?

What do you think of that proposal?

Hello, I maybe found a bug when using this app.
Just click the place shown in the picture below for several times, and the bug will be triggered.

Here is the error message:

java.lang.NullPointerException: Attempt to invoke virtual method 'void android.hardware.Camera.release()' on a null object reference
 	at rocks.poopjournal.morse.MainActivity.lambda$setKeySelectedForTelegraph$25$rocks-poopjournal-morse-MainActivity(MainActivity.java:1267)
 	at rocks.poopjournal.morse.MainActivity$$ExternalSyntheticLambda9.run(Unknown Source:2)
 	at android.os.Handler.handleCallback(Handler.java:942)
 	at android.os.Handler.dispatchMessage(Handler.java:99)
 	at android.os.Looper.loopOnce(Looper.java:201)
 	at android.os.Looper.loop(Looper.java:288)
 	at android.app.ActivityThread.main(ActivityThread.java:7898)
 	at java.lang.reflect.Method.invoke(Native Method)
 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

I think maybe in somewhere the field camera is assigned to null before the Runnable posted in MainActivity#setKeySelectedForTelegraph executes.

Review on Google Play:

I have but one greivance. It dosen't add the / , so everything I type is one word. You gotta put the slash inbetween. Example: "hello world" .... . .-.. .-.. --- / .-- --- .-. .-.. -.. "helloworld" .... . .-.. .-.. --- .-- --- .-. .-.. -..

If this app could be able to convert a punctuation to morse code or vice versa, this app can present not only a simple phrase like SOS or Hello World but also a complete sentence.

This feedback came in:

I used to be a radio ham 50 odd years ago and still use Morse in my electronic projects (search Deodorino). Lately I've been aware that a few of my acquaintances have unfortunately suffered strokes leaving them with speech problems. With this in mind, would it take much to add to your excellent project the facility to generate Morse by tapping the screen?
[...]
As for tapping the screen, we used to send Morse code by pressing a switch ( Morse 'key') which was connected to the transmitter. If you pressed the switch the transmitter was 'on' for as long as you pressed, so by pressing for short and long periods we sent the codes. On a mobile phone screen it would be necessary to switch on the screen, led, or speaker tone whenever there was finger contact. The sender adjusts the speed automatically in this case.
[...]
The amount of time the finger is in contact with the screen would determine whether a dot, dash, space etc was intended.

I think this video shows it quite nicely.

Hi, it would be great if you added a screenshot in README.md so people can see what does the app look like.
I honestly find it looks great, it is unfortunate to not show it!

Try the whistle in Trail Sense to see what I mean

This feedback came in:

[...] can I suggest that there be two screen flash modes:

1. as it is now, whole screen flashing,
2. just a small area at the top of screen, say 1cm^2 or 2cm^2.

I found the whole screen flash difficult at close range, but it would be OK over a distance. I seem to recall that the eye is most sensitive to yellow/orange light, as in the sodium lamps on the roadside. [...]

(I'm using 1.5 from F-Droid. Sorry if this is fixed in 1.6; that's not on F-Droid at the moment.)

As far as I can tell, there are no pauses between letters. For example, if I enter "ssiii" and then press the screen-flashing button, my screen flashes 12 times and I can't discern any variation in timing.

Even if there is some variation I'm not able to perceive, I'm sure this is wrong, both based on my (extremely limited) experience and based on some reading. See for example this Wikipedia section on Morse code timing or this random other page. "ssiii" for example should look like this (= represents a beat spent on, . represents a beat spent off)

=.=.=...=.=.=...=.=...=.=...=.=

What I am observing from the app is more like this:

==.==.==.==.==.==.==.==.==.==.==.==

(There is a similar issue when I press the speaker button instead of the screen-flashing button, but it is compounded by a second bug, which is that the audio seems to cut in and out at the wrong times.)

When I installed and opened the app, it keeps on crashing.
Device: SM P555
Achitecture: Armeabi v7a
OS: 7 Nougat

Google introduced a new icon technique starting with Android 13 and higher called Themed Icons.

⚠️ Is your feature request related to a problem? Please describe

Not a problem, an application. I have used ToneDef for automated output, your app seems to be a neat way to do it as well, but, that type of output would not be useful to most people, so I am going to ask about sending phrases.
Examples:
"How are you?" "Nearby" "yell out" "come back" "go home" "don't do it" "proceed"
"Check on them" "[keep/toss] it" "something's up" "go get it" "seen that before" "take a break" "look back"

💡 Describe the solution you'd like

Requirements.
I cannot read the code I will be sending so a description field is needed (e.g. Travis's Callsign). The code I may use could be just Ts and Es.
I would like to adjust the speed.

📊 Describe alternatives you've considered

Can't think of any other app or way…

📄 Additional context

The installed phrases as a scrollable list. The automated output idea was to communicate with a machine, so pushbutton-like trigger for code output.

🙋 Do you want to develop this feature yourself?

• Yes
• No
• no idea how, got a tutorial? I'll decide afterwards.

Fix the error warning reported by gradle :app:lintDebug

The character Ñ does not translate to Morse.