Jelly Bean update for Motorola RAZR and RAZR MAXX, finally

It would appear that after Verizon's promise of Jelly Bean for the Motorola RAZR and RAZR MAXX in November of last year, the accidental roll-out in December, and the recent "soak test," the update is finally reaching users. It's a doozy, at better than 330 megabytes, so be sure the phone is plugged in or has a good deal of battery before starting the update.

The gradual release of this update on Verizon has seemed erratic. The RAZR M, I, HD, and HD MAXX, all got the update. The Samsung Galaxy S III got it. Naturally, the Nexus got it. So it's bizarre the way this has been coming out in waves without any apparent rationale for what devices gets it, when. Over the years there has been plenty of criticism in discussion groups for the way carriers deploy updates in comparison to the way Apple does it. That being, independent of the carriers. None-the-less, it's here so the complaining can start to wind down now. Happy Jelly Beaning!

Comments

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ). From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE: At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned. If it solves an authentication problem, then great. The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward. It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE: Step 1 assumes a connection being made from a Windows machine. If the connection is being made from something else, user credentials may actually be necessary. If the connect...

Orsburn (Static Content)

Search This Blog