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
sorry for my english
i have a n5110 and when i use skype i cannot listen nothing, not my voice and not voice of my caller.
Instead if i insert headset it is ok.
how can i solve?
Nobody use skype?
Inviato dal mio GT-I9505 con Tapatalk 4
Only for sketchy for stuff.
on topic: I haven't had this issue but I'm on a n5100. What rom are you running?
nickdollahz said:
Only for sketchy for stuff.
on topic: I haven't had this issue but I'm on a n5100. What rom are you running?
Click to expand...
Click to collapse
uk 4.2.2
i read i'm not only one but i didn't find solution
So I got the N-5120 LTE version, running Android 4.1.2., a couple of weeks ago. I'm very pleased with this versatile tablet. I intended to use this with Skype Out. Making Skype to Skype calls works fine through a BT headset. However when using Skype Out, calls are initiated through the headset, but as soon as they start, they are then switched over to the phones earspeaker. The loudspeaker function is not available for Skype Out.
Both the BT and the Speaker Phone functions are turned on/off only through Samsung's sofware, it seems, and then only once the call has started.
I can tell I'm not the only one with this challenge. That said, since there are so few complaining about this here I'm wondering if there are fixes?
Gadgety said:
So I got the N-5120 LTE version, running Android 4.1.2., a couple of weeks ago. I'm very pleased with this versatile tablet. I intended to use this with Skype Out. Making Skype to Skype calls works fine through a BT headset. However when using Skype Out, calls are initiated through the headset, but as soon as they start, they are then switched over to the phones earspeaker. The loudspeaker function is not available for Skype Out.
Both the BT and the Speaker Phone functions are turned on/off only through Samsung's sofware, it seems, and then only once the call has started.
I can tell I'm not the only one with this challenge. That said, since there are so few complaining about this here I'm wondering if there are fixes?
Click to expand...
Click to collapse
I have this problem too. Haven't found a fix yet. On UK XXCMK1 4.2.2
deviant_cryptic said:
I have this problem too. Haven't found a fix yet. On UK XXCMK1 4.2.2
Click to expand...
Click to collapse
I did. This is apparently a common problem among Note users on the Skype forum, and according to them, this appeared with the latest version of Skype. What to do?
1. Uninstall Skype through the Play store, as usual.
2. In the Google Play store, click on the uppermost left hand side corner, choose my apps, and unclick auto updating. Otherwise Skype will auto update to the new version again... BTW you will henceforth have to update all your apps manually.
3. On your unit, go to Settings, Security (the padlock symbol) and allow unknown sources of programs, outside of the Play store
4. Go here http://skype.en.uptodown.com/android/download/44494 and install the older version: Skype 3.2.06673
5. Go back to the Security, and deselect unknown sources if you want to lock down your device again.
This enabled me to make Skype Out calls with both headset and speakers. It's not entirely fool proof, as sometimes it starts on the speakers before handing over to the headset, but at least it works.
Gadgety said:
I did. This is apparently a common problem among Note users on the Skype forum, and according to them, this appeared with the latest version of Skype. What to do?
1. Uninstall Skype through the Play store, as usual.
2. In the Google Play store, click on the uppermost left hand side corner, choose my apps, and unclick auto updating. Otherwise Skype will auto update to the new version again... BTW you will henceforth have to update all your apps manually.
3. On your unit, go to Settings, Security (the padlock symbol) and allow unknown sources of programs, outside of the Play store
4. Go here http://skype.en.uptodown.com/android/download/44494 and install the older version: Skype 3.2.06673
5. Go back to the Security, and deselect unknown sources if you want to lock down your device again.
This enabled me to make Skype Out calls with both headset and speakers. It's not entirely fool proof, as sometimes it starts on the speakers before handing over to the headset, but at least it works.
Click to expand...
Click to collapse
I'll try it. Thanks.
Sent from my GT-N5110 using Tapatalk
Let us know how it went. BTW, please go to Skype and assist in filing an Android Issue on
http://community.skype.com/t5/Android/How-to-create-a-good-Android-issue-report/td-p/211384
So v. 3.2.0.6673 was probably a blessing in disguise. Skype on Android via the loudspeaker or BT continues erratic behavior, although it's better than v. 4.5.. from that sspect I discovered on here that a bug in v 3.2.0.6673 allows an attacker to bypass the lock screen on your Android device.*
Yup the above method works
Sent from my GT-N5110 using Tapatalk
deviant_cryptic said:
Yup the above method works
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
And as of Feb 18, 2012, v. 4.6.0.42007 the problem has been fixed. No need to use the insecure v 3.2 any more.
After upgrading to ND8, I was really disappointed that Bluetooth would not stay connected in my car. It paired find and would happily connect. The car then sent a MAP request and a PBAP request. I accepted both (just as I would with 4.3) and all seemed to work. I could play audio and use the phone, and the car even reported that the phonebook transfer succeeded. But then somewhere between 2 and 10 minutes, it would disconnect. Then in about 15 seconds it would reconnect and be fine for another 2 to 10 minutes. And this repeats non-stop. This made phone calls almost impossible.
At first I guessed I got a bad flash. I re-flashed stock, I flashed Wicked X, then I re-odin-ed. Nothing helped. After looking at similar threads for other phones, I tried playing with WiFi settings, but that didn't do anything. Tried some Xposed settings... nope.
Finally I found that if I repaired the phone (deleting the old records on both the car and phone) and this time I refused the PBAP request, all was fine. No more disconnects!!! I don't really need my car accessing my phone book, but it was nice with 4.3 to see caller names and pictures on the car display during a call. Also I have found that an initial MAP requests is being made when bluetooth connects, but when I receive a text, I no longer get a notification on the car. So MAP is not working.
Are other people finding that MAP and BPAP are working for them on ND8? I haven't seen this reported, so I have to imagine this is not a common problem. Everything worked fine for me with 4.3 so it seems my car does support MAP/BPAP, but now there is some incompatibility and I am not sure if the bug is with ND8 or my car.
Car is a Toyota Rav4 EV. Phone is a Sprint 16G SG3.
For the MAP issue, I am wondering if I need to use Samsung Messaging to get MAP? I use Hangouts. 4.4 added a new way to select a default messaging app. In 4.3 it seemed that both apps were active, but I had turned off notifications in Messaging. In 4.4 only Hangouts is active.
It is so frustrating that the Bluetooth stack changes from version to version isn't it. You'd think they would only add features rather than break things, right?
Well, luckily I haven't had disconnect issues, but the MAP profile you are mentioning for text messages, well it comes up on the screen, but doesn't display the originator of the message in the Toyota Entune's nav screen the way it used to. Seems to display message header garbage rather than the text message originator like it used to do.
I've also noticed that the display of title metadata on the cars screen for what's currently playing isn't showing the title changes as often like it was working on 4.3.
Sent from my Nexus 7 using Tapatalk
After a bit more experimenting it seems that I was wrong. It seems that MAP is what is causing the disconnects and not PBAP. I had tested disabling MAP and PBAP together for many days which made me confident that I had found a solution. But I assumed that, of the two, PBAP was the issue. Next I tested disabling PBAP only and it seemed to be working fine so I decided my assumption was right. But I didn't test that long enough and the problem returned. I am now running with PBAP enabled and MAP disabled and it looks to be working, but its still early. I'll report back after some long drives which will test it much more effectively.
I assumed PBAP because looking through threads, others have reported disconnect issues with PBAP on other phones. It seemed a logical conclusion, but BZZZZTTTTT! OK, more after further testing...
My experience is that if I have my Sony Smartwatch 2 connected I do not have random Bluetooth audio disconnections, however if the audio accessory is the only Bluetooth device connected it will disconnect every 10 or 15 minutes. Not sure if that is helpful.
Fred
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.
I am frustrated with the phone application, for me it works only reliable for outgoing calls.
I have two major issues
Incoming calls frequently drop/disconnect while answering (unable to even start a call).
I get an incoming call notification, slide to pick up. The screen becomes gey and nothing happens for a while until a missed call notification is displayed and the home screen.
Successfully answered calls frequently drop/disconnect after 10 seconds of talking. The connection stays open but I no longer hear the other side. The other side no longer hears me.
I have tried:
- disabled WIFI calling,
- Disabled 2G fallback,
- cleared the phone applications cache
- reset networks/carrier settings
- as last effort even factory resetting the entire phone
The software is fully updated:
Android 13, build TPIA.220905.004
Is this a know issue? Are there any fixes for this?
EDIT: Google is replacing my phone, they confirmed this is a known issue
i have same issue with calls. do you have e-sim installed? my problems started right after e-sim setup
It's because of the poor modem, it's a fairly well known issue for the P6 and there's no fix. It's a hardware problem.
lazyswordfish said:
i have same issue with calls. do you have e-sim installed? my problems started right after e-sim setup
Click to expand...
Click to collapse
Yes, I have an esim + regular installed.
Reached out to Google support who confirmed it is a known issue under internal investigation. I need to wait two weeks to see if they can push a software update. Bit disappointed by that, they must be aware that if you are affected by this you have this issue since its purchase. I expected a swap or refund and would be very surprised if they fix this so late in the game.