Re: [PATCH] Fix fix false positive "Misconfiguration in the phone table detected."

[Daniele Forsi]

Hello Ladis,

with the version that you modified to get the list of SMS, what
happens if you try commands like the following?
gnokii --getsms SM 1 end
gnokii --getsms ME 1 end
gnokii --getsms IN 1 end
gnokii --getsms IN 229

>         {"C1-01", "RM-607",     PM_DEFAULT_S40_3RD },  /* Series 40 6th 
> Edition Lite */
>         {"C1-02", "RM-643",     PM_DEFAULT_S40_3RD },  /* Series 40 6th 
> Edition Lite */
> +       {"C2-00", "RM-704",     PM_DEFAULT_S40_3RD },

maybe we are doing the wrong thing also with with C1-01 and C1-02
as you have seen, the #define for PM_DEFAULT_S40_3RD is uses other
existing flags so we can't tell a Series 40 testing single bits and
maybe not even testing the whole flags int

we can add another flag, that would be the 17th (I don't know if other
parts of gnokii assume that ints have more than 16 bits, maybe use
AC_CHECK_SIZEOF(int) in configure.ac)

> Message: SMS Folder status received
> Message: Number of Entries: 229
> Message: IDs of Entries : 2576, 2528, 2448, 2432, 2433, 2128, 3200, 3168, 
> 3136, 3120, 3104, 3088, 3072, 3056, 3040, 3024, 3008, 2992, 2976, 2944, 2912, 
> 2896, 2880, 2832, 2816, 2784, 2785, 2768, 2752, 2753, 2624, 2720, 2688, 2689, 
> 2690, 2672, 2384, 2640, 2544, 2545, 2512, 2464, 2368, 2369, 2336, 2320, 2304, 
> 2256, 2257, 2258, 2240, 2241, 2242, 2224, 2208, 2192, 2176, 2177, 2160, 2096, 
> 2080, 2064, 2048, 2049, 2050, 2032, 2033, 2016, 1968, 1952, 1936, 1920, 1904, 
> 1888, 1889, 1890, 1891, 1872, 1856, 1840, 1792, 1776, 1777, 1760, 1761, 1744, 
> 1728, 1712, 1696, 1664, 1665, 1648, 1649, 1650, 1651, 1632, 1633, 1616, 1617, 
> 1600, 1568, 1569, 1552, 1536, 1537, 1538, 1539, 1520, 1504, 1488, 1489, 1490, 
> 1472, 1473, 1456, 1457, 1458, 1459, 1440, 1424, 1408, 1392, 1376, 1360, 1344, 
> 1345, 1346, 1347, 1348, 1328, 1296, 1280, 1281, 1282, 1283, 1264, 1265, 1266, 
> 1232, 1216, 1200, 1184, 1168, 1152, 1120, 1104, 1105, 1106, 1107, 1088, 1089, 
> 1072, 1073, 1074, 1075, 1056, 1040, 1024, 1025, 1008, 992, 976, 960, 944, 
> 945, 928, 912, 896, 880, 864, 848, 832, 833, 816, 817, 800, 784, 768, 752, 
> 736, 737, 720, 704, 688, 656, 640, 624, 625, 608, 592, 576, 560, 544, 512, 
> 496, 480, 464, 448, 432, 416, 400, 384, 368, 352, 336, 320, 304, 288, 272, 
> 273, 256, 240, 241, 224, 208, 192, 193, 176, 160, 144, 145, 112, 96, 80, 81, 
> 64, 32, 16, 17,
> Get message list from SM
> Message sent: 0x14 / 0x000a
> 00 01 00 0c 01 02 0f 55 55 55                   |        UUU
> Message received: 0x14 / 0x000a
> 01 7f 00 0d 00 00 00 00 00 00                   |
> Received message type 14
> Message: SMS Folder status received
> Message: Number of Entries: 0
> Total number of messages in the folder: 229
> Getting SMS from location 3600
> Getting SMS message (3600 in folder 14) status...
> Message sent: 0x14 / 0x000a
> 00 01 00 0e 02 02 0e 10 55 55                   |         UU
> Message received: 0x14 / 0x0006
> 01 7f 00 0f 02 00                               |
> Received message type 14
> status not supported?
> Subtracting 1024 from memory location number

I don't know if subtracting 1024 makes sense for your phone, but
--getsms 1 end could find a valid location anyway because it ignores
some errors

> Getting SMS from location 2576
> Message sent: 0x14 / 0x000a
> 00 01 00 02 02 02 0a 10 01 00                   |
> Message received: 0x14 / 0x000e
> 01 7f 00 03 02 00 02 02 0a 10 00 00 00 00       |
> Received message type 14
> Trying to get message #2576 in folder #2
> Getting SMS failed (location 1 from IN memory)! (The given memory location is 
> invalid.)
> device: closing device

it should be safe also to try all 256 values for req[3] req[4] req[5]
to see if some combinations give a valid location

--
Daniele Forsi