Skip to main content

Verizon Wireless in application store shutdown mode

Verizon Wireless users can expect a change in the next month, and Motorola RAZR users should expect a second.  Verizon has chosen to shutter its app store with a stated timeline of the end of March 2013.

According to the announcement the company has made available, users will have the store removed from their devices by March 27.  This presumably means that all the Verizon-developed applications will be gone as well.  With some digging around the Internet, it's easy to see that this change is welcome and that users will be happy to get space back on their phones, relinquished by the seldom used applications.

RAZR users have also been promised an update to Android version 4.1 Jelly Bean with roll-out time frames going as far back as December of last year.  Currently, the roll-out is expected to be before the end of March which leaves the company with about a month left of wiggle room.

This coincides nicely with the application store removal.  And it would make sense that the removal would be wrapped into a single update.  Besides "soak testing" the Jelly Bean update for these phones, it's practical to hold off until the store removal is all set to go, and then do them together.  Since the update was already leaked-and-then-pulled by the company around Christmas it's safe to assume that the currently hold-up is, at least in part, related to the store removal.


Citations

Verizon Apps Closing January 2013
http://developer.verizon.com/content/vdc/en/verizon-app-market/verizon-market-va-anouncment.html

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

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.
7 comments
Read more

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...
7 comments
Read more