search

tmassie / aospx

Automatically exported from code.google.com/p/aospx
0 stars 0 forks source link

unable to see text #100

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Please describe the problem in detail. Be sure to include:

Whenever I scroll fast through a tweets,Gmail etc. When I stop text becomes 
weird and it isn't readable some of the letters look correct 

What steps will reproduce the problem?
Scroll fast 

What is the expected output? What do you see instead?

Normal letters, unreadable weird letters 

What version of aospX are you using? And when did the issue first start?

Latest one, few days after I installed it 

Have you performed a full wipe/factory reset? (If not, then do so)

Yes

Inspire4G or DesireHD? (If Inspire, did you flash Inspiremod?)

 Desire hd

Please provide logcat ouput and any additional information below.
(logs required or I will discard the ticket.)

Original issue reported on code.google.com by htcdesir...@gmail.com on 14 Aug 2012 at 11:17

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Merging into Issue 23,..the text corruption issue is a known AOSP issue. It 
seems to happen mostly with the launcher, but it does happen in some apps as 
well.

Original comment by robbe...@gmail.com on 15 Aug 2012 at 2:32

GoogleCodeExporter commented 8 years ago 
It's different from 23 for me it only happens in twitter and Gmail app

Original comment by htcdesir...@gmail.com on 15 Aug 2012 at 2:36

Attachments:

GoogleCodeExporter commented 8 years ago 
Kindly make it separate from 23

Original comment by htcdesir...@gmail.com on 15 Aug 2012 at 2:37

GoogleCodeExporter commented 8 years ago 
Its still the same issue as 23. The original ticket was only described as 
Launcher, but it has been known to happen in various apps as well. I renamed 
Issue 23 to be more generalized so it covers both Launcher and Apps. Theres 
quite a few reports regrading this on stock Galaxy Nexus, so hopefully a fix 
comes down from AOSP soon.

Waiting on Google to respond to BUG:25393
http://code.google.com/p/android/issues/detail?id=25393

Original comment by robbe...@gmail.com on 16 Aug 2012 at 9:01