Hi,
since the last two monthly updates I can't start the timer by voice command. Timer is set correctly and the phone says it has started, but it didn't.
Does anybody else have this problem?
Works fine here. USA firmware version ....85.
Related
Has anyone else who has installed the latest version of Google Maps including the Latitude feature for seeing where your friends are had any problems with receiving calls?
I'm not 100% sure it is related but since installing it I have had loads of calls going straight to voicemail with my phone not ringing, sometimes I immediately got the text saying that someone had called but not left a message. It was usually fixed by me rebooting the phone, or making an outgoing call, but after a few hours it seemed to break again.
I have now uninstalled Google Maps and so far the problem has not reoccurred so I'm interested to see if anyone else has noticed this?
Not seen this at all and had Latitude installed since it was announced.
Hard to see why g maps could be causing the problem as it uses the gprs channels.
I suspect the problem might be you are running too many apps at once and then with g maps the memory usage is too much ?
if you are using GM on EDGE or 2G, and you have it running, you cannot have voice and data at the same tine coming through.
this is why 3G came by to allow data and voice simultaneously. no way you can have both on a 2G Network. And since GM will ALWAYS keep your Internet connection alive and transfer data, guess what? ur calls go to VM all the time
I've been searching and searching to see if there was a post about this already and haven't seen one. With every phone I had before my G1 I was able to send SMS messages during a phone call. Currently my G1 is not able to do so. Does anyone else have this problem? Has it been resolved? or Am I expecting too much from my G1? I have been on the phone with T-Mobile for 6 months now trying to figure it out and "engineering" has yet to come up with a solution. Any suggestions?
I think it might depend what type of service youre connected to....
I can send sms fine when I'm on the phone and connected to 3g. I'm using 5.0.2h build.
When you say "type of service" do you mean the fact that I have T-Mobile?
Sorry I meant whether or not youre on 3G, 2G, or just plain ol G.
Do you take notice?
Well I checked in the Phone Info and I noticed that once I get on a phone call my GPRS service goes from connected to suspended and sometimes disconnected. I am not sure why this happens. I also noticed that when this happens I will get the persons text message continually. My phone worked fine when I first got it. I also just rooted and installed the 1.5rev3. Still the same thing. Any ideas?
Did you ever install any of the radio updates through your rooting process
You said you're using r3 of ADP1.5.
You need to flash this radio update:
http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
Let me know if you already have....
Yes I actually did that radio update a few hours before you posted this. I am in the process of testing it. So far out of 6 tries I have only one successful attempt of being able to text while on the phone. I am going to run the update you listed and retest the phone just incase something went wrong during the installation.
Cool, lemme know how it goes.
Okay so here is the update. The phone is still doing the same thing. I say 50% of calls my GPRS Services goes from Connected to Suspended during a call.
Is this good? I know it should always be Connected.
So I am attempting to set up a VOIP calling solution to replace skype/fring after their spat. I'm using the google voice --> SIPGate/Gizmo --> Fring method with the iDailer/iContact app as detailed on lifehacker and other places (can't post external links yet).
Everything is set up correctly, as when I have SIPGate forward calls to my mobile number (using Verizon minutes) it works like a charm. However, despite the fact that the SIPGate control panel shows fring as a connected VOIP phone (fring is subscribed to SIP account properly) and fring rings correctly, when i attempt to pick up I get the following error dialog
"Unable to make a call. Please correct the date on your device and restart fring"
Any help would be appreciated. My device date is obviously correct. Fring is connected over 3G cellular broadband, and seems to do other things (like call fring-to-fring and AIM correctly).
I'm having exactly the same problem on an HTC Tilt 2. Quite frustrating and I'd love to know if there's a solution.
When fring is booting...read the fine print and read its manufacturer date... i.e. mine said 2006-2008.
Then set your device date year in that range. Try that. That way i don't get that error message, however my phone freezes up as soon as i make a call. Working on that issue.
Hey!
I started getting this after 6.0.1 update on my Canadian version (SM-N910W8)
Basically it shows data over mobile network connected but shows no signal for the phone part (see attached). Data is working fine but you cannot make or receive calls as well as SMS ain't working.
I reset the phone to defaults after getting OTA (well OTA wouldn't work for me so I used the new Samsung Smart Switch desktop app to update the phone).
Upon reboot everything gets back to normal and after half a day or so the above happens again.
ANy ideas?
Thanx!!!
Google your APN settings for your carrier and add it in to a new entry. Save, select then reboot.
I have been going through a weird issue on Total Wireless. When I use Android 6.0.1 and below, I have no issues with my service at all, everything works as it should. The issue comes into play when I use any Android 7.0 ROM, be it official or custom. Outgoing calls/4G data are fine, but I cannot receive any phone calls or send/receive texts. The only way for me to be able to receive calls and send/receive texts is to dial out once. After this, everything works as it should, that is until I reboot. Then I it goes back to the partial working state until I dial out again.
The issue persists whether I am using CDMA/LTE or Global Network modes. I have tried every single possible combination of starting with a fully working 6.0.1 firmware and upgrading through Smartswitch, with and without a full Wipe performed afterwards, doing a full 7.0 firmware flash. The issue is always present, and I am not sure if TW has issues with Android 7.0 or if there is a problem with my account. Their CS is absolutely useless in helping me with the issue, and our chats always end with if I can make a phone call, then the issue is resolved. They don't understand that the issue is still present, but it only crops up after a reboot of my device.
I have tried 3 different SIM cards and they have deleted and re-added/reprovisioned my device/number to their system but nothing seems to help this issue. APN is the usual TRACFONE.VZWENTP. It's really weird that it happens on two separate devices that I activate with my mobile number.
My only thought as to what it could be is maybe some weird provisioning error with the number coming from Verizon. Total Wireless doesn't have any type of VOLTE capabilities on their network, yet I was able to use a rooted Note 4 device and activate Advanced Calling/HD Voice and I believe Wifi calling as well and use it fine on their service. One oddity I noticed is that when the phone is in the initial 'Searching for Service' state on a fresh boot when I dial out while connected to Wifi, sometimes I will see Mobile Network Type change to IWLAN, whereas it usually says LTE. After dialing everything works correctly.
Any ideas on further troubleshooting steps I can take? If nothing can be done, maybe there is some way I can have a boot up script that makes a ghost phone call to any random number and immediately disconnects so I don't have to remember to dial out whenever I reboot my device?
Thanks
I don't have a solution yet, but you're not alone. I have a stock G935V (running Nougat) with Tracfone service running over Verizon's network. Whenever I start up the phone, the phone will indefinitely remain in a "Searching for Service" status until I initiate one phone call. Then the network instantly switches to "Verizon Wireless" and everything works correctly for as long as the phone remains on.
A long phone call with Tracfone and Verizon yielded no solution: They indicated everything is configured correctly in my account. Various replacement SIM cards didn't change anything either.
This issue happens with both stock Samsung S6 phones and the Samsung S7 phone in my household. All are running Nougat.
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
dbldown7 said:
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
Click to expand...
Click to collapse
Tracfone tried, half-heartedly, to solve the problem by sending me 3 different sim cards. The problem never went away. I just got in the habit of initiating a call to voicemail whenever I restarted my phone.
The problem went away when I upgraded my S7 Edge to Android v8 Oreo.
I have flashed the Nougat "U" firmware on my Verizon S7 Edge. I had VoLTE, hotspot, HD voice when calling someone on Verizon (but the HD symbol doesn't show on my dialer, only on theirs).
Only issue was that. when I introduced the TW SIM, the APN was auto set for Tracfone (and it wasn't working), so I had to manually change it to the TotalWireless one.
Since then I had received the Oreo upgrade and the following security update... and it's still OK.