I am not able to use internet in my Android Emulator. Even though it will show 3G connection - android-emulator

I am not able to access internet in my Android Emulator, I give the Internet permission in Manifest file. Even I am not able to open any site in the default browser.
When I use URL in my application then it will display "request time failed: java.net.SocketException: Address family not supported by protocol" error.
And when I use default browser then it will display "07-28 12:09:57.434: ERROR/Tab(607): onReceivedError -2 http://www.google.com/m?client=ms-android-google&source=android-home The URL could not be found." error.
It is also display "07-28 14:05:01.501: ERROR/ActivityThread(295): Failed to find provider info for com.google.settings" error
Please anyone help me.
Thanks.

Firstly check, if you set proxy settings in your emulator or not .For that settings->Wireless and networks->mobile networks->access points->Telkila .Here you can set proxy and port for your system. Then try to browse Google or other site in your emulator browser.

Related

How to open an EJS file with Live Server

I have a Server App created with Nodejs using "ejs" view engine.
When I start the Server and is running on the port, I click the URL and it sends me to my APP with no problem.
When I try to do it with Live server is when I am facing issues.
In Live Server instructions says: [NOTE: In case if you don't have any .html or .htm file in your workspace then you have to follow method no 4 & 5 to start server.]
That is what I do and I get redirected to, please see image below:
Could any one help me with this issue, please ?
Thanks
You can see it here
i wrote app.listen(3000);
thats mean i can access from 3000 port on my browser.
like this.
Just write to your server.js "localhost:(your-port)"
and you are ready to go

Geofence alert and remote feature

I have 2 concerns.
1. How can I configure geofence alert in WsO2iot3.1.0-Updte7?
I did it in Update1 but according to documentation online: Monitoring Devices Using Location Based Services
<GeoLocationConfiguration> bloc is missing in cdm-config.xml file of Update7.
This is missing geofence settings in cdm-config.xml file
When I run the script mvn clean install -f siddhi-geo-extention-deployer.xml, and deploy Geo Analytics artifacts in devicemgt, nothing is displayed about geofence alerte (exit, enter, stationnary, speed) as in Update1.
nothing is displayed about geofence alerte (exit, enter, stationnary, speed)
2. New remote feature in devicemgt. We really appreciate but when we clic on active/connected device, it just in waiting device to connect status. Nothing is prompted.
Wainting on device to connect even when the device is active.
Remote session is enabled in cdm-config.xml file.
1. How can I configure geofence alert in WsO2iot3.1.0-Updte7?
From IoTS-3.1.0-Update 5 onward <GeoLocationConfiguration> configuration has been changed as <OperationAnalyticsConfiguration>. Please refer IoTS 3.2.0 Documentation for more details.
2. New remote feature in devicemgt.
This feature is only work with COPE type enrollments. You might need to enroll your device as COPE device, by installing vendor signed system service. Please refer Integrating the Android System Service Application documentation for more details about integrating the system service.

AEM login screen is not apprearing in a linux machine AEM6.3

I have set up AEM 6.3 on remote Linux machine. But when I try to access the AEM from browser, it says "Connection has timed out".
I am not getting any error in the error.log file. Also, in stdout.log file, it says "Startup completed".
Also, I checked that port(4502) is not blocked on the server.
When I put command "curl http://localhost:4502/" on the server, I am not getting any error, which makes me assume that the connection is established.
Do I need to do any other configuration or something in order to access it from the browser? I am using http://ip:4502/ in the browser..
Almost certainly a firewall issue, check and check again :)
Look in the AEM Access log (same folder as the other logs you looked in) can you see any requests coming in from your browser? There is no other config required on AEM to access other than starting it up, assuming there is nothing network/firewall related blocking then you should be able to access it.

error opening dashDB

After I have added a service dashDB to my Bluemix application and I click on it, I got in IE11 this message:
The website declined to show this webpage
HTTP 403
When I did the same in the Google crome I got a square head which looked sad.
Does anyone know what to do?
Thank you!
There is not much information to go but I would suggest the following to narrow down the cause of the problem or resolve the issue:
- verify that service has been provisioned successfully (unless it's an existing instance that is known to work in the past)
- clear browser cache/restart to eliminate any transient issues
- BlueMix status page (https://developer.ibm.com/bluemix/support/#status) is currently reporting some authentication issues which potentially could cause problem, it should be check if the 403 error is still reported after the problem is resolved.
It might be worth to create the service with the "leave unbound" option and try to click on it. After you could bind it to your app.
You can verify if the dashDB instance is up or not by accessing the https_url from the VCAP variable associated with the dashDB instance (for e.g.: https://bluemix05.bluforcloud.com:8443) and provide your username and password (also from the VCAP variable) for that instance and see if you can log in.

Why are my REST methods not even reachable from Postman after moving the app with the REST methods to another machine?

With my app running locally (in Visual Studio), I can hit a REST method within it from Postman using either of these URLs:
http://shannon2.nrbq.ad:21609/api/inventory/sendXML/duckbill/platypus/poisonToe.xml
http://localhost:21609/api/inventory/sendXML/duckbill/platypus/poisonToe.xml
So localhost and the machine name both work.
But since I wasn't able to reach the method when calling it from a handheld device connected to my PC, I thought moving the server (REST) app to another machine on the network would clear up that problem.
However, not only can I not reach the REST method from the handheld, I can't even reach it from Postman! I get a "Could not get any response" response in Postman using any of the following URLs; I've tried, I think, every possible permutation:
https://martienda.nrbq.ad/api/inventory/sendXML/duckbill/platypus/test.xml
https://martienda.nrbq.ad:21609/api/inventory/sendXML/duckbill/platypus/test.xml
https://martienda.nrbq.ad/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
https://martienda.nrbq.ad:21609/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
https://199.96.39.231/api/inventory/sendXML/duckbill/platypus/test.xml
https:/199.96.39.231:21609/api/inventory/sendXML/duckbill/platypus/test.xml
https://199.96.39.231/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
https:/199.96.39.231:21609/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
...and none of them work (they all respond with the utterly demoralizing "Could not get any response"). What gives? What takes? Why all the hissing snakes? (apologies to Wm. Blake)
Note: If I use "http" instead of "https", I get a "404 - File not Found" error when using the IP Address (but still get "Could not get any response" when using the machine name).
Note: the REST app I can hit when the REST app is run locally is in CCR.API.Controllers and is decorated thus:
[Route("api/inventory/sendxml/{userId}/{pwd}/{filename}")]
Why has the server gone on strike?
Looking at URLs it seems you are hosting your application in either Visual Studio development web server or IIS express. (not necessarily true though). If its either dev server or IIS express then
With VS Dev server you will not be able to access urls/app from other machine but where it is hosted. See this link
If you are using IIS Express then you need to enable remote access. See this link
If you are hosting it in IIS then check firewall settings.