Not too long ago, we talked about how Sony was continuing its AOSP efforts on the Sony Xperia Tablet Z. Now, we have given the device its place in our forums. For the uninitiated, the Xperia Tablet Z is Sony’s most recent flagship tablet. It features a 10.1″ 1920×1200 LCD, equating to approximately 224 ppi. The high resolution panel is backed by a 1.5 GHz quad-core Qualcomm Snapdragon APQ8064 processor and 2 GB of RAM. It also features a 6000 mAh battery to help keep the device powered all day.
We also added a home in our forums for LG’s latest flagship phone, the LG Optimus G Pro. It features a full 1080p 5.5″ IPS LCD, coming in at around 401 ppi. The device is powered by a 1.7 GHz quad-core Qualcomm Snapdragon APQ8064T, as well as 2 GB of RAM and 32 GB of internal storage. The G Pro also packs a 13 MP camera and is backed by a 3140 mAh battery.
Do Sony’s AOSP efforts have you excited? Is the Optimus G Pro going to be your next phone? Let us know in the comments below. And for those interested in getting in on the discussion of these new devices, visit the newly created forums below:
During the first half of 2012, XDA initiated the Recognized Contributor (RC) program to recognize members’ exceptional contributions and general helpfulness towards other members. Over the last 12 months, the program has become extremely popular and successful.
We have continuously upgraded the program and adjusted our vetting standards and criteria. As part of our review and monitoring procedures, it was felt that in addition to exemplary adherence to the site rules, Recognized Contributors should also be held to a Code of Conduct (CoC).
A short Code of Conduct was developed and will also bring the RC program in line with the Recognized Developer program that has for some time included a Code of Conduct for its titleholders.
Recognized Contributors – Code of Conduct
1 — The RCs primary role is to create harmony by helping other users. In doing this, RCs will seek to help by giving information and pointing users in the correct direction. RCs do not act as a monitor of the rules.
We try to be friendly here, and expect RCs to be at the forefront in setting a good example for others. RCs must not only follow the site rules but reflect a spirit of friendliness and sharing.
2 — RCs should be a model of good behavior on the forums. This means always avoiding conflict and arguments with users. RCs will discuss conflicts with a Moderator rather than contributing to arguments within forums.
3 — The RC title confers recognition for the valuable help given by the title holder to the site and its members, it does not confer added authority over other users.
4 — RCs are not allocated to specific fora, but aim to spread their help across the site as a whole.
The Code of Conduct reflects the high standards we expect from RCs, and in turn what other Members should expect when interacting with an RC. Finally, to further enhance the RC program and to keep it progressing efficiently, a Committee is being formed to help assess and review applicants.
May 15, 2013 By: Will Verduzco
When we launched the Recognized Developer program here at XDA, we did so in order to help support some of the most valuable members of the site: the people who create all of the cool modifications, hacks, apps, and tweaks that go into better optimizing our mobile experiences. However, in order to keep up with our ever changing mobile needs, the program has seen its share of revisions and expansions during its course.
Today, we are announcing a few more changes to the Recognized Developer program in the form of tweaked Minimum Requirements necessary to obtain the RD title. And if you’re thinking of applying as a Recognized Developer, we highly suggest taking a closer look to make sure you qualify before applying.
Some of the noteworthy changes involve projects. For example, projects need to be at least three months old to be considered, rather than the previous requirement of one month. Furthermore, applicants must have two projects, rather than two ROMs or one project. We are also requiring that changelogs be clear and free of meaningless “information.” Finally, we will no longer be giving RD status to team accounts in the future.
If you would like to read more and are thinking of applying to the Recognized Developer program, I would highly suggest visiting the Minimum Requirements page and making sure you qualify. Those who still want more clarification can then visit the development template thread we created to showcase the ideal way of sharing your development work with the community. Happy devving!
April 30, 2013 By: Will Verduzco
Not too long ago, we covered the release of the HTC One and gave you a quick glimpse of its performance. Shortly after, we gave the One a home on our forums for both the international and some US carrier variants. Now, however, we have also created a forum for the T-Mobile HTC One variant.
Similarly, we covered the release of the Samsung Galaxy S 4 and gave the international version a forum here last month. However, now we are happy to also give the AT&T and Sprint variants their place as well.
Those looking to get in on the discussion can do so by visiting the links below to the newly created forums:
This is a multipart series on planning the XDA Development Conference to be held in Miami August 9 – 11 (http://www.xda-devcon.com). We want to give everyone a sense of what the event’s all about—and maybe some insight on what it takes to put on even a small conference.
Before we start, we want to apologize for stupidly using the same web “event” template (as well as some sponsorship language) as the Big Android BBQ. We’ve since changed our site, and we have no excuse other than that we’ve been focused on organizing a great event—and the website was the 100th thing on a long list of to-dos. In any case, the Big Android BBQ is still the premiere Android community event (which we still plan on sponsoring again this year)—and it is very different from our DevCon. So, please consider this an official apology.
First thing’s first: Putting on a conference is expensive: similar to a multi-day wedding, without all the flowers. This is a true community event. All the speakers are graciously contributing their time and expertise (for free). All sponsorships and ticket fees are being plowed back into the event, and we (XDA) are making up the difference. XDA moderators (and even some wives) will be organizing and staffing the event. It is our way of trying to give back to the development community that has made XDA so amazing. If there’s anyone out there who wants to attend but for whom the conference registration fee is too much, send a message to the DevCon contact email (firstname.lastname@example.org). We’ll send you a code for a free ticket.
The hardest part of organizing a conference is making it different and memorable. Free food, fun, and giveaways can help (and we’ll have all that); but the key is being interesting, educational, and unique. Our goal with the event is to interactively cover a broad range of development topics, and attendees should be prepared to contribute actively to the discussion. We hunted for presenters who could go well beyond a PowerPoint to engage an audience while teaching. And in addition to all of those speakers, every attendee will have the opportunity to get on stage, present a project, ask questions, and solicit feedback. We expect to have attendees with all levels of development skills– so please don’t feel intimidated. XDA is all about community and learning. DevCon will be the same.
We’ll leave you with bios of just a couple of our speakers. All of this is on the DevCon website, but for those too lazy to click over, hopefully this will help you get interested:
From HTML to LEDs, or Android to Arduino — Pearl Chen takes on a cross-disciplinary approach to her work. With over 9 years of professional experience in web technologies, Pearl has a body of work that includes Facebook campaigns for Google Chrome and microsites for Nike. Pearl also tackles more unusual jobs such as modifying the guts of Nintendo Wii controllers and dynamically creating origami objects from SMS messages.
Pearl was most recently the Senior Manager Research & Technology at the Canadian Film Centre’s Media Lab and is now working independently as an educator teaching web development, Android, and electronics — while also building tools for other educators.
Alongside contributing to open source educational resources hosted on Github, Pearl is a published author and contributed the NFC and Open Accessory API chapters to Professional Android Sensor Programming published by Wrox.
Pearl enjoys building tools for other educators and her goal is to raise the bar for technology education by using collaborative platforms to help construct open source curriculums, and by creating engaging and effective educational user experiences.
Justin Case, known as jcase, is a mobile security researcher, CTO of Applied Cybersecurity LLC, a contributor to the popular Android blog AndroidPolice.com and the developer of many Android exploits.
Justin will be discussing vulnerabilities and common security shortfalls in Android applications and firmware. He will also be walking the audience through identification of a vulnerability, and development of an android root exploit. Additionally, he will be speaking about application and firmware security, citing and explaining common mistakes and how we can mitigate them.
April 21, 2013 By: Jimmy McGee
Recently, XDA added a set of forums focusing solely on App Development. We knew that XDA was missing a central hub for app developers to converse about things like development tools, prototyping, analytics, monetization, testing, security, localization, education, and so on. In addition to the forums, we are providing assistance to app developers in any way we can.
To assist app developers, XDA Developer TV Producer Jayce takes a break from talking about how to become a hacker and hacker schools and asks you what you want to hear about regarding app development. Jayce will then find experts and get their insights on the topics you want to hear about, so leave a comment and tell us what you want to know, and be sure to check out this video.
We might be the only site on Earth that doesn’t beg you to register at every turn. Outside of posting, guests on our forum can do almost everything members can, including downloading attachments. The rationale for this is that we want to do our best to keep the forums clear of junk posts (cue the chuckling from the people who already think XDA is overrun by noobs). Our moderation team does an outstanding job of keeping XDA ‘on topic’ and free from spammers and other ne’er-do-wellers.
So, we’re not popping champagne to celebrate this milestone. But still, 5 million members is pretty impressive. It took 10 years to get there, and we’re kind of proud of it.
April 17, 2013 By: Will Verduzco
Some may say that we here at XDA like to celebrate from time to time. And why wouldn’t we? After all, thanks to the hard work from the many talented developers who call this little place on the web home, we’re able to do much more with our mobile devices than their manufacturers ever intended.
How exactly do we celebrate? Often, it’s through various fun contests. So at this time, we’d like to thank both our contest entrants and our supporters who have given us the goods that we then shared with you.
Let’s start with our most recent contest, which was in honor of reaching 100,000 subscribers on our YouTube channel. This contest was sponsored by XDA itself. While the winners of the two Nexus 7 tablets have not yet returned our messages, they are Niko Novak and Almir Vuk. So if either of you are reading this, please send a PM to yours truly or XDA TV Admin JimmyMcGee so we can send you your tablets.
Next up is our Valentine’s Day contest, which was sponsored by SolidRun. This RD-exclusive contest asked entrants to come up with fun and exciting development projects in order to get a chance to win a CuBox unit from SolidRun. The winners for this contest were Dexter93, regaw_leinad, and netham45. Those who are are interested in obtaining their own CuBox unit at a discount can do so by visiting this link and using the following coupon code for a $10 discount: XDASE10-001
Finally, we held a contest back on Thanksgiving asking users to give thanks to their favorite developers. This contest was sponsored by Poweramp (two Nexus 7 tablets) and Meizu (Meizu MX Quad-Core Phone). Rather than the initial two winners, this contest ended up having three winners: Quarx, ::indie::, and srijithn (Meizu MX Quad). Those interested in giving Poweramp a try can do so by visiting their website and Google Play listing. Similarly, those interested in the MX should check out our review.
Thanks to all who entered and to those who made these contests possible. We look forward to having many more contests in the future!
There’s so much stuff happening on XDA that it’s sometimes tough to get a handle on it all. Obviously we have root tools and a bevy of ROMs, along with all the related conversation. However, we also have people discussing specs of upcoming devices, talking about what cases provide the best protection, providing community tech support (in practice shaming online efforts by phone manufacturers), posting screenshots of their home screens, and even just letting loose in our off-topic forum. And for the past several years, some of the most popular forums on XDA have been populated with developers discussing the challenges of building apps and then releasing their creations to the community. This is especially evident by the popularity of our Android Apps and Games forum.
We’re not sure if there are any (other) great communities out there for app developers to converse about things like development tools, prototyping, analytics, monetization, testing, security, localization, education, etc. But we do know that the XDA was missing a central hub for all of that. There is obviously much related discussion spread through several general or OS-specific forums and even in the device-specific app forums. But there has never been an organized set of forums that app developers could call their own to help them be better app developers. Today, we’re changing that with our new set of App Developer Forums.
It’s still early and the forums have generally sparse content, so we’re asking anyone that has something to contribute pertaining to app development (tutorials, guides, tips, etc) to please make some posts in the new forum so that everyone can benefit from you knowledge. If you’re not an app developer (or an aspiring app developer), please do not post in this forum.
About a year and a half ago, we introduced the XDA Job Board to aid both community members looking for new employment opportunities and companies wishing to fill various positions. Unfortunately, however, these efforts have been abused by our robotic forum goers—failing to realize that much like Trix Cereal, jobs listed on XDA are for humans. Despite rumors that resistance is futile, we on the XDA administration team have deemed it necessary to shut the forum down in order to protect against the enemies of the Federation.
OK, OK. April Fools! We’re not actually closing down the XDA Job Board. We’re also not helping you stalk those poor lost souls running inferior OSes, and Jordan’s not leaving us. *PHEW* However, we would like to see more use come of the XDA Job Board.
If you are in Human Resources, or are otherwise recruiting for a legitimate full-time job or large development project, please send me a complete description at jobs (at) xda-developers.com from a valid company email address. We will do our best to validate the job before posting it live.
For those unfamiliar, GitHub is the most popular software repository, and it is used by a large portion of the XDA community for code management. We’ve added the ability for XDA users to add a link to their GitHub page in their profile. Just go to Edit Details in UserCP and add your GitHub username in the field towards the bottom of the page. Then, when someone clicks your name while in the forums, they can check out your work by hitting the link in the drop down. We’re likely to support other repositories in the future.
It is truly great to see that the United States has a rather active Government that worries about its people. Its people have opportunities to speak their mind and make requests to all the branches of this bureaucratic machine, and they are bound to get a response in one shape or another. This seems to be the case for the “little petition that could,” in which over 114,000 people expressed and shared their concerns with the US Government regarding network unlocking of devices legally purchased. This petition received official replies from the White House and the Librarian of Congress, and gained nationwide interest, thus making what many thought would be a silly “nerd rage-filled rant” into a topic of national importance. However, as with most systems, this one is not one without its faults and pitfalls, thus making it quite imperfect.
For the sake of illustration, just imagine that you had a 3 year old silver Civic that was dying and that you wanted a bright red Ferrari. Someone told you that if you worked hard enough and made a certain amount of money within a 2 month period, there would be a chance for you to get your hands on the wonderful beast. Two months later, you had completed your target, got all the money you needed, some people winked at you when you asked if you would get it (raising your hopes in the process). Then, that someone puts a blindfold on you and takes you outside. You proceed to take the blindfold off and upon opening your eyes, you see your 3 year old silver Honda Civic, but with a fixed engine.
Are you happy to have a car? Sure, but to say that you are disappointed would be the understatement of the year. You are simply baffled and trying to pull yourself together in dismay as to what kind of person would lift your hopes high up in such a manner. This was the case for the bill that everyone in the mobile scene was waiting for. Earlier yesterday, US Senator Patrick Leahy (Chairman of the Senate Judiciary Committee) along with several other Senators from both parties announced the drafting of a new bill that they were hoping to pass in the hopes of addressing the issues raised against the Librarian of Congress’ new incarnation of the DMCA. More specifically, the bill, known as the Unlocking Consumer Choice and Wireless Competition Act, was aimed to target the cell phone unlocking debacle as well as the consideration for tablets. At first sight, the law addresses the main concern presented to Congress, but when you sit down and analyze it a bit further, its that fixed up 3 year old Civic.
There are several concerns regarding the wording on the write up like the fact that it will still be up to the carriers to grant you an unlock code while you are on contract. On the flip side, at the very core, the law would reinstate the 2010 exemption that made it legal for people to pursue other “venues” to get their devices unlocked. It still grants a lot of power to the carriers, but at least it does not grant them complete control, which the removal of said exemption was achieving. The problem (the elephant in the room if you will) is the fact that the law fails to address the main, biggest point of this entire ordeal: why is this in the DMCA in the first place? Why are we depending on the (lack of) knowledge of someone who is not an elected official to determine the future of our rights as consumers with products that we legally own? In other words, why is this harbored/lumped with a law SPECIFICALLY made to tackle piracy? Unlocking cell phones has 0, zip, null, nada to do with piracy and/or intellectual property rights. Yet the decision on this will be based solely on the following:
9 upon the recommendation of the Register of Copyrights,
10 who shall consult with the Assistant Secretary for Commu-
11 nications and Information of the Department of Com-
12 merce and report and comment on his or her views in mak-
13 ing such recommendation, shall determine, consistent with
14 the requirements set forth under section 1201(a)(1) of
15 title 17, United States Code, whether to extend the exemp-
16 tion for the class of works described in section
17 201.40(b)(3) of title 37, Code of Federal Regulations, as
18 amended by subsection (a), to include any other category
19 of wireless devices in addition to wireless telephone
So, the Library of Congress needs to hear from, at least, two departments before anything can be done. Again, this is someone making actual law without being part of the overall process and certainly not someone who is chosen, but rather who applied for a job vacancy. Congress had a wonderful opportunity to separate the wheat from the hay and decided to simply apply a fix. Why a fix you ask? The DMCA exemptions and provisions are revised every 3 years. If this long standing provision was taken out without much thought or consideration, who is to say that we will not be here once again 3 years from now? CTIA will certainly still be there much like the little red guy standing on your left shoulder telling you to set your building on fire. They went through great lengths and found a twisted enough argument to sound pseudo-plausible, and 3 years is an eternity in terms of mobile development. So, chances are that we will find ourselves here fighting once again. However, lets assume that we fix it yet again 3 years from now. We will be back in 2019, this time around from within the Matrix and trying to avoid Sentinels.
There are enough experts on the scene to give the people who need the explanation, the best possible and most logical, level-headed argument they will ever get to hear. And best of all, it comes from the people with the people’s interest in mind. I made a small point in my previous article about the Library of Congress’s statement about the general public being consulted prior to amending DMCA. Maybe they should follow their own processes and ask ACTUAL PEOPLE as opposed to corporation conglomerates when the time comes to make law.
It looks like we have gotten quite good at making noise, so maybe we should make one final stance before this band-aid comes to pass. Please share any and all articles with colleagues, media outlets, your Congressmen and Senators, all the people who need to see this in order to make the voices heard. We did our share of work, we expressed our views and told them why things should be different. Please, lets try to push forward so we can finally get rid of that Civic and go for the Ferrari.
You can find the entire proposed law in the following link and the official announcement made by the Senator of Vermont by following this link. Additional links with interesting articles can be found in PublicKnowledge and TechDirt,
Thanks for reading.
[Thanks to OEM Relations Manager jerdog for the tip!]
Around the middle of last year, we realized that in order to best moderate the forums of newer devices, we had to close the forums for a handful of old, legacy devices. We now have a few more forums to add to that list. Just as before, while these forums will be closed for posting, they will still be completely accessible for your read-only viewing pleasure.
Like last time, our criteria for closing forums was post activity. More information on the specific criteria used can be found in our previous announcement. Hopefully by closing these legacy forums, we will allow the site’s moderation teams to focus on XDA’s more active forums, instead of having to worry about cleaning spam in old forums to which very few still contribute.