stock browser on android 4.2.2 not being monitored

  • 1
  • Problem
  • Updated 4 years ago
I have Covenant Eyes 2.9.9.68 installed on a phone running Android 4.2.2.  Urls accessed using the stock browser do not appear in the url log or the activity report.  Is this a known problem?
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like

Posted 4 years ago

  • 1
Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Hey Arturo,

Sorry to hear that the logs are not being recorded, that is something that should not be happening. I will get with our development team to figure out what is going on for you....

Can you tell me what make & model phone you are using? That will help us get to the bottom of what is going on.
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
The phone is a BLU Advance 4.0.  I tried installing the chrome browser, and as far as I can tell it is not logging activity on the chrome browser either.

I have the same problem on an LG G2 running Android 4.4.2 and Covenant Eyes 2.9.9.68 .  I use the chrome browser on this phone.
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
Are there any updates to this ? As of now I have three android devices where covenant eyes is not logging internet activity on either the stock browser or chrome .
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
Are there any updates?  A big reason I chose to purchase Covenant Eyes was because it allegedly had support for Android.  As of right now, it is simply not working on Android.
Photo of Patrick Smith

Patrick Smith, Alum

  • 147 Posts
  • 21 Reply Likes
Arturo, Thanks for checking in again. I've done some digging, and we're just not seeing this reported elsewhere. I see your username logging in on 4 distinct Android devices is that right? Is CE running ok on the other two? 
Photo of Jellybean

Jellybean

  • 1 Post
  • 0 Reply Likes
My husband's phone has been unmonitored for the last 2 1/2 weeks as well. That occurred after second last update and wasn't fixed after the most recent. In fact it isn't monitoring anything aside from app time usage.
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
Hi Patrick, the android devices I have are:

Project Tango running Android 4.4.2
Samsung Galaxy Tab2 running Android 4.2.2
LG G2 phone running Android 4.4.2
BLU Advance 4.0 running Anrdoid 4.2.2

As far as I can tell, it is only working on the Project Tango device.  It was at one point working on the other three devices.  When I first installed Covenant Eyes on these devices, I tried browsing the internet and verified it appeared in the Covenant Eyes URL Log. 
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
Patrick/John: any suggestions for how to resolve this issue?
Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Hey Arturo,

We haven't had any luck reproducing what you are experiencing yet. Our test devices (including our very own LG G2) have not displayed the behavior you have seen. 

On the flip side, we have some more improvements coming down the line, including some additions to the way our code handles interacting with the accessibility service on Android devices. It is very possible that this will eliminate the no reporting troubles you have been experiencing. Hopefully we can ship this build soon, but we need to make sure it works properly before we can.

Thanks for your patience.
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
FYI, I've uninstalled and re-installed Covenant Eyes on my LG G2 device.  For the time being, Covenant Eyes appears to be working (URLs appear in the URL Log as well as in activity reports).  I will try the same on the other devices.  
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
Uninstalling and re-installing has fixed the issue on the following devices:
Project Tango running Android 4.4.2
LG G2 phone running Android 4.4.2
BLU Advance 4.0 running Anrdoid 4.2.2

The issue persists on despite uninstalling and re-installing covenant eyes on this device:
Samsung Galaxy Tab2 running Android 4.2.2

Do you have an update?
Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Hey Arturo,

Quick update:

I'm glad to hear that your issue has been resolved on the majority of your devices.

Regarding the Galaxy Tab2, if we had an update that fixed it I promise that you would have it by now. We have released at least two updates to our Android app since you have initially posted this thread, each of them targeting as broad a range of devices as possible. It remains impossible unfortunately (from a practical standpoint) to ensure that each update is able to cover every conceivable issue. This does not mean that we are not constantly working toward fixing current issues, just that we can only code so fast...

Meanwhile our Android team continues to make great progress in increasing our stability on the Android platform, while working towards developing major features that have been requested for a long time (Read: we really want to figure out how to deliver reliable filtering to Android users)

In the meantime stay tuned for updates to our app in Google Play, we do not hold back on shipping them, so as soon as a build is ready it will be delivered to you.

As an aside, I realize that experiencing bugs with your device & our service is frustrating, and I can appreciate your eagerness to have them fixed. A word of caution however, taking time to publicly post and bump threads that highlight vulnerabilities in a software like Covenant Eyes can cause trouble for others who are really struggling and cannot handle the existence of exploits. 

Thanks
Photo of Arturo Flores

Arturo Flores

  • 17 Posts
  • 1 Reply Like
How should I communicate these vulnerabilities to CovenantEyes?