Delay with navigation keys with AM1808 based platform and Android 2.2

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open the menu explorer in Android (where all menu items will be displayed 
-Browser, calculator, Calendar etc). 
2.Navigate the menu items through navigation keys of the physical keyboard 
(DPAD_LEFT,DPAD_RIGHT,DPAD_UP, DPAD_DOWN)

What is the expected output? What do you see instead?
Expected focus on the item should move quickly from one item to anther but most 
of the time there is more delay in the movement of the focus from one item to 
another.    

What version of the product are you using? On what operating system?
AM1808 based platform. Android 2.2

Please provide any additional information below.
When I press navigation the event (for ex: COL3 the pressed KEY is [33], 
newstat:2 COL3 the pressed KEY is [33], newstat:0) is coming quickly but there 
is more delay in shifting the focus between the items.

Regards,
Bala
Mindtree

Original issue reported on code.google.com by balafrom...@gmail.com on 12 Apr 2011 at 11:06

[GoogleCodeExporter]

AM1808 does not have graphics acceleration so I think the 'slowness' you see 
would be expected.

Original comment by vishvesh...@aim.com on 13 Apr 2011 at 6:40

[GoogleCodeExporter]

Thanks Vishvesh for your comment.

Also I see flickering in the screen when I enter values from the keypad, even 
this is due to graphics acceleration absence?

Is there any other way to overcome this 'slowness' issue with AM1808 processor?

In which TI Low-Power Applications Processor the graphics acceleration is 
supported?

Thanks,
Bala

Original comment by balafrom...@gmail.com on 13 Apr 2011 at 11:39

[GoogleCodeExporter]

Re: flickering...
In file rowboat/hardware/libhardware/modules/gralloc/framebuffer.cpp change the 
line
#define NUM_BUFFERS 2 to
#define NUM_BUFFERS 1

This will reduce the flickering, but the graphics will remain slow.

Original comment by vishvesh...@aim.com on 14 Apr 2011 at 4:57

[GoogleCodeExporter]

Thanks Vishvesh. I informed these to settings to driver team. we will check it.

Original comment by balafrom...@gmail.com on 14 Apr 2011 at 11:20

[GoogleCodeExporter]

The change for this is done now.

Original comment by vishvesh...@aim.com on 26 Jun 2013 at 1:07

• Changed state: Fixed