[Q] Issues with Moto X running CM11 - pls help! - Moto X Q&A

Model: Moto X 2013 [XT1060], Verizon.
Running Cyanogenmod 11 (4.4.4) + Google Apps.
These are the issues I am facing:
1. During calls, recipient is not able to hear me (handsfree works fine though).
Tried wipe, ROM reinstall and disabled Google check in service.
2. Unable to send SMS (but able to receive)
Tried uninstalling Voice+, updated carrier SMSC and rebooted multiple times.
3. During calls, when dealing with an IVRS, keypad entries I make are not recognized by recipient system.
No idea what to do.
Suggestions pls?
Yes, I am a noob.

Related

[Q] CM 10.0 Cant receive and open SMS messages

Hello,
Sorry if my English is broken, English not my native language.
This is my first post here, i am a noob (yes i watched the noob video). I searched on this forum using the search engine of this website, and i used google to try and find an answer for my problem. so far no succes or match with my problem found.
problem
After succesfully installing CM 10.0 (going from android 2.2, froyo), I recoverd all SMS messages, contacts, user apps etc. from titanium backup. Everything seemed to be working fine, but then I noticed that I can not open any SMS messages. any time i try to do this a pop/up appears showing that Messages has stopped. after some testing i found out that no new messages were shown, while sending messages was no problem. since sending/receiving SMS messages is rather essential on a phone, i would really like to fix this problem
problem details
I CAN send SMS messages
I CAN NOT open SMS messages (view SMS threads)
I can not see any new incoming messages, those might either be not visible or not received at all. (also no notification is shown)
Sending an SMS message to a unknown phone number resulted in a new thread, this could also not be opened.
I think that titanium backup caused this problem, I didnt test it before restoring the back-up of titanium, so it might be something else as well.
phone details
Samsung Galaxy S GT-I9000
android version: 4.1.2
smallband: I9000XXJVT
kernel: 3.0.31-gdabec1a [email protected] #1
CPU: ARMv7 Processor rev 2 (v7l)
CyanogenMod-version: 10.0.0-galaxysmtd
Build-number: cm_galaxysmtd-userdebug 4.1.2 JZO54K eng..20121113.054130 test-keys
Message app details:
Came with CM 10.0
version: 4.1.2-eng..20121113.054130
Who can help me or point me in the right direction?
if possible, i'd rather not do a factory reset or delete all my messages
Deleted, wrong post
I tried two other things so far: deleting all messages and re-installing the messaging app. Neither of these worked... and the messaging app is still closing when trying to open a message.
I also checked the SMSC number, this seems all-right.
sending SMS still works, so i really have no idea what the problem could be... Any suggestions?
edit: upgraded to 10.1.0 RC2, receiving works now, opening does not. I replaced the stock app with handcent, which works well enough.

[Q] Can't see restored call log

Hello Everyone,
First my compliments to this forum. It's simply amazing.
I have update my ZR to 4.3 unlocked the bootloader rooted it and did the dual recovery thing.
This all works execellent.
I restored the call log with Titanium Backup (and with SMS Backup +). Now I can not see the call log in the dialer.
Installed "Call Log Monitor" and with that program I can see the complete log.
New calls are visible in the dailer and in the "Call Log Monitor".
I am confused :silly:
Who can un-confuse me please?
Tried a factory reset.
Tried the complete installation of 4.3 again.
Still the same.
??
I used the Nordice RC2 version of the firmware. Because that was the first one I found on XDA.
Should I have used the Dutch RC3 one?
http://forum.xda-developers.com/showthread.php?t=2465088
Am I the only one with this problem?
The default dialer does not display the restored calll log.
Other dialers (and call log monitors) from the playstore display the complete call log.
Is this normal behaviour for the stock dialer?

No WhatsApp connection on mobile data on CM 12.1 !!!SOLVED!!!

Hi,
I installed CM 12.1 (Version 10.31 nightly) on my D405. I´m not able to receive Whats App messages, also FB Messenger seems not to be connected. Opening a webpage in Chrome works fine.
When I´m connected to WIFI everything also works fine.
Is it a bug or do I need to change some settings??
Greetings
Its a bug, update and everything will be fine
Updates did not help / Still no connection with WhatsApp
Hi!
Unfortunately updating to the newest nightly did not help. My WhatsApp is still does not receive messages.
I tried the following things:
Downgrading back to stock KitKat, then Updating to CM12.1 --> problem remains
Changing APN from wap.vodafone.de to web.vodafone.de --> problem remains
Right now I installed CM 11. No problem with WLAN or Mobile Data. WhatsApp also works fine. But This is not a real solution.
Please help!!!
Problem persists!!
Please help, guys!
Right now I tried to go back to KitKat via flashing KDZ file. So the system should be completely stock.
After installing CM 12.1 I installed WhatsApp from Play Store as usual.
When I try to set up my WhatsApp account, while being connected to mobile data, the verification process fails.
Doing the same with WIFI connection works fine.
What am I doing wrong??
SOLVED!!!
SOLVED!!!
I deleted whole APN list. Then added just one APN provided by my carrier. After switching mobile data off and on again I was able to receive WhatsApp.
Peace!

After Binary Update - Cannot Make Outgoing Calls...???

Hello Everyone...
Posting here first rather than in the "Update Failure" thread because I'm not so sure I have a "failure" with the update....just an issue after the udpate.
I have 2 cloned HTC M9 phones. I say "cloned" as they are exactly the same make, model, ROM, etc (one business, one personal phone). They have the following information if needed:
Sprint HTC M9
SuperSU Free v2.65
Custom ROM ViperOneM9 3.5.0 with no custom kernal
Android 5.1
HTC Sense 7.0
Kernal (standard) 3.10.49-perf-g26c593c
[email protected] #1
SMP PREEMPT
I updated some apps this as I normally do through Google Play. A little while afterward I was prompted to update the SU Binary. I did so on one of my phones. I hit the TWRP option (on the right side of the prompt screen), nothing happened, phone did not reset so I rebooted into recovery. The update ran automatically and the phone rebooted.
I noticed two issues (perhaps there are more). The huge problem is that I cannot make OUTGOING calls. I use a custom dialer PixelPhone Pro. I click on a contact to dial and nothing happens. I type in number to dial, hit the green "send" button to make the call, nothing happens.
I also tried the stock Phone app....same thing, cannot dial out.
I attempted to update the Profile and PRL for the phone, however, as that appears to need to make a "special call" that function is not working either
The other problem I noticed is with an app I have called Quick Settings. The app is always accessible through the pull-down notifications on the phone. Although the app is still installed and functional, it no longer appears in the pull-down notifications. I tried to reset the option to show it there (turning the option off and back on) and it will not show up despite the proper setting chosen.
I still have full root access as I tried a couple root apps (such as Titanium Pro) and have full root access.
I have been prompted on my other phone to update the SU Binary and I am concerned with doing so. Any idea why this is happening and how I can troubleshoot and fit my outgoing call issue??
THANK YOU all very much!!
Scott
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Scudderb said:
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Click to expand...
Click to collapse
**UPDATE**
Still problems....
Right after I first updated the binary the "only" problem was that I could not make calls which I could use the other functions of the phone. I rebooted the phone and I cannot reach any function of the phone because I constantly get the message "...the process com.android.phone has stopped" obviously related to the previous problems.
I dirty-flashed the ROM...that did no help. I even tried to flash an older SuperSU version (I don't know what that would have done....I'm running on HOPE now ) and that didn't help. Re-dirty-flashed the ROM a second time. Again that didn't help.
I flashed an old backup and THAT WORKED fine. Problem is that the backup is 6 months old. I could quit and totally clean/wipe/install the ROM and start again from scratch but I reeeeeeallly don't have time for that at the moment.
Is there ANY way I can simply get my com.android.phone process back?? Why did all this happen in the first place??
ANY help is greatly appreciated!! THANK YOU!!!

SMS not working at all!!!

Hey guys! My Le-X526 is not able to send or recieve SMS at all. It was previously not working only with Jio but was working fine with airtel, now it isn’t working on both. Airtel still receives but when I try to send the balance is deducted and it says sent but I don’t receive the message on other phone and sometimes it straight shows up not sent and on jio? Completely blocked both ways. Nor does it receive any message nor does it send. I’ve tried various custom roms until now, flashed the 19s bootloader but it’s still the same, nothing wrong with the apn settings. VoLTE is working fine, mobile data is and so are calls.
What must’ve caused this guys? Is it hardware problem or did I **** up somewhere? It was working all fine before, it just happened out of blue.
What should I do?
Should I go back to stock? HELP PLS :crying:
Solved for me.
I installed stock, dialled *#*#4636#*#*.
Chose sim 0 or 1 (jio)
Enable option called SMS over SMP Or something.
At end update smsc number.
Voila.
Done.
Enjoy.
Not gonna find in custom ROM s dialer. So try n fix in stock ROM n then move to custom ROM.
I met a similar problem before, then I flash 2 different stock roms and it works again.

Categories

Resources