yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] BrutalHoe:
Its all the greedy russians in the google....disgrace to my nation ugh.

ILY Cyan.
[G1 Android Development] texasaggie1:
Great Article, my thoughts

Great article, thanks for clearing the air.

One point I wanted to make though. Cyanogen may be only programming .01% of the total package but what he does MAKES ALL THE DIFFERENCE in the world (the other awesome devs, too).

I am ready for his newest iteration. I have uninstalled google voice and I am now using the mobile versions of it and also of gmail.

Bring on the google free roms baby.

No, I don't hate google now. LOL
[G1 Android Development] Spon4ik:
1. is it possible to make a MOD, which modifies only the public portion of source code in the system, applications, and adds new applications, features, etc.?

it would be a perfect solution for any legal problems.

2. I really do not understand what is illegal in back up files to the device for my personal use?

those files that were originally built into the phone and have their part in the price that I paid for the phone.

files are belongs to me, I can do with it what I want - even erase it.

If I knew that I could not restore these files, because Google or HTC will not allow me, I certainly would not buy this phone.

3. is it even possible to make drivers without sdk for hardware?
[G1 Android Development] amack10:
What I don't get is that the hero and cliq come with the same google apps my g1 did. Its not lik cyan put these apps on a rom that is used for a phonee that dosnt come with them. And why isn't google going after the peopl makin hero for the g1 since all the same google apps are in it. And its not like the google apps are what made me buy this phone. Heck when I rooted all I kept was market, and g mail, for obviouse reason. I don't care about any stupid google voice anytime I use google voice search it brings up the wrong crap anyway. And as for all the google instant messaging crap idc about. Why would you wanna sit here and Im peopleee when you can text
[G1 Android Development] uberingram:
Blah blah blah.

Google doesn't want us distributing their apps? Fine. We wont. It would behoove us to not even use them. But you know what would be awesome? If AOSP was even usable. About the only glimmer of hope was that JBQ posted yesterday he managed to boot it and even get calls working.

Ugh. This whole thing is so stupid and was easily avoidable if Android wasn't rushed and made so dependent on closed source materials at launch.
[G1 Android Development] jashsu:
Download a release branch if you want a frozen and reasonably debugged codebase to work with.
[G1 Android Development] danguyf:
Well, that depends on what you mean by "a working Android environment", I suppose. It will not, when compiled and flashed to an Android phone, result in a working phone.

If Google only cares about the apps distribution then, great, removing them is easy. If Google doesn't want any of their proprietary code distributed, like that which controls the radio and the LED, then that's a whole other matter.
[G1 Android Development] jashsu:
The ril (radio), wifi, opengl es binaries, etc are all provided under license by entities other than Google.
[G1 Android Development] darkomen:
I've read a few people saying the reason cyanogen got the letter was because he leaked a version of the market? That may have been true but I also find it to be a big coincidence that right after his ROM gets mentioned on TwiG (This week in Google) podcast he got the letter. So it may have been a mix of both, just throwing it out there.
[G1 Android Development] danguyf:
So we're banking on modders continuing to distribute binaries without a license?
[G1 Android Development] Janis:
Is there a list of what belongs to whom?

Since this is a developers forum, I'm wondering if we can work toward fair development by:

1. giving credit where credit is due

2. getting code from the appropriate places

3. releasing, if that's the case, on an acceptable schedule.

It seems as though ROM development isn't just hacking anymore, it's got a legal side. Rather than each ROM developer checking permissions and doing all the needed legal research, why not have a repository (thread and wiki) for this info. As developers learn new things, it could be updated appropriately. I think the devs on XDA have grown up a lot in the last couple of years and could handle this. If bumps arise, hopefully the discussion thread would help work them out.

If anywhere currently in existence, I would think XDA-dev would be the place for multiple platforms to have lists of what's included in a stock ROM, what can and can't be in modded ROM, and all the "who's" associated with the "what's." Links to Android-dev, etc and other sources would be included. Given the conglomerative nature of ROMs, though, this site seems to be the forerunner in all those things coming together.

I'd be able to live with closed-source release dates, or exclusions, as I would imagine other "greedy" users, if I knew what they were, perhaps why the dates and rules are set as they are, and who's setting them.

If the information is accurate and developers respect it, we would have an easy way to appropriately address any legal issues before they happen.

By the way, I can't imagine anyone better suited than Cyanogen to negotiate with Google. He sure is showing a very level-headed, deliberate front to us, which we need, even though those of us who lean toward the hot-headed side might be a bit irked by his centrist approach. I think he knows how much is riding on the outcome of these discussions he's having, and he's feeling the stress. Rather than spending our energy griping, I think we ought to try to help out, accept the situation as it is, and start thinking of possible solutions.
[G1 Android Development] prince.siraj:
+1 :) very well written
[G1 Android Development] raitchison:
Sorry I disagree with this, the Google bits, especially the sync and market features are so integral to the Android experience that for an average user, an Android device without those components cannot be considered "working"

Maybe that's because when Google was developing and promoting Android they talked about how "open" it was going to be, even if they are completely within their rights (which I'm sure they are) they still violated the spirit of what they promised Android to be, which makes people justifiably upset.

IMO this is just semantics, since an android custom ROM without the Google bits is not a usable system for almost all end users, the net result of this action is to effectively kill off custom ROMs.

We should "respect" their legal rights, and certainly should not overtly violate those, but in no way should we respect how they are handling this situation, how they have violated the spirit of Android's promised openness and their own motto reminding them to "don't be evil".

Many (such as myself) feel that the Android hacking community is in peril as a result of these actions by Google. Since it's my opinion that Google's only possible reason for this action is to effectively kill off android custom ROMs, I fear that they will take additional steps, using legal and/or technological means, to shut down Cyanogen's proposed workaround.
[G1 Android Development] jashsu:
I'm sure a lot of developers in Google's position (having someone redistribute your work without permission) would have done the same thing with a clean conscience. In the world of software rights enforcement, a C&D letter is a pretty mild first move.
[G1 Android Development] macudc:
A mild first move, but a dumb one. Google have suffered a lot of grief from this C&D not to mention a loss of reputation. And all to stop the redistribution of the new market for 2 weeks before it became public. Someone in Google's legal department will have to answer for this (I hope).
[G1 Android Development] btmec:
Google should release their software as public domain and allow it to be freely copied. Google makes their money from advertising and selling some of their services. Google will only benefit from people having their software available to the public. If I use Google maps on my phone I will more than likely use it on my computer and then that opens the door for more advertising to be pushed to me by Google. If I use Gmail on my phone then I will use it on my computer, and so on. It is a win win situation for Google no matter what. This is why they offer free apps on other platforms.

Google wishes that everyone would have a "Google Experience" so the more available it is the better off they will be.
[G1 Android Development] Charrion:
That part of the C&D always struck me as a bit disingenuous. The market app would be their main "direct" money maker as people are buying apps through it and Google gets their cut. So why would you want to limit access to that market? I can't even see carriers or OEMs saying they don't want their customers to access the market.

It really comes down to a legal temper tantrum on Google's part. Cyanogen stole their thunder by distributing the market app before Google intended to.

Yes, they had every legal right to enact the C&D, but no practical reason to do so, other than for the sake of flexing their muscles. The argument that the market app could have been altered is disingenuous also. They've tacitly trusted Cyanogen to this point, why assume he's suddenly doing something malicious, now?

The C&D was a PR snafu, but once the tiger was out of the cage, Google had to make like it was the perfect business decision by effectively spreading FUD about the mod community in general and Cyanogen in particular. It doesn't help that we have effective shills like Jashsu trying to convince people that Google made the right move.
[G1 Android Development] raitchison:
A lot of developers aren't Google, they have set for themselves a higher standard of ethical and moral standards. When they don't live up to that people are going to be upset.

It doesn't help their case that beyond asserting that they were being "harmed" by what Cyanogen was doing they haven't even attempted to explain how they were being harmed, some have speculated that HTC or T-Mobile pay them for the "Google Experience" but that hasn't been confirmed, and considering that they don't (to my knowledge) charge for any software for other mobile platforms (such as iPhone or BlackBerry) I don't see how they are suffering any kind of harm at all.

I don't disagree with that, of course if they had gone any harsher I suspect they would have far fewer apologists than they do.
[G1 Android Development] raitchison:
I don't even agree with that, these components interact with Google services and I can totally see why they would want to keep them closed source, what they could/should have done to solve this problem without all the controversy is simple, they have two choices.

1. Allow all their released (not pre-release) components to be redistributed via a redistribution license

Or

2a. Allow the critical registration & sync bits to be redistributed via a redistribution license.

2b. Provide the Market app on the android web site as an APK download

2c. Provide the remaining apps for download via the market
[G1 Android Development] jashsu:
I see nothing ethically or morally wrong with asserting ones

rights

to ones property. One side of the argument here has legal rights, the other one has flimsy justifications and weak excuses.
[G1 Android Development] BrooklynAvi:
I couldn't agree more. The phone was marketed as being different that the other mobile device platforms currently available. I fully understand the situation and feel that Google was, and still is, completely within their rights. However, by waiting nearly ONE YEAR to assert those rights kind of gives people the impression that you never cared. Like has been said here a million times, if Cyan didn't release the Market early then none of this would have happened.

By not saying something sooner, Google was, in some small way, okaying what was going on because we all know good and well that they did know what was going on. Again, I'm fine with what Google did. I just wish they'd done it sooner and more gracefully. I think Cyan should also have kept it a bit more quiet so as not to "yell fire in a crowded theater," so-to-speak. I think that since, as was said above, Google marketed the platform in such a way as to make it sound okay to redistribute their apps since they were such an integral part of the platform (just search Google for the early Android video from Sergey Brin and you'll see what I mean).

Still, Google is in the right and so be it. Given Google's position I believe they should find a way to market their apps for "private" use since there is such an integration between the platform and their apps in Android's current state. I don't believe that Android would be even 1/1000 of what it is without Google doing what they do best and they marketed it as such. They wanted people to think that Android = Google and Google = Android and now they are complaining that people bought into the hype.

Alright. I've spent waaaay too much time discussing what basically amounts to nothing. Google did what is within their rights to do and everyone needs to get over it and move on. Solutions already exist and better things can quite possibly happen as a result of all this (With Yahoo!/With Hotmail/With Anything anybody?).

EDIT: There is such a thing as Squatter's Rights. It is a real concept. I wonder if by not asserting their rights for so long if Google can actually lose those rights. Just a thought. LOL.
[G1 Android Development] giantcrazy:
Not when it comes to copyrights. That's applicable to trademarks - if you don't defend unauthorized uses of it then it can become public domain, but with a copyright you can sit and wait forever until you decide to enforce it.
[G1 Android Development] raitchison:
If you promise "openness", then violate that promise hiding behind fine print you are absolutely not ethically or morally right. That's exactly what Google has done, while it's 100% accurate that the components in question were never part of AOSP and were never F/OSS the fact is that the vast majority of users don't even know what AOSP or F/OSS are, they only know that Google promised that Android was going to be different, that it was going to be "open", it never even occurred to them that it was going to be open unless you wanted to have a usable (from an end user's perspective) phone.

What's "legally" right and what's right are frequently completely different things, "don't be evil" is not a legal disclaimer it was supposed to be the opposite of that, it was supposed to be a guideline for Google to behave

better

than the law required them to. When Google starts hiding behind their "legal rights" to justify bullying behavior, especially absent any evidence of harm to them they have failed to live up to their own standards.

I never attempted to justify or excuse anything, I simply am criticizing Google for how they handled the situation and how they have in my opinion failed to live up to their own standards as well as our expectations, you seem to be the one making justifications and excuses.
[G1 Android Development] blueheeler:
Not from a legal standpoint, but from a user standpoint, that sums up the reason there has been a whole lot of outrage over this nonsense.

I don't think any of us doubt they have the legal right to do what they did, but very few seem to think that they had the ethical right to do it considering how they marketed the phone. Thus the rants and the outrage.

For a good many of us, Google has now tainted their reputation ... and worse ... they've tainted our experience with the Android platform. I have made the conscious decision to avoid Google products just like the plague. I'll choose alternatives any time I can seeing how they don't have a monolopy on hardly anything anymore. In fact, I'd say many free services and products beat them hands-down (as an Outlook user, I've never liked the threaded conversation mode of Gmail ... YouTube has plenty of competition now ... Voice, that one's gonna be hard ... Market, another hard one until the alternatives grow ... Calendar & Contacts, Exchange wraps all that up nicely and apps are available now ... Reader, not implemented all that well on the Android platform, etc.).

My next phone likely won't be an Android. As much as I love it, if I see that Google's powerplay (and the resulting fear of HTC/Qualcomm/etc now that notice has been served) hampers what should have been robust hacking & modding community, I'll pick something different for sure. If legal workarounds prove to be a viable option, then who knows what I will. I was just starting to work on developing my own hacking skills for the Android platform when this bombshell was dropped. I'm not sure I want to invest the time now in learning what it takes for Android if I cannot commit longterm. It's sad.
[G1 Android Development] BrooklynAvi:
Yes, I know. It was more of an observation that Google decided to let it slide for so long. I am aware that it refers to "real" property. One must wonder why they openly allowed what is essentially considered the theft of their apps for a really long time and then decided to say "hey, stop sealing from us." Very strange but well within their rights. Hey, they could, for example, allow everyone except Cyan to continue freely distributing their ROMs. It's their right. It's just weird.

Damn. I thought I was done talking about this. LOL. BTW, Why does the original author of this thread get to say the last word? Every thread like this was "the last word." :) Now I'm really done. Looking forward to this from Cyan and moving on: "Expect a present sometime this weekend from me."
[Hero, G2 Touch Android Development] Amdathlonuk:
Hi all,

I really miss the opportunity to tweak the colour of my led like I could with G1. does the Hero have the same functionality and it's just not used?

Or is it a hardware issue?
[Hero, G2 Touch Android Development] Breakthecycle2:
Try this:

http://xdaforums.com/showthread.php?t=565015

I'm going to try myself.
[Hero, G2 Touch Android Development] Golgo:
Does NOT work on Hero.
[Hero, G2 Touch Android Development] Drizzy Drake Rogers:
this dont work as the commands and codes are made for the g1, though i have found the source to where LED's are in the hero, but I havent made any progress yet on changing the colors!
[Hero, G2 Touch Android Development] Breakthecycle2:
Well...C'mon man!!

JK!!
[Hero, G2 Touch Android Development] soulonfirexx:
Is there a possibility to have the trackball change colors as well? My girlfriend's old BlackBerry was able to do that with a software update and I always thought that was cool. Not a big deal though, just wondering.
[Touch Pro, Fuze Themes and Apps] venkss:
Hi Guys,

I am coming from Symbian to Windows Mobile. I have a HTC Fuze and can't seem to figure a few things out.

1. In Nokia (Symbian) you can setup your email and other data services to use your home wi-fi when you are in home. When you are outside, it will use 3G/GPRS etc. automatically (once preferred access points are setup). I can't figure this out with HTC FUZE. Everytime I have to turn on and off the Wi-FI Connection (Connection Manager -> wi-fi ON or OFF). if I leave it on, it keeps popping up with networks that it finds. If I leave it Off, it doesn't use wi-fi to retrieve emails and other things when am at home. I am sure this should be easy... Help !!!

2. When I set my phone in Vibrate mode, it doesn't even play music through headphones. I have to set it "ON" mode for it to even play music. This is annoying. At work, I want the phone to be in vibrate mode but still listen to music through head phone every now and then and not worry about my phone ringing. Is there a simple fix? Am I missing something??

3. When the phone is in Vibrate mode, I would like it to vibrate for incoming emails. it does not do that.

4. What is the best recommended "TODAY" Screen plug-in/program for wm 6.5 other than the titanium one?

I am using NATF's Win 6.5 latest ROM.

I appreciate all your help.

Best,
[Touch Pro, Fuze Themes and Apps] willr001:
1) I think you can go to Settings>personal>Sounds&Notifications and turn off the found new network notifications on the notifications tab (you also may be able to settings>wifi and change whether it scans or not, scanning seems like it would drain the battery)

2) The volume screen usually (depends on rom) has two tabs, one for sounds, one for ringer, so you could have sounds but vibe instead of ringer. Other than some 3rd party service that switches the volume settings based on the headphone port, i think that's about as good as it gets.

3) In that same settings>personal>sounds menu, you can change the new email notification to vibrate or sound and vibrate or whatever. it has to include vibrate in that setting though to vibrate ever.

4) I like the old-school HTC Home, or similarly SPB PocketPlus or SPB Diary. If you're looking for something fancier, lots of people use the Touchflo 3d (which can work in 6.5) or SPB Mobile Shell (there's a demo of version 3 on their website)

Hope I helped some, I know the windows mobile limitations can be annoying, but they're pretty minor overall (imho). All things considered, I've been a big fan for years, you just need to use a lot of 3rd party apps and tools.

Good luck, finding XDA was probably the best thing I ever did for my WinMo phone, hope you have the same experience.
[Touch Pro, Fuze Themes and Apps] venkss:
Thank you very much for your reply. I can't seem to find the setting that you mention for turning off wireless scanning. Is this because of the ROM?

Also, if I have both Data Connection and Wi-Fi connection enabled, and say for example run Opera, how do you know which connection it is using? How do we change/specify the connection that opera uses? I am just using Opera as an example... bigger question is emails.
[Touch Pro, Fuze Themes and Apps] willr001:
Hmm, I think I may have made that setting up :D

As long as your email account is set to use your Internet Connection (versus Work Connection), which should always be the default, and when you first connected to your wifi, it should have asked something like "This networks connects to: <radio buttons> The Internet, Work Network". As long as everything is "The Internet" you should be good. I don't know how to double check what connection it is actually using except looking at the activity light on your access point, but it should always use wifi over cellular data if wifi is available.

As far as the scanning / battery life, the performance slider in wifi was all i could find. I just use the Comm Manager to toggle wifi as needed, but admittedly I don't use it alot. I could see it being annoying.

So the nokia would know when you were by certain wifi spots and connect, without killing the battery life completely by having wifi on 24/7? That's pretty sweet...

I wonder if it just low power scans Wifi AP's every 5 min or so, maybe someone could make a similar WinMo Service?
[Touch Pro, Fuze Themes and Apps] willr001:
I know this is way off topic for this thread, but if anyone has a more raphael specific programming guide, I'd appreciate a link.

I'm taking a look at http://msdn.microsoft.com/en-us/library/aa457716.aspx

to see how hard programming is.

Both the headphone thing and the wireless thing would be nice to have as features. I'll see what I can do, but I've never developed for WinMo before, so absolutely no promises on anything =)