Result section - Incorrect symbol is not show correctly on LG Optimus Phone

[shawnkim]

On a LG Optimus Phone, the incorrect symbol is not displayed correctly. (Screenshot included)

[truedat101]

Hmm, can you provide the Android OS version. Also, is character input set of US/EN ? Curious, because the character used is part of the unicode character set.

[shawnkim]

The character input method was in English with default Android keypad. Models are the same as the one I've provided on first comment. Another thing I've noticed is that, sometimes sending questions doesn't always work. On my phone it says that it was waiting for other people to finish their questions, but on my teacher panel, I don't see any questions displayed. It happened 3 times while I was testing.

[truedat101]

On teacher panel, are you referring to SMILE Teacher for Android, or SMILE Teacher Desktop App?

[truedat101]

Can you write up a different issue for "Submit questions?"

[truedat101]

Also, when submitting device specific issues, please be sure to include the Android OS version. Perhaps we should create a page on our wiki with device profiles, and refer to them? I'm having trouble keeping my versions straight ... and I don't remember all the devices and names.

[truedat101]

And please be sure to identify which version of SMILE Student. We won't always remember which is the version when we go back to review bugs.

[truedat101]

Verified this problem on The LG Optimus. This is such a low-end phone. I don't think it is worth fixing. Works fine on other devices tested.

Problem is explained here:

http://stackoverflow.com/a/11444058/796514

It's a problem with the default fonts used in the application.

[shawnkim]

I see, however, LG Optimus phone is the phone we use mainly to deploy for SMILE project. We have like more than 200 phones distributed worldwide and still have more phones to distribute in the future. Not so sure if it is still not worth fixing.

Shawn

From: truedat101 [mailto:notifications@github.com]
Sent: Tuesday, March 26, 2013 12:52 AM
To: SMILEConsortium/smileplug-bsp
Cc: Kim, Shawn Nak-Kyung
Subject: Re: [smileplug-bsp] Result section - Incorrect symbol is not show correctly on LG Optimus Phone (#8)

Verified this problem on The LG Optimus. This is such a low-end phone. I don't think it is worth fixing. Works fine on other devices tested.

Problem is explained here:

http://stackoverflow.com/a/11444058/796514

It's a problem with the default fonts used in the application.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-15445433.

[shawnkim]

The version and the model for this phone: Hi. they are LG Optimus VM670 with Adnroid Version 2.2.2

[truedat101]

The fix is simple ... Let's pick a different unicode character that is available in the font on the optimus.

-----Original Message-----
From: shawnkim notifications@github.com
Date: Tue, 26 Mar 2013 11:13:06
To: SMILEConsortium/smileplug-bspsmileplug-bsp@noreply.github.com
Reply-To: SMILEConsortium/smileplug-bsp reply@reply.github.com
Cc: truedat101dkords@gmail.com
Subject: Re: [smileplug-bsp] Result section - Incorrect symbol is not show
correctly on LG Optimus Phone (#8)

I see, however, LG Optimus phone is the phone we use mainly to deploy for SMILE project. We have like more than 200 phones distributed worldwide and still have more phones to distribute in the future. Not so sure if it is still not worth fixing.

Shawn

From: truedat101 [mailto:notifications@github.com]
Sent: Tuesday, March 26, 2013 12:52 AM
To: SMILEConsortium/smileplug-bsp
Cc: Kim, Shawn Nak-Kyung
Subject: Re: [smileplug-bsp] Result section - Incorrect symbol is not show correctly on LG Optimus Phone (#8)

Verified this problem on The LG Optimus. This is such a low-end phone. I don't think it is worth fixing. Works fine on other devices tested.

Problem is explained here:

http://stackoverflow.com/a/11444058/796514

It's a problem with the default fonts used in the application.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-15445433.

---

Reply to this email directly or view it on GitHub:
#8 (comment)