Sony Ericsson Arc S [maybe others?] font issue

Solar2D Daily Builds and Public Releases
#1

Hi,

I’ve got a small text displaying current score.
I’ve noticed, that on Arc S, in some cases it will break the text into two lines [I am not specifying width nor height].
It doesn’t happen always. For example it will happen for 337, and it looks like this:

33  
7

also in other places we see the same thing happening to a regular text, where on other devices we have tested [ipad, galaxy S2] this does not happen.

Is this something you are aware of?
It’s the first device we have this issue with.

Thanks,
Krystian [import]uid: 109453 topic_id: 32224 reply_id: 332224[/import]

#2

Here’s a sample project to test the issue:
https://docs.google.com/open?id=0B-ptSmwqNQMqUE9EZXRib3ZZSVE
APK file ready to install is included

Here’s how it looks like on our Arc S:

All of the lines should be 337. [import]uid: 109453 topic_id: 32224 reply_id: 128284[/import]

#3

This issue has been confirmed on Sony Ericsson Neo V [import]uid: 109453 topic_id: 32224 reply_id: 128325[/import]

#4

Here’s a sample project to test the issue:
https://docs.google.com/open?id=0B-ptSmwqNQMqUE9EZXRib3ZZSVE
APK file ready to install is included

Here’s how it looks like on our Arc S:

All of the lines should be 337. [import]uid: 109453 topic_id: 32224 reply_id: 128284[/import]

#5

This issue has been confirmed on Sony Ericsson Neo V [import]uid: 109453 topic_id: 32224 reply_id: 128325[/import]

#6

Krystian,

Would you mind sending your code to us please so that we can reproduce it? You can do so by clicking the “Report a Bug” link at the top of this web page. We have a Sony Ericsson to test with, so we should be able to do something about this.

Also, you should be able to work-around this issue by appending spaces to the end of your string.
[import]uid: 32256 topic_id: 32224 reply_id: 128656[/import]

#7

I’ve created case 18336 & 18337.

18337 is another issue which occurs only on Arc S and Neo V.

Please note, we have SE Xperia X10 and none of the issues occur there. [import]uid: 109453 topic_id: 32224 reply_id: 128700[/import]

#8

Krystian,

Would you mind sending your code to us please so that we can reproduce it? You can do so by clicking the “Report a Bug” link at the top of this web page. We have a Sony Ericsson to test with, so we should be able to do something about this.

Also, you should be able to work-around this issue by appending spaces to the end of your string.
[import]uid: 32256 topic_id: 32224 reply_id: 128656[/import]

#9

I’ve created case 18336 & 18337.

18337 is another issue which occurs only on Arc S and Neo V.

Please note, we have SE Xperia X10 and none of the issues occur there. [import]uid: 109453 topic_id: 32224 reply_id: 128700[/import]

#10

Thank you for your bug submissions.

Yeah, we spend a lot of time working on compatibility issues between Android devices. Getting features to work consistently between devices is one of the most challenging aspects of Android development and is why development tends to take longer compared to iOS. It involves a lot of testing and experimentation. Sending us these test results is a big help to us and makes Corona better for everyone, so thanks for that. [import]uid: 32256 topic_id: 32224 reply_id: 128813[/import]

#11

No problem.

Issue 18337 is about touch detection.
Till now we have figured out, that near the bottom/top edge of the screen, tiny touch movement on screen, which would normally correspond to 1 point change in corona, corresponds to more. It looks like 1 point finger movement on screen equals 2-3 points moved in corona. [import]uid: 109453 topic_id: 32224 reply_id: 128862[/import]

#12

Thank you for your bug submissions.

Yeah, we spend a lot of time working on compatibility issues between Android devices. Getting features to work consistently between devices is one of the most challenging aspects of Android development and is why development tends to take longer compared to iOS. It involves a lot of testing and experimentation. Sending us these test results is a big help to us and makes Corona better for everyone, so thanks for that. [import]uid: 32256 topic_id: 32224 reply_id: 128813[/import]

#13

No problem.

Issue 18337 is about touch detection.
Till now we have figured out, that near the bottom/top edge of the screen, tiny touch movement on screen, which would normally correspond to 1 point change in corona, corresponds to more. It looks like 1 point finger movement on screen equals 2-3 points moved in corona. [import]uid: 109453 topic_id: 32224 reply_id: 128862[/import]

#14

Thank you for the bug submission. It sounds like the DPI is being miscalculated just for that device. [import]uid: 32256 topic_id: 32224 reply_id: 129117[/import]

#15

Thank you for the bug submission. It sounds like the DPI is being miscalculated just for that device. [import]uid: 32256 topic_id: 32224 reply_id: 129117[/import]

#16

Another issue with this device

In logcat we are getting this errors all the time when displaying texts:

D/dalvikvm( 1863): GC\_FOR\_ALLOC freed 346K, 54% free 10433K/22663K, paused 17ms  
E/Adreno200-ES11( 1863): \<1913\>: GL\_INVALID\_ENUM  
E/Adreno200-ES11( 1863): \<2055\>: GL\_INVALID\_ENUM  
E/Adreno200-ES11( 1863): \<2055\>: GL\_INVALID\_ENUM  
E/Adreno200-ES11( 1863): \<2055\>: GL\_INVALID\_ENUM

every time we create display.newText or modify existing we get this error. [import]uid: 109453 topic_id: 32224 reply_id: 131567[/import] 2055>2055>2055>1913>

#17

Another issue with this device

In logcat we are getting this errors all the time when displaying texts:

D/dalvikvm( 1863): GC\_FOR\_ALLOC freed 346K, 54% free 10433K/22663K, paused 17ms  
E/Adreno200-ES11( 1863): \<1913\>: GL\_INVALID\_ENUM  
E/Adreno200-ES11( 1863): \<2055\>: GL\_INVALID\_ENUM  
E/Adreno200-ES11( 1863): \<2055\>: GL\_INVALID\_ENUM  
E/Adreno200-ES11( 1863): \<2055\>: GL\_INVALID\_ENUM

every time we create display.newText or modify existing we get this error. [import]uid: 109453 topic_id: 32224 reply_id: 131567[/import] 2055>2055>2055>1913>