South Cape

Oh baby! That rocks!

  • UMBT Datacenter – Partial RTKL Response

    PA_OOR-Stine_redactedDownload

    Last month, I submitted a Right to Know Law (RTKL) request to Upper Mt. Bethel Township, Pennsylvania. This township is embroiled in a battle between residents, a datacenter developer, and the Township Supervisors (analogous to city board members) concerning a proposed datacenter development.

    I should note for transparency: I am not a resident of Upper Mt. Bethel Township and would not be directly impacted by the proposed datacenter development. I do have family in the township with a stake in the outcome, but my primary interest is as a computer scientist with a general interest in datacenter proliferation across the United States.

    Concerns expressed by township residents have been noted across a wide range of issues: environmental, infrastructural, land preservation, property value, and other issues have been raised.

    Some observers have noted an apparent lack of impartiality with certain Supervisors. This perceived partiality has purportedly been so strong that there is some question amongst residents as to whether there has been improper dealing involved in the project.

    My RTKL’s objective has been twofold: first, to determine how much due diligence has been expended by the Supervisors and Township personnel when discussing and researching the datacenter project; and second, to look into whether there are any undisclosed relationships or conflicts of interest between the developer and elected officials – questions raised by some residents.

    In the interest of this project’s full transparency, attached above is the partial response I have received from the Township today. I have not yet reviewed the documents provided; this post describes the reasons the request was made, not any conclusions drawn from what’s been received.

    The RTKL Appeal remains open, as some items are still considered “deemed denied” under Pennsylvania law.

    I will provide updates in further posts on this website as new information becomes available.

    Update 9/23: I have an open appeal with the PA Office of Open Records (OOR). The record on that appeal closes today, September 23, 2026. I have submitted correspondence for the docket conveying my position that the production is not entirely responsive to the request. I will add new posts for any further productions I receive from the Township.

  • UMBT Datacenter – Revised MOU

    UMBT Talen MOU Revised-4908-3404-7178-v1Download
    UMBT Talen MOU OriginalDownload

    During a Township Supervisors meeting on August 24, the solicitor mentioned near the end of the meeting that a revised Memorandum of Understanding (MOU) was received from the developer of the project.

    This previously unannounced MOU is subject to public review and comment prior to consideration for execution.

    The TLDR of this revised version is that there are a couple of minimally-invasive changes from “may/should” to “must/shall”. Furthermore, a LERTA tax abatement commitment is removed. Finally, a binding decommissioning plan with pre-funding is required.

    That said, revisions continue to exhibit toothless language. For example: the water usage addition, which is a highly contentious topic in the community, is functionally unenforceable due to the language “to the maximum extent feasible” which essentially hands the applicant full discretion to such limits.

    To foster productive consideration and discussion within the community, below are the substantive changes identified between the original and revised MsOU.

    1. A party was dropped

    The original is a three-party agreement among Slate Belt Holdings, the Township, and the Upper Mount Bethel Township Municipal Authority. The revised version removes the Authority entirely – it’s now a two-party agreement between just Slate Belt and the Township (recitals, signature block, and all references updated accordingly).

    2. Section 2.1 – Text Amendment (stronger obligation)

    • Original: the amendment “may contain” environmental protections (noise, parking, utilities, etc.)
    • Revised: it “shall contain” those protections – makes the environmental protections mandatory rather than optional.

    3. Section 2.2 – Community Benefits Agreement (different beneficiary)

    • Original: Slate Belt donates to “non-profit causes or entities designated by the Township”
    • Revised: Slate Belt donates “to the Township for future infrastructure and/or community-based projects or entities designated by the Township” – broadens the donation to include direct Township infrastructure funding, not just third-party non-profits. The $50M trigger at 2 gigawatts is unchanged.

    4. Section 2.4 – Outstanding Litigation (narrowed, and a term dropped)

    • Original: names the Township, Authority, and River Pointe as litigants, and adds a sentence requiring the parties to also terminate a Facilities Agreement dated April 16, 2024 between the Township and River Pointe once the litigation is discontinued.
    • Revised: drops the Authority as a litigant (consistent with its removal as a party) and deletes the Facilities Agreement termination requirement entirely.

    5. Section 2.5 – LERTA tax abatement extension (deleted entirely)

    The original had a section where the Township agreed to extend the existing 10-year LERTA tax abatement on the Property and to encourage other taxing bodies to do the same. This entire section is removed in the revised MOU – there’s no more LERTA commitment.

    6. Marshfield Drive vacation (weakened and re-triggered)

    • Original (§2.6): “Upon execution of the Community Benefits Agreement, the Township shall commence, and then complete,” the vacation procedures – a firm, unilateral Township obligation.
    • Revised (§2.5): “After execution of this Agreement, the Parties shall confer on the status and resolution of the conditions to vacate” – a softer, joint “confer” obligation triggered earlier (at MOU signing rather than CBA signing), with no firm completion commitment.

    7. Two new sections added in the revised version

    • §2.6 Water Usage (new): Slate Belt commits each data center building will use, to the maximum extent feasible, either a closed-loop cooling system or recycled/non-potable water for cooling, and must disclose its cooling system/water source and coordination with the water provider in future applications.
    • §2.7 Decommissioning Plan (new): each building’s land development approval must include an approved decommissioning plan and posted financial security for decommissioning.

    8. Section 3.8 – Assignment language tightened

    • Original: Slate Belt “may freely assign” the MOU to an affiliate, tenant, or purchaser (also contains a stray typo, “Parties Slate.”).
    • Revised: Slate Belt “will assign” the MOU – changes from permissive/optional language to what reads as a stated intention/commitment (and fixes the typo).

  • Using BNE2 for ROM analysis

    (Followed up from back-story post.)

    BNE2 can be a helpful reference utility for hacking on video game ROM files. It is, apparently, used somewhat frequently by the JRPG hacking community in Japan.

    Unfortunately there isn’t much documentation in English for this utility that I could find. Hopefully this quick user-oriented howto will be helpful to some. This short guide will assume someone else has already dissected your ROM file and provided BNE2 files to work with…

    To start off with, the BNE2 utility is kinda old and therefore not UTF8-enabled, so you’ll want to set your system locale to Japanese for Shift-JIS support. This can be done in the Control Panel regional settings. Alternatively,  you may use Microsoft’s AppLocale utility.

    BNE2 will require the installation of the XTRM Runtime package, otherwise it won’t do anything when you try to run it.

    Once that’s installed, download the BNE2 archive (link updated on 4/9/2020 due to Geocities Japan shutdown) and unpack it all to a location of your choice…

    For my example, I’m using the Final Fantasy VI T-Edition ROM hack. The developer of the hack has kindly provided BNE2 files with his patch file…

    Inside the “FF6 T-Edition” directory, there’s a huge bunch of .IDN and .INI files, which will be what BNE2 uses to give you a nice, friendly spreadsheet-like interface to the ROM space.

    To get BNE2 to use that information, you’ll have to copy that entire directory to BNE2’s Settings directory…

    Now, BNE2 will have all kinds of information about the ROM’s layout. To make sure it uses that information, let’s open BNE2…

    BNE2 Main Window

    To verify that it has loaded the settings, select “その他(O)” (Other) in the menu bar, then select “設定” (Settings) in the submenu that pops up…

    BNE2 Settings Property Sheet

    Bingo! So, all that’s left is to load our ROM using Ctrl+O or “ファイル(F)” (File) in the menu bar, then “開く (O)” (Open) in the pop up submenu.

    If you choose the correct ROM file, you should see something like this…

    BNE2 program in action

    Hopefully this very short guide will be useful to others who may need BNE2 as a reference.

    This post is based on a great, simple Japanese language guide.

  • Upcoming post: Using BNE2 for ROM analysis

    I have been playing a super-extensive ROM hack of Final Fantasy VI, the T-Edition, by a gentleman named tsushiy, which is available here (Japanese only).

    Things have been going smoothly for a while and I’m about 30 hours into the game. I’m now in the World of Ruin and now looking to take advantage of the item upgrades offered by the Dragon’s Neck Coliseum.

    Normally you can easily find guides to the Coliseum on GameFAQs or Final Fantasy VI-specific fan sites. My quandary comes as a result of the many changes made by tsushiy. Aside from adding tons of items, tsushiy has also modified the stakes of the Coliseum. He has changed which monsters you face, the victor’s spoils, and even the behavior of the battles. So all those Coliseum guides are fairly useless for the T-Edition.

    Luckily I got some sagely advice from Mato of starmen.net fame, a thoroughly accomplished ROM hacker himself. Mato suggested using BNE files, included by tsushiy in the T-Edition package. These BNE files, when used by the BNE2 program, offer an analysis of the ROM data. That includes, among other things, the Coliseum information I needed.

    Unfortunately, documentation on how to use BNE2 in English is hard to come by. So after tinkering and finally figuring it out, hopefully I can provide some help. I’ll be following up this post with a dedicated post about using BNE2, so that people who just need the information won’t have to sit through a rambling description of why I got into it.

    UPDATE: The short howto has been posted.

  • XDAndroid postmortem: xland mirror down, donations closed, etc

    This post is long overdue; my apologies for that.

    Obviously, the XDAndroid Project has been inactive for quite some time. Despite that inactivity and the age of the hardware, some people still like to tinker around with it. One of the things I like about the XDA community is that there will be people playing with hardware for years and years… very few of the forums are permanently dead.

    On that note, I received an email from a user pointing out that the non-US download mirror for our file repository is dead. I have disabled geographical load balancing since we don’t really need it anymore. All files are now served by the main server in New Jersey, USA. I will continue to maintain that server indefinitely.

    Since the project is inactive, I have closed donations and removed all links to the paypal donations page. Disbursing the remainder of the donations account will be done eventually. I currently use funds only for renewing the domain name — the server hosting XDAndroid content is also my personal server, so I don’t feel right using project funds for that expense.

    Lastly, the IRC logs were down for a while. I have restored those to a working state in case anybody needs to search for information from when the project was active. IRC was our main collaborative environment.

    In closing, the skyrocketing of Android’s market share has obsoleted the XDAndroid Project, of course. In addition, projects whose goal were to introduce a stock flavor of Android on phones with manufacturer customizations, have been obsoleted by the introduction of low-cost, unlocked, stock Android devices (the Nexus line) by Google. While the death of projects is unfortunate, users now have more freedom than ever in mobile devices.

    A market that was once dominated by Windows Mobile and Blackberry has become a competitive war ground featuring several combatants. Apple and Google have helped level the playing field on the device side. As a result, we have seen significant advancements in user experience and hardware. It’s a great time to be a smartphone user.

    Thanks to all the developers who have helped XDAndroid extend the life of great phones that came with crap software. Thanks to Pierre for running the show throughout its most successful time. And thanks to all the users who helped the developers, tested, commented, donated, and helped each other — this project would have been nothing without you.

    (By the way, a few of us are still on IRC! Drop by and say hi!)

  • Of the Atrix, XDAndroid, and Kernel.org

    Howdy folks. Been a while since the last post, so I thought I’d fire off a quick update about what I’ve been doing personally…

    First off, XDAndroid. We’re still doing some work on the gingerbread branch. Michael (emwe) has fixed the GPS library and is currently working on some smaller items, including the proximity and light sensors. He’s currently the one getting most of the work done. We’re still working on the critical crasher for TI devices (non-RHOD) when activating bluetooth. Once that’s done, we can finish/clean up the merges from froyo and make a release.

    On a related note, kernel.org is still down. This means, for our project, that we cannot merge any changes from the upstream Android project. Google’s public Android source code was hosted exclusively on kernel.org, so until those services are restored (or Google relocates its git repositories), we cannot pull any of their changes into our forked repositories. Additionally, users are currently unable to download or update our source tree, since the majority of source tree is unmodified Android code.

    In the headline, I mention the Motorola Atrix 4G. This is a Tegra-based phone which, of course, runs Android natively. On XDA, there has been an ongoing effort to port CyanogenMod 7 to the Atrix. Since nobody had stepped up to port vanilla Android to the Atrix, I snuck into their development channel on IRC, stole their code, and got (most of) the job done. I plan to release the source tree to the public as soon as kernel.org is restored, or perhaps earlier if I can gather clones of the Android source tree. To be clear, this is going to be targeted at ROM developers (or the “chefs” term I so dislike to use). It’s working extremely well as an everyday phone for me, thanks to the wonderful work of the Atrix Dev Team, but I’m not confident in my solo efforts to bring vanilla Android to their awesome stability. Therefore, I cannot offer proper support for end-users. I’ll be making another post about Atrix stuff after I go public with a released build.

  • New Froyo Release: FRX07

    Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.

    A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.

    Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.FRX07:

    • frameworks/base:
      • Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
      • Fixes for data connection handling to improve startup time. (hyc)
      • Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
      • Stagefreight (media codecs) fixes. (hyc/viruscrazy)
      • Fixes for Sprint’s wonky MMS markup structure. (hyc)
      • Fix MediaScanner not finding audio files (including ringtones) in system.ext2
    • hardware/libhardware_legacy:
      • Minor GPS driver fixes. (Alex[sp3dev])
      • Rename wifi interfaces to wlan0 on all devices (hyc)
    • hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
    • packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
    • packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
    • packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
    • packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
    • system/extras/su: Added as a dependency for the Superuser package
    • vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)

    To coincide with the FRX07 system image, the following rootfs changes have been made:

    • init.froyo.rc modifications…
      • Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
      • Abstract the hciattach service to provide bluetooth support on both chipsets
    • Rename wifi interface to wlan0 on all devices
    • apns-conf.xml updated
    • keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
    • default.prop: set ro.secure=1 to lock down the adb shell – su can be used with the Superuser app to authorize root access in adb if needed.

  • What About FRX07?

    It’s been a long time since the last release — and for that matter, my last post here. A lot has been going on, both in the XDAndroid Project and in the real lives of developers, which has made posting updates a bit of a low priority.

    Users love to know what’s going on, though. Since most of our users frequent the XDA forums, but not our mailing list or IRC channel, it seems to them that there isn’t a whole lot happening with the project. In reality, there’s been a huge amount of progress made by a few contributors, in terms of both fixing bugs and adding features.

    Because of that progress, the next iteration in the Froyo series, FRX07, is going to be a major release. One of the main contributors to this release is hyc, who has largely rewritten our RIL, proposed rootfs reforms, improved wifi driver handling, and proposed various other changes so far. hyc has kept the team very busy with testing and implementing merge requests.

    Additionally, some work has been done by virus_crazy (on the forums) for bluetooth, including implementation for Rhodium and improvements for other devices. Alex (on #htc-linux) has been doing some work on improving the GPS driver and has a kernel update project using the 2.6.35 codebase.

    For technical users, information about all pending changes can be found in the merge requests section on my personal Gitorious page. Go there, look for the third box down in the right-side column, and click on “merge requests” to see the long list of changes submitted by the aforementioned folks.

    Thanks to these brave code warriors, the next release of XDAndroid will be huge. And don’t forget, any donations you make will go to our contributors. Thanks!

  • Dual XDAndroid Releases – FRX06 and new Gingerbread

    It’s that time again! And this time we’ve got a release for both froyo and gingerbread.

    First of all, our official froyo branch release, FRX06… We’ve got a couple minor changes, backported from Gingerbread:

    • Switched to touch-friendly dialer, along with the VGA layout improvements as seen in Gingerbread
    • Added HSPA icon (for GSM models)

    FRX06 is available for download now as a system.ext2 update.

    And for Gingerbread, we’ve also got just a couple minor updates:

    • Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
    • World-phone settings support (very important for future RIL enhancements especially on CDMA)
    • Enabled HSPA icon (someone on GSM please let me know if it actually works)

    The new Gingerbread testing image is also available for download now as a system.ext2 update.

  • New Gingerbread Testing Image Available

    Evening folks. Got another release for you tonight!

    Decent list of changes…

    • Further keyboard size fixes, should be perfect now (and goes fullscreen in landscape)
    • Updated Google apps package (Books phone version is now included)
    • Switched to GLES1.1 library with patches from bzo (you probably won’t see much difference here)
    • Phone app switched to touch-friendly in-call user interface (and fixed its layout on Raph)

    Regressions from the last system image that were fixed:

    • Added the missing camera bits
    • Re-added a graphical speed-up that was accidentally lost in merge

    A few of these changes are important.

    The software keyboard should be considered functional (but with some small bugs) at this point. If you see any issues, please report them on the bug tracker after searching for them to make sure it’s not a dupe.

    The Phone app change is important for a couple reasons. On Rhodium, this allows us to set the end-call key to Home without crippling the user in a call, since there’s now a nice big button on the screen for hanging up. This will be further improved by implementing the proximity sensor. Our support for VGA devices precluded using this UI due to the buttons blocking some of the dialpad keys in the in-call screen. This has been fine-tuned to be useful on both resolutions.

    Google Apps speaks for itself. Updated stuff, woo.

    Anyway, without further ado, you may download the updated system image.

Categories

Archives