Galaxy S6 & Edge get €100 Price Cut—New Models Incoming

Samsung has dropped the price of both the Galaxy S6 and S6 Edge by … more

How To Port Fully Featured Sony Xperia Z4 Camera

Xperia Z4’s hardware may not impress, but its software is definitely … more

Experimental TWRP Available For Moto G 2015

XDA Senior Member squid2 has posted experimental builds of TWRP for the Moto G … more

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

[BUG?] Toggle delay on ?123 (symbols) key on AOSP keyboard

388 posts
Thanks Meter: 79
 
By androidmeda, Senior Member on 10th June 2014, 10:49 AM
Post Reply Subscribe to Thread Email Thread
Don't know where to put this but ever since the 2.6.1 update there's a considerable delay in toggling from alpha keyboard to symbols/number. I can count up to two seconds before it first toggles then acts normal while it's open. I uninstall Xposed and it works fine again. The odd thing is that it only affects AOSP keyboards and variants. Non-AOSP ones work without a hitch. Or is this just me?
 
 
10th June 2014, 08:46 PM |#2  
rovo89's Avatar
Senior Recognized Developer
Thanks Meter: 37,187
 
Donate to Me
More
Did you test without any active modules?
11th June 2014, 11:02 AM |#3  
OP Senior Member
Flag Manila
Thanks Meter: 79
 
More
Quote:
Originally Posted by rovo89

Did you test without any active modules?

I did. Started off by disabling one module after another until all that was left was the framework. I'd like to go back to an earlier version but the modules I use needed the update.
11th June 2014, 08:21 PM |#4  
rovo89's Avatar
Senior Recognized Developer
Thanks Meter: 37,187
 
Donate to Me
More
Not sure how well this will work, but could you please try to take a logcat of that situation? There are many apps which can also clear the log before you start, so it can hopefully be reduced to just the relevant lines (if there are any - not sure about that).
14th June 2014, 08:22 AM |#5  
OP Senior Member
Flag Manila
Thanks Meter: 79
 
More
Quote:
Originally Posted by rovo89

Not sure how well this will work, but could you please try to take a logcat of that situation? There are many apps which can also clear the log before you start, so it can hopefully be reduced to just the relevant lines (if there are any - not sure about that).

I have attached two logs. The larger one with xposed 2.6.1 installed, the other without. I did the exact same thing for both: Start recording, go to home screen, open messaging, open keyboard, toggle between alpha and symbols a few times, then stop recording. Hope the logs make sense because it's all alien to me. :-S Viewing it from catlog, though, shows xposed doing something with the keyboard.
Attached Files
File Type: zip saved_logs.zip - [Click for QR Code] (176.6 KB, 3 views)
16th June 2014, 08:44 PM |#6  
rovo89's Avatar
Senior Recognized Developer
Thanks Meter: 37,187
 
Donate to Me
More
Starting to hate MIUI (oh well, I probably already do):

Code:
06-14 15:06:22.026 I/Xposed  (  844): java.lang.IllegalArgumentException: Cannot transfer object from class android.content.res.MiuiTypedArray to class android.content.res.XResources$XTypedArray
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge.setObjectClass(XposedBridge.java:773)
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge.access$6(XposedBridge.java:759)
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge$7.afterHookedMethod(XposedBridge.java:358)
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:645)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.TypedArray.<init>(Native Method)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.MiuiTypedArray.<init>(MiuiTypedArray.java:13)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.Resources.getCachedStyledAttributes(Resources.java:2267)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.Resources.obtainAttributes(Resources.java)
It would need a more detailed analysis and even more workarounds... Sorry, currently I don't have the time for that. You can try to use the "disable Resources API" option in Xposed Installer, which should prevent these messages, but some modules won't work anymore.
17th June 2014, 09:06 AM |#7  
OP Senior Member
Flag Manila
Thanks Meter: 79
 
More
Quote:
Originally Posted by rovo89

Starting to hate MIUI (oh well, I probably already do):

Code:
06-14 15:06:22.026 I/Xposed  (  844): java.lang.IllegalArgumentException: Cannot transfer object from class android.content.res.MiuiTypedArray to class android.content.res.XResources$XTypedArray
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge.setObjectClass(XposedBridge.java:773)
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge.access$6(XposedBridge.java:759)
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge$7.afterHookedMethod(XposedBridge.java:358)
06-14 15:06:22.026 I/Xposed  (  844): 	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:645)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.TypedArray.<init>(Native Method)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.MiuiTypedArray.<init>(MiuiTypedArray.java:13)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.Resources.getCachedStyledAttributes(Resources.java:2267)
06-14 15:06:22.026 I/Xposed  (  844): 	at android.content.res.Resources.obtainAttributes(Resources.java)
It would need a more detailed analysis and even more workarounds... Sorry, currently I don't have the time for that. You can try to use the "disable Resources API" option in Xposed Installer, which should prevent these messages, but some modules won't work anymore.

I was just able to read your sentiment about MIUI. I didn't realize it went that far. Well, since I'm the only one reporting this problem, I won't bug you about it any further while I'm on this ROM. I've dropped back to 2.5 for now. Looks like the updated modules that wanted a higher version still run for some reason. Thanks for taking the time to look at it. :beer:
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes