Froyo update

If you haven’t already heard, the source for Froyo dropped yesterday. After merging, and applying 7 more patches, I was able to get the “generic” product to build in the Project Durden tree. This essentially means that we can currently build and test all of the open-source bits of Android, with all of the changes we’ve made to those bits.

As it stands, the only thing left to do is to update our vendor overlay (the repo that stores all of the proprietary binaries that can only be obtained by pulling files off a Droid running Froyo) to pull the Froyo files. This is actually slightly more complicated than it may sound. Because the files in question are all proprietary, the process of locating and pulling the files is very much trial and error.

If you’d like to help, we’d very much appreciate if someone could sort the vendor overlay for us, so we can focus on the kernel.

Source released for Durden/CM mashup

I’ve released the source code for the Durden/CM mashup. You can check out the source by using the repo init command:

repo init -u git://git.droiddev.org/platform/manifest.git -b camel-cm

An exercise in merging

I spent some time yesterday merging Project Durden with CyanogenMod, in an effort to see how far the projects have diverged. As it turns out, most of the code fits together very cleanly. I’ve put together an engineering snapshot, and am looking for feedback from the community. If you’d like to give it a try, please visit #droidmod on freenode, and ask for a link to download the ROM.

This is by no means a polished or stable ROM. Some of the known issues include: The power off and reboot options on the power menu do not work; you will have to use adb reboot, or pull the battery to power off. YouTube does not work. The Camera app has some weird bugs, and there is a visible checkbox for apps2sd that is not actually implemented (I didn’t merge the code for apps2sd because Froyo is dropping soon).

We have not officially decided whether this will be the future of Project Durden. For now, this is just an exercise in seeing what is possible.

Gerrit

I am happy to announce that we have installed Gerrit on our git server, and it can be accessed at http://review.droiddev.org/. The use of Gerrit allows us to open the doors to our git servers to anyone who wants to contribute, because any change that a user makes must go through a vetting process where it is reviewed by the community before being merged in to the world-visible repository.

Gerrit allows us to use the ”repo upload’ command to accept patches from the community. It’s quite easy to configure, and I’ll go in to more details on how to do that in a future post.

I look forward to seeing what the community has to offer!

P.S., If you currently have Project Durden’s source cloned, you need to know about a change to the location of the manifest. You can rectify this by re-initializing

repo init -u git://git.droiddev.org/platform/manifest.git; repo sync

RIP Alldroid, you were too young to commit suicide.

I have just been informed that the person who had control of Alldroid.org’s hosting package at Slicehost has canceled the account.

It is too early to tell if there are backups of anything important, but it seems that all data is irretrievably lost.

I would like to extend a hand out to those who are displaced, and let you know that you are welcome here.

It stings, knowing that all record of the past 6 months of my life on Alldroid are lost, that it’s gone, that it won’t be back.

Hopefully we as a community can band together and overcome this loss.

sgx

OTA update warning

Another OTA update has appeared. Users who have rooted, but are not using SPRecovery should take extreme care, as this update contains a complete /system image, which means that it will not break the way the previous one did; it will simply erase /system and flash a complete image. If you already have SPRecovery flashed, you can safely accept the update as you did with the ESE81 update.

Oy vey, Google I/O

We’re still looking to get an I/O ticket for trevorj, so anyone who’s willing to sell or knows someone selling theirs please contact either him or myself via email (one_of_our_usernames@droidmod.org). Either full shot or academic, doesn’t really matter.

We didn’t find out till a few days after the registration was filled that his schedule allowed it, and everyone expected it to be open for a bit longer anyways, but these things happen.

We’re only interested in the ticket, not the surprise gift phone, so you effectively get a free phone, and maybe even a bit more cash in your pocket than you started with ;)

All offers will be considered.

Thanks for all your continued support,

sgx, on behalf of trevorj and the DroidMod team

EDIT: Trevorj  has a ticket now, and we’re booked for I/O. Now for the hard part, waiting for the 18th so we can fly out…

Project Durden is making headway!

An unofficial from-source engineering snapshot of Project Durden was dropped in IRC a few hours ago, and aside from wifi not working due to a missing driver and launcher2 freaking because of landscape, it’s apparently working good.

No direct support will be given, as this is an unofficial snapshot, but members of the community can most likely help you out if you do need it.

Webkit and superuser are from the Cyanogen repository, and our vendor overlay is based on Koush’s. You can browse the manifest in our repo at git.droiddev.org. This is only the beginning of whats to come, we are looking forward to working with as many teams and people as possible to create something really great.

The snapshot is an update.zip format file with an md5sum of 62a5a149a354a9da30d5abbd3a845083 please verify this before instalation for some peace of mind. Data and cache will need to be wiped before install.

Let me stress again that this is not a fully finished release, or even an alpha or beta. It’s a snapshot of what we’re doing that we felt we should let out. It’s plain vanilla.

sgx, speaking on behalf of the DM team

EDIT: A wififix.zip that cures the wifi issue has been dropped on irc, md5sum of 7d3720320bd3e1a955175c0e91a6b0d7

Chargebacks explained

I’ve been getting a number of chargebacks over the past few days for the SMUpdater application, so I’d like to explain what chargebacks are, and why you should only ever send them as a last resort.

When you purchase something with a credit or debit card, you give authorization for that purchase by signing off (electronically or otherwise) on the transaction. If someone were to steal your payment information, it would be trivial for them to fool the seller and the payment processor in to accepting and approving fraudulent payments. To protect you against this type of fraud, there is a thing called a chargeback. If you choose to dispute a charge, the payment processor will take back the money from the seller, and tack on an additional fee (that the seller has to pay) for the service.

The most important thing to know about a chargeback is that it is fundamentally different from a refund. When you are refunded, the seller credits you the amount you were charged, and everyone goes home happy. When you send a chargeback, your bank forcibly removes the money from the seller’s account, and fines them for making an unauthorized charge. If an account receives too many chargebacks, these fines can get huge (hundreds of dollars per chargeback).

There are a number of legitimate reasons to send chargebacks, but none of them are applicable to this post, so I won’t go in to detail. These include identity theft, duplicate billing, items returned but not refunded, and advertised services not being provided. What I’m focusing on here is simply buyers’ remorse, which is not a legitimate cause for sending chargebacks.

It’s actually very common for people (assholes) to abuse the chargeback system in this way. People will purchase items, change their minds about wanting the product, and send chargebacks to get their money back instead of dealing with the seller in an equitable way. Disputing these illegitimate chargebacks is nearly impossible for online services (it is usually impossible to prove that services were rendered), and when it is possible, it is almost always cost prohibitive.

In the case of the Andriod Marketplace, the chargeback fee is $3.00. As the number of apps that cost more than $10 in market can be counted on one hand, it typically costs more money for a seller to dispute a chargeback than it does to pay the fee, so there is really no point in trying.  Because of this, Android application developers bend over backwards to grant timely refunds, usually with no questions asked. It’s simply not worth the risk of having to pay a fee that, usually, is many times more than their profit margin was to begin with. If an app costs $1.00, the developer only takes home $0.70 after Google takes its cut. That means that for every chargeback the developer recieves, they have to sell the app more than 4 more times to make their money back on the chargeback fee – just to get back to zero.

In the case of the old SMUpdater app that I pulled off of market, I have not once refused a refund to anyone that has asked for any reason, and it was made clear in the application description that the money was a donation to the project (Read: buyers’ remorse is not even a legitimate [i]feeling[/i]). By sending me a chargeback, you are not only taking your money out of the pool, but you’re taking an additional $3 out of my personal income. It is a completely unnecessary and insulting step.

Chargebacks are bad for everyone – it’s a lose-lose scenario. They make you (the buyer) look back for sending them, because fraudulent charges mean you were not careful with your personal information. They make the seller look bad, because they approved a fraudulent charge. They’re even bad for Google, because if they receive too many chargebacks, Google will end up making less money (Visa or whoever will rapidly increase the fines associated with each chargeback).

So, the next time you think about sending a chargeback over a tiny charge, you ought to give the seller a chance to do the right thing privately. It will not hurt to ask, and if the seller still refuses to refund you, only then should you consider taking such a hostile action.

PS (from trevorj): If you do request a chargeback, it is legally considered bank fraud, as it was a donation, not a payment for any sort of service or product in any way, shape, or form. It was a donation, get over it.

Misc upgrades to git.droiddev.org

I’ll be performing some miscelaneous updates/upgrades to the underlying systems on git.droiddev.org today. (mainly updating to latest version of git/gitweb and adding mirroring to github)

I’ll try to keep impact minimal, but be advised that clones might fail randomly throughout the day.

Snapshots will still be downloadable via the gitweb interface.

sgx

EDIT: updated to git/gitweb version 1.7.0.4 from 1.5.6.5 (damn Debian takes FOREVER to update to the latest packages… sid FTW!) next stop gitosis… :D