DroidForums.net & Ultimate Droid ROMs

[ldimick]

Was it only etiquette that was breached?

Yes, that is what it boils down to.

No copyrights, trademarks, not other legal stuff was breached.

I am not denying what you are saying. I am pointing that there is a huge ethics problem with BDs actions. You may disagree.

My reasons for stating this:
-He claimed it was HIS code and HE built it from source with ERE81
-He asked for an accepted donations
-He flamed CM and Koush and then copies their product as his own
-He has been banned from AD for distributing copyrighted software (aka piracy)
-He complained about ROM Manager trashing his UD9.5 ROM and yet he was not capable of finding the problem, nor fixing it. I never did see him acknowledge that it was his cache file that caused the problem.

I did not want his removal. I wanted hm to come clean and acknowledge or defeend his actions. Instead we got a BS stroy about an XML file. My desire for action was based upon his unethical actions, dishonesty and theft.

I do not deny that many people think he improved upon the CM product. But to me the improvement is a matter of definition. I used UD9.8 and the only reason I went to CM was that I was looking for a more compact ROM. with UD9.8 I was left with about 20MB of space. With CM I have ~80MB. If I had not had more space left I would still be trying new ROMs.

I liked running UD9.8 But because we are rooting our phones, and literally exposing them to all sorts of nefarious actions, I want a ROM that I can trust. With such a pattern of dishonesty, deceit and/or incompetence I don't trust his ROMs.

 

[TheMarkness]

So if I compile the code without any changes, it would be mine. How would that effect the MD5 calculations?

From Wikipedia, the free encyclopedia

Jump to: navigation, search
md5sum is a computer program that calculates and verifies 128-bit MD5 hashes, as described in RFC 1321

. The MD5 hash (or checksum) functions as a compact digital fingerprint of a file. It is extremely unlikely that any two non-identical files existing in the real world will have the same MD5 hash (although as with all such hashing algorithms, there are an unlimited number of files that will have any given MD5 hash).

Exactly. Compiling the exact same code will produce the same MD5 results.

Yet, as TheMarkness confirmed, the simple act of compiling code makes the project my own.

Therefore, the Google MD5 spreadsheet arguments are moot.

And I thought you where understanding it after all.

It is extremely unlikely that any two non-identical files existing in the real world will have the same MD5 hash - EXACTLY TRUE!

Compiling the exact same code will produce the same MD5 results - FALSE READ ABOVE STATEMENT FROM WIKI

Everytime a MD5 is generated it's always different even if I take the same exact file as you, our digital footprints will be different that's the point of an MD5 :icon_eek:

 

[hairdewx]

Google Source = Open to all to build and compile a rom from
Cyanogen Source = Open to all to build and compile a rom from (he encourages using it)
Cyanogen 5.0.5.7 = Compiled and cooked rom for distribution and use.

Wasn't just etiquette it was stolen work, he took a cooked rom and claimed as his own. He is more than welcome to build his own rom from either open source.

How can you tell if a module came from a cooked rom vs source code?

 

[Shelooga]

man i really wish i wasnt a newbie and knew what this was about. sounds like some serious biz went down

 

[superkeest]

copyright or not, im pretty sure the GNU licence still applies.

 

[Sodner]

I just had to repost this from another thread in the ROM section. This is simply unbelievable.

A user posed a question in the the Koush sub-forum about switching from Ultimate Droid to CyanogenMod. The user asked if he needed to do a data and cache wipe during the install. Koush responded:

"Originally Posted by koush
You may need to just bite the bullet and do a fresh install, without your app backups. The "base" of UD and CyanogenMod are so different, that I would highly recommend this, as things may go really wrong otherwise."

Didn't Koush recently flame the every living heck out of blackdroid, along with Cynanogen, because they were claiming Ultimate Droid nothing more than CyanogenMOD that had been skinned?

:icon_eek::icon_eek::icon_eek:

Nice find. EXPLAIN THAT ONE CM FANBOYS!

PWNED! KANGED!

 

[Pdigg]

man i really wish i wasnt a newbie and knew what this was about. sounds like some serious biz went down

There's plenty of it still around to read, but you should probably be thankful you missed it and just turn around and walk away now.. Welcome to the forums though

 

[GryphonD]

Why is it so hard to understand that these guys take what they do seriously. And they feel like they were spit on by greg so they are angry.

Nowhere did I state that it is hard to understand. What I stated is that continuing the debacle in such a manner is in my opinion highly unprofessional.

If they want to keep it going as they are, I believe they should do so in a direct contact aspect, not continue to make it a glaring glow in the eyes of the users.

This sort of thing happens, all the time. Devs copy other devs, they always have. So when the next occurrence takes place, do we who have paid for RM have to be subject to more of such ilk?

To say that it was another CM based ROM seems fine, but beyond that, they are just pissing in the faces of all who use RM. Those who have paid for the RM are in effect customers of a service. When you go to a local cafe or restaurant, no matter who originally made what ever you ordered, do you really want to be inundated with the servers personal drama?

 

[ldimick]

So if I compile the code without any changes, it would be mine. How would that effect the MD5 calculations?

From Wikipedia, the free encyclopedia

Jump to: navigation, search
md5sum is a computer program that calculates and verifies 128-bit MD5 hashes, as described in RFC 1321

. The MD5 hash (or checksum) functions as a compact digital fingerprint of a file. It is extremely unlikely that any two non-identical files existing in the real world will have the same MD5 hash (although as with all such hashing algorithms, there are an unlimited number of files that will have any given MD5 hash).

Exactly. Compiling the exact same code will produce the same MD5 results.

Yet, as TheMarkness confirmed, the simple act of compiling code makes the project my own.

Therefore, the Google MD5 spreadsheet arguments are moot.

Quoting from RFC1321:
"
t is conjectured that it is computationally infeasible to produce
two messages having the same message digest, or to produce any
message having a given prespecified target message digest."

Since we know that CM DID, in fact, make changes to the code how did those changes end up in BD's own work?

 

[jroc]

Someone has plans to build a doghouse. Someone has the same plans to build the same doghouse. The "plans" come from "open source" so anyone can use them. One person builds it plain and another adds heat/air conditioning. But both start from the same plan? (google source code)
What is the difference?

Taking someone else's idea (or work) is what is done every minute of the day in the world. Thats how development works and gets better.

Isn't this more like waiting for your neighbor to build the doghouse, going over there during the night, stealing it, repainting it and calling it your own?

Not if both doghouses are prebuilt or you and your neighbor have identical part to build with

TY TY TY!!!! I been trying to figure out a way to say this since this all started!!!! How can yall use an analogy like that? It aint like CyanogenMOD all of a sudden disappeared of the face of the earth. His was still there to install too. BD never dissed ANY other ROMS out, saying "use mine its better than all the rest". Its a credit and popularity thing. He didnt give credit where credit was due...egos got bruised.

IMO, if thats the case ANY CUSTOM ROM FOR DROID THATS MADE NEEDS TO GIVE A CREDIT TO GOOGLE, AND NOT JUST SAY ITS SOURCE! Since this "give credit where its due" is sooooo important. I see less fighting on modded Windows OS's.

Was it only etiquette that was breached?

Yes, that is what it boils down to.

No copyrights, trademarks, not other legal stuff was breached.

EXACTLY. When I go thru the entrance at work, I hold the door open for ppl, some dont say 'thanks'. Do I call em out and say "Hey U didnt say thanks!" No, I keep it moving.

And the fact of the matter is, right now I got the latest CyanogenMOD installed. Runs very smooth. And I still have UD 9.8 as a main back up. And I might try UD 10.0 this weekend.

 

[Sodner]

"Originally Posted by koush
You may need to just bite the bullet and do a fresh install, without your app backups. The "base" of UD and CyanogenMod are so different, that I would highly recommend this, as things may go really wrong otherwise"

PWNED!!!!!!!!!!!!!!

 

[TheMarkness]

Google Source = Open to all to build and compile a rom from
Cyanogen Source = Open to all to build and compile a rom from (he encourages using it)
Cyanogen 5.0.5.7 = Compiled and cooked rom for distribution and use.

Wasn't just etiquette it was stolen work, he took a cooked rom and claimed as his own. He is more than welcome to build his own rom from either open source.

How can you tell if a module came from a cooked rom vs source code?

Again the MD5. When you compile the a source those files have a date/time generation on the file which won't match the date/time of another persons compile (unless magically you both did it at the same exact date, time, sec, ms, etc). Then when our MD5s are generated it takes into account that completely unique file in it's size, build time, and all the aspects to generate that hash. Having two identical hashes is next to impossible.

 

[ldimick]

I just had to repost this from another thread in the ROM section. This is simply unbelievable.

A user posed a question in the the Koush sub-forum about switching from Ultimate Droid to CyanogenMod. The user asked if he needed to do a data and cache wipe during the install. Koush responded:

"Originally Posted by koush
You may need to just bite the bullet and do a fresh install, without your app backups. The "base" of UD and CyanogenMod are so different, that I would highly recommend this, as things may go really wrong otherwise."

Didn't Koush recently flame the every living heck out of blackdroid, along with Cynanogen, because they were claiming Ultimate Droid nothing more than CyanogenMOD that had been skinned?

:icon_eek::icon_eek::icon_eek:

Nice find. EXPLAIN THAT ONE CM FANBOYS!

PWNED! KANGED!

This happens because it was a themed ROM. Some of the trash (for lack of a better description) would still reside. Same thing happens in Windows. Also, you will notice that there is no description of which version the OP was migrated from UD9.8 or 10. Given the response I would suspect that the OP was on 9.8 and not 10.

BTW, I am not a FANBOY, I am just a user who wants transparency and honesty. Which is something that BD/UD FANBOYS are willing to forego. So be it. You deserve what you get.

 

[Shelooga]

man i really wish i wasnt a newbie and knew what this was about. sounds like some serious biz went down

There's plenty of it still around to read, but you should probably be thankful you missed it and just turn around and walk away now.. Welcome to the forums though

i picked up some things here and there. it looks like someones work was stolen. im glad im not smart enough to do work and then have it be so excellent people steal it. drama drama drama.

ill keep my crappy sponges thanks

 

[hairdewx]

Google Source = Open to all to build and compile a rom from
Cyanogen Source = Open to all to build and compile a rom from (he encourages using it)
Cyanogen 5.0.5.7 = Compiled and cooked rom for distribution and use.

Wasn't just etiquette it was stolen work, he took a cooked rom and claimed as his own. He is more than welcome to build his own rom from either open source.

How can you tell if a module came from a cooked rom vs source code?

Again the MD5. When you compile the a source those files have a date/time generation on the file which won't match the date/time of another persons compile (unless magically you both did it at the same exact date, time, sec, ms, etc). Then when our MD5s are generated it takes into account that completely unique file in it's size, build time, and all the aspects to generate that hash. Having two identical hashes is next to impossible.

I see. I'm used to generating exact MD5 results here at work. I forgot that we have uniform compilers, paths, compile clusters, etc.

Sometimes I get so used to my ways that I overlook conventional methods.

But then this still leaves the issue that if BD simply recompiled then it wouldn't be an issue... still petty IMO