Hi Guys,
I recently find a lagging in my samsung galaxy s3 it is usually in the dialer when i dial a contact it takes some few seconds like 10 sec to get the number dialed any idea how to resolve this issue. Thanks in advance.:good:
Fahimxda said:
Hi Guys,
I recently find a lagging in my samsung galaxy s3 it is usually in the dialer when i dial a contact it takes some few seconds like 10 sec to get the number dialed any idea how to resolve this issue. Thanks in advance.:good:
Click to expand...
Click to collapse
U are on which rom?
Hi Bibin,
I am in stock rom.
Fahimxda said:
Hi Guys,
I recently find a lagging in my samsung galaxy s3 it is usually in the dialer when i dial a contact it takes some few seconds like 10 sec to get the number dialed any idea how to resolve this issue. Thanks in advance.:good:
Click to expand...
Click to collapse
Have you tried factory resetting your phone yet? just to double check, this lag does not exist any where else right?
to factory reset, turn off phone, when phone is off, press volume UP + lock +home together, then select factory reset.
this should solve your issue, remember to do a back up.
you can also try clearing all your contacts then adding only one in to see whether the lag persists. although i would think a factory reset would be the most appropriate.
hope i helped
Conflict94 said:
Have you tried factory resetting your phone yet? just to double check, this lag does not exist any where else right?
to factory reset, turn off phone, when phone is off, press volume UP + lock +home together, then select factory reset.
this should solve your issue, remember to do a back up.
you can also try clearing all your contacts then adding only one in to see whether the lag persists. although i would think a factory reset would be the most appropriate.
hope i helped
Click to expand...
Click to collapse
Hi I will try thanks for your suggestion.
Mine does and I have done a factory reset. Its just a feature of the S3, You could upgrade to the SGS 2! its much faster
My phone does this too when dialing. I have to dial slowly, wait for a tone after each digit.
Don't know if it's always been like this or just recently. I'm on CM10.
Fortunately dialing manually isn't something I have to do very often.
I also get lag in the dialer loading the recent call tab. Im on beans rom. Shouldnt really see any lag on this phone but its not a deal breaker.
I'm having lag everywhere, especially multi tasking
I am on stock 4.04 and have no dialer lag in buttons or dialing.
Install ExDialer from play store.
Problem solved.
:thumbsup: :thumbsup:
I have lag as well. Not only that, it BUFFERS the dialing. I kept hitting dial on my wife's phone number and nothing was happening. So I kept pressing dial, finally it went thru. I talked for about a minute, hung up, and it then proceeded to dial her 4 or 5 more times. I'd quickly hit hang up and it would dial again. I finally just rebooted the phone.
I'm running stock rooted rom from AT&T
Use ExDialer
DramatikBeats said:
Use ExDialer
Click to expand...
Click to collapse
its not just the dialer. sometimes the whole phone will lock up for 20 or 30 seconds. not even hard buttons work. in a few cases ive had to yank the battery.
Dunno then lol, I've never had the dialer lock up on me
I know this is an old post but try this and see if it helps.
http://forum.xda-developers.com/showpost.php?p=48824534&postcount=88
Related
Hello All!
i looked all over the net but could not get any help, so i hope someone can help me here.
I have a galaxy S3 i9300
since 2 days, the counter on the phone calling icon (the green one in the main page) is stuck showing 1 missed call!
i have tried going into call logs, calling the missed call number, deleting all call logs, restarting & turning of my galaxy a couple of times but still the same!!
can anyone tell me what can i do noting that my phone is not rooted, and that i am still using the original dialer app!
attached is a screen shot of my home
What about factory reset?
Sent from my GT-I9300 using xda premium
hima1978 said:
Hello All!
i looked all over the net but could not get any help, so i hope someone can help me here.
I have a galaxy S3 i9300
since 2 days, the counter on the phone calling icon (the green one in the main page) is stuck showing 1 missed call!
i have tried going into call logs, calling the missed call number, deleting all call logs, restarting & turning of my galaxy a couple of times but still the same!!
can anyone tell me what can i do noting that my phone is not rooted, and that i am still using the original dialer app!
attached is a screen shot of my home
Click to expand...
Click to collapse
1) Open the Messaging app>Menu>Delete>Select all at the top and delete.
And/Or
2) Try deleting data of the messaging.
This worked for a colleague of mine but in her case, she had a '1' stuck for both messaging and call log.
Seeing as the call log also shows messages, this might work for you too.
Good luck!
this happening to me... but in message
ruterjunior said:
this happening to me... but in message
Click to expand...
Click to collapse
me too. us cellular version.
i found clearing the ram works till another message.
also go to settings. then hit developer options, you should have the "Dont Keep Activities" unticked. (works for some)
with that i found the battery doesnt last as long.
i sure this is a known issue and will be fixed soon i hope
my specs;
baseband=r530uvxlf9
let me know i want to get this figured out and fixed asap
I have tried clearing the ram, clearing phone app data, clearing messaging app data but still the same issue! Do you have any recommendation beside factory reset as I am not in favor for that option
me too have same problem ,, please help
same problem here, don't want to factory reset..this is very annoying from a flagship phone!
Same problem here
I have same problem on message, though so far I've been able to clear it by rebooting. Seem pretty dumb. I wonder if any bug report has been file to Samsung.
i also experienced this problem on messaging. i factory reseted the phone. it worked fine for a while but then again samething started happening..the second time i cleared all data on messaging app, unchecked "do not keep activities" in developer options. seems to work fine till now. and also make sure you dont have any unreaded conversation on "whatsapp messenger".
@SilentMODE,vet4snak,mrmozz,xxdesire5044XXX,hima1978 and others who have a problem with bug of missed call counter which hangs.
I found a solution to this problem bug of missed call counter.This is what you need to do:
-Make a backup of your contact,msg,logs,etc
-under settings -> application manager-> all find
-badgeprovider.apk
-logs provider.apk
-Contact storage.apk
and clear data and the problem will vanish
B.R. Nexus
Use thanks button if i helped you
Thanks! It works!
nexusino said:
@SilentMODE,vet4snak,mrmozz,xxdesire5044XXX,hima1978 and others who have a problem with bug of missed call counter which hangs.
I found a solution to this problem bug of missed call counter.This is what you need to do:
-Make a backup of your contact,msg,logs,etc
-under settings -> application manager-> all find
-badgeprovider.apk
-logs provider.apk
-Contact storage.apk
and clear data and the problem will vanish
B.R. Nexus
Use thanks button if i helped you
Click to expand...
Click to collapse
GREAT! IT WORKED! THANKS A LOT!
The 3 'clear data' seem to have only wiped the call log. Anyway I had backed up everything using Titanium PRO.
I called myself to get a missed call, the '1' appeared again, and then disappeared when I opened the log again. Hopefully the bug won't come back!
Thanks again!
fred1976 said:
GREAT! IT WORKED! THANKS A LOT!
The 3 'clear data' seem to have only wiped the call log. Anyway I had backed up everything using Titanium PRO.
I called myself to get a missed call, the '1' appeared again, and then disappeared when I opened the log again. Hopefully the bug won't come back!
Thanks again!
Click to expand...
Click to collapse
I also found that if you clear the call log it'll fix the problem. It comes back once in a while but is easy to clear.
nexusino said:
@SilentMODE,vet4snak,mrmozz,xxdesire5044XXX,hima1978 and others who have a problem with bug of missed call counter which hangs.
I found a solution to this problem bug of missed call counter.This is what you need to do:
-Make a backup of your contact,msg,logs,etc
-under settings -> application manager-> all find
-badgeprovider.apk
-logs provider.apk
-Contact storage.apk
and clear data and the problem will vanish
B.R. Nexus
Use thanks button if i helped you
Click to expand...
Click to collapse
Hi, thanks! it worked with only clearing the 1st 2 data.
What i did was i cleared the 1st 2 data, worrying that the 3rd would delete all my contacts.
so i synced my contacts with kies into the computer. after disconnecting the phone the notification was gone.
Only clear data from BadgeProvider
nexusino said:
@SilentMODE,vet4snak,mrmozz,xxdesire5044XXX,hima1978 and others who have a problem with bug of missed call counter which hangs.
I found a solution to this problem bug of missed call counter.This is what you need to do:
-Make a backup of your contact,msg,logs,etc
-under settings -> application manager-> all find
-badgeprovider.apk
-logs provider.apk
-Contact storage.apk
and clear data and the problem will vanish
B.R. Nexus
Use thanks button if i helped you
Click to expand...
Click to collapse
Thanks Nexus!
I had the problem with a 1 stuck on my Phone icon [Samsung Galaxy S3, GT-i9300, Android 4.1.1]. This was a problem that persisted across the update from Android 4.0 to 4.1.
I followed a single step in your proposal:
-Clear data from "Badgeprovider"
And added step:
-Enter Phone app and exit.
This removed the badge, which seems fairly harmless I guess no backup is necessary for such an action.
Not to add flamebait, but coming from iOS, things like this gets on my nerve. Since I'm new to Android, I don't know if this is a bug coming from Android or from TouchWiz or something else Samsung slapped on. Please tell us if this is one argument to run vanilla Android on the S3!
Try....Settings - Application manager - All - BadgeProvider, Clear data and restart phone
it worked for me
Hello all, this might be kinda strange, but I need your opinion about this issue.
I have updated my S II I9100 to the latest update found on Kies ICS 4.0.3, everything was kinda smooth had to install the update twice, but everything went just fine when the update finished in the second time.
The only problem I found is that the Log/Phone/Keypad screen is a bit different than what it is supposed to look, kindly check attachements. You will notice that the contacts button/tab at the upper right corner shouldn't be there - yes, some people might say this is good, but I just love the update to be just right. -
Also, from the Home screen, when I try opening Contacts from the 4 buttons at the bottom, it sometimes takes 2 to 3 seconds to launch and the same happens when using the tab in the Keypad screen.
I did hard reset my phone a couple of times, but nothing changed.
If the solution is to re-install the firmware, kindly advice me how to do it through Samsung Kies.
Thanks in Advance!
bingorabbit said:
Hello all, this might be kinda strange, but I need your opinion about this issue.
I have updated my S II I9100 to the latest update found on Kies ICS 4.0.3, everything was kinda smooth had to install the update twice, but everything went just fine when the update finished in the second time.
The only problem I found is that the Log/Phone/Keypad screen is a bit different than what it is supposed to look, kindly check attachements. You will notice that the contacts button/tab at the upper right corner shouldn't be there - yes, some people might say this is good, but I just love the update to be just right. -
Also, from the Home screen, when I try opening Contacts from the 4 buttons at the bottom, it sometimes takes 2 to 3 seconds to launch and the same happens when using the tab in the Keypad screen.
I did hard reset my phone a couple of times, but nothing changed.
If the solution is to re-install the firmware, kindly advice me how to do it through Samsung Kies.
Thanks in Advance!
Click to expand...
Click to collapse
Same Here ,, seems to be normal :cyclops::cyclops:
bingorabbit said:
Hello all, this might be kinda strange, but I need your opinion about this issue.
I have updated my S II I9100 to the latest update found on Kies ICS 4.0.3, everything was kinda smooth had to install the update twice, but everything went just fine when the update finished in the second time.
The only problem I found is that the Log/Phone/Keypad screen is a bit different than what it is supposed to look, kindly check attachements. You will notice that the contacts button/tab at the upper right corner shouldn't be there - yes, some people might say this is good, but I just love the update to be just right. -
Also, from the Home screen, when I try opening Contacts from the 4 buttons at the bottom, it sometimes takes 2 to 3 seconds to launch and the same happens when using the tab in the Keypad screen.
I did hard reset my phone a couple of times, but nothing changed.
If the solution is to re-install the firmware, kindly advice me how to do it through Samsung Kies.
Thanks in Advance!
Click to expand...
Click to collapse
Your Dial Pad looks perfect, there is nothing wrong with it. If you don't like it the way it is, there are many other alternatives in Market.
Hi,
[I'm posting here because I'm new at xda-developers forum and it won't let me post into the development threads.]
Yesterday I installed a new Beanstalk ROM (with Android 4.4.2) on my Samsung Galaxy S2 (GT-I9100). Everything worked well from the beginning except... that incoming calls could not be answered. The phone rings, and a rectangle shows at the bottom of the screen, without the number / picture of the caller (even though it knows the caller because it's in the contacts). It seems like the screen stops responding the moment the phone begins to ring. Also, there are no "Accept / Reject" buttons to drag the rectangle to. The only thing I can do is press the Power button to lock the phone, but it doesn't help - pressing it again to wake the phone brings me back to the same state - phone still rings, but nothing can be done.
A google search revealed that the same problem existed on a Nexus 5 device, and Google suggested to do a factory reset. So I did... and after that, I could answer incoming calls. But a few hours have passed, and I made a couple of reboots (manually), and again - can't answer incoming calls. Does anyone have a solution?
There was another small issue, which is much less important - after logging in to my gmail account, the apps weren't automatically downloaded, as with other ROMs.
Thanks,
Shlomy
sreinst1 said:
Hi,
[I'm posting here because I'm new at xda-developers forum and it won't let me post into the development threads.]
Yesterday I installed a new Beanstalk ROM (with Android 4.4.2) on my Samsung Galaxy S2 (GT-I9100). Everything worked well from the beginning except... that incoming calls could not be answered. The phone rings, and a rectangle shows at the bottom of the screen, without the number / picture of the caller (even though it knows the caller because it's in the contacts). It seems like the screen stops responding the moment the phone begins to ring. Also, there are no "Accept / Reject" buttons to drag the rectangle to. The only thing I can do is press the Power button to lock the phone, but it doesn't help - pressing it again to wake the phone brings me back to the same state - phone still rings, but nothing can be done.
A google search revealed that the same problem existed on a Nexus 5 device, and Google suggested to do a factory reset. So I did... and after that, I could answer incoming calls. But a few hours have passed, and I made a couple of reboots (manually), and again - can't answer incoming calls. Does anyone have a solution?
There was another small issue, which is much less important - after logging in to my gmail account, the apps weren't automatically downloaded, as with other ROMs.
Thanks,
Shlomy
Click to expand...
Click to collapse
1) reboot to recovery and then do wipe cache and Dalvik cache and then reboot the phone and see
2) Also open the phone app and go to it settings (press the menu key for the same) and once there Scroll down to 'Interface' heading and there uncheck 'Non Intrusive' and see
Sun90 said:
1) reboot to recovery and then do wipe cache and Dalvik cache and then reboot the phone and see
2) Also open the phone app and go to it settings (press the menu key for the same) and once there Scroll down to 'Interface' heading and there uncheck 'Non Intrusive' and see
Click to expand...
Click to collapse
Thanks a lot for the quick answer! Is this supposed to solve the problem entirely? The factory reset solved it for limited time...
Can you also please provide a link that explains this?
sreinst1 said:
Thanks a lot for the quick answer! Is this supposed to solve the problem entirely? The factory reset solved it for limited time...
Can you also please provide a link that explains this?
Click to expand...
Click to collapse
There is no link ma8, ALways a wipe cache/Dalvik will solve many issue's for u, give it a try and see.
Also u can check other KK based roms like 'Slimkat' or 'Omni' for instance and see
Sun90 said:
There is no link ma8, ALways a wipe cache/Dalvik will solve many issue's for u, give it a try and see.
Also u can check other KK based roms like 'Slimkat' or 'Omni' for instance and see
Click to expand...
Click to collapse
Well... I did (1), and it didn't solve the issue. I'm not sure what it was good for - when I install a new ROM, does it come with a cache? I thought all these custom ROMs come with no cache (and Dalvik cache) at all and these are filled-up when booting the ROM for the first time.
I also did (2), and this solved the issue indeed (giving up the non-intrusive interface which I don't need anyway). Thanks a lot for your replies!
I don't like to check other KK ROMs as long as this one is okay. I think the ROM is really great.
Thanks again!
Shlomy
sreinst1 said:
Well... I did (1), and it didn't solve the issue. I'm not sure what it was good for - when I install a new ROM, does it come with a cache? I thought all these custom ROMs come with no cache (and Dalvik cache) at all and these are filled-up when booting the ROM for the first time.
I also did (2), and this solved the issue indeed (giving up the non-intrusive interface which I don't need anyway). Thanks a lot for your replies!
I don't like to check other KK ROMs as long as this one is okay. I think the ROM is really great.
Thanks again!
Shlomy
Click to expand...
Click to collapse
Although (2) solved the main issue - I can now accept or reject calls - I am still interested to know why the "non-intrusive" dialog doesn't work for me, while it works for others using the same ROM on the same device. I see the incoming call card, with an icon (that should show the picture of the caller), but nothing else in this card, it is just white with no buttons.
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
I have to same issue that just happened and same as the screenshot.
Same issue...
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
mikeinstlouis said:
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
Click to expand...
Click to collapse
Latest update have little bugs
Sent from my Nexus 5 using Tapatalk
I am also having this issue on my Galaxy S4.
---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------
mrneoz81 said:
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
Click to expand...
Click to collapse
One way I found that I can close it is by opening the menu that has active apps, then going to RAM, next turn the phone on its side (<--- yes do that), then hit clear memory a few times. And done its gone.
Thanks! That worked on my Sprint S4! (restarting phone has also worked for me, but this is easier.)
After holding down Home button to open the menu that has active apps, the options were still covered by the text to speak box. So I had to FIRST turn phone on its side to make visible the pie chart icon on bottom left, THEN then going to RAM tab and hiting clear memory a few times. When I turned it back to portait orientation, the text to speak box was gone. Thanks!
This has been happening to me all day long. so frustrating. I am also not the tech savy one in the house and hubby is not around. So thanks for the quick answer to get rid of it until he can uninstall the new update. Thanks
What is the pie chart menu option? What is the RAM tab? And will just be a little easier for Google to fix this? Lol
same problem here
Galaxy S6, same problem, started last night (September 24, 2015) . I do know that some updates were performed last night, not sure what. How do I uninstall the update? Which one is it? Help! I use voice typing constantly, and my phone is a brick when this thing locks up. It covers all my buttons. "Restart" doesn't clear it, I have to totally power off and back on. Right now, I have disable my voice key on my keyboard so that I don't accidentally touch it while waiting for solution.
Me too - just started today after some updates yesterday.
Same here....has anyone responded with a fix yet??
THANKS!
Glad it's not just me and my Note 3, but where does google get off sending out this kind of crap? It's enough to drive me to a windows phone.
Having the same issue only way I can get ride of it is to turn off my phone
same issue on moto droid mini; have to turn off phone too! poor QA google!!!!!
Me too. Galaxy S4. Have to shut the phone down and restart it to resolve the issue.
Piece of crap
Note 4 same problem started on the 24th
Same issue, Note 4
Same issue, Samsung Note 4.
Yep me too Verizon Galaxy s6
Sent from my SM-G920V using Tapatalk
I have the Huawei Mate 20 Pro unlocked. However, one major bug that is annoying me so much to the point of potentially changing phone is when I get a notification that I received say for example an email, I swipe down to see the preview and then I have to press the Delete button several times - Im talking sometimes 6-7 times - for it to delete the email.
Anyone else got this issue and any ideas how to resolve it?
Cheers
Robert
I got it to with "read" at handset sms!
Very annoying!!!!
POWER1FM said:
I got it to with "read" at handset sms!
Very annoying!!!!
Click to expand...
Click to collapse
It is, it's really got me debating the handset tbh
I don't have this issue with any app and first time I see a post about it so guessing most people are ok.
You might want to try the option to reset phone settings (doesn't wipe data or apps) to see if it fixes it?
Same issue. Happens with Gmail. Except I think the issue is more of a delay (for me atleast). After pressing delete, I have to wait several seconds (usually over 5 seconds) for the notification to disappear).
PhilMorin said:
I don't have this issue with any app and first time I see a post about it so guessing most people are ok.
You might want to try the option to reset phone settings (doesn't wipe data or apps) to see if it fixes it?
Click to expand...
Click to collapse
Dont know about the other guys, but tried this, plus it was happening on my first LG screen mate 20 pro and then on 2 replacements afterwards so dont think its the phone, personally I think its a bug in the OS but doesnt appear to be widespread.