Thanks :)
Its perfect solution.

BR
Srinivas

On Wednesday, March 14, 2012 1:27:54 PM UTC-5, Solution 9420 wrote:
>
> Hi, 
> Is your Acer Iconia on R3.0 (HoneyComb)? 
> If so, I "guess" you will have to set the option "Use physical 
> keyboard" to OFF. 
> (ON means you want to use physical keyboard only) 
> It is on the input method selection icon (left to the right-most 
> digital clock.) 
> This option will only show when you connect the physicak device (a.k.a 
> NFC or keyboard). 
>
> Best Regards, 
> Solution 9420 
> www.solution9420.com 
>
>
>
> On Mar 14, 11:47 pm, Srinivas Nainala <srito...@gmail.com> wrote: 
> > Dear All, 
> > 
> > I am facing strange behavior on my Acer Iconia tablet when I connect NFC 
> > reader to the tablet USB port. Its killing my soft-keyboard on my screen 
> (I 
> > am not able to enter any data on my application and even I observed with 
> > other application. The result is same). When I remove my NFC reader its 
> > immediately showing keyboard on the screen. How can I get the Keyboard 
> even 
> > I have connected the my NFC reader to the tablet. 
> > 
> > Is there any way to call smart keyboard explicitly the tablet even Acer 
> > guys event manger kills soft keyboard whenever I connect my NFC reader 
> > through USB port. 
> > 
> > I am giving some of log, how its detecting and behaving :- 
> > 
> > 03-03 21:12:24.810: D/BatteryService(139): level:57 scale:100 status:3 
> health:2 present:true voltage: 3827 temperature: 286 technology: Li-ion AC 
> powered:false USB powered:false icon:17302701 invalid charger:0 
> > 03-03 21:12:24.810: D/WifiService(139): ACTION_BATTERY_CHANGED 
> pluggedType: 0 
> > 03-03 21:12:39.420: D/dalvikvm(226): GC_EXPLICIT freed 929K, 15% free 
> 22433K/26247K, paused 8ms+7ms 
> > 03-03 21:12:41.660: D/EventHub(139): No input device configuration file 
> found for device 'RFIDeas USB Keyboard'. 
> > 03-03 21:12:41.670: I/EventHub(139): New device: id=15, fd=221, 
> path='/dev/input/event5', name='RFIDeas USB Keyboard', classes=0x80000003, 
> configuration='', keyLayout='/system/usr/keylayout/Generic.kl', 
> keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false 
> > 03-03 21:12:41.670: I/InputReader(139): Device added: id=15, 
> name='RFIDeas USB Keyboard', sources=0x00000101 
> > 03-03 21:12:41.670: I/PowerManagerService(139): WakeLock: 
> SCREEN_FROZEN(PARTIAL_WAKE_LOCK             ) is acquired by pid(139), 
> uid(1000) 
> > 03-03 21:12:41.670: I/ActivityManager(139): Config changed: { scale=1.0 
> imsi=0/0 loc=en_US touch=3 keys=2/1/1 nav=1/2 orien=L layout=0x10000014 
> uiMode=0x11 seq=21} 
> > 03-03 21:12:41.960: I/PowerManagerService(139): WakeLock: 
> SCREEN_FROZEN(PARTIAL_WAKE_LOCK             ) is released by pid(139), 
> uid(1000) 
> > 03-03 21:12:44.030: D/dalvikvm(139): GC_EXPLICIT freed 333K, 46% free 
> 15799K/28935K, paused 6ms+5ms 
> > 03-03 21:12:46.990: D/dalvikvm(624): GC_EXPLICIT freed 22K, 5% free 
> 6301K/6595K, paused 1ms+2ms 
> > 03-03 21:12:54.890: D/BatteryService(139): level:57 scale:100 status:3 
> health:2 present:true voltage: 3826 temperature: 286 technology: Li-ion AC 
> powered:false USB powered:false icon:17302701 invalid charger:0 
> > 03-03 21:12:54.900: D/WifiService(139): ACTION_BATTERY_CHANGED 
> pluggedType: 0 
> > 
> > I hoping get some solutions for this problem:) I really appreciate 
> someone give a comment on it. 
> > 
> > BR 
> > 
> > Srinivas

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to