Lately I've noticed the system to be laggy intermittent. Often it's media-related, such as going into the gallery, activating the camera, or trying to attach a video to WhatsApp
Otherwise, what's been CONSISTENTLY slow is the dialer. After I enter a phone number and press dial, I've waited up to 10-15 seconds for the phone to actually transition to the next screen of actually dialing the number. Also frustrating is after I hang up, it takes 5-10 seconds to actually go from the active phonecall screen (with the call timer) to screen where it says "call ended" at the top of the screen where it will pause for another few seconds (during which I cannot call up the number pad so can't make another call) and then FINALLY it gives me back the number pad.
Most infuriating is the splash screen. Yes it's only 1-2 seconds. But my work requires me to make lots of quick short phone calls. The 1-2 seconds interrupts my work rhythm severely.
Is there a faster, free dialer out there? I wish the dialer was like what I had on the OnePlus X: simple, fast, no splash screen silliness and just works.
I never had anything lag in 3 months now. Maybe the multitasking animation skips frames when switching between apps, but that's it. I did disable 3rd party apps and most of Google **** except Play Store and YouTube.
Related
The reason for this is when I am in the car and am using the bluetooth to answer the phone is in my case on my belt. When I get a call the screen comes on and even after the call is completed it stays on for 2 minutes. I then end up calling someone in the last called list if the screen bumps the case. I don't notice because my dumb car always wants to download the phonebook after every call and the stereo doesn't connect the outgoing call. Then someone tells me that they got 2 minutes of my music on their voicemail if they didn't answer. Ended up being very embarrassing when call went out and I made some comments that "someone" was not supposed to hear.
I looked with the advanced config tool but could not find anything.
Any ideas appreciated.
Tks
Perhaps stopping the screen from waking is too drastic. This means you effectively disable caller-id. I would suggest looking into installing a screenlock tool.
I am trying pocketshield for now. I was going to look at su2u but I was told that incoming calls still turned the screen on. Will see how this works for a few days.
Thanks
Well I tried pocketshield and it doesn't really do what I need. It still lets the damn phone call after I have hung up. It leaves the screen on and at the lasted called screen. bump the screen and it calls one of my last called list. Going to try Touchprolock now and see how that goes...
I have "locked" (AT&T stock ROM - using long press end key to lock) my device and then hit the power button momentarily.
This turns off the screen. When an incoming call hits, screens lights up. After call is terminated, screen turns off.
TP2 - WM 6.1 - T-Mobile
Self Dials last number and Voice commands turn on - Spooky
About a week ago I started noticing a microphone (ala Larry King) in my notification area at the top of my home page. I would come and go and make a small beep sound. Finally realized it must be voice commands. Well I keep turning voice commands off but they keep turning on. I have loaded no new software in the last week. I have never used voice comamnds.
Also about a week ago - and it is getting worse - after making a phone call and hanging up, my TP2 will start dialing the last phone number out of nowhere. It usually happens when I am on my home screen and I now move the phone. TP2 is my first touch phone and I have always had a lot of fat finger dials. I always assumed it was something that I did. But now out of nowhere, I am on the home screen, the phone starts to dial. If I pick the phone up and shake it, it will start to dial. this will happen a couple of times and then it stops. thinking that it might be related to the voice commands, but not sure.
Any help or ideas?
OK, still baffled. I do have a voice mail notification and voice commands are turned off. If I pick up my phone kind of rough and shake it a bit it starts to dial my last phone call consistently now.
Please someone help me. My friends are hating me.
OK, so it is definately related to having the voice mail notification. If the voice mail notification is present, then picking up my phone, kind of like tossing it in the air a couple of inches and catching it, will make it start to dial my last call. Once I listen to the voice message (and the notificaiton is no longer there), picking up the phone roughly does not make it dial.
I do remember that about 10 days ago I uninstalled T-Mobile visual voice mail. Then I kept getting a text message and had to call T-Mobile to have them do something on their end.
Still I need help to understand how to stop it.
yea my phone was doing the same thing recently but it was only when i had it plugged up to my car charger. I assumed it had something to do with the charger but im not sure if thats the real problem
It may be that mine only does it when it is plugged to charge also. At work, where I have really begun to notice it, my phone is always plugged into a split that has a charger and headphones.
Sounds like your talk/phone button is getting stuck. On most roms if you press and hold it it initiates voice comm. Pressed once brings up dial pad, twice calls the last number, press and hold is voice comm. So most likely its the hardware. Either that or paranormal activity. Set up a camera to catch it in the act.
I was starting to wonder if it was hardware, because if I shake it it dials. The phone button getting stuck makes sense. I did not know that click twice would dial last number and click and hold would turn on voice commands. Thanks for the info - exactly what i was looking for. Luckily I bought additional coverage (I have a six year old that likes to play games on my phone). Love the keyboard of the TP2, but would really like to get an android os. We will see.
Thanks again.
Hi,
I've got the latest FW and am running on DooMLoRD's kernel #8 (now on #9), min/max 256/1209MHz and everything was fine until a couple of days ago when some random Force closes started appearing, and today I experienced SIM lock skips. By that I mean that when my phone boots, it shows SIM lock screen, but after a few seconds it continues to main screen without me entering the code. This second thing started happening after I've installed WidgetLock Lockscreen.
The phone also didn't allow me to connect to my operator. It showed me a toast message Your SIM card can't connect to this operator, or something along that line.
Also, some system apps started FCing, and when I was receiving a call, I saw only the notification bar and black screen, thus could not answer. My phone usually vibrates for a few seconds, then starts ringing, and a bit after that shows the screen with who's calling and the answer/reject slide bar (this whole action is way too slow :/ ).
I went into recovery mode and restored one of the backups, then turned on my phone and everything was alright. After that I restored the newest backup from today and now everything seems to be in its place.
Any ideas what might have been the problem? The call screen delay is still there (it show up after 10 seconds of ringing + a second or two to be able to answer). Is that normal? I also noticed that with WL Locksreen enabled I have to wait SEVENTEEN seconds to be able to see the call screen and answer the call.
Usually the dialing pad, and call history shows up quickly, i noticed in pass 3 weeks it is getting slower.
Sometimes when I tab it to dial, it just hangs there doing nothing even I can see a response after tabbing the name. Sometimes it will come up wait, force close or ok window. Sometimes I need to wait like 1 minute for the call to dial out.
Any idea why this is happening? Perhaps due to dial log too big? Or something else?
thanks.
Anyone has any idea?
Hey guys,
On my OGP, I have noticed that once I press the side button to unlock the screen, the touch keys light up instantly but the actual screen takes 1-2 seconds to light up after the button press. It may have gotten worse over time, or that may just be me being paranoid. Also, in messaging settings I experimented with messaging skins, and those seemed to lag my messages a lot (like when I clicked on a conversation, it took 2-3 seconds for the conversation to load, whereas before it was instant). When I removed the skin and went back to the default one, the lag still persisted. If anyone knows how to fix these issues, I would be grateful! My device is stock unrooted with value pack update, US AT&T. Only settings I changed was turned on quad core optimization.
Thanks,
killer
Fixed the lock screen lag by removing my dewdrop screen animation. Leaving it at basic drastically increased speeds to easily under a second. Now for the messaging lag...