Database Develop

Netflix and (Original) Droid w only WIFI - error?

Hi,
I just got an old (original) Motorola Droid from my son. It was was taken out of service, so it's got no phone service, just WIFI. He flashed it to 2.2 before he gave it to me.
Almost everything seems to work ok on it: I can connect to my WIFI network, browse, etc. Market works, Flash works after I installed from Market.
I installed Netflix from the Market, and it starts up ok, but then I get a popup error that says:
"Please make sure that your device has network connectivity and the Date and Time settings are accurate."
and it kind of just hangs the Netflix app at that point.
Does anyone know what the problem might be, and how to get Netflix working in this case?
I'm guessing that it might be looking for a phone network connection or something?
Thanks,
Jim

Hi,
My son has a friend with a same (original) Droid, with the same firmware, but his phone is still active on Verizon, and he's able to get Netflix app to work on it.
He (my son) said that he thinks that he has another friend that also has a Droid that's deactivated, and he's going to ask him to try to see if Netflix will work on that.
If that latter doesn't work and get that same error message, I'm guessing that it's, as I mentioned above, trying to connect to Netflix via the 3G, rather than over the WIFI.
Anyone know if it's possible to get the Netflix app to use only WIFI?
I had a similar problem with Sipdroid this weekend when I tried to get that to work. It actually, at one point, connected me to a Verizon operator, presumably over the Verizon wireless network. Sipdroid has a configuration setting that allows you to tell it to use only WIFI, and once I set that, Sipdroid worked ok over WIFI. I think that I need to find some kind of setting in the Netflix app to do something similar.
Jim

Hi,
I just got off the phone with Netflix support. I don't know if the person that I spoke to actually knew what he was saying, but he said that the Droid is not "on their list of supported phones", so according to him, it would then try to "connect to their website".
I didn't think that I needed the build.prop changes, because I'm not getting an "unsupported device" message, plus, like I said, my son's friend has it working on his identical (except it's still on Verizon) phone, but I'm going to try some of those build.prop hacks, to see if that makes a difference.
Jim

Hi,
For the record, no joy with changing the build.prop. That seems to be ineffective.
So, I'm still stuck on this...
Anyone?
Thanks,
Jim

Hi,
I had left the phone on the Netflix error screen and it went to sleep last night, and when I woke up this a.m., and woke it, there was a different msg saying that it couldn't access some web site.
So, I started thinking that it was a firewall problem, and I put the phone's IP address in my router's DMZ, and VOILA!!
Got Netflix !!
Jim

[Q] Can not access android market on wifi I HAVE TRIED everything

OK. I see a lot of this, in a lot of threads. I have a bionic. This is actually the THIRD one I have had since I got it (now outside of my 14 days of course). The issue as brief as possible: all three phones i have rooted, ROM'd , factory reset, reinstalled stock ROM, re ROM'd , factory reset, etc.. OK now so you know. Wifi alone works well with browser. Sometimes (and I mean extremly rarely) I can get wifi to act with 3G IF I turn it on AFTER i'm in the market but then it is 'stuck on downloading'. I called verizon tech support three times: first two times they said that is normal as verizon network is secure and the droid market needs thats. Third time I was told it happens to 'some' bionic devices and is a known issue. WTF is the deal? I've tried FXR and I work in IT and even my open wireless connections from people I know do NOT WORK. Only works with 3G/4G on.

Really ? No one else ? i know that's not the case at all because the guy I work with was able to get to the market thru wifi just fine until last nite and today. It isn't just me

I am accessing the market on WiFi just fine. Though, to be honest, I rarely check, and I often install apps from https://market.android.com/ (I installed three from there yesterday while on WiFi - it worked just fine.)
The phone is two days old - never rooted.

Even weirder still...
see that's another werid thing. The times I try to go to market.android.com/rl] I get web page can't be displayed. anything with the words 'market' or 'android' give the page can't be displayed (over wifi). anything else at all on wifi internet wise works perfect.

Maybe I'm misunderstanding the issue... but have you tried connecting to a different WiFi AP? It sounds to me like access to the market is being filtered. Can you get to market.android.com on your PC while it's connected to the same AP as your Bionic?

effinay said:
Maybe I'm misunderstanding the issue... but have you tried connecting to a different WiFi AP? It sounds to me like access to the market is being filtered. Can you get to market.android.com on your PC while it's connected to the same AP as your Bionic?
Click to expand...
Click to collapse
Plus one for this. It's the wifi not the Bionic.

Yeah I can get to the wifi on my laptop at both places and can get to market.android.com from both computers. somethng else funny I can't download from market.android.com on the pc to the phone with wifi on; it never downloads. I don't know what the hell the issue is but it's frustraing. i'm hearing another of my friends lost access to the market over wifi yesterday all of the sudden. It's got to be some sort of coding as the wifi does work, just not for the marketplace

PDAnet USB tether no longer working

Hello,
I have both PDAnet and the Foxfi key that I purchased last month when I first received my Moto X. Up until now it has worked excellent (aside from only being able to tether via USB). I really never used tethering that much as I have an internet subscription for my home. Fast Forward to today I needed to use it. I entered USB debugging on my phone as usual plugged in the usb cord clicked connect on the PDAnet in the icon tray and it would rapidly go from connected to reconnecting about every second. I've tried reinstalling both apps, soft reset, hard reset. Uninstalled PDAnet on the computer and reinstalled. Nothing is working. It no longer shows that it's trying to reconnect. Now it simply connects and then disconnects in about 5 seconds. Does anyone know of any recent updates to the Moto X, android, pdanet that might be causing this?
I don't know if it's relevant but I spoke with Verizon about a week ago to upgrade my minutes and the lady was locked out of my account because my phone was still pending activation even though I had been using my moto x for over a month. Apparently the activation doesn't always go through so they activated a "hotline" or something on the my phone to push it through. Could they have seen I've been using PDAnet and done something to my account/phone to prevent me, or is that not possible?
If anyone can lead me to the solution for this I will send $20
Thanks,
GaB

bump

PDAnet is working fine for me. I'm connected through it right now. I've used it for years from my office because of company restrictions on web traffic and haven't had any real issues.

Did you recently upgrade to 4.4? Neither app works on 4.4.

PDANet+ works fine on 4.4. If you don't have the paid (full unlocked) version, it will disconnect in less than a minute. The FoxFi part of PDANet+ no longer works in 4.4 for wifi hotspot. I am USB tethering everyday most of the day using PDANet...right now in fact. Make sure you are using the most current version in Windows and on your phone. Get the installer from http://pdanet.co/ again, you will need the paid version to not lose connection.

[Q] Connected to WiFi network, but no internet connection [WebOS]

Last night, I found my TouchPad sitting under a pile of papers in my office after a few months of wondering where it was and charged it on the dock. Before this long gap of not using it, it had been working perfectly fine - internet browsing, apps, etc... and the internet definitely worked.
After turning it on, it will connect to my WiFi network without a problem, but when I go to open up a web browser page, it says: "Error: No Internet connection." I also can't get it to load stories in the USA Today app and it won't check email in the email app.
I tried enabling/disabling Airplane Mode and then reset the WiFi settings (gave it a new IP address under the WiFi Preferences menu, like this HP forum post says to do), but it still doesn't want to let me go to websites or anything.
Any ideas on how to fix this?

karmapuhlease said:
Last night, I found my TouchPad sitting under a pile of papers in my office after a few months of wondering where it was and charged it on the dock. Before this long gap of not using it, it had been working perfectly fine - internet browsing, apps, etc... and the internet definitely worked.
After turning it on, it will connect to my WiFi network without a problem, but when I go to open up a web browser page, it says: "Error: No Internet connection." I also can't get it to load stories in the USA Today app and it won't check email in the email app.
I tried enabling/disabling Airplane Mode and then reset the WiFi settings (gave it a new IP address under the WiFi Preferences menu, like this HP forum post says to do), but it still doesn't want to let me go to websites or anything.
Any ideas on how to fix this?
Click to expand...
Click to collapse
As you say that you haven't used it for a while I'm wondering if you updated the root certificate.
If you didn't here are instructions on how to :
http://forum.xda-developers.com/showthread.php?t=2329264
Hope that this helps.

sstar said:
As you say that you haven't used it for a while I'm wondering if you updated the root certificate.
If you didn't here are instructions on how to :
http://forum.xda-developers.com/showthread.php?t=2329264
Hope that this helps.
Click to expand...
Click to collapse
It won't even let me go into the App Catalog to download the update, actually. When I try to, it says: "You must connect to a network to use this application." After I click "Retry," there is a brief moment where it flashes a screen asking me what country I'm in before it goes right back to the screen telling me to connect to a network.
I don't think this is an issue with my router, since all of my family's phones (a Galaxy Nexus, a Galaxy S3, and two iPhones), two laptops, and a Kindle are all using the network with no problems at all. It seems to me like it must be an internal problem with the way my Touchpad is interacting with the network.
Thanks for the suggestion though! That could be another issue I'll have to fix too (since I don't remember downloading an update to fix that problem, which I hadn't heard about before, though I think I've probably used my Touchpad at some point since July 2013).

Invalid teleservice ID error when trying to send SMS or MMS

I recently bought a Verizon Note 9 (first Samsung phone) so I'm not well versed on things. I have noticed from time to time when I am not receiving carrier signal (still connected to wifi) my texts will start failing with the error "Invalid teleservice id".
After some digging I noticed that my phone number in "About Phone" was incorrectly set to an invalid number 1-265-000-000.
I have cleared all caches and reset all settings I can think of. This problems occurs on all SMS applications. So far I have tried: Google Messages; Samsung Messages; Verizon Messages+.
Where does the "About Phone" page get populated from?
My hunch is the internal number of the phone is getting set by some screwy logic and that is throwing off everything that relies on it.

Invalid teleservide id soulution found
I need people to test this solution to make sure it works across all devices as the error seems to affect all android devices under certain conditions. If you would like to read how I came to this solution to help me check my work or you are just interested please keep reading, If you just want the solution feel free to skip to the bottom paragraph beginning with SOLUTION. If you try this solution, which I actually believe to be a solution and not a hotfix, please respond with 3 pieces of information: 1) Did it work. 2) What Android device you use and the version of Android you are using and 3) Your ISP (Internet Service Provider).
This data is very important.
STORY:
So, last month I switched to Android for a couple of reasons after having used iPhones since the iPhone 5. The two most important things to me were being able to stream music using the LDAC Bluetooth codec and having a crack at Samsung Dex to see if I could avoid buying a laptop next year. I was immediately happy with these features that had been the impetus for switching, but then something unexpected happened: the thing that I have always taken for granted, i.e. my phone sending/receiving calls and texts, was incredibly unreliable on this phone (Galaxy S20 Ultra). After doing some googling and finding the official forums (there seem to be 2 devoted to this issue and I will post this both places) I found the incredibly disheartening ‘hotfix’ of disabling WiFi calling to be completely unnaceptable. Not only because I don’t actually get cell service in my apartment but because a $1400 flagship smartphone should certianly not have less functionality in any area that an iPod Touch circa a decade ago.
Normally I would just take my faulty device down to a Verizon store because although I am in IT I specialize in computers more than phones, however since we have been in isolation this began an approximately 20 hour saga via the phone over the span of May 25th to June 19th. After trying everything I could glean might work from google, and following every step that Verizon tech support asked me to try and actually convincing them to update the carrier settings on my account I was finally given the OK to get a replacement device. It is important to note at this point that I had only been searching this error for my model phone and mistakenly had the idea that it was an incredibly rare issue that was a problem with a select few devices.
So, you can imagine my complete and udder shock after getting the replacement phone, setting it up, and getting the Invalid Teleservice ID Error 4 on the second text message I tried to send on the device. It took me about an hour to really get my wits together because at this point I was trying to come to terms with the very possible reality that I was not going to be able to use my phone at home reliably because I don’t have good reception over WiFi. When my faculties returned, I resolved to read every post I could find on this issue.
What I found is that this problem has been around since certain people started installing Android 8 on their phones and that they have been trying to get Verizon to offer an actual solution since 2017. So here we are 3.5 years later and almost 4 generations of Android later and “the best network” has so far failed to offer any sort of real solution to this problem. However, from getting the error on my new phone and seeing that the error was effecting essentially every model device Verizon sells (that runs Android) gave me a key piece of data: the problem has nothing to do with the device.
After getting deeper and deeper into some forums I noticed that one person reported that this problem only occurs for them when they use an Xfinity WiFi hotspot. That was my lightbulb moment. I am also an Xfinity customer. I then started searching the problem from that perspective and found that most of the people reporting the error and mentioning their ISP were either Xfinity or Spectrum customers, and now I was starting to feel like I might be onto something.
In terms of IT, networking is my weakest area. Nevertheless I dove into some forums that have tried to approach this problem from a networking perspective and although a lot of it was over my head I started to suspect there was something about the firewall on Xfinity and Spectrum routers that is causing the problem. After 72 hours of exhaustive testing ( not only is 24 hours approximately my previous record for not having the error, but I used that time to send out as much information via text messaging as possible to try to cause the error) I am ready to posit a hypothesis as to what is actually causing the problem and post the solution that is currently working for me.
As I have noticed that the problem is most likely to crop up for me when I am using Dex and a physical keyboard and have tried to send many texts in quick succession, the idea came to me that somehow trying to send a large volume of data exacerbates a problem that Xfinity and Spectrum routers have reliably delivering packets in the right order and format over the internet to the Verizon network. So, this is what I decided to try, and it has now worked for approximately 84 hours straight and has performed flawlessly under stress testing (Spamming 500 word texts and hi res photos to multiple people in quick succession using copy/paste).
SOLUTION:
I’m sure many of you who play video games have used a function on your routers to get around NAT issues called the DMZ. The DMZ allows you to put a device using a specific IP address on your personal network outside of the firewall and connect it directly to the internet. For a device that exists on this network wirelessly there is a simple step you must take first. You must assign your device a static IP. If you go into your router settings you will likely find that all devices on your network are assigned IP addresses via a system called DHCP. This essentially means your device will probably have a new IP every time you leave the house and return, so we need to make it the same every time so that the DMZ will function the way we want it to. Every router is going to have a slightly different settings menu, but you should be able to find a tab that lists the CONNECTED DEVICES on your network. What you need to do is change your phone from being a DHCP connected device and assign it a STATIC IP address. Finding the option to do this may be harder than actually doing it, all you need to do when you find the option is change the connection type from DHCP to Static and pick and IP address that will work for you. My network uses 10.0.0.XX for the devices on my home network so I assigned my phone to 10.0.0.99. Then I placed the 10.0.0.99 in the DMZ. In my router menu, the DMZ is under ADVANCED SETTINGS and when you select the DMZ tab, simply enter the IP address you chose for your phone.
To recap:
1) Set your phone to a static IP
2) Put that IP in the DMZ
That’s it. A valid criticism of this solution is that your phone is less secure, however I would respond that the likelihood of your phone being hacked is much smaller that that of a PC and if this slightly loosened security really bothers you, just use a VPN. A VPN will keep you safe in a Starbucks on their free public WiFi and it can protect you here (I actually had a VPN when I got my device and originally I thought it was the cause of the Invalid Teleservice error). CAUTION: There has been a crop of predatory VPN services lately that provide working VPNs, but will charge you a ridiculous amount. I use NordVPN (I found a code on YouTube that gave me 70% off six devices on a 3 year plan, that ended up costing about $100) but there are plenty of good services that will allow you to connect to the internet via a VPN on one device for approximately $2-3 a month.
So please, try this and report back. This error has been the bane of my existence since switching to Android and it is completely unacceptable that Verizon has had literally years to do figure out a solution to this problem and yet they have not. My end goal is not to receive credit but to make sure that in the future Verizon Tech Support actually knows how to help people solve this problem, and their techs don’t take your calls and then look the problem up on google, proceeding to be completely transparent in terms of having no actual knowledge of this issue and literally reading the same forums I have already been over and suggesting the non-solutions posted there in order, i.e. turn off WiFi calling and if that doesn’t work turn off ‘Advanced Calling’.
REMEMBER: If this solution does not work for you, please double check that your changes the router you use have stuck. I have previously had routers that will for reasons I don’t understand change the DMZ domain or switch a device back to DHCP from static or simply fail to save your changes properly.
I await responses eagerly.

You need to take your device to your local high street retail branch of your cell provider and ask them to check your SMS/MMS settings

I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.

K_A_Beausoleil said:
I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.
Click to expand...
Click to collapse
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
---------- Post added at 04:37 PM ---------- Previous post was at 04:05 PM ----------
hkjxda said:
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
Click to expand...
Click to collapse
Scratch this... Wifi calling uses it's own IPsec VPN tunnel, VPN clients only encrypt internet traffic, not cell service. Back to square one...