Skip to main content

Don't wait for OTA, upgrade your Nexus S now

When @googlenexus tweeted that Nexus S GSM phones will be given the ICS upgrade, I immediately went to Settings -> About Phone -> System Updates and found the dreaded: "Your system is currently up to date." message.

Fortunately, Android Central posted a timely article on how to upgrade manually. The update file appeared to be coming from google's server and the comments didn't mention anybody bricking their phone so I proceeded to download the 130MB file and followed the instructions. So 10 minutes later, my Nexus S was running ICS. If you got your Nexus S from Globe Telecom Philippines (Nexus S i9023 GSM), then the manual upgrade procedure from Android Central should work seamlessly. All your apps and data will remain intact.

So, is the upgrade worth it? DEFINITELY! If you have a Nexus S, by all means, do the upgrade right now. With the new fonts and default apps, you'll feel like you have a new phone. The SMS and email apps really make composing and replying a pleasant experience.

POST INSTALL TIPS

One thing I noticed after the upgrade was that the battery was draining faster than usual. It turned out that the upgrade switched the mobile network settings to 3G (mine had been set to 2G to conserve battery). The email settings defaulted to sync the last 30 days. In Gingerbread, the email default sync was 4 days. After doing all the changes, battery life went back to normal (maybe a little bit worse).

In the People (Contacts) app, you may notice that new contacts are appearing there. Those are probably from your Google+ circles. To switch back to the Gingerbread default which shows only people from "My Contacts," go to Menu -> Contacts to Display -> Customize and check only the My Contacts option. Other tips: To take a screenshot from the phone, hold power and volume down button.
Labels:

Comments

Post a Comment

Popular posts from this blog

Get uptime alerts in Telegram

You will be configuring 3 services. The assumption is that you have accounts already for these services. UptimeRobot — source of the uptime/downtime notifications. It currently supports email, Twitter, Slack, Pushover, Pushbullet and others but not Telegram. We will use the webhook notification as the way to send messages to Telegram. IFTTT — bridges UptimeRobot and Telegram by providing the webhook for UptimeRobot and triggering a message to Telegram. In IFTTT terminology: IF {event trigger from UptimeRobot}, then {send message to Telegram group} Telegram — destination of the notification. You will need to create a group for this. Telegram Configuration In Telegram, create a new group, if needed. You may opt to use an existing group. Go to @IFTTT and follow the instruction so link your Telegram account to your IFTTT account. Send /connect_group to @IFTTT and connect the group where you want to send the notifications. IFTTT Configuration Sign in to IFTTT and add a ne...
1 comment
Read more

iReport Default Date Parameter

If you want to set a default date for a jasperreports parameter, you can enter the following in the default value expression of the parameter. new Date() However, if you wanted the default to be relative from today, for example, 3 days ago, you will need to do go outside of the standard java date libraries (Date, Calendar) because JR parameter does not allow you to have multiple statements. You can write your own utility package or you can use Joda , a replacement library for the JDK date and time library. To use Joda in iReports, you need to extract the jar file and add it to Options -> Classpath. You may also drop the jar file in iReports' lib directory. You will also need to add this library to your application or report server. For setting a default date 5 days prior from today, use this: new org.joda.time.DateTime().minusDays(5).toDate() or this if you want the time part set to the beginning of the day: new org.joda.time.LocalDate().toDateTimeAtStartOfDay().minusDays(5).to...
5 comments
Read more

CI/CD for .NET Core

If you have a .NET API that you want to containerize, here are the steps to prepare it. Create docker image Push to repository Setup ECS The TLS 1.0 option is needed if your SQL Server database does not support TLS 1.2. The recommended option is to update your database to the secure protocol. You may also change sdk and aspnet version to 5.0 if you haven't updated to 6.0 yet. This Dockerfile uses a multi-stage build to get an optimal image size. Dockerfile FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build-env WORKDIR /app # Copy csproj and restore as distinct layers COPY *.csproj ./ RUN dotnet restore # Copy everything else and build COPY . ./ RUN dotnet publish -c Release -o out # Build runtime image FROM mcr.microsoft.com/dotnet/aspnet:6.0 WORKDIR /app # Enable TLS 1.0 RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /etc/ssl/openssl.cnf RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@...
Post a Comment
Read more