OUR NETWORK:PogoPlugged TiVoCommunity TechLore Explore3DTV My Open Router About UsAdvertiseContact Us
Previous Thread | Next Thread

 
Learn about scoring Forum's Raw Score: 100467.0
December 17, 2011 04:36 PM
Rating (0 votes)
  • 1
  • 2
  • 3
  • 4
  • 5
Rate This!

Member Avatar

Reid Sartin

Member
Joined: 12/17/2011

There's a problem with the new Samsung Galaxy Nexus and the Griffin dijit connecting.  The two can pair - but not connect.  My wife's HTC Thunderbolt connects with no problem.  Can the Galaxy Nexus problem be fiixed in a firmware update for the digit? 

Discussion:    Add a Comment | Comments 1-8 of 8 | Latest Comment

Zach Avatar
dijit
  • member since: 08/12/2011
  • rank: 12 of 8131
  • 33 comments
December 17, 2011 6:36 PM

Hi Reid. Sorry to hear you're having trouble and thanks for sharing your experience. I haven't had a chance to try it on the Galaxy Nexus yet, but I'll see what I can find out. Anyone else here have a shiny new Galaxy Nexus and can tell us your experience? Do you get an error message? If so, what does it say?

Please do confirm that your Beacon has the latest firmware from Griffin. You can use the Griffin Utility application to install any available updates.

-- Zach Lipton, Dijit Software Engineer

Generic Member Avatar
Member
December 17, 2011 8:51 PM updated: December 17, 2011 9:03 PM

Nice to get such prompt response. I'm not a dev or eng-type but I'm guessing it has something to do with the bluetooth stack utilized in the Nexus, compared to the T'bolt. I had similar problems connecting a bluetooth keyboard to a phone - and it tuned out the stack was the problem. Maybe a starting point here? The unit does have the latest firmware installed, and again - works fine with the Thunderbolt.

Generic Member Avatar
Member
  • member since: 12/26/2011
  • rank: 152 of 8131
  • 3 comments
December 26, 2011 3:22 PM

I had no issues connecting via Bluetooth. However, the Dijit app itself leaves a lot to be desired on my Nexus. I assume it the drastic change in DPI from my past phone (HTC Incredible) but the remotes are unusable. The buttons are far too large for the screen and overlap. Probably the app assumes such a high resolution means a tablet-sized screen?

Back to the point - no issues with Bluetooth whatsoever.

Generic Member Avatar
Member
December 26, 2011 8:02 PM

I have a GSM Galaxy Nexus and I was initially having some problems connecting to the Beacon.  I would pair the device, then immediately start Dijit, and it would connect.  However, if I ever exited the Dijit app, and started it again, it would fail to connect, and I'd have to re-do the pairing process in order to get it to connect again.

However, upgrading the Beacon firmware to 1.0.3 seems to have fixed this issue.

I have to agree with the above poster, though, that the remote buttons are way too big on the galaxy nexus.  I also have a Galaxy Tab 10.1 which is almost the same resolution (1280x800) as the nexus (1280x720), and it gives me lots of space for reasonably sized buttons, but on the nexus I can only seem to fit a few oversized buttons on a single screen, and there doesn't seem to be any way to zoom out.  Just the volume dial control itself pretty much takes up the entire screen.

Zach Avatar
dijit
  • member since: 08/12/2011
  • rank: 12 of 8131
  • 33 comments
December 27, 2011 1:41 PM

Thanks for the reports. It sounds like Bluetooth is working fine for Ethan and Jesster, but not for Reid, even though you all have the latest Beacon firmware. I know Griffin is working with us to do more testing on the Galaxy Nexus too.

I'll look into the remote button issue. It does sound like something isn't working properly with the xhdpi screen on the Galaxy Nexus. We do want to add resizable buttons at some point, but we should be able to get things back to normal size in the meantime.

-- Zach Lipton, Dijit Software Engineer

Zach Avatar
dijit
  • member since: 08/12/2011
  • rank: 12 of 8131
  • 33 comments
December 28, 2011 8:19 PM

Hi guys. We've been investigating the Galaxy Nexus here at Team Dijit and think we've got a solution. We're still putting it through our testing process, but I wanted to give you guys a sneak peek and let you try it out early.

You can download the beta version of the app at: http://www.dijit.com/android/Dijit-0.9.58.apk

This is pre-release software; use at your own risk.

If you have a Galaxy Nexus (or even if not) and want to give it a try, I'd appreciate your feedback. Does this version fix the giant buttons issue? Any new problems? Anything else you noticed?

If all goes well, we should be getting this up on the Android Market shortly. Thanks!

-- Zach Lipton, Dijit Software Engineer

Generic Member Avatar
Member
  • member since: 12/26/2011
  • rank: 152 of 8131
  • 3 comments
December 29, 2011 2:17 PM

It does appear to fix the oversized buttons! Great! Thanks!

Generic Member Avatar
Member
  • member since: 02/12/2012
  • rank: 148 of 8131
  • 4 comments
February 12, 2012 11:08 PM

Hi Folks,

I am running my new Samsung Nexus S and although I can pair to the beacon, the dijit software never can connect to the beacon; even when it finds the device in the scanning window on initial setup...... VERY frustrating.

My beacon is HW 0.0.4 FW 0.4.15 Model P3771

My samsung nexus S is running OS 2.3.7, dijit 0.9.59.

I also tried the griffin utility 1.1 and it CANNOT find my beacon, even though it is paired to the OS ok.

PS: My beacon works well via my 4rth gen IPOD touch running IOS 4.2.1, dijit 3.0.1.

PS: The Android app needs to be polished big time. The EPG page looks hideous compared to the IOS dijit app. Also, I did not see the ability to download my dijit account into on the Android app. I put alot of time into my remote-pages and need to be able to download them.

Thanks,
Fabian

Discussion:    Add a Comment | Back to Top | Comments 1-8 of 8 | Latest Comment

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

You can also log in using OpenID.

close this window
close this window