Comment by ~arjunaithal on ~mil/sxmo-tickets
One issue i have observed -
- open dmenu.
- Incoming call rings.
- The call pick menu is not visible even after closing the dmenu.
on ~mil/sxmo-tickets
REPORTED RESOLVED FIXED
Comment by ~arjunaithal on ~mil/sxmo-tickets
Workflow:-
- Make an outgoing call, and hangup the call -> This creates <callid>.discardedcall file (which is actually not required for an outgoing call)
- The above scenario repeats when making outgoing calls, creating a number of <callid>.discardedcall files.
- And there is no housekeeing for .discardedcall files.
- And when there is an incoming call with same id as cached *.discardedcall file, the phone rings but there would be no notification indicating the call was missed.
Reason :- The existing old cache file gets deleted, instead of going to else block to create notification.
if [ -f "$CACHEDIR/${FINISHEDCALLID}.discardedcall" ]; then #this call was discarded echo "sxmo_modemmonitor: Discarded call from $FINISHEDNUMBER">&2 rm -f "$CACHEDIR/${FINISHEDCALLID}.discardedcall" printf %b "$TIME\tcall_discarded\t$FINISHEDNUMBER\n" >> "$LOGDIR/modemlog.tsv" else #this is a missed call # Add a notification for every missed call pkill -f sxmo_modemcall.sh echo "sxmo_modemmonitor: Missed call from $FINISHEDNUMBER">&2 printf %b "$TIME\tcall_missed\t$FINISHEDNUMBER\n" >> "$LOGDIR/modemlog.tsv" if [ -x "$XDG_CONFIG_HOME/sxmo/hooks/missed_call" ]; then echo "sxmo_modemmonitor: Invoking missed call hook (async)">&2 "$XDG_CONFIG_HOME/sxmo/hooks/missed_call" "$CONTACTNAME" & fi CONTACT="$(lookupcontactname "$FINISHEDNUMBER")" sxmo_notificationwrite.sh \ random \ "st -f Terminus-20 -e sh -c \"echo 'Missed call from $CONTACT at $(date)' && read\"" \ none \ "Missed call - $CONTACT" fi
Comment by ~arjunaithal on ~mil/sxmo-tickets
This issue is due <callid>.discarded file which gets created in cache dir when call is hangup even after the call was received. This file is never deleted and piles up. When a call is received with same id as *.discarded file, the notification is not shown in such scenario.
Ticket created by ~arjunaithal on ~mil/sxmo-tickets
Megapixels version 1.0.1 stops during startup with below error -
(megapixels:13784): Gdk-WARNING **: 06:42:00.590: The program 'megapixels' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadFBConfig'. (Details: serial 221 error_code 167 request_code 152 (GLX) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Comment by ~arjunaithal on ~mil/sxmo-tickets
Now it doesn't reboot after kernel 5.11. Resolving this issue.
REPORTED RESOLVED FIXED
Ticket created by ~arjunaithal on ~mil/sxmo-tickets
Caller hangs up the call after few rings. The phone in crust just rings and again goes back to sleep. There is no green led and no indication of missed call. Modem log or dialer menu should be checked to know a call was missed.
Ticket created by ~arjunaithal on ~mil/sxmo-tickets
I will have to override the sxmo_appmenu everytime I do an upgrade. Is it possible to have a hook to define user preferred apps? Cawbird, Kodi and evolution are few apps which i use not present in app menu.
Comment by ~arjunaithal on ~mil/sxmo-tickets
The phone gets pretty hot when in a call when the battery is low. I prefer to use wired headphones. But this seems to not work. Can anyone confirm it is same for all?
Comment by ~arjunaithal on ~mil/sxmo-tickets
I guess toggling the modem this way may provide a temporary fix on sms missed in CRUST. At present a restart is required to receive messages received during CRUST.