Skip to main content

Android 2.1 Eclair on HTC Magic

Finally. I made the leap from official Android 1.5 with HTC Sense to a rooted 2.1 Eclair. The rumors said HTC was going to release an update in March, then May, then June and now September. I had enough of the waiting. Apps (Twitter, NY Times) that run only in 2.0+ were being released and I felt left out. Now, which ROM should I choose? The net pointed to Cyanogen as the most respected Android developer.

I then started to read and reread the instructions on Cyanogen's wiki. You'll be asked to download a total of 9 files. I had done the Gold Card method before so I didn't need to do it again. The rooting and upgrade to 5.0.7 took a lot less time than expected. Everything went smoothly and I was able to boot into Eclair after about an hour of work.

Everything was faster and more responsive than before. The look and feel was actually very nice. There were some things I missed like the Sense Gallery, the built-in Facebook-Contacts integration, the Sense calendar widget, the Sense bookmarks widget and the Teeter game. The upgrade, on the other hand, gave me Gesture Search, multiple Gmail account integration, Twitter, a faster browser and Google Maps with buzz support.

A day later, Cyanogen released 5.0.8. The upgrade was a simple case of downloading 2 files, copying it to the SD card, rebooting into recovery mode and applying the zip updates. After the update, I rebooted to a 5.0.8 and the ADW.launcher was waiting for me. The upgrade was well worth it and would recommend it to anyone in the Philippines with an HTC Magic. A few weeks from now, Cyanogen would probably have Froyo ready for use.

Comments

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

Activating NDD on your Globe landline

NDD and IDD is not available by default on your new Globe landline to protect you from inadvertent charges due to calls to mobile phones and long distance numbers. Note that these instructions are for Metro Manila accounts. To activate NDD, you need call 730-1000. The problem is, an Interactive Voice Response (IVR) menu greets you at that number and there is no menu option to activate NDD. There is also no easy way to get to a human in the options. For credit card companies, I always use the "Report a lost card" option to reach an agent immediately. It appears there is no such shortcut with Globe's number. After several attempts at the menus, the way I got to an agent was to pretend to customize my plan and select the option that says the information is not helpful. Here's the guide: 730-1000 IVR Menu: 1 - English 1 - Globelines 1 - Customize your plan 1 - Customize your plan 2 - Not helpful 1- Talk to a customer agent It will take about 3 minutes for the

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@