[HD2 Windows Mobile 6.5 ROM Development] :
For all that doubted that we are the bad guys in the coredroid drama, I will put here some facts/proofs here.

But first a little explanation what happend.

One month ago I contacted Sergio(coredroid) and asked him why he kanged the tweaks from our pkmn v3 (venusaur):

as you see in this pm, i didn't reported him, just put a mod inot the pm, so he is aware of it.

Later in gtalk with sergio:

Well, you see sergio even admitted that he kanged our tweaks AND PROMISED TO FIX IT.

...I was so kind and gave him time to revert the update - well it took over a month. AND I didnt reported him.

After one month he released an update, but instead of reverting the stuff mentioned above he even took LOTS of code from our v5 rom.

Well he had his chance to fix things which he ****ed up...Maybe it was a missunderstanding in teh first place...I dont think so, but who cares/knows.

FACT is he kanged me a 2nd time...AND HE KNOWS THAT HE DID!.

Sergio is talking about open source and that I hoarding ideas and can't call that ideas mine.

Well let me quote a part of the xda rules:

The code I wrote is 100% ours and there is a huge difference between taking an idea and implement it ownself or just kang the whole code.

I will show you now some code stuff that 100% prooves that sergio is stealing our code AND IMPLEMENTED NOT ONE SINGLE LINE BY HIMSELF IN SMALI.

The main code is handled in android.policy and systemui...and I will show you both of you and some others.

here you can see a diff of both android.policys.jar of the Phonewindowmanager.smali. Here a lot of tweaks are done. on the left you can see the differences (red marks).

you see that there are not much diffs between ours and coredroids.

..here you can see, that sergio just changed a key string which is required to communicate with android settings.db

99,999999999% code steal

The red marked methods are completly wrote by me...no way sergio too the same one and contains the 100% same content, huh?

And this has nothing to do with hoarding ideas..if you steal an idea you implement it on your own and dont copy paste the code.

To show people that we changed a lot in the code not just a few single lines, I used vts to show the java code..and diff a stock file with our modded one:

..and diffed it:

..etc

now you can imagine what huge code changes we are doing and there is NO WAY that the code is 100% the same when

you take our idea and implement it yourself.

Especiall not taking the same methodnames and variables.

theres a lot of **** sergio kanged in android.policy. let me list all here:

Button remapping/longpress actions:

- huge modifications to interceptbeforedispatching method.

- modifications to ShoworHiderecentappsdialog

- huge modifications to $300 method

own methods:

- handleLongPressOnHomeLockscreen

- startCustom(J)V

- SendMediaCMD

- startMenu

- startTimer

- getFlashlightenabled

- setflashlightenabled

- lockscreen.smali: implemented new broadcast receiver which listens for an incoming call and makes it possible to unlock the AOSP lockscreen

- slide2unlock in lockscreen smali

Sergio kanged actually the whole android.policy and claimes I cant call it mine and hoarding this ideas.

I wonder if I gave him any of mine ideas, if he is able to implement it himself. I can tell you: NO HE CANT.

Well, that was the android.policy, lets continue with with Rosie and I will tell you what I unerstand about taking ideas:

Here is an example how to enable landscape on rosie:

this requires not much knowledge, well you need to know how to build a toggle around it, if you want to hardcode enable it you would just need to add a "const x, 0x1"

value before the return statement.

I agree that here for this small tweak in Rosie.apk isnt much space to implement it different.

But when its again something like this: (also in Rosie.apk)

its 100% code steal.

i compared here the stock rosie with a modded one from coredroid.

You see that the method updateHIddenAppsList ist there in the stock rosie and written by us...and completly kanged from coredroid.

And again the hint, theres NO WAY that each character/line is completly the same when you take the idea and implement it yourself.

THATS 100% code stealing.

Some more examples from SystemUI:

here you can see, that sergio is again just able to rename some variables and the tweaks keys.

NOT ONE SINGLE line he implemented himself: 100% steal.

- he stole the implementation of the quicksettings with tabs

Sorry, but there are 100 ways to implement it different..though he just copy pasted the code again

- he stole the cm7 brightness mod

- fyi: the way it was implemented on v3 is different than on v5, here are also 100 differnet possibilities

possible to implement it in another way...though he just copy pasted it again.

- he stole the complete code to show the cpu/memory/etc stuff in the carierlabel under the carrier text:

here you see that those files are not present on stock SystemUI and complete our compiled/written files...again sergio just copy pasted them and just chnaged the tweaks strings:

...again THERES NO WAY YOU CAN WROTE THAT MUCH CODE ON YOUR OWN AND THERE ARE NO DIFFERENCES TO OUR CODE!

- he stole the possibility to set color/transparency/background image

- theres are lots of code chnages required to accomplish this

- well there are soo much other things in systemui and other files that are just copy pasted...I could mention several others.

Conclusion:

NONE of the mods in coredoids smali code is wrote by himself, all stuff is just copy pasted. The android.policy is completly kanged a file.

Systemui/Rosie/etc he didnt took the whole file. He decompiled a stock syystemui and or modded one and copy pasted stuff from ours to his.

I checked nearly each framework file which is included in our tweaks...not one single method shows me that sergio isnt able to write own smali code.

I also see no reason how in hell sergio can claim to wrote it himself or say that I can't hoard ideas and call them mine.

Well yeah, i can't hoard this ideas, but the code behind it. And each one that says there are no way to implement that idea in another way, then you havent

the knowledge about java/smali or programming in general to rate this.

I can tell you that there are unlimeted ways to code an idea in another way, especially when huge code has to be written/alteres, which happend in our case.

When just one little thing is required to chnage, like in my example with the landscape thing in rosie I agree that theres isnt much space to implement it in another way.

But well this applies maybe to 5% of the code or less that we implemented, though sergio copy pasted all of our code and still thinks he is still in the right.

fyi: (pls dont share/publish it)