Hey gents,
After some searching with no answers, I decided to ask the question myself. I apologize if this has been addressed before. I'm currently running a stock r800x with the 2.3.3 ota update. I've had the phone for about six months, but shortly after the update my leading had been acting up. It's almost impossible to send messages now. When the icon is tapped, the window opens but is completely empty for at least 40 seconds. when the keyboard is pressed, it takes another 30 seconds our so and words lag five seconds after key presses (swype and android keyboard). finally, after tapping enter, the message won't appear in the window for some time and I get the "force close or wait" option. After 2 or 3 times touching "wait" and a good 45 seconds to a minute each time, the message will send. I'm at a complete loss here, because I have plenty of space on both my phone and sd card. Does anyone know wtf is going on? Any help would be greatly appreciated and I thank you in advance.
nom nom apple said:
Hey gents,
After some searching with no answers, I decided to ask the question myself. I apologize if this has been addressed before. I'm currently running a stock r800x with the 2.3.3 ota update. I've had the phone for about six months, but shortly after the update my leading had been acting up. It's almost impossible to send messages now. When the icon is tapped, the window opens but is completely empty for at least 40 seconds. when the keyboard is pressed, it takes another 30 seconds our so and words lag five seconds after key presses (swype and android keyboard). finally, after tapping enter, the message won't appear in the window for some time and I get the "force close or wait" option. After 2 or 3 times touching "wait" and a good 45 seconds to a minute each time, the message will send. I'm at a complete loss here, because I have plenty of space on both my phone and sd card. Does anyone know wtf is going on? Any help would be greatly appreciated and I thank you in advance.
Click to expand...
Click to collapse
Do you have a lot of messages in there? The next time you go in try deleting all threads, then make sure to set you limits to 50 messages per thread and 10 MMS per thread. If you have too many messages/threads it takes a long time of the phone to load them, and unfortunately unless you set those options properly the phone has no way to communicate this other than crashing.
My settings were all good, so I decided to bump it down 20 per conversation. It may have had something to do with 58 different threads open and almost 50 messages each :/ . Turns out you even androids need some good old fashioned house keeping. A quick wipe of all threads did the trick. Thanks for helping me out
-jason
nom nom apple said:
My settings were all good, so I decided to bump it down 20 per conversation. It may have had something to do with 58 different threads open and almost 50 messages each :/ . Turns out you even androids need some good old fashioned house keeping. A quick wipe of all threads did the trick. Thanks for helping me out
-jason
Click to expand...
Click to collapse
No prob glad it worked out and that my folly (I battled with this over a week before I figured it out) can help others!
Related
For the past few weeks ive been searching the forums and remember coming across a App that integrates into the long hold on the standby button, once activated it pops up a swipe to shutdown, reset, and standby I think it was. They are swipes like the iphone I can not find this app anymore and have been searching today for 4 hours with no luck If anyone has any idea what im talking about please let me know, and no it is not the action screen one, I might use that as a last resort.
Here you go - http://forum.xda-developers.com/showthread.php?t=554177 (Only 4 minutes )
Once again Clyde you are awesome, I may just start messaging you instead of asking in threads, Thanks man!
Hey there.. I just installed the Energy ROM after having received this phone as a gift from a friend (with an unknown other ROM installed). I haven't had any problems with it for several weeks until just earlier today when the Quick List has decided to randomly start appearing on my screen. I don't even know how to trigger that screen to appear myself, but I can leave my phone unlocked on my desk and it'll randomly show the Quick List for a little while, then it'll vanish, sometimes extremely quickly. But I can't do anything on the phone anymore since it's constantly appearing and interrupting whatever I'm trying to do.
Like I said, I attempted to install an Energy ROM (Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.Mar.08.7z, according to the file I downloaded from the Energy website) and it just finished no more than 30 minutes ago. As soon as I turned the phone back on from a reboot, that dang Quick List screen appeared.
Does anyone know why it keeps popping up and how I can get it to quit? Or is there some way I can just disable the Quick List altogether (as the options on it aren't really useful anyway..)? Thanks for any help ya'll can provide!
Started having this problem a few weeks ago. Did some hardresets, some task29 and tried different roms. But this quick list keeps appearing outof nowhere. Starts to get frustrating.
It's happening again...
So, for no reason that I could tell, it magically started working again (same rom as listed above) and I never saw the Quick List window again until today.
Today, I was using that same ROM as before, but the Quick List window started appearing. I thought that perhaps it was just something to do with that build, so I upgraded to the English build available at (well, tried giving the link but apparently I haven't posted enough, so never mind). It's at "http : // Energy Roms dot com forward slash www forward slash flavors forward slash sencity.html" for the HTC Touch Pro 2 Cookie (April 8, 2011 version). The ROM installs without a problem (absent the annoying attempts to get the phone to not constantly display the Quick List) but as soon as I power the phone on, the Quick List starts blinking on again.
I searched around as before for a solution and thought I could just disable the setting so that when I hold the end call button, it displays the Quick List, but after 10+ attempts to get to the settings window without the Quick List appearing and interrupting me (then closing itself automatically and displaying the Home screen), I finally got the setting saved and it didn't change anything.
Is it possible to just turn the Quick List feature off? Is there some known reason why it has possessed my phone? Thanks for any help ya'll can give.
Is there still no solution for self appearing Quick List? because I have the same problem :/
EDIT:
I've solved it The front keys flex need to be reconnected to main flex because "endkey" was self pushed what in energy rom is configured to turn on Quick List.
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Dubadai said:
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Click to expand...
Click to collapse
Happens sometimes to me too and I am rooted on stock. Pretty sure it has nothing to do with us and everything to do with whatsapp having an ICS bug.
Sent from my Galaxy Nexus using Tapatalk
Whatsapp used to have exact same problem on my Nokia 5800XM too, I think it happens because of Whatsapp.
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Confirmed bug for me too
Galaxy Nexus GSM
AOKP M4
Franco M2
To everyone who replied, thank you! Makes my life easier knowing its not ROM/Kernel etc...
Filed a complain to Whatsapp, such a great app apart from this bug!
Miasmic said:
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Click to expand...
Click to collapse
I usually press home button and then my Whatsapp icon on my main screen, usually goes fast, but still... rather annoying
How deep would this 'error' lie? Could devs fix it?
I get this exact same problem with Handcent! Currently using Swype, and like 30% of the time I will have to go back to the conversation list and re-select my conversation to start typing again.
Sent from my Galaxy Nexus using Tapatalk
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
ohh3nry said:
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
Click to expand...
Click to collapse
I am also using Nova, but I'm not sure why that would affect other apps like this.
Any solution to this problem?
Got the very same at my galaxy s6, too. Android 5.1.1
I'd also like to know if there's any workarounds for this. My wife's having the issue and she's blaming me. :silly:
I may have a workaround. I have the galaxy note 3 and i use a custom rom thats pretty much close to stock and I notice that if I lock the device and unlock shortly after, I can't type anywhere, on kik, what'sapp, gosms pro, even google search. So I've just decided to test things out and see what's going on and here is what I found....
Eventually I can type again if I simply wait, but no one likes to wait but this is the longest solution.
Clearing the RAM using built in cleaner or 3rd party memory cleaner seems to allow me to type again.
I didnt like playing the guessing game in knowing how long to wait before I can type again so in kik or go sms pro, I would type one of the native apps' emoticon and then hold the backspace button down until it erases it...then I knew it was ready to let me type again (I have haptic feedback on for keyboard presses so I can look away as I hold down the backspace button - this would let me know when it eventually erased due to the haptic feedback of the smiley getting deleted).
Since the issue occurred only after unlocking, I tried turning off the lock screen completely and turning off phone and back on again....keyboard types right away with no issues!
Its more secure to have a lock screen on the phone so turning off lock screen isn't the best option unless you're like me and are the only person at home with no worries of someone else taking your phone so I decided to try something else that seemed to solve the issue, and that is..............turning off "Multiple Widgets" in lock screen.....tested and worked! I can totally type again right away after unlocking the lockscreen shortly after locking it.
This is what worked for me and for you developers out there....if you can use this to pinpoint why this happens on android, perhaps you can use this information to rectify it.
Hope I helped!!!
Ive sort of tried to search this one (How do I search JUST the Epic 4g section of XDA??) and found no one describing this problem the way I do...
This is my second time having this issue, and the fix for it last time was a pain in the ass, so id like a new fix-
Every app, every aspect of my phone, continuously resets/reloads. This is most noticeable with Hancent SMS, as it saves a message as a draft when you close out of the app... Well, right now, ill be typing and "message saved as draft" will constantly pop up at the bottom of the screen (about once every 2 seconds), and the phone will lag and it will erase 1 or two characters(making me look like I cant type :silly: ).
If this was the only problem, maybe I could live with it, but it affects everything. Launcher Pro randomly/continuously resets. The notification bar often resets while trying to pull it down. The phone app will close or freeze as soon as I start receiving a call. Sometimes it'll play my ringtone without a way for me to answer, other times I never knew I missed a call unless they leave a voice mail... And sometimes its worse than others, sometimes its fine for an hour, then something goes stupid and even a reboot doesn't help. For instance, right now, it was happy. I launched aLogcat to check it out and now the screen orientation REFUSES to stay one way. Even setting the phone down, it switches directions every few seconds, which makes aLogcat reload and therefor its unusable.
I haven't mentioned what im running because Ive had this exact same issue on a totally different rom, almost a year ago, but im running-
build - SleeperROM_3.0.0_FC09
kernal - 2.6.35.7-Shadow-FC09_v1.0
baseband - S700.0.5s.FC09
firmware - 2.3.6
Ive had this happen on EB13 on the EpicExperience ROM too.
SOO, if anyone has advice on how to fix this, id be extremely interested.
On the other hand, last time I had this issue I was convinced it was a corrupt piece of memory somewhere early in the OS, something I corrupt during install, and I went ahead and reflashed and wiped and reflashed and wiped and returned to stock and etc. etc. etc... and that seemed to work... actually, I dont know exactly what part of the process fixed it, thats why I do not want to repeat it unless I have to... BUT, if someone would like to explain/point me in the right direction. I'd like to know how to DELETE AS MUCH AS POSSIBLE and FLASH as CLEAN as possible. (that is, if no one else knows of a fix for my problem)
thanks all!
Err, well only thing I can think of is a truly clean install using Odin. This means do not restore any data from backups. Then slowly begin installing applications 1-by-1 through the play store website (for speed sake) to see if your issue creeps up again.
It also couldn't hurt to format your SD card too. Corrupt data on the SD card can cause some wonky things at times.
get another device...i hope u have the equipment protection plan
Thanks for the advice guys OFF TO THE ODIN MACHINE! haha.
I don't know exactly what I did that made this start happening, but right now every time a toast message pops up it stays on the screen for over 10 seconds. If there are other messages queued up then it will display all of them one after another each for over 10 seconds. I did a Google search and could not find a solution. Has this happened to anyone else?
I've tried everything short of a factory reset. I rebooted and safe mode and it still happens. I reset all of the application preferences, as far as permissions and that sort of thing goes, that fixed a few issues I've been experiencing but the toast problem persists.
Is this a bug? is there a solution? Can you adjust the timeout for toast messages? Are there any third party apps that change this setting on an unrooted phone that I unwittingly may have used?
Will I be forced to do a full factory reset to fix this problem? It's really annoying, haha!
thanks in advance for any help
I did everything including a factory reset and those toast messages still did the same thing, so I am thinking it definitely is an OS system upgrade problem!!! It is so annoying !!
twowreally said:
I did everything including a factory reset and those toast messages still did the same thing, so I am thinking it definitely is an OS system upgrade problem!!! It is so annoying !!
Click to expand...
Click to collapse
I still don't understand if this happens on everybody's Pixel 3 or if it's just ours. if it's just a few people then there has to be a common thing that caused it to start doing this. I haven't thought about it too much but my first suspicion was SystemUITuner. did you by chance install that and change anything using it?
I can't think of anything else that I have had to enable permissions with ADB for on here that would have messed with the display settings.
I've been rooting every phone I owned since cupcake. usually owning more than one at a time because well that just makes your power level go up exponentially ... through carelessness and not reading what I needed to before purchasing my Verizon Pixel 3 XL, This is the first phone I've had in my life for more than a month or so that was a daily driver without root.
my point is, I really can't think of a reason why the timeout for all toast messages system wide would suddenly change to be 30 seconds long instead of three. I would have bet on it that that is something that you need root to alter. ??*
typos are speech to text
Sent from my Google Pixel 3 XL using XDA Labs
looking at Google's past release schedule and also starting to hear rumors about Android 11 (they did put a system image up on Google's page but you cannot install it without an unlocked bootloader), we should start hearing official announcements about it soon, with beta1 probably end of April beginning of May.
Even if there are a few not annoying bugs I think it would be worth the upgrade to get rid of these toast messages covering all kinds of stuff that I need to be reading NOW! not in (in the case of three or four toasted pop-up great after each other) 2 minutes later when I've already Ben distracted and can't remember what I was wanting to be able to tap on that was under the eternal-1 toast message timeout.
it's very interesting to me that if you Google this problem there's maybe one or two results. I'm very curious what we are doing to cause this issue. if you or anyone from the future is reading this and knows This information please leave a little response or just post a link it, so maybe I can die happy having finally solved this riddle
thank you in advance
Sent from my Google Pixel 3 XL using XDA Labs
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.
testbug said:
... it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Click to expand...
Click to collapse
Oh my, thank you so much, I had the same problem and this solved it!!!
I wish there was a way to make it shorter than 3 seconds but from my research it can not be changed can it?
syndre said:
looking at Google's past release schedule and also starting to hear rumors about Android 11 (they did put a system image up on Google's page but you cannot install it without an unlocked bootloader), we should start hearing official announcements about it soon, with beta1 probably end of April beginning of May.
Even if there are a few not annoying bugs I think it would be worth the upgrade to get rid of these toast messages covering all kinds of stuff that I need to be reading NOW! not in (in the case of three or four toasted pop-up great after each other) 2 minutes later when I've already Ben distracted and can't remember what I was wanting to be able to tap on that was under the eternal-1 toast message timeout.
it's very interesting to me that if you Google this problem there's maybe one or two results. I'm very curious what we are doing to cause this issue. if you or anyone from the future is reading this and knows This information please leave a little response or just post a link it, so maybe I can die happy having finally solved this riddle
thank you in advance
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Just an FYI, coming from AT&T prepaid 6 years during the covid party the depth AT&T is it has taken me 9 months to move to postpay. It is a corporation a complete morons above customer support. All my problems are met with an upsell attempt and I have bit once or twice in return I was kindly bitten all this to say that they put a Motorola one 5G Ace 64 4G ram in my hand and I have the same issue except might hang for 20 to 45 seconds it seems like 90 seconds! May well be. Obviously they're not translucent but the desktop or any operation underneath it will take a finger command if you know where the hell to push. I did not get it from Amazon but I was looking to upgrade to the 128 prior and post this phone and one of the main salesman there with Motorola America which of course is not a Motorola product it's just a Motorola name. The ruination of a long-standing pioneer groundbreaking company! and he wanted to know more information from me and wants me to become a free paid intern or some crap and help them figure out what's going on so there you go? I am sure I am not the only one and just as sure as I am of that, I am sure that the people that make them and sell them and talk about them all day to potential customers or two customers have no freaking idea what their products do.!!
metpet said:
Oh my, thank you so much, I had the same problem and this solved it!!!
Click to expand...
Click to collapse
testbug said:
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.
Click to expand...
Click to collapse
dude... thank you.
i dunno how leaving a toast message on top of the buttons you need TO take action helps but that is what caused, likely, or at least what corrected the issue for me.
Moto G7 Supra (Power)
testbug said:
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.II
Click to expand...
Click to collapse
I can't find this accesability option on my note 10 + g975fd bubi know it was some kind of setting somewhere because I remember turning it on trying to see some message it waS throwing while I was setting up some Tasker task. Which makes me think it might have been turned on by option for a tasker action but I'll be damned if I can find it again. It's actually nice most of the time but lately it's been really annoying to me because it shows over the keyboard and most of the time an OK or cancel prompt. And like previously mentioned if there are ten of them its quite a long time to wait. And I also turned something on that does a toast every time an intent is launched so you can see how this has multiplied the issue. I think it's one of those situations like (in Tasker you can say launch so n so app, one of the potions is to make the app launch a new instance and another is to have the app not appear in recents. That's all fine gravy for that instance but nobody anywhere ever says that from now on any time you launch that app that it will launch a new instance and it won't appear in recents) whether it's in Tasker or from the Launcher or if you just switch to another app and back. It quickly becomes an issue when you are trying to enter passwords or watch Netflix and do something else real quick. And if you don't put 2 together with 2 because you didn't notice right a way it can be a brain bender trying to figure the little problem out. I'm thinking that's what I have done is set some obscure option for God knows what experimental task and now its stuck that way. But it's really not something I want to bother joĆ£ (Tasker de"sorry for spelling") with and he may not know anyway. But thanks for the thread and any other suggestions would be appreciated.