Ticket #234 (closed defect: invalid)

Opened 3 years ago

Last modified 3 years ago

can't accept calls from numbers with 8 digits after prefix.

Reported by: slappinjohn Owned by: ainulindale
Priority: major Milestone:
Component: SHR Image Version:
Keywords: Cc:

Description

Using latest SHR image on GTA2. everytime I recieve a call from a cellular number with more than 8 digits after prefix (like it's often in german prepaid cards), I can push accept and it shows 'call is active' but ringtone and vibrating doesn't stop and I can't talk either. Ringtone and vibrating continues even after killing phone app. All that helps is reboot. Any ideas?
The error occoured right from the beginning when I started to use SHR a month ago. But I just got it, that it has to do with the length of the number. It worked on 2008.9 and FDOM

Change History

comment:1 follow-ups: ↓ 2 ↓ 3 Changed 3 years ago by piratebab

Hi,
I have similar problen (impossible to answer, phone still vibrate). The only solution is to reboot.
In my case it doesnt seem to be dependant of the calling phone number. With the same phone number, sometimes it work, sometimes it doesnt.
It seems to be related to the suspend mode:

  • if I wait 60 sec, phone go in "sleep mode", and wake up is OK
  • if I use power button and "moon icon", the wakeup is not OK

Hope it will help to solve the problem (SHR testing, uptodate)

comment:2 in reply to: ↑ 1 ; follow-up: ↓ 4 Changed 3 years ago by piratebab

After loosing many incoming calls, I discovered that it is with incoming phone numbers begining with +33, +32, +34 (country identification).
I receive mainly this type of number, and cant answer, so I lost calls from customer.
This situation is critical for me. I f not solve in a few days (SHR testing), I will be obliged to change distribution.

Replying to piratebab:

Hi,
I have similar problen (impossible to answer, phone still vibrate). The only solution is to reboot.
In my case it doesnt seem to be dependant of the calling phone number. With the same phone number, sometimes it work, sometimes it doesnt.
It seems to be related to the suspend mode:

  • if I wait 60 sec, phone go in "sleep mode", and wake up is OK
  • if I use power button and "moon icon", the wakeup is not OK

Hope it will help to solve the problem (SHR testing, uptodate)

comment:3 in reply to: ↑ 1 Changed 3 years ago by slappinjohn

Replying to piratebab:

It seems to be related to the suspend mode:

  • if I wait 60 sec, phone go in "sleep mode", and wake up is OK
  • if I use power button and "moon icon", the wakeup is not OK

Doesn't change anything when manually switching to suspend or automatic suspend. Today it worked for my wife calling, the first time ever, because she has a 8 digit phone number. So maybe it's not the problem with numbers length, but in 9 of 10 cases, it is.

comment:4 in reply to: ↑ 2 Changed 3 years ago by slappinjohn

Replying to piratebab:

After loosing many incoming calls, I discovered that it is with incoming phone numbers begining with +33, +32, +34 (country identification).
I receive mainly this type of number, and cant answer, so I lost calls from customer.
This situation is critical for me. I f not solve in a few days (SHR testing), I will be obliged to change distribution.

I only receive calls from country code +49, so I don't think that's the problem. It might be the number of digits afterwards.?

comment:5 Changed 3 years ago by dos

  • Status changed from new to closed
  • Resolution set to invalid

It's FSO/frameworkd problem. If it's still happening, fill bug report in FSO tracker.

Note: See TracTickets for help on using tickets.