Sorry if this is answered somewhere else... was wondering if anyone else has this issue and what can be done to fix it. I am using Damage control ROM on my evo and when i'm in an application that uses the keyboard and then press my home button it does a weird/slow animation thing. The Application switches to the homescreen quickly but the keyboard stays on screen for a split second and the launcher/home screen drops down from the top. its just annoying me to no ends.
I'm using ADW launcher.
Related
okay so I've had this problem a few times on 2 different G2s
not sure what happens but the phone seems to trick it's self into thinking its still in landscape mode even though its in portrait and I end up with a black screen though I can see the notification bar and can even drag it down and see it so I know the screen isn't turning off and if I open the keyboard i can only see the very right side of the screen or what would be the bottom if it were in portrait mode yet the notification bar seems to work. It usually happens when I close the keyboard. It's not a huge problem as I can just hold the power button down to bring up the "power down, airplane mode, silent mode" screen up and that fixes it. I managed to get it to happen and was able to grab some screen shots. Anybody else have this problem?
I used to see that same issue on my G1 with ADW Launcher installed
ya it happens to me using the adw launcher... i think it is just a rendering issue. also if you use adw launcher you notice the pull down shade doesn't cover the very top when pulled down? just launcher glitches still runs like a champ now that i use temp root. beautiful thing about temp root is that unlike the g1 you don't have to reboot this thing every 8 hrs lol.... i do it just cause i feel like i'm still using my g1.. autostart kills all those damn google apps that run. setcpu is running great. no oc obviously but now you can throttle it... wireless tether plus they have it on a 3 click apk that you can use. SDk/adb knowledge needed though for it...
I've searched around but doesn't look like people even bring these two problems up, maybe you can help?
1. Whenever my phone is locked for over 2 minutes or so, and I unlock it, it seems to lag when i swipe to another home screen for just about 1/2 second after i swipe my finger. It runs fine after that. I've tried tweaking some settings but it doesn't seem to go away. Didn't experience this on a non-sense rom. Anyone with help on that?
2. Also, I noticed that if you open the keyboard when in the home screen, it moves the entire screen up with it. Is it possible to not move the screen up? It causes problems when I'm in a messenger and press the home button with the keyboard open because the entire screen flickers. Not much of a problem, just didn't experience this before either.
Thanks for any help at all guys.
If it's the original ADWLauncher then it isn't that well optimized and with Sense, I get that little like stutter as well. Sense is just a massive ***** to load up.
I don't know how your getting your keyboard on your homescreen. By default, the keyboard moves everything up no matter what with no settings really. You can have a look in Language and Keyboard but I doubt it.
Even before flashing a new ROM I was getting this lag. When you're in a message with the keyboard showing then press home, the messaging app clears but the keyboard stays up for literally like a full second then disappears. Yet, if you are within a message and go back out of the message (press upper left) it has no issue disappearing as it should.
Any way to fix this, it's really annoying.
Had the same thing. No matter which rom
Sent from my Galaxy Nexus using xda premium
Yep same here...
Its about half a second lag if you actually time it. But it never bothered me at all, i'm surprised it bothers so many people. This issue was posted before too.
I dont think its a lag but more just a transition type effect issue.
It is because the keyboard is its own application. The way android runs is it shuts down the messaging app first then the keyboard second thus the lag. Manually close keyboard before exiting if it bugs you. It bugged me a lot coming from my iPhone where the keyboard is a UI element and closes at the same time. I've just learned to close my keyboard then go home.
I've had it with every Android phone I can remember having. It's not remotely an issue for me.
theherodrownd said:
It is because the keyboard is its own application. The way android runs is it shuts down the messaging app first then the keyboard second thus the lag. Manually close keyboard before exiting if it bugs you. It bugged me a lot coming from my iPhone where the keyboard is a UI element and closes at the same time. I've just learned to close my keyboard then go home.
Click to expand...
Click to collapse
This. I now always press back, then home or my OCD kicks in.
Sent from my Galaxy Nexus using XDA App
Yeah, I'm having to do that too. Pretty bootsy if you ask me. Doesn't make sense why the OS can't close both applications at the same time though. Actually pressing back in the upper left closes the message and the keyboard at the same time.
shoman24v said:
Yeah, I'm having to do that too. Pretty bootsy if you ask me. Doesn't make sense why the OS can't close both applications at the same time though. Actually pressing back in the upper left closes the message and the keyboard at the same time.
Click to expand...
Click to collapse
When you hit back in the app it doesn't have to close the messaging app itself and just closes the keyboard app
Also, the way Android is written, is when you hit home it has to draw the launcher which is why it doesn't simultaneously close the two apps. Downside of the way android is programmed.
Is anyone having Jelly Bean issues? I am having the following issues:
1) Marking Messages as Read. If I have an unread message and the Messaging app is open under the home screen, if I use the lock screen shortcuts to open Google Now, it marks the message as read and then opens Google Now. It never did this on ICS.
2) Home Button Issues. If the screen turns off and I hit the home button to turn it on, it goes directly to the home screen. On ICS, it would just go to the most recent app (I have mostly avoided this happening again by enabling S Voice, but there's got to be a solution). Also, when I hold down the home button to open the Recent Apps screen, it will sometimes go to the home screen, and then open Recent Apps. Also, sometimes there is a delay between when I close an app and when it shows up in the Recent Apps screen.
Does anyone have any suggestions? Your help would be much appreciated!
I'm running FreeGS3 with Ktoonz 10/28 kernel and the blue battery bubble icon (with mod file flashed first) and I have the following issues.
1) The LED isn't as bright when on the charger when the phone is on... the red and green are quite dim. No issues when the phone is off (believe this is directly related to the JB ROM itself.
2) After 7 hours on the charger the battery was charged to 98%, When I was running w/o either the kernel or battery morph no issues.
3) Something took away the boot animation as I have just a black screen after the Samsung Galaxy SIII screen until you see the home screen.
Thanks in advance for detailed answers
Home button
I also had the same issue with the home button since s voice was frozen, enabling s voice double tap seemed to be the only way to fix. Hopefully a way that does not require s voice is found soon.
This is my first post here. I searched but didn't find anything like this. I posted on another site and nobody could help.
Ok so I just got my M8 yesterday and so far love it. However I have found a small issue that really bothers me. For some reason when on the lock screen gestures, if I swype left to go to home screen it always takes me to the screen just to the right of blinkfeed. I have changed my home screen and reset it so that my home screen is in the middle of two panels. (Blinkfeed is two to the rignt). However regardless each time I swype left on lock screen it takes me to the (what was the default) panel where the home screen used to be.
Anybody else experience this or know how to fix?
bump