Related
Let me start this question with a big thanks to all the developers/etc. out there. The work being done is AMAZING!
I am a new "rooter", but learning fast. I am running Cyanoginger 1.1 on my MT3GS. I have noticed a few things that aren't quite right, and I am unsure if they are related to each other, or to Cm 6.1.1, or ~ginger 1.1, or...
1. Incoming phone calls seem to sporadically go to voicemail instead of the phone. My phone can be sitting on my desk with full bars, I'll call my phone from my desk, it'll ring once or twice and jump to voicemail (nothing shows up on the MyTouch). I'll call again 10 seconds later, and it goes to my phone. Very sporadic (maybe 1 in 20 calls?)
2. My phone number shows Unknown in Settings > About phone > Status. I read in a few forums that this may be the case untill you place/receive a call, but mine is still showing unknown.
3. My market purchases are no longer integrated with carrier billing. It's asking for a credit card instead of automatically billing me at T-Mobile.
Like I said, I'm a noob at rooting/modding, but I learn quick Any help with these issues would be greatly appreciated!
qjudge said:
Let me start this question with a big thanks to all the developers/etc. out there. The work being done is AMAZING!
I am a new "rooter", but learning fast. I am running Cyanoginger 1.1 on my MT3GS. I have noticed a few things that aren't quite right, and I am unsure if they are related to each other, or to Cm 6.1.1, or ~ginger 1.1, or...
1. Incoming phone calls seem to sporadically go to voicemail instead of the phone. My phone can be sitting on my desk with full bars, I'll call my phone from my desk, it'll ring once or twice and jump to voicemail (nothing shows up on the MyTouch). I'll call again 10 seconds later, and it goes to my phone. Very sporadic (maybe 1 in 20 calls?)
2. My phone number shows Unknown in Settings > About phone > Status. I read in a few forums that this may be the case untill you place/receive a call, but mine is still showing unknown.
3. My market purchases are no longer integrated with carrier billing. It's asking for a credit card instead of automatically billing me at T-Mobile.
Like I said, I'm a noob at rooting/modding, but I learn quick Any help with these issues would be greatly appreciated!
Click to expand...
Click to collapse
The unknown number thing has to do with cm6.1.1. It shouldn't affect you anyway. For the first issue, probably t-mobile issue, neither your phone nor your ROM. Happens to me on all my phones, even my dumbphones.
The market thing is something that you give up when you flash a custom ROM. I think there might be something that can tie market to your tmobile account, but I can't find it again, it was mentioned in a thread recently.
Thanks for the quick response!
On points 2 and 3, I guess that's just the way it is. Little things, I can definitely deal.
On the first point, I just want to make sure this isn't happening because of how I flashed new roms, or how I upgraded the radio, etc.
FWIW, here's the process I used:
- rooted phone with adb/file copy, etc., etc.
- booted to ESPRIMG.zip (oops, rebooted, no backup of system!)
- booted to Clockwork
- cleared data, cleared cache, flashed CM 6.1.1, flashed gapps, rebooted
- went back to clockwork flashed radio from 7.07.(????) directly to 7.09.35.10, rebooted
- "stumbled" across Cyanoginger 1.1...
- booted to Clockwork, cleared data, cleared cache, flashed to Cyanoginger 1.1
The phone prior to rooting never had any issues receiving calls, but who knows, maybe it's because I'm staring at it, maybe it's solar flares, maybe I've angered the cell phone gods...ok, humor's "off" a bit today
If you have any further thoughts, let me know; otherwise thanks for your help! I really appreciate it!
Yeah that all sounds right. I haven't ever had issues with my phone number showing up, it seems to only happen to some people, and like you said, normally it goes away after placing or receiving a call. Who knows. I don't think it affects any apps though. I could be wrong about that, not sure. It might be your sim card, which would explain some calls not going through as well.
I know there is a way to tie the market to your t-mobile account, I just can't remember at the moment. I googled around, couldn't find anything. I think it's called market fix or something rather. I could be thinking of something else though. Frankly I like paying with my debit card better, it was never a huge deal for me, so I never thought too much into it.
MusicMan374 said:
I know there is a way to tie the market to your t-mobile account, I just can't remember at the moment. I googled around, couldn't find anything. I think it's called market fix or something rather. I could be thinking of something else though. Frankly I like paying with my debit card better, it was never a huge deal for me, so I never thought too much into it.
Click to expand...
Click to collapse
I know exactly what you're talking about... I just can't seem to find it either. It was in a thread recently, like you said.
Maybe it's just vanished
I'm gonna keep searching though.
EDIT: So I was starting to flip out, cause I could not for the life of me find the thread...
But I decided to go to my phone and see if maybe I could just find the app in the market. Then I saw that I had already searched for it before, because I actually have the same issue. I just never downloaded it and tested it out.
It's called "Market Enabler"
I'm going to download it now and test it myself.
EDIT 2: Or maybe that's not it. I don't know, I can't seem to figure it out. Maybe MusicMan can take a look? I could have sworn this was an app suggested for that, but it just looks like it makes it so you can see apps that aren't on certain carriers.
SefEXE said:
I know exactly what you're talking about... I just can't seem to find it either. It was in a thread recently, like you said.
Maybe it's just vanished
I'm gonna keep searching though.
EDIT: So I was starting to flip out, cause I could not for the life of me find the thread...
But I decided to go to my phone and see if maybe I could just find the app in the market. Then I saw that I had already searched for it before, because I actually have the same issue. I just never downloaded it and tested it out.
It's called "Market Enabler"
I'm going to download it now and test it myself.
EDIT 2: Or maybe that's not it. I don't know, I can't seem to figure it out. Maybe MusicMan can take a look? I could have sworn this was an app suggested for that, but it just looks like it makes it so you can see apps that aren't on certain carriers.
Click to expand...
Click to collapse
It could just be that we were thinking of something else and such an app doesn't exist. I'll look some more when I get home
Sent from my T-Mobile myTouch 3G Slide
Well, I "stumbled" across the solution to #2. As far as I've heard from others so far, it's purely cosmetic, but...
Go to Settings > Call Settings > Additional Settings > My phone number and enter the number. Now when you go to Settings > About phone > Status it will show the number you entered.
Again, this may be purely cosmetic, and I've noticed if you reboot, the setting gets wiped. Strange...but there you go...
Sorry to bring up this issue back up but I just recently Rooted my phone as well and am having the same problem with sporadic calls not coming to my phone.
For example, last night my father told me that he tried to call me at least 3 times in a row and it would go straight to voicemail, however today he called me (like 2 mins ago) and the phone rang as normal. Heres what I've noticed on the phone:
-the phone will drop all bars sporadically for no apparent reason, as I have never had any service issues in my house.
-it does this when its been idle for a couple of minutes and as soon as I wake it up it will show 0 bars then jump to the normal 2-3 I usually get at my place.
-whenever the bars drop to 0 my 3g/HSPA service will still show as normal
I'm not completely new to Rooting (Rooted my original G1), however my last experience with it was back on CM4.1 on my G1, so there may be a o couple of things I missed
Thanks in advance for any help!
Hi, I've a similar problem: on outgoing calls anyone on any phone is able to see my number, they always get calls from "unknown" from my phone. I use wolfbreak's rom with cyanogen and I've allready set in the settings the option to show my number on outgoing calls, but doesn't work. how can I do?
Tony84 said:
Hi, I've a similar problem: on outgoing calls anyone on any phone is able to see my number, they always get calls from "unknown" from my phone. I use wolfbreak's rom with cyanogen and I've allready set in the settings the option to show my number on outgoing calls, but doesn't work. how can I do?
Click to expand...
Click to collapse
had this prob too even if u set it in cm you still have to call your carrier to get them to make you number show
So I noticed about 2 months ago that I have absolutely no sound (voice in/out or ringing while call is being placed) when I make or receive calls using the Phone app. I have various VOIP apps that all work fine. All media plays fine. Headsets all work fine for watching movies and whatnot. No sound during calls.
I had a factory unlocked N7100 that I was told came from Spain originally (I'm in Toronto). I had flashed some other country (I think South Africa) because they got a newer version and my phone wasn't updating automatically. Never had any issues until I noticed this with the calls. I have no idea how long it's been like that as I have a second phone I use primarily for voice calls and this one I usually just use basically as a tablet or I use VOIP apps for calling.
Yesterday I tried to flash to DN4 2.1 but after numerous times it would never get past the Samsung logo so I went with a France 4.4.2 stock ROM. That one has since autoupdated. Everything is working great including data. I can place calls and the other line will ring but there is no audio in/out of my phone (other end can't hear me, I can't hear them). Although it's not a huge issue for me I'd like to fix it. I have previously messed around with hidden menus and possibly even tried to play modifying with the phone app (as various hidden menus stopped working after the last update and I was trying to get them back). But when I was trying to get DN4 to work I wiped EVERYTHING repeatedly so I don't think anything could be hanging around to mess stuff up.
I don't think it's a hardware issue otherwise why would it work fine for VOIP using the same mic and speaker? Also, it doesn't work through a headset either. No voice, no ringing, etc.
Currently my phone is showing the following:
Baseband:
N7100XXUFNG1
Kernel:
3.0.31-4587314
[email protected] #1
Tue Mar 31 14:58:35 KST 2015
Build:
KOT49H.N7100XXUFOC2
Suggestions?!?
No suggestions?
Found the answer here: http://forum.xda-developers.com/showpost.php?p=57436919&postcount=39
Settings
Apps
Scroll right to All
Scroll down to Google Play Services
Tap Disable
Repeat for Google Services Framework.
Click to expand...
Click to collapse
Instant call volume after I do this. But now my Google apps don't work. I need a better solution!
Edit: Nevermind, turned them back on and calls are still working. Hopefully it doesn't stop working the moment I need to make an emergency call or something.
Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.
Tell me please
Skoda car has music Bolero MIB 3 (VAG regular), which works just fine with a Motorola phone via bluetooth, you can both make and receive calls to the car. When my Sony 10 III is connected via Bluetooth, everything seems to be OK at first - contacts are loaded into Bolero, the signal level is visible, etc. ... But I can make a call by selecting a subscriber on the Bolero screen, only ONE time. With all the following attempts to call - "connection setup error". Only restarting the phone helps, after rebooting you can make one call again.
Where to dig? I really want to conveniently call from the car ... All available settings have been tried. Change phone?
phone: Sony 10III, XQ-BT52, 62.0.A.3.137
Make sure all power management is disabled.
Try a network reset.
Try loaded factory app version for involved apps or that failing see if any updates are available.
If you did any major OTA firmware updates recently without doing a factory reset... it's time to do so.
I found out that when the phone starts making a call, its bluetooth turns off and the connection with the car is broken.
how to fix it?
dag3dag said:
I found out that when the phone starts making a call, its bluetooth turns off and the connection with the car is broken.
how to fix it?
Click to expand...
Click to collapse
Did you try what I suggested above?
Try clearing cache or data in associated apps but be very careful about clearing data in the phone apps. Normally this isn't required.
dag3dag said:
Where to dig? I really want to conveniently call from the car ... All available settings have been tried. Change phone?
Click to expand...
Click to collapse
Try to change Bluetooth AVRCP and MAP version.
Anybody else experiencing unable to make and receive call while using e-sim? Only fix is to either reboot the device or enable airplane mode for a short period of time; basically having to disconnect to the network for as few seconds fixes it. Texting and internet browsing via mobile data is working properly though. And if I remember correctly, I've also experienced this from my galaxy S21U before. Wondering if this is a device problem, a carrier problem, or a samsung problem.
reproduce the issue and report to samsung members app > get help > error report.
surely samsung engineers will be able to look into what might be causing this