Hi XDA! I kind of need help. I recently flashed the 5.1.1 SlimLP rom, but until the first boot and up until now, Dialer has stopped working. I can't call and likewise, people can't call me. When I try to call, the said dialog will appear. When people try to call me, it will ring on their side. My phone will ring, but nothing shows up. After they put down the call, I'll receive a notifcation saying I missed a call. Any help?
P.S. It also soft reboots, any help?
PPS. Any tips on performance and battery life? This thing sort of lags here and there and the battery life LEAKS. I think I may have done something wrong with the isntallation since it's doing me more bad than good.
THANKS IN ADVANCE AND PLEASE EXCUSE MY NEWB-NESS. Hope you bear with me.
Ciao.
Go to recovery, wipe everything (data, cache, /system) and flash the ROM and Gapps again. This sometimes removes bugs for me.
Related
3 days ago I started experiencing weird phone behaviour. I tried calling someone but i didn't hear the "calling" beeping sound nor i could hear if there was any answer on the other end. Then i couldn't hear anything when i was getting calls. It didn't matter if i use the "loud" speaker or the "on-ear" speaker, the result was the same - no in-call volume. Microphone and "loud" speaker seem to work fine as i could use them as usual with other apps. Mobile data was working, so antenna was also OK, SIM card seemed to function properly as well. Other people who I tried speaking to did hear me fine, just i couldn't hear anything.
I tried freezing, then uninstalling all the non system apps that i thought could have impact on this matter, but that didn't help. I was using AOKP Rom and i had nand backup of Omega Rom 5.2 with stock samsung touchwiz, I tried restoring back to it, but for my surprise the in-call sound was still quiet. I didn't know what else could be and let it alone for an hour or so. Suddenly, the next time I tried it again, it WORKED!. After 2 hours of it working, i got back to my AOKP as i have it backed up right before switching to Omega Rom backup. I defrosted the apps and reinstalled the uninstalled ones. Nothing was influencing the in-call sound of the phone, everything worked fine.
The next day this problem popped up all of a sudden again. I got mad, i tried everything i did before except restoring the stock rom. Nothing helped. I then booted into CWM and set to fix permissions, to wipe Dalvik cache and i flashed the latest modem. Rebooted. The in-call sound was OK again. Something of these actions fixed it.
Today i got this NO IN-CALL SOUND bug once again. Seems like it wasn't the new modem that helped me. I booted to CWM and wiped Dalvik cache, rebooted, the in-call sound was working fine again. So, wiping Dalvik cache does fix the problem so far.
I'm keen to understand what exactly could cause this weird behaviour of disappearing in-call sound. Do you have any ideas?
I have the same problem.
If you find any sollutions, let me know.
You may delete some system apps.the solution is that you can just flash a rom and don't delete the apps you don't know
I've experienced something similar. I think in my case the MIC wasn't working either, but not entirely sure about that.
This thread seems to be about the same issue:
http://forum.xda-developers.com/showthread.php?t=1721604
Also while browsing the developer forum, I bumped into something interesting:
http://forum.xda-developers.com/showthread.php?t=1745974
This is for a ROM I don't use, but if the it's the same issue, and affects other ROMs too, I'd be very interested in knowing what exactly was fixed here.
Experienced this problem for the first time today, the volume actually disappeared during a call. Read through the posts suggested above and cleared cache and dalvik, but it didn't make any difference. Finally, I removed the battery, re-fitted and re-booted and it's currently working again. There does seem to be an issue with Omega/Siyah 1.2.6 combinations which is what I'm currently running
Hi community!
My phone mutes if i pick it up while ringing.
Kinda remember there is a mod or app which makes ringing less loud when the phone senses being picked up to recieve the call.
That might be useful sometimes, but i don't have any of such installed.
I browsed through settings, ROM control, but haven't find any motion controlled sound option.
This is quite annoying, i miss a lot of calls, cause most of the time i carry the phone in my pocket, so it's always moving and never ringing.
Vibration works perfect though.
Any help is much apprecited.
Btw.: i'm on P.A.C. ROM, with latest Dorimanx kernel.
I never had any issue whatsoever, that's why i try to avoid wiping the phone and put the whole thing together again from scratch.
Cloned as second ROM and installed again without wipe, to get rid of the mods, but didn't help.
Thanx for your help in advance! :highfive:
pederzen said:
Hi community!
My phone mutes if i pick it up while ringing.
Kinda remember there is a mod or app which makes ringing less loud when the phone senses being picked up to recieve the call.
That might be useful sometimes, but i don't have any of such installed.
I browsed through settings, ROM control, but haven't find any motion controlled sound option.
This is quite annoying, i miss a lot of calls, cause most of the time i carry the phone in my pocket, so it's always moving and never ringing.
Vibration works perfect though.
Any help is much apprecited.
Btw.: i'm on P.A.C. ROM, with latest Dorimanx kernel.
I never had any issue whatsoever, that's why i try to avoid wiping the phone and put the whole thing together again from scratch.
Cloned as second ROM and installed again without wipe, to get rid of the mods, but didn't help.
Thanx for your help in advance! :highfive:
Click to expand...
Click to collapse
Sounds like a ROM issue.
So ask in ROM thread.
Could also be a hardware issue, but check all ROM settings first.
Good luck !
It_ler said:
Sounds like a ROM issue.
So ask in ROM thread.
Could also be a hardware issue, but check all ROM settings first.
Good luck !
Click to expand...
Click to collapse
Tried them all, didn't help.
No ideas in rom thread either.
I think i'm gonna have to make a clean install to get rid of this for good.
Thanx anyways!
Hey everybody.
My girlfriend is having a terrible problem with her new Xperia Go. It's running the latest Stock Firmware and Kernel without Root and every time she gets an incoming call, the phone won't react for about 15 seconds and then a FC Popup appears. This happens as soon she tries to answer the call. We rebooted it and it worked as it should after a fresh boot, but as soon she uses apps like Whatsapp, Facebook and so on, the problem persists and it's kinda of frustrating. A smartphone should be able to handle those things and she's really disappointed. Thinks I've tried:
-Clear data and cache of Contacts and Phone.
-Hard Reboot
-Recently installed the latest update via OTA (I hoped the problem would get fixed, but unfortunately it's still there)
-Tried using the stock launcher since she uses Nova Launcher
If someone has got an idea of what's going on please reply this post. I don't know if I should root her phone or maybe install a custom ROM. Honestly I wouldn't like to do that since she's a Noob in Android and basically in Technology Stuff. But if that's the solution, I would do that. It's really frustrating.
Thanks! Hope anybody could help
EDIT: SOLVED!
I tried to limit the background processes in developer settings and set the maximum to 4 processes and it magically solved the problem!
Moderator please delete this thread
Sent from my GT-I9305 using xda premium
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,
I have an very extrange problem with last stock firmware ( 10.5.11.BE86AA) on my Nord N10 5G (model BE2029), when i receive a call, not show caller on screen (nothing appears, black screen), i need to scroll down notification bar and see who is calling and answer or end call. I use default phone app, no dialer app installed.
Any kind of help is welcome .
Thanks
This is one of many issues I had, and just posted my solution that fixed this issue as well. It also fixed the camera app, SMS receiving causing reboots, and a ton of other "Google app" related problems.
Solution: Constant Reboots Stock Oxygen OS 10.5.14BE86AA
Sorry men, but i'm continuous with my issue on stock 10.5.14BE86AA.
Please, i don't understand your solution.
Regards
I have the same issue, please let me know if you resolve!
Reboot your phone.
Tried many times, even did a factory reset. Still occurs.
Ok, I solved it. And I feel very foolish. It was the case. Take the case off and it worked. @nosenose I hope that helps.
ianwatts said:
Ok, I solved it. And I feel very foolish. It was the case. Take the case off and it worked. @nosenose I hope that helps.
Click to expand...
Click to collapse
Hi, i have no case ;(