You may wonder, “What does SOPA/PIPA have to do with me?”

These two pieces of US-based legislation have the potential to change the way the internet works, worldwide. This could effect us here at Unforgiven Development, in the sense that one user posts the wrong thing, the entire website could be pulled off of the GLOBAL INTERNET with no court order, no due process, no proof of infringement, NOTHING.

Bringing mass censorship to the global internet will do nothing but stifle innovation, break the chain of trust within the domain name system, destroy the integrity of the internet as a whole, and introduce many security issues.

You will be greeted by a page showing what Unforgiven Development could look like had t be taken down due to one of these draconian laws. You will also have the opportunity to learn more, and contact your local representative urging them to vote against this travesty. And I wholeheartedly encourage you to do so.

Thank you for your patience and support, and see you on the 19th!

Hey everyone!

Along with the ICS update for the Nexus S (I9020T), we got a new radio image (I9020XXKI1)and a new bootloader (I9020XXKL1).

I have the new radio image in both update.zip format, and fastboot format. You can flash the update.zip via your recovery, but the preferred way to update your radio is fastboot.

You can use fastboot to update your radio image by issuing the following command:

fastboot flash radio radio-I9020XXKI1.img

Also included in the update is a new bootloader, which I am only releasing as a raw image for flashing via fastboot (this may change if there is demand for it in update.zip format. However, I do not see any need to update your bootloader in general. But it’s here if you want it.)

You can use fastboot to update your bootloader by issuing the following command:

fastboot flash bootloader bootloader-I9020XXKL1.img

I have had the new radio and bootloader on my phone for a few hours now, and I have not noticed any issues with either. I haven’t really had much of an opportunity for testing, though. The initial speed tests seem to be decent. However, it seems something finicky is going on with ping times. They’re either really high, coupled with really high speeds (~5mbit), or really low, coupled with so-so speeds (~1.5mbit).

Please leave feedback on the new radio in the comments below!Download links:

Nexus S radio: I9020XXKI1 [UPDATE.ZIP] MD5: f2c4d5b01eff6cf7a6befd5588981ef7 Nexus S radio: I9020XXKI1 [FASTBOOT] MD5: 5d6c3cc500132ff7081942b436b6a6e7 Nexus S bootloader: I9020XXKL1 [FASTBOOT] MD5: b8a773113c448c448bd847899bb5adac

As always, donations are appreciated — I do everything I do free of charge, in the interest of helping others. This is not my job, so anything, $1 or $100 helps. Thanks!

Well, as I’m sure quite a few of you have heard, I am officially a daddy! This is wonderful news, and I am incredibly excited! Well, I wanted to let everyone know what’s going on.

My fiancee and I have been going through some of the best, and some of the toughest times of our lives. While I will say, the birth of our daughter was, put simply, the most amazing day of our lives, we also have been experiencing some tough times. Our beautiful daughter has been admitted to the NICU (Neonatal Intensive Care Unit) due to being unable to hold her food down well. This has been extremely hard on me, and I can’t even begin to imagine how difficult this is on Jocelyn.

Jocelyn and I have been spending nearly all of our time at her bedside, giving her love and affection. She is expected to make a full recovery and come home, however, they are unable to give us even the slightest idea as to when this will occur. She has been making improvements, but she has also had regressions. The doctors are unsure of what is wrong, and they’re pretty much hoping that it “fixes itself”. I’m really hoping that she improves rapidly, and is able to come home in the near future.

What does this mean for Jocelyn and I? Well, this has been making a serious dent in the amount of time I have been able to work, so this is going to affect us financially, big time. It also means that we will be travelling to and from the hospital every day, to see her. We will be dedicating almost all of our time to her.

What does this mean for everyone else? Unfortunately, over these coming days, I will not be able to dedicate nearly as much time to working on my projects (namely the Samsung Admire). I know you guys have been patiently waiting for the release of both ClockworkMod recovery, my custom kernel, and (most anticipated) CyanogenMod 7.2. I greatly, greatly appreciate your patience. I will be trying to get some time in there to work on the project. But, unfortunately, as of right now, I am tightly split in between having to work, and spending time with my daughter.

As I’ve said before, $10 buys one hour of dedicated time of working on the Samsung Admire. This offer is still on the table. In all honesty, I would rather work on the Admire than going to work. But unfortunately, as this is on a purely volunteer basis, it does not help pay the bills, nor does it help pay the expenses of travelling to and from the hospital, purchasing meals while at the hospital, etc. If you’d like to donate, I will definitely spend some time working on the project, and this should allow me to get things done much, much faster. And, as I’ve said before, no matter how much or how little you donate, every penny is greatly appreciated. And it’s appreciated even more now than ever. If you care to donate, you can do so at the bottom of this post.

Now for the update on the Samsung Admire: I know you guys want to know what’s going on in Admire-land. I have been making great progress with the device. I have ClockworkMod recovery almost 100% functional, however, I am stuck with one naggling bug related to Samsung’s RFS filesystem. As soon as this is fixed, it will be released. I have been consulting with a few people on a fix, and it should be in place soon, so that’s something for you to look forward to. I know some of you have asked: “Well why don’t you release it as it is?” Well, I would, but with the RFS bug, it’s completely unusable with any stock configuration. With there being no custom ROMs or anything out there, it would be (essentially) useless at this point. This also prevents NANDROID backups of your stock image from working correctly. From my findings with the Samsung Admire, if you do not have a stock NANDROID and you have issues, it puts you in quite a sticky situation. I had to restore partition data from another device, using a version of ODIN that was also for another device, get back into recovery, and manually untar all the data to the partitions after doing rm -rf /{system,data,cache}/*. It was about a 5 hour process to get the Admire functional again. But it will be coming soon, trust me. For any of you who plan on developing ROMs, you can get started, it’d be nice to have a couple ROMs (perhaps a cleaned up stock ROM, or a rooted/deodex ROM, maybe some themed ROMs, etc) available at release of CWM.

Now, for CM. I have been making nice progress. A lot of things are working. But there are still quite a few that are not working. Some things are partially working. Notable things that are not working: RIL (radio interface layer), Camera, GPS, light sensor, battery meter. Pretty much everything else is working. I can not provide an ETA as to when a public beta will go out. I’m sorry. Once again, the more time I can dedicate to it, the faster it will happen. That’s all I can say.

I know, also, a few of you have talked about CyanogenMod 9, wondering if I would try to make it happen on the Admire. Of course! Once the CM team works with the code, and betas start trickling out to various devices, I will definitely work with the code, and see what I can do. This is not a guarantee of whether it will be successful or not, but I will definitely be putting in the effort, and trying. I will say, though, that CyanogenMod 7.2 is the priority right now.

Some of you have also asked “How much should I donate?” — Donate as much as you’d like! I appreciate each and every penny, however, the more the merrier. The more you donate, the more time I can dedicate to working on the project. I can not provide an estimate in the amount of hours it will take to finish the project, simply because it is a rather large project, and there are a lot of variables that can affect speed of development. But, please, feel free to donate as much as you’d like. My family and I appreciate it.

Thank you so much for your support, everyone. You, all of you, are amazing. I’ll try to keep you updated!

As a lot of you know, I have been doing work on the MetroPCS Samsung Admire. I want you to know that I have not given up, and progress is being made. I have CWM recovery almost perfectly working, and I have been making quite a bit of progress on CyanogenMod for the device. While I can not give an ETA on either (please do not ask), I can tell you that I am continuing work, and eventually a release will be made.

If you’d like to support development, and make things move along faster, feel free to donate. Every $10 donated earns 1 hour of totally dedicated, uninterrupted time of working on the Admire, and this will allow me to finish the project faster. I wish I was able to work on this project full time, however, I have a family to feed and take care of, and bills to pay. As such, I am forced to work full time. If I receive donations, this will allow me to replace time at work with time sitting here, in front of my computer, working on the Admire. I appreciate each and every donation, and I am working on some type of special program for donators. Thank you for your consideration.

So, with all of the recent changes in the CyanogenMod codebase, I decided that I wanted to build my own ROM from source.

I have done this in the past, on Debian testing, with no issues. Though, it has been a while since I’ve built from source, as I’ve been using the official nightly builds.

So I did my typical things:

repo sync
source build/envsetup.sh
lunch cyanogen_crespo-eng
make -j12 bacon

Everything seemed to be working correctly at first…and then…:

target thumb C: init <= system/core/init/parser.c
system/core/cpio/mkbootfs.c: In function ‘_eject’:
system/core/cpio/mkbootfs.c:82:20: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
target thumb C: init <= system/core/init/logo.c
In file included from /usr/include/bits/errno.h:25:0,
                 from /usr/include/errno.h:36,
                 from build/tools/acp/acp.c:22:
/usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or directory
compilation terminated.
In file included from /usr/include/bits/errno.h:25:0,
                 from /usr/include/errno.h:36,
                 from build/libs/host/CopyFile.c:24:
/usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or directory
compilation terminated.
make: *** [out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/CopyFile.o] Error 1
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

After doing some research, I discovered that the files in question should be located in the package linux-libc-dev. Interestingly, this package was already installed and current on my system.

So I started digging in...

I discovered bug 638418 on Debian's bug tracker. It seems as if the problem is fixed in sid, however, it is not yet fixed in wheezy.

So, to over-ride the bug, we can manually intervene, and create the symlink ourselves.

sudo ln -s /usr/include/`uname -m`-linux-gnu/asm/ /usr/include/asm

This fixes the build issues, however, I am unsure of the long-term implications of this workaround. I am not sure if we will have issues when we update our packages to the version where this is corrected (ie, the packages can't make the symlink themselves because it's already present.) If this is the case, we may need to remove the symlink manually:

sudo rm /usr/include/asm

In the meantime, enjoy! Have fun building KANGs!

So, somewhere in the past few days, Google decided to push out a new update for the Nexus S (i9020t) – Android version 2.3.6, build GRK39F. If you’re looking for the full update (from stock 2.3.4 (GRJ22) only), go ahead and grab it directly from Google’s servers.

Anyhow, included in the update, we have a new radio: I9020XXKF1

Since we do not have a full update, the update linked above only contained a patch for I9020XXKD1. As such, I took it upon myself to create a full radio image, ready for flashing with fastboot. This has been tested, and is proven to work. You do not need to be running any specific radio version to update.

The command to update is fastboot flash radio I9020XXKF1.img

You can grab the download here: I9020XXKF1 MD5: 9e0e2086fbc5adcff88e6ca0bfe2d0b8

If anyone would prefer that I package this up in update.zip format, just leave a comment here, and I’ll take care of it.

UPDATE: I have packaged an update.zip for those who wanted it. It is self-signed, so CWM may or may not complain about it. If you have issues, please turn off signature verification.

You can download it here: I9020XXKF1 update.zip MD5: a6c85d0ea70b26a09af1655e8f78c3ca

UPDATE2: These two files differ from the other one that was released. The other one is a straight dump of /dev/block/mtdblock5. It includes about 1.5MB of excess “junk” at the end of the file. This one has been stripped down to the correct length, as per all of the other officially-released full radio images. I’m not saying there is anything wrong with the other release, as it should work just fine. This release just conforms to the format of all previously-released full radio images.

As always, donations are appreciated — I do everything I do free of charge, in the interest of helping others. This is not my job, so anything, $1 or $100 helps. Thanks!

Well, I’ve managed to get it working, so I wrote a wiki page on our (new) wiki describing how to do it.

Note that, with the nature of being a wiki, the content on this page may change from time to time. Hopefully, it will get better, and become even more descriptive.

In the themes department, I am quite a fan of spacefun and spinfinity, with spinfinity being my current default.

I hope this helps save you some time (and headache) with getting things working, enjoy!

I just got it up and running on my second system (my laptop). I’ve been enjoying it dearly. It may take a little more configuration than Ubuntu to get things how I like them, but, that’s just it. Things are how I like them.

At first, I thought Unity was a cool idea. But then I used it. For a few weeks. To put it kindly, it needs work. I’m quite comfortable in my “classic” GNOME session. I know Ubuntu 11.04 still offers the “Classic” session, however, it had other issues as well (random crashes, etc — on my desktop).

I will be posting tutorials and what not about things I have done with Debian, so please stay tuned!

I have been extensively researching some of the issues people seem to be encountering. In my opinion, it seems as if a lot of the issues are being caused by inadequate space on the /system/ partition, which is causing some of the files to not be installed correctly. These missing files are creating some of the issues you are experiencing (not able to connect, invalid SIM, etc)

I am looking into a more suitable, long-term solution to this issue. Unfortunately, we are limited on space, and we can only do so much.

Also, I have been quite busy with things in “real life” — my fiance and I are having a baby (it’s a girl!!) — so we’ve been busy with doctors appointments and trying to prepare.

I also want to thank the Android community for being so patient, and so awesome. You guys rock!

It only took all of 4 hours to get my phone to be recognized by adb on my new Debian testing (wheezy) system. I can thank udev for that one.

I’ve found the solution. The standard Ubuntu “/etc/udev/rules.d/51-android.rules” will not work here. Debian’s udev is slightly different.

Through chatting with some people in #debian, it was learned that changing

# usbfs-like devices

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", \

				MODE="0664"

in /lib/udev/rules.d/91-permissions.rules to

# usbfs-like devices

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", \

			MODE="0666"

allows adb to work. After some thought, this led me to realize that 51-android.rules is parsed before 91-permissions.rules. Therefore, that rule in 91-permissions.rules is parsed after 51-android.rules.

So, first off, we need to use /etc/udev/rules.d/99-android.rules. And, the syntax is slightly different for Debian. Here is what I used.

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="18d1", MODE="0666"

After reloading udev (from a root shell: /etc/init.d/udev restart), I unplugged my phone, and plugged it back in. Bam! It worked!

You may have to substitute 18d1 for your phone’s manufacturer (18d1 is for Nexus-branded devices). Some examples include “0bb4″ for HTC, and “04e8″ for Samsung. You can find the full list over at the Android Developers website.

I sure hope I saved you the headache I experienced!