gnokii - Bugs: bug #59653, Optional init sequence
You are not allowed to post comments on this tracker with your current authentication level.
bug #59653: Optional init sequence
Submitter: | Raphaël Droz <drzraf> | ||
Submitted: | Fri 11 Dec 2020 02:42:38 AM UTC | ||
Category: | gnokii | Severity: | 3 - Normal |
Item Group: | minor malfunction | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
Fri 11 Dec 2020 08:19:34 AM UTC, comment #1: |
Ladislav Michl <ladis> |
Fri 11 Dec 2020 02:42:38 AM UTC, original submission:
Back in 2011 December (98a87466), after 0.6.31 release, a change was introduced so that if any of ATZ, ATE1, AT+CMEE=1) returns the error, fail Initialize()
|
Raphaël Droz <drzraf> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-12-11 | drzraf | Attached File | - | Added optional-init-sequence.patch, #50436 | |
2020-12-11 | drzraf | Attached File | - | Added optional-init-sequence.patch, #50435 |
Powered by Savane 3.13-758e.
Corresponding source code
Providing empty connect script should overcome that ATZ problem.
Is there any way to identify that phone using AT commands? If you eventually find it out, could you provide minicom session log?