Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Update: still not implemented in v1.1.2.16v1.1.4.28

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Update: still not implemented in v1.1.4.28v1.1.6.27

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Update: still not implemented in v1.1.6.27v1.1.7.24

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Update: still not implemented in v1.1.7.24

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Update: still not implemented in v1.1.7.24

Update: still not implemented in v1.1.9.28

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Update: still not implemented in v1.1.7.24

Update: still not implemented in v1.1.9.28

Update: still not implemented in v2.0.0.10

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !

Character and message counter

It would be nice for people like me who use prepaid cards to have a small character and message counter displayed continuously (as on this good old Symbian) when writing an SMS message. This way we know what we will pay for it. It is really something useful, if not mandatory.

Update: still not implemented in v1.1.7.24

Update: still not implemented in v1.1.9.28

Update: still not implemented in v2.0.0.10

Update: still not implemented in v2.0.1.11

Text message encoding

It would be also nice to be able to force the encoding of any SMS sent (not Facebook/GTalk messages, only for SMSes) as it was done in good old days - for instance if a non-supported character (let it be 'ê') is encountered, replace it by a simpler one that is supported (here 'e' for the example). It is indeed very frustrating to not be able to know that we are restricted to 70 characters by message instead of 160 for the same price (this issue is linked to the problem stated above, about character and message counting). It was done in the past, why not anymore now just because we have full keyboards?

Thanks !