chooloo / koler Goto Github PK

Describe the bug
When ever I make a phone call on the app and during the phone call I make use of the the dial pad, I now try to go back to the call in progress to hang up I can't cause the app just stays same even after pressing the back button.

To Reproduce
Steps to reproduce the behavior:

1. Launch the app
2. Click on any number to make a call
3. During the call click on the dial pad,
4. Now try to go back to the call in progress to be able to hang up

Expected behavior
I expect the app to go back to the call in progress so I can be able to hang up the call.

Smartphone (please complete the following information):

• Device: [infinix s2pro]
• OS: [Android 7.0]
• Version [Version 0.3.1 ]

Expected behavior

To successfully refresh an empty page.

Actual behavior

Refreshing an empty page crashes the app.

How to reproduce

• launch Koler
• Refresh the Recent page if it's empty. If it isn't, delete any call history, and then, refresh.
• Watch the app crash.

Browser/App version:

Koler v0.27

Operating system:

Android 0

Recording Of The Bug

Logcat

2019-05-15 20:39:38.921 2770-2917/com.chooloo.www.callmanager E/AndroidRuntime: FATAL EXCEPTION: ModernAsyncTask #2
    Process: com.chooloo.www.callmanager, PID: 2770
    java.lang.RuntimeException: An error occurred while executing doInBackground()
        at androidx.loader.content.ModernAsyncTask$3.done(ModernAsyncTask.java:164)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
     Caused by: java.lang.SecurityException: Permission Denial: opening provider com.android.providers.contacts.CallLogProvider from ProcessRecord{dd5cd08 2770:com.chooloo.www.callmanager/u0a462} (pid=2770, uid=10462) requires android.permission.READ_CALL_LOG or android.permission.WRITE_CALL_LOG
        at android.os.Parcel.readException(Parcel.java:2004)
        at android.os.Parcel.readException(Parcel.java:1950)
        at android.app.IActivityManager$Stub$Proxy.getContentProvider(IActivityManager.java:4889)
        at android.app.ActivityThread.acquireProvider(ActivityThread.java:5864)
        at android.app.ContextImpl$ApplicationContentResolver.acquireUnstableProvider(ContextImpl.java:2527)
        at android.content.ContentResolver.acquireUnstableProvider(ContentResolver.java:1780)
        at android.content.ContentResolver.query(ContentResolver.java:738)
        at android.content.ContentResolver.query(ContentResolver.java:704)
        at androidx.core.content.ContentResolverCompat.query(ContentResolverCompat.java:81)
        at androidx.loader.content.CursorLoader.loadInBackground(CursorLoader.java:63)
        at androidx.loader.content.CursorLoader.loadInBackground(CursorLoader.java:41)
        at androidx.loader.content.AsyncTaskLoader.onLoadInBackground(AsyncTaskLoader.java:307)
        at androidx.loader.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:60)
        at androidx.loader.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:48)
        at androidx.loader.content.ModernAsyncTask$2.call(ModernAsyncTask.java:141)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) 
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 
        at java.lang.Thread.run(Thread.java:764) 

Describe the bug
After every time the call ends, The phone profile switches to vibrate only. Please fix this coz the rest of the app is amazing.

Smartphone (please complete the following information):

• Devce: LG Q6 M700
• OS: 8.1.0

Expected behavior

I except both the search and button_keyboard button not to display when the user is using the Table_Numbers.

Actual behavior

When the Star ( * ) button is pressed, it turns the interface into a search page while Table_Numbers is still active on the screen. And if the user presses the back button, Search Button And Button_Keypad Covers Star ( * ) And Hash (#) Button.

How to reproduce

• launch Koler, then, locate the interface to press a number
• click on the Star ( * ) button (at times, you might need to click it more than once)
• Watch it turn the interface into a search interface
• click back button, then, you will notice that the Search Button And Button_Keypad will cover the Star ( * ) And Hash (#) Button.

Browser/App version:

Koler v0.27

Operating system:

Android 0

Recording Of The Bug

Actual Behaviour

Expected behavior

How to reproduce

1. Install the apps and open the app
2. Call someone
3. Click dial pad and input a number.
4. Click back to go to the dialing page to cut the call
5. See you can not cut the call and you will not found the dialing page.

Information

• App version:v0.2.8
• OS:Android 9.0
• Device:Samsung A10

Recording Of The Bug

Describe the bug
The app crashes every time I type a number and place a call.

To Reproduce
Steps to reproduce the behavior:

1. Launch the app
2. Click on dialer
3. Type the number you want to call and call
4. The app will crash

Expected behavior
I expected the app to call the person instead it crashes

Video proof
https://youtu.be/8cwmCF_9v1Y

Smartphone (please complete the following information):

• Device: [Infinix note 4 ]
• OS: [Android 7.0]
• Version [ joker v0.3.1]

Additional context
Here's my phone full logcat report to assist you
https://drive.google.com/file/d/1Fg-37psOVUpq1g0VOgFdK6Kjgd-Snh1x/view?usp=drivesdk

When i opened an app and i called a number which is in my contact list and then i dialed same number on dialpad, then tried to call that number. After clicking on call icon, app crashes.
Screenshot/Video
https://youtu.be/uU1ZBeMGQ3E
Device
Android: RedMi Y2/S2
OS:8.1.0
Version:0.3.1

Expected behavior

To successfully load or recognize numbers if the user share or open the number with Koler, from another app.

Actual behavior

It loads the Recent Page instead of Table_Numbers after a number is opened with it.

How to reproduce

• Share a number into Koler from another app ( I used WhatsApp) )
• You will notice that It won't recognize it while other similar applications does.

Browser/App version:

Koler v0.27

Operating system:

Android 0

Recording Of The Bug

Describe the bug
When we're in a call and open the dial pad and try to note a number or anything, after dialing those digits when we try to get back by pressing the back button, the app doesn't respond at all. So whenever we want to cut the call we are not able to do so unless we remove the app from recents. I think this is something major that needs to be fixed.

To Reproduce
Steps to reproduce the behavior:

1. Dial a number from your contact list.
2. During the call, press on the dialpad.
3. Press any digit or even if you don't press any digit and then try to get back on the call.
4. You can't go back. The back button doesn't work at all.

Expected behavior
During a call when you're trying to write a number after opening the dialpad of the app, you should be able to get back to your call where you can close your speaker after keeping it on, or mute, or end call. You're not able to do so because the back button doesn't work after you've opened the dialpad, which is unexpected and it's expected to get back on that screen normally.

Video
https://youtu.be/K2Zm-orNf3g

• Device: [Motorola Moto G5 Plus]
• OS: [Android Oreo 8.0]
• Version [v0.3.1]

Description

When the app asked for three permissions, I granted two and denied one. The one I denied has to do with not managing my messages, but permission was given to access my contacts and manage my call. Afterwards, I find it difficult to place calls, access other feature, dial a new number and so on. App keeps hanging at intervals.

Expected behaviour

Since only the permission not to manage my message was denied, I believe I should be able to make and receive calls with the app because the permission that tackles that part( to access my contacts and manage phone calls) was granted.

Steps to reproduce

After launching the app

• It will pop up some request for permission. Grant the permission to allow the app to manage your contact and manage phone calls, but don't give access to manage your messages.

• Try using the app after this by switching through the app features, dialing a new number and note the behavior.

Device used

Techno spark k7
OS: Android 7.0

Reproducing the behavior

https://youtu.be/1buDq19hQUQ

Components

The app is in its test phase for volunteers who are ready to contribute to it. As an open-source enthusiast, I am really glad to contribute to this project.
After downloading the app and in the course of my exploration, I found out some very important features that can enhance user experience which are currently missing in the app. Non-implementation of these features will negatively affect the app, as users might lose interest in the app for the lack of these features. So, I'm suggesting the implementation of "Cursor and Ability to Select, Copy and Paste numbers to the dialer".

Proposal Description

Koler app is a call managing app as earlier mentioned, and it thus has a dialer page(dialing window) where users can input and dial numbers. But while using it, I found some things missing in the dialer page which I'm now proposing to be added. They are;

• Addition of Cursor: While trying to make a call with, after inputting the phone number to call, I noticed I made a mistake in between the number and I had to delete a number and replace it, so I tried going straight to the point of the mistake to make the correction, but to my surprise, there is no such ability, which means I had to delete all the other numbers that were after the point where the mistake occurred. This was really stressful and time wasting.
  So, I'm suggesting that "Cursor" should be introduced to the app, which users can move anywhere they plan to use it.

• Ability to Select, Copy and Paste numbers: This feature is also missing in the Koler app. I mean the developer said the app was designed keeping the users in mind, then they have to know that basic ability to select, copy and paste is necessary to ease the use of the app. Most times, users might need to paste a phone number copied from another place on the device directly and place a call immediately or even might want to copy a phone number directly from the app, sadly this is not currently possible using the app. I really wish the developers will implement this feature also.

Mockups / Examples

Below are pictorial illustrations of how the features I recommend can be implemented by the Developer.

This is how the app currently looks like without the feature
This is a picture showing how the "Cursor" feature can be implemented(Note that the cursor position can be changed to any point, it's just static in this mock up because it's an image)
This is a picture showing how the "Select, Copy and Paste" feature can be implemented in the app

Benefits

The benefits of the features suggested above are as follows:

• Cursor Addition will allow users to carry tasks such as deletion of a particular number or addition of number at a particular point without having to delete the "unconcerned ones".
• Select, Copy and Paste will save users time and reduce the stress involved in typing number every time. This will also allow users to transfer numbers easily to and from the app.

Conclusion

In general, Implementing these features will go a long way to improve the application. It will increase user experience positively, thereby increasing the user base of the Koler app.
I hope, App developer implements this feature very soon.

Thank You.

Describe the bug
I had an incoming call and checked my phone screen to see who it was, but no number/name was displayed. When I picked the call, I discovered it was a number that isn’t stored on my phone. After the call, I tried calling my line with a number stored on my device, and the caller’s name showed. I later discovered that if any number that isn’t stored on the device enters as an incoming call, it is displayed as anonymous.

To Reproduce
Steps to reproduce the behavior:

• You can notice this if a number not stored on your device enters as an incoming call, or
• Call your line with a number not stored on your device and note the error.

Expected behavior
I was expecting to see the number that called whether or not stored on my device.

Reproducing the behaviour
https://youtu.be/tb0AK2jDzSU

Smartphone

• Device: [Tecno spark k7]
• OS: [Android 7.0]
• App Version [0.2.9]

Similar HenriDellal/emerald-dialer#12

Koler only support phone number search, no contact search.

Is your feature request related to a problem? Please describe.
1 Hello, please you can add indicator fast scroll.
Most manufacturers: Xiaomi, samsung, huawei ... have a similar mechanism in their system apps

It is more convenient to reach the contacts by clicking on the letter.

2 Please add a system to block calls

Describe the solution you'd like
Solution 1

https://github.com/reddit/IndicatorFastScroll

Solution 2 I do not know

Expected behavior

Click or press on (+) option to join another caller while calling

Actual behavior

i cant join another caller when i press on (+) option

How to reproduce

• Call someone
• then press (+) option
• and see the bug

Operating system

• App version:v 0.2.8
• Android v8.1.0 OPMI

Recording Of The Bug

https://youtu.be/usECSq_avVg

Describe the bug
The Recent feature on koler displays all the received, and dialed calls altogether, so I searched for one number that have called me, to save the time of scrolling to find the name. When I clicked on the search Icon and typed the name of the person I want to call, the name was not fetched.

To Reproduce

• Launch the app
• Accept all permissions
• Click on Recent
• You will see the search icon below to the left side. Click on it and type the name of the person you want to call. (I made sure the person is on the call list)
• The name will not be fetched.

Expected behavior
When I typed the name, I expected koler to fetch any name related to what I’m typing and eventually fetch the main name I typed just as it’s working when you search for names in the contact. The search should be able to seach the contact I typed.

Screenshots
https://youtu.be/0kgBzmZXoro

Smartphone (please complete the following information):
 - Device: [Tecno spark k7]
 - OS: [Android 7.0]
 - App Version [v.0.2.9]

Describe the bug
When accessing voicemail it asks for a 4 number pass code. Upon entering 1234#, the voicemail system says "111222333444 isn't a valid pass code". It seems to be receiving each tone 3 times.

To Reproduce
Dial voicemail and input pass code to log in.

Expected behavior
To login to the voicemail system.

Smartphone (please complete the following information):

• Device: Motorola G7 Plus
• OS: Android 9, Security patch October 1, 2019
• Browser: Bromite (Chrome)
• Version: 78.0.3904.119

Additional context
I can hear the tones being pressed, It sounds like 3 rapid tones, about 100ms each. When using Google Dialer, the tone can be heard for the duration of the finger on the number.

Describe the bug
Each time I make a call and end it few minutes into the call, the application crashes almost immediately. This is a major issue as it bars me from enjoying the full benefits of the application. I enjoy the application and would love of this is resolved.

** Steps To Reproduce**

Launch the app.
Click on the contact you want to call.
End the call after few seconds into the call.
The app crashes after that.

Expected behavior
I expected the application to return me to the homepage to enable me perform the basic functionality of the application.

Screen recording
https://youtu.be/mD8LBDV6uoE

Test Environment

Device: Infinix Hot 7 Pro
OS: Android 9.0
Software version: Koler version 0.3.1
Logcat
Here is the full Inbuilt android logcat to help you.

bugreport-H624EF-PPR1.180610.011-2019-07-03-15-21-56.txt

Project Information

• Repository-----------:Here
• Project Name---------: call_manage
• Publisher------------: Chooloo
• My GitHub account----: Here

Expected behavior

When I click on the Google Play Store button, The Call-manage application should appear in the Google Play Store so that from where I install this application in my mobile

Actual behavior

When I click the Google Play Store button, the application does not appear further, but there is an error in which it is written (no app such found)

How to reproduce

• Open github link on mobile

• Click the Google Play Store button

• Note the Bug

• Operating system----: 9.0.0

Recording Of The Bug

Hello, I'm Harry. I engage in creating documents for open source projects. It's part of my contribution in helping open source projects. One of the documents I engage in creating is a privacy policy. The privacy policy will give details about user information collection, use and security. I really don't know if you externally collect user information, but, if you don't, it's good to let end users know via a privacy policy.
Contributor's guidelines is also an important document that will help prospective collaborators contribute easily to your project.

I'll love to hear your thoughts on this.

Hi, great app, congratulations!

What are end call and answer call timer?

Expected behavior

I expected The Hash button to respond while clicking on it.

Actual behavior

It doesn't respond on click except until the user clicks on the empty space beside it.

How to reproduce

• launch Koler, then, locate the interface to press a number
• Try clicking on the # Button
• Watch it not respond (But it will respond when you click on the empty space beside it.)

Browser/App version:

Koler v0.27

Operating system:

Android 0

Recording Of The Bug

Possible Fix

Reduce the Width of the chip_hex or Table_Numbers.

Describe the bug

I wanted to call from the app and when I clicked the number I want to call, I got redirected to my phone default caller.

To Reproduce

1. Open the app
2. Pick any number and dial.
3. Note the issue

Expected behavior*

I expect that I should be able to use the app to call out because it works well on my second device. (Andriod 7.0)

Screenshots
https://youtu.be/m6dDWy8zpdc

Smartphone

• Device: [itel]
• OS: [6.1]
• Version [0.3.1]

Hey, I appreciate the effort towards this project. I love the UI and I can't wait to see it function as everyone expected. 👍

Btw, while making calls with it, I noticed that the call timer counts even before the other party picks up the call. Was this intended?

Thank you.

Describe the bug
When ever I make a phone call on the app, after ending the call the app crashes

To Reproduce
Steps to reproduce the behavior:

1. Launch the app
2. Click on any number to make a call
3. After making the call for some time, hang up
4. App crashes

Expected behavior
I expect the app not to crash after I make a call on the app

Smartphone (please complete the following information):

• Device: [infinix s2pro]
• OS: [Android 7.0]
• Version [Version 0.3.1 ]

Expected behavior

user should be able to see their phone imei number with typing dial-pad

Actual behavior

when i typing in dialpad ( * # 0 6 # ) in koler app it shows nothing .

How to reproduce

• open the koler app
• type ( * # 0 6 # ) for imei number
• see the bug

Operating system

• App version:v 0.2.8
• Android v8.1.0 OPMI

Recording Of The Bug

https://youtu.be/8DBcPlee75Y

I have a Android Smart Watch (Non-Wear Android). I want to transmit call to Smartwatch via bluetooth using this app. Where can I find audio and mic data in code to transmit?

I use a redmi 6 phone (miui 10, android 8.1), and when receiving calls I usually use the speaker function so that I can do other things at the same time.

Problem is, since I downloaded Koler, this function doesn't always work. It does sometime, but I can't find any pattern that determines whether it works or not. 😔

When you click on tel HTML5 tag on the website, the call number isn't reported on koler dialer.

1. Go for example to PagesJaunes.fr or on website where you can find a tel HTML5 tag.
2. Click on tel number after search
3. A message is displayed to select application to open. Select koler
4. Koler application is opening but not with the number on the dialer keyboard. We must put it manually.

Test on firefox, chrome, it's the same problem

Expected behavior

I expected both buttons to display their logo even after searching and dialing a number.

Actual behavior

Search button and the button that displays the interface to dial numbers turns blank after dialing, and searching a number.

How to reproduce

• launch Koler, then, locate the interface to press a number
• Type any number
• Click on dial button, then, end the call
• Click on search button
• Click on dial button, then, end the call again.
• Watch as the buttons turn blank
  

Browser/App version:

Koler v0.27

Operating system:

Android 0

Recording Of The Bug

Is your feature request related to a problem? Please describe.
Problem is, that a open source App would be be greatly suited for the FOSS Fdroid store, so privacy consious and open source supporters dont need to trust and use the Google Play Store.

Describe the solution you'd like
Publishing this App on FDroid

Describe alternatives you've considered
APK downloads can in the meantime help out those who dont want to use play store and give their data and privacy to Google. But only in FDroid can the app be auto updated, instead of manually downloading and installing APK files.

Additional context
FDroid is the standard way for open source Android App. The open source community expects this on Android; Plus it would greatly help this App to become more well known in the community and to new users.
As there are no good open source dialers out there, this App would be a huge benefit for anyone who wants to use Android as open sourcy and privacy minded as possible.

I would like to get a notification on my pc when there is an incoming call and don't want to make yet another account for this.

The easiest way to implement that is to have the app make a web request (HTTPS POST) somewhere when a call is received. The user is then free to setup their end to handle it however they see fit (e.g. netcat + shell script).

Example of payload for an incoming call:

{eventName:"INCOMING_CALL",contactName:"John Doe", phoneNumber:"0123456789"}

I suggest to add two settings to this app:

• A text field to specify the target url
• A checkbox group to select what events are to be notified externally (e.g. incoming call, missed call, call ended)

ps. It would be interesting to see if the existing windows 10 facilities from the native android notification bridge could be hijacked for re-use with koler and without a microsoft account

Pls add possibility to choose accent color and to enable night mode

Can the app be translated? With something like weblate, poeditor, crowdin or transifex.

Is your feature request related to a problem? Please describe.
My phone switches from light to dark theme back and forth automatically. Most apps switching their theme, too, but Koler always stays with same theme
Describe the solution you'd like
I want Koler to became dark/ligth according to system's settings

Description

I tapped a number from my contacts list to place a call and discovered the number started dialing without asking which sim card I wanted to use. That isn't the main point because the app might be designed that way, and if not, then it can be seen as a bug. However, the main issue is that the dialed number will start reading and no call will be placed. That means the call is not connecting.

Expected behaviour

My expectation was to use either of my sim card for calls, and also see the dialled call connected.

Steps to reproduce

After launching the app

• accept the whole permission
• Dial a number from your contact list and note the behavior. The call will start without asking to select sim card and the call will not be connected.

Device used

Techno spark k7
OS: Android 7.0

Reproducing the behavior

https://youtu.be/nxew0-xnGtk

Describe the bug
The behavior is a bit strange because it affects two things. Sometimes when I just click the call function without adding any number, the app will crash. Other regular behavior is when I click the call function to dial out, which it will dial a certain unknown number. Then if I stop the call, and dial back after 10 secs, the app will crash.

To Reproduce

1. Open the app
2. Click on the dial pad
3. Click on the call button, let it dial and cut the call
4. Wait for some seconds. Maybe 10sec or more and re-click again.

Expected behavior

Crash causes hinderances and I don't expect to encounter one while performing such activity in the app.

Screenshots
https://youtu.be/8YSBYouMlqE

**Smartphone

• Device: [Gionee X1]
• OS: [7.0]
• Version [0.3.1]

Log

06-19 18:50:30.930 16342 16342 E AndroidRuntime: Process: com.chooloo.www.callmanager, PID: 16342
06-19 18:50:30.930 16342 16342 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.chooloo.www.callmanager/com.chooloo.www.callmanager.ui.activity.OngoingCallActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.isEmpty()' on a null object reference
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2417)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2477)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.ActivityThread.-wrap11(ActivityThread.java)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1345)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:148)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:5452)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:671)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.isEmpty()' on a null object reference
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at com.chooloo.www.callmanager.util.CallManager.getDisplayContact(CallManager.java:221)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at com.chooloo.www.callmanager.ui.activity.OngoingCallActivity.displayInformation(OngoingCallActivity.java:522)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at com.chooloo.www.callmanager.ui.activity.OngoingCallActivity.onCreate(OngoingCallActivity.java:199)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.Activity.performCreate(Activity.java:6305)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1110)
06-19 18:50:30.930 16342 16342 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2370)
06-19 18:50:```

Actual Behaviour

Expected behavior

Step to reproduce

1. Install the apps and open the app
2. Go to contact
3. Click dial pad and input any ussd related to your sim card.
4. call and the error.

Information

• App version:v0.2.8
• OS:Android 9.0
• Device:Samsung A10

Recording Of The Bug

Expected behavior

I expected Koler not to crash when a user types a number while dialing a call.

Actual behavior

It crashes immediately after pressing the first number.

How to reproduce

• dial a number
  ^{( mute, pause, loud speaker, an option to dial a number, and a + sign button will pop up.)}

• Click on the option to dial a number

• Type a number

• Watch the app crash

• Browser/App version:
  Koler v0.27

• Operating system:
  Android 0

Recording Of The Bug

Descriptions

After selecting the XLS file from my document/device, I was able to import contacts from spread sheet. But clicking on the exported file made the app to crash

Expected behavior

I expected the file to open when I clicked on it after importing from spread sheet.

Steps to reproduce

• Launch the app
• Swipe or click on the Excel
• Fill the blank spaces and select a file to import
• Click on done
• After the file has been imported, click on it and note the error.

Reproducing the bug

https://youtu.be/NmjwqPKsvN8

Device used

• Tecno spark K7
• Android 7.0

Logcat

06-16 12:25:52.825 32716 32716 E AndroidRuntime: FATAL EXCEPTION: main
06-16 12:25:52.825 32716 32716 E AndroidRuntime: Process: com.chooloo.www.callmanager, PID: 32716
06-16 12:25:52.825 32716 32716 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.chooloo.www.callmanager/com.chooloo.www.callmanager.ui.activity.OngoingCallActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.isEmpty()' on a null object reference
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2724)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2789)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.ActivityThread.-wrap12(ActivityThread.java)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1527)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:110)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:203)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6251)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1063)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:924)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.isEmpty()' on a null object reference
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at com.chooloo.www.callmanager.util.CallManager.getDisplayContact(CallManager.java:221)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at com.chooloo.www.callmanager.ui.activity.OngoingCallActivity.displayInformation(OngoingCallActivity.java:522)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at com.chooloo.www.callmanager.ui.activity.OngoingCallActivity.onCreate(OngoingCallActivity.java:199)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.Activity.performCreate(Activity.java:6670)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1118)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2677)
06-16 12:25:52.825 32716 32716 E AndroidRuntime: 	... 9 more```

Expected behavior

To save call logs.

Actual behavior

It doesn't save them any of the calls made in the past.

How to reproduce

• launch Koler, then, locate the interface to dial a number
• Dial a number, then, end the call
• Navigate to the recent interface
• You will notice that it won't save the call.

Browser/App version:

Koler v0.27

Operating system:

Android 0

Recording Of The Bug

When a contact is saved with country code in the beginning, say +91 844xx xxxxx, it doesn't display the name of the caller but when I edit the contact to 91 844xx xxxxx, it does.

To Reproduce
Steps to reproduce the behavior:

1. Go to contacts
2. Select a contact whose name is displayed when they call
3. Edit the number, adding the country code (+XXX) before the number
4. See error

Expected behavior
The name of the contact will no longer be displayed, when they call. Instead, something like %2B(country code)(phone number)

Screenshots

Smartphone:

• Device: Motorola one power
• OS: Android 9
• v0.3.1

In dual SIM devices, its important to see incoming calls are for SIM1 or SIM2. Right now RECENTS doesn't show the SIM details

Describe the bug

When I dialed a number on my on with my phone set to loud, which I mean my phone is not mute or in vibration. After I dialed a number and cut the call, the app will trigger my mobile vibration.

To Reproduce

1. Open the app
2. Dail a number, and make sure your phone is on sound
3. Cut the call and note the bug

Expected behavior

I don't expect that when I cut a call it will trigger my vibration.

Screenshots
https://youtu.be/RoVo4Z2uU_c

Smartphone

• Device: [Gionee X1]
• OS: [7.0]
• Version [0.3.1]

2020-04-23 09:06:26.534 19069-19069/com.chooloo.www.callmanager E/AndroidRuntime: FATAL EXCEPTION: main Process: com.chooloo.www.callmanager, PID: 19069 java.lang.IllegalStateException: View 'item_header' with ID 2131362031 for field 'mAnchoredHeader' was of the wrong type. See cause for more info. at butterknife.internal.Utils.castView(Utils.java:109) at butterknife.internal.Utils.findRequiredViewAsType(Utils.java:101) at com.chooloo.www.callmanager.ui.fragment.ContactsFragment_ViewBinding.<init>(ContactsFragment_ViewBinding.java:33) at java.lang.reflect.Constructor.newInstance0(Native Method) at java.lang.reflect.Constructor.newInstance(Constructor.java:343) at butterknife.ButterKnife.bind(ButterKnife.java:170) at com.chooloo.www.callmanager.ui.fragment.base.AbsBaseFragment.onActivityCreated(AbsBaseFragment.java:17) at com.chooloo.www.callmanager.ui.fragment.ContactsFragment.onActivityCreated(ContactsFragment.java:152) at androidx.fragment.app.Fragment.performActivityCreated(Fragment.java:2717) at androidx.fragment.app.FragmentStateManager.activityCreated(FragmentStateManager.java:346) at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1188) at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1356) at androidx.fragment.app.FragmentManager.moveFragmentToExpectedState(FragmentManager.java:1434) at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1497) at androidx.fragment.app.BackStackRecord.executeOps(BackStackRecord.java:447) at androidx.fragment.app.FragmentManager.executeOps(FragmentManager.java:2169) at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1992) at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1947) at androidx.fragment.app.FragmentManager.execSingleAction(FragmentManager.java:1818) at androidx.fragment.app.BackStackRecord.commitNowAllowingStateLoss(BackStackRecord.java:303) at androidx.fragment.app.FragmentPagerAdapter.finishUpdate(FragmentPagerAdapter.java:246) at androidx.viewpager.widget.ViewPager.populate(ViewPager.java:1244) at androidx.viewpager.widget.ViewPager.populate(ViewPager.java:1092) at androidx.viewpager.widget.ViewPager.onMeasure(ViewPager.java:1622) at android.view.View.measure(View.java:26367) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7231) at androidx.coordinatorlayout.widget.CoordinatorLayout.onMeasureChild(CoordinatorLayout.java:760) at com.google.android.material.appbar.HeaderScrollingViewBehavior.onMeasureChild(HeaderScrollingViewBehavior.java:99) at com.google.android.material.appbar.AppBarLayout$ScrollingViewBehavior.onMeasureChild(AppBarLayout.java:1892) at androidx.coordinatorlayout.widget.CoordinatorLayout.onMeasure(CoordinatorLayout.java:831) at android.view.View.measure(View.java:26367) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7231) at android.widget.FrameLayout.onMeasure(FrameLayout.java:194) at androidx.appcompat.widget.ContentFrameLayout.onMeasure(ContentFrameLayout.java:143) at android.view.View.measure(View.java:26367) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7231) at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1552) at android.widget.LinearLayout.measureVertical(LinearLayout.java:842) at android.widget.LinearLayout.onMeasure(LinearLayout.java:721) at android.view.View.measure(View.java:26367) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7231) at android.widget.FrameLayout.onMeasure(FrameLayout.java:194) at android.view.View.measure(View.java:26367) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7231) at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1552) at android.widget.LinearLayout.measureVertical(LinearLayout.java:842) at android.widget.LinearLayout.onMeasure(LinearLayout.java:721) at android.view.View.measure(View.java:26367) at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7231) 2020-04-23 09:06:26.535 19069-19069/com.chooloo.www.callmanager E/AndroidRuntime: at android.widget.FrameLayout.onMeasure(FrameLayout.java:194) at com.android.internal.policy.DecorView.onMeasure(DecorView.java:1003) at android.view.View.measure(View.java:26367) at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:3551) at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:2300) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2592) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2148) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:8831) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:996) at android.view.Choreographer.doCallbacks(Choreographer.java:794) at android.view.Choreographer.doFrame(Choreographer.java:729) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:981) at android.os.Handler.handleCallback(Handler.java:883) at android.os.Handler.dispatchMessage(Handler.java:100) at android.os.Looper.loop(Looper.java:237) at android.app.ActivityThread.main(ActivityThread.java:7777) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1047) Caused by: java.lang.ClassCastException: Cannot cast androidx.appcompat.widget.AppCompatImageView to android.widget.TextView at java.lang.Class.cast(Class.java:2446) at butterknife.internal.Utils.castView(Utils.java:106) ... 67 more

Is your feature request related to a problem? Please describe.
I'm a very privacy-minded individual and I'd like to be able to use Koler as a dialer only, without it getting my contacts. I have a separate Contacts app that I trust and I'd like to give the Contacts permission to as few apps as possible.

Right now, Koler requires the Contacts permission no matter what.

Describe the solution you'd like
When I'm asked for Contacts and reject, I should be let into the Koler app anyway. The Contacts tab should be empty with a button "Allow access to contacts", allowing me to always change my mind.

Additional context
This behavior is recommended by the official Android guidelines: "Only use the permissions necessary for your app to work. Depending on how you are using the permissions, there may be another way to do what you need (system intents, identifiers, backgrounding for phone calls) without relying on access to sensitive information."

Lineage os 16.0 based on android 9 OP3T

Does the dialer control the ringtone? Would it be possible to play a specific ringtone for contacts in a specific contact group?

During Incoming call it show OnGoingCallActivity and if new incoming call arrive then it open new instance of activity instead it should show notification and after pick second call it should also give option to swap calls.

Is there any option available already?

Thanks !!

In Mi devices if app is in foreground then works perfectly but when it goes in background or removed from background calling screen not appear