- 4,430,900
REGISTERED - 28,493
ONLINE NOW
May 24, 2012 By: PoorCollegeGuy
One of the best parts of Android development is when developers take it upon themselves to find an application they like, and crank it to 11. What started out as a nice experience turns into a much more fun experience thanks to the defining characteristic that makes Android great: Options. So, what happens when a developer picks up an already popular texting app like WhatsApp and gives users even more choice?
XDA Senior Member rafalense has done just this. What started out as a stock WhatsApp experience is brought to life with rafalense’s modified version of the application, called WhatsApp PLUS. While we have brought you heavily themed versions of the stock WhatsApp. This version is different because users have much more control over the theming of the app as opposed to simply installing a pre-themed version. The features, in addition to what is already included in WhatsApp, include:
- ‘PLUS theme’ option added. Change icons and images distribution to make WhatsApp more functional
- Chat Bubbles color now can be changed
- Stock round chat bubbles can be changed to square ones
- Headers color option added too (for Chats, Contacts and Conversation screens)
- Added option to discard annoying update message when opening WhatsApp (for the ones who suffer of it)
- “online”, “typing” and “last seen…” MODs are back
- Added transparency control for bubbles in Chat screen
- Added color mod for status icons in Chat screen (clock, check and double-check icons)
- Now inside Conversation Colors, Header and Chat MODs sepparated for a better comprehension
For more information, visit the original thread.
May 23, 2012 By: Will Verduzco
Not too long ago, we highlighted the launch of FreeYourAndroid. For those who don’t remember, FYA was created by the folks at VillainROM (namely XDA Recognized Developer nprussell and Developer Admin pulser_g2) in the hopes of delivering structured information to help noobs and seasoned veterans alike.
Naturally, FYA has found great success in its mission, amassing a rather large following in the process. And how do they intend on rewarding that following? By having a meetup, of course! As its name implies, the event will be in Glasgow on May 25, 2012. It will run from 3:00 PM to 8:00 PM, local time, and will be held in the Piper on the Square. In the words of VillianROM and FreeYourAndroid community member and event organizer Gary Weldon:
It seems rather strange that the Glasgow Android meetup started out as a chance for 6-8 Android Fans to meet up in the Glasgow City Centre for a few drinks and Android related banter considering where we are now.
Planned from scratch by Gary Weldon (@UbuntuBhoy) and born out of a love for socialising and all things Android, the Android Glasgow meetup is now considered an event which looks to be attended by somewhere between 30 and 50 people.
Now officially hosted by Android websites Free Your Android and Land of Droid, the Glasgow Android Meetup has support from a number of major OEM brands, Mobile Networks and Retailers alike.
Those interested should check out the event’s official website, and follow their Google+ and Twitter pages. While they’re currently at-capacity, you can still stay in the loop by visiting the aforementioned links. For those lucky enough to attend, there will be cool swag given away such as a number of XDA-Developers T-Shirts!
May 23, 2012 By: PoorCollegeGuy
Android users have a lot of options when it comes to weather. The big two, namely the Weather Channel official app and Weatherbug, usually give users what they need. Both apps even have tablet-friendly versions, albeit with mixed reviews. While these two apps are definitely the most popular in the weather app world, there is a new contender looking to make its way into the weather app market. Called Recast, the application provides all the features users enjoy from the others, along with a few fun features the others don’t have.
XDA Forum Member mstroud, one of the members of the Recast team, posted a launch page on XDA for users to check out their new app. Currently, it’s in beta testing, so they’re asking for help from the community to help find bugs so they can squash them before official release. The app itself is quite nice. There is a streamlined interface that displays all the info a user could possibly want, and it’s easy to read and use.
The big draw, however, is in its distribution and customization. Rather than coming in the form of a main app and a less highly-regarded tablet or Google TV app, Recast comes in a single version that is compatible with Android phones, Android tablets, and even Google TV. It’s all compatible with everything, and that’s a big plus for users who have multiple Android devices. Additionally, the Recast team has put some focus into customization—users can choose their weather icons and have a large variety of widgets to select from. In fact, the widgets are even resizable for those running Android 3.1 Honeycomb or newer. The only con? While the app is available world wide, for now the only supported language is English.
For anyone wanting to give the beta a try, hit up the original thread for a full feature list, download link, screen shots, and more.
May 22, 2012 By: PoorCollegeGuy
While the majority of XDA’s community members prefer vanilla-flavored Android, there are those who prefer their mobile OS to have a bit more of a unique touch. While there are always themes and other modifications to help color your experience, some prefer to load derivative OSes that only loosely resemble their Android core. For those, there are aftermarket operating systems such as LewaOS and JoyOS. Bearing striking resemblance to Xiaomi’s MIUI and Meizu’s FlymeOS, these variants could be just what the doctor ordered for those looking for a unique experience.
XDA Recognized Contributor blindndumb has released a guide that walks users through turning CM7 into Lewa or Joy in a process that, despite it’s many lines of code changing, really isn’t all that difficult. The process involves using tools that are easily available such as your favorite zip program, Notepad++, and ADB. It is essentially a crash course in porting, except all the steps have already been figured out. The guide runs through changing various lines of code in certain files, and replacing folders with stuff from the Lewa and Joy base ROMs.
While somewhat tedious for those not accustomed to working with code, the process for porting both OSes is very simple. Additionally, sometime in the near future, the guide will be expanded to support even more OSes. As always, make a backup in your favorite custom recovery before flashing one of your creations.
To get started with your porting efforts, visit the original thread.
May 22, 2012 By: FallenWriter
Earlier, we reported that the S Voice application that was ripped from the Samsung Galaxy SIII leak had stopped functioning. Now though, in what appears to be the final chapter of the S Voice saga, the application is back up and running, XDA-Developers style thanks to XDA Senior Member ithehappy.
Apparently the original application had a build.prop check that caused the unsigned version that was leaked to fail. Rather than griping to Samsung about the problem, ithehappy took it upon himself to fix the problem with his latest signed version here. By signing the application, it’s fooled into thinking that your phone is a Galaxy S3, so non-SGS3 users can once again use their Siri clone voice command application in peace.
Head on over to the original thread, and check out all the other i9300 goodies that ithehappy has in store.
May 22, 2012 By: egzthunder1
If you own an HTC device, you may recall that one of the hardest things to bypass is the locked bootloader. Sure, you can unlock it by using the HTCDev web service that HTC offers for its customers. This essentially allows you to flash unsigned code such as ROMs and kernels onto these devices. But since the S-ON flag is still up, you are severely restricted as to what you can flash on your device. What if you just want to do more? Lets say that you want to roll back the latest radio upgrade that you applied because battery life was negatively impacted. The problem comes in the fact that in order to flash a radio while you have a semi-locked bootloader (with S-ON), you would need to flash the stock RUU that contains the radio in question, then flash back or Nandroid restore what you had before going back to stock. Problematic, right?
Recently, we have been covering the discoveries and developments that have allowed most HTC devices to achieve S-OFF by means of smart hacking. One of the only remaining devices to be left with S-ON was the Sensation XL, a.k.a. Runnymeade. Since it was not really fair for this to be the case, XDA Forum Member fardjad decided to try his luck at unlocking the device entirely. Needless to say, he was successful in this. Much unlike some of its predecessors, the method here does not seem to involve anything other than a Windows PC, a few files, and the corresponding drivers for the device. Please note that originally this was believed to bypass CID checking by the device, but according to a few reports this does not seem to be the case, so please tread carefully.
Please leave some feedback for the dev to try and iron any bugs that may be present.
The following have been tested and working:
erase (system, recovery, boot)
flash (zip, system, recovery, boot, hboot, radio)
boot
It also by passes the CID check.. (See these posts: #26,
#27, #31, #38, and #60)
…and here is the flash ZIP, HBOOT, and Recovery demo:
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.
May 21, 2012 By: FallenWriter
As many of our readers are aware, the much lauded Samsung S-Voice application from the Samsung Galaxy S III was ripped two days ago and made available for the world (and most of XDA) to ravenously consume. Many users today, however, are reporting that the application is no longer functioning.
When the app is opened and a command issued, the application comes back with, “Network error. Please try again.” Users across several device forums have confirmed this error as well. At the time of this writing the issue is still occuring on this writer’s Samsung Galaxy Nexus.
One can only wonder if this is intentional on the part of Samsung or if they are simply encountering technical difficulties. If any of you are not experiencing the issue, please sound off in the comments section below.
May 21, 2012 By: AdamOutler
Historically, the officially sanctioned Nexus line has come from just one manufacturer. While the manufacturer has changed through the passing iterations, there has never been more than one for any particular generation.According to a recent report by the Wall Street Journal, Google plans to allow 5 manufacturer the ability to produce the Nexus development platform.
Google plans to give multiple mobile-device makers early access to new releases of Android and to sell those devices directly to consumers, said people familiar with the matter. That is a shift from Google’s previous practice, when it joined with with only one hardware maker at a time to produce “lead devices,” before releasing the software to other device makers. Those lead devices were then sold to consumers through wireless carriers or retailers.
Not all manufacturer’s devices are created equal. There are several characteristic traits that each manufacturer places on a device’s hardware. HTC notoriously places non-standard screws on their devices and makes their devices out of metal. Samsung makes highly servicable devices out of plastic with on-board crumple-zones. Motorola makes it easy to get into the device, but solders down shields over each component.
How can it be logical to have 5 different manufacturers, each with their own idea as to what makes the ideal device, make the official Google Nexus Android Development Platform? While at first it makes no logical sense to have 5 totally different devices bear the name “Nexus,” there may be some technical reasoning behind this seemingly irrational move.
One idea is that having 5 separate manufacturers provide 5 similar devices is an attempt to gain control over the carriers. Having several manufacturers provide similar products will flood the market and strong-arm carriers into carrying Nexus device as well as foster a bloatware-unfriendly environment.
However, there has been no official news that these Nexus devices would be phones. Google is on the verge of launching a line of tablets, which is rumored to be in a competitive price-range with the Kindle Fire. This would provide a pure Android experience out-of-box at a reasonable price for the every-day user. Considering this news, it is entirely possible that the 5 Nexus devices could be entirely separate pieces of hardware, including a possible lineup of phone, tablet, TV, wrist-watch, set-top box, laptop, car-stereo, head-gear, and perhaps even something entirely different.
One glaring problem stands out among all of the speculation and rumors—the Android Source tree. The pure logistics of supporting 5 devices with entirely different characteristics seems like a substantial issue. How could AOSP support so many separate devices?
If Android entirely skips the Linux 3.1, 3.2 and 3.3 kernels, several benefits await. The Linux 3.3 developmental kernel had several additions that incorporated Android into the heart of Linux. One of the biggest changes in the Linux 3.3 development cycle was the integration of key Android components, which bring the Android kernel into the Linux mainline.
While the old scheme of odd-numbered releases not being intended for daily use is no longer the case; Several issues, including power-managment made the 3.3 kernel non-viable for use as a replacement for the current 3.0 Android kernel. We now stand on the verge of the 3.4 stable release kernel, which has been prepared to split Android and Linux. The vanilla 3.4 mainline Linux kernel will be interchangable between devices that support it. This brings the burden of maintaining Linux to the front doors of each hardware manufacturer. In other words, if Qualcomm wants their processors to run Android, they must support Linux development and not just Android development.
With this in mind, it is entirely possible that there may be 5 Nexus phones made by 5 separate manufactures. However, no reports stated they would be phones,which means we may have to change our ideas about what exactly constitutes a Nexus?
Sources: XDA-Developers Forum, Wall Street Journal, Linux via Google+, Engadget
May 21, 2012 By: mustangtim49
Recently, we voiced our opinion lambasting Apple and their substitution of litigation in place of innovation. However, it appears as if Apple isn’t the only company trying to prevent others from releasing their products to the public. Motorola was dealt a decisive blow by the International Trade Commission on Friday. The Commission banned the import into the U.S. of 18 Motorola devices running Android. This ban includes Motoblur and Google Experience devices.
This decision comes via a 2010 complaint filed by Microsoft claiming that Motorola was in violation of nine of it’s patents. Of Course, Motorola was quick to comment that they would not be immediately affected by the decision due to a 60-day presidential review period. During this period, Motorola can continue imports albeit with a 33 cent fee per unit. The company was quoted as saying in a public statement they were “disappointed,” and that they “will explore all options including appeal.” At this point, Motorola will either have to alter it’s software or come to a licensing agreement with Microsoft in compliance with this ban. The latter seems more likely, given that a majority of manufacturers of Android devices already have licensing contracts with Microsoft.
Those looking to learn more should visit the discussion thread and the LA Times article.
May 20, 2012 By: PoorCollegeGuy
It’s almost assumed that when the stock firmware is released for a highly anticipated device, developers will jump through hoops to make it work for their devices. As is the case with the Samsung Galaxy S III firmware, which was leaked yesterday. Developers have been getting their hands on it to give the users of their phone some SGS III love. Of course, it is assumed that the first thing to start making its rounds around the forum would be Samsung’s S Voice.
Originally posted for the International Galaxy Note by XDA Senior Member Zanr Zij, which showed that S Voice worked on the Note and probably many other Samsung Galaxy S devices, the S Voice has begun slowly making its way from device to device as users figure out whether or not it works for them.
Fortunately, XDA Senior Member dolcedavinci was brave enough to give it a shot and found out that the proprietary Samsung app actually does work on the HTC One S. And of course, this means that it doesn’t require any Samusng-specific framework and will likely work on many, many other devices as well. Installation is simple, just install the apk and give it a whirl.
For additional information, check out the Galaxy Note thread where you’ll find the download link to the apk for S Voice. You can also check out the One S thread to see it working for the HTC phone. Since you can just install the app like any other apk, and thus uninstall it easily, there’s no risk in trying this for yourself on your own device!
May 20, 2012 By: mustangtim49
XDA Forum Member necro_ may be new to Android development, but don’t be fooled by this inexperience—he is a professional software engineer with experience in Symbian OS and Windows development. After rooting his first Android phone less than a month ago, he found the whole process, in his words, to be a “pain in the asre.” Surprised with no easy solution for creating or editing YAFFS2 images, he set out to remedy this.
Necro_ started to working with the unyaffs code, and put together a GUI app that listed an images contents. Once he got that working, he kept developing to allow for extracting files and then creating images. The fruits of his labor is Yaffey—a GUI utility for reading, editing, and creating YAFFS2 images in Windows written in Qt 4.8.1. The utility is still very young, but necro_ hopes that others will find it to be a useful utility. He hopes to get feedback from users such as feature requests and bug reports to help him better his utility.
If this is just the tool you have been looking for, head over to the original thread and its Google Code page.
May 20, 2012 By: PoorCollegeGuy
Most users load an AOSP ROM to get away from the OEM experience. Many users who like HTC, Samsung, Motorola, and LG hardware sometimes do not like the software that comes with them. HTC Sense has always been a little too bloated, and some have even considered TouchWiz bloatware from the start. Due to these common complaints, users often end up flashing AOSP ROMs like AOKP or CyanogenMod to free their phones and run vanilla Android. However, many users would be remiss if they didn’t admit that there’s always those one or two features that they loved about the OEM Android skins, and wouldn’t really mind having back.
It is with that in mind that the OpenDESIGN project was created. Posted to XDA by Recognized Developer XpLoDWilD, the project has a number of developers working on it. The point? To bring OEM features to AOSP ROMs so users can have even more options for customization, and make their Android experience truly their own. As XpLoDWilD explains:
Our goal is to have features coming from various manufacturers’ layers seamlessly integrated into your phone, as if it was always part of Android Ice Cream Sandwich. Why is it cool? All CyanogenMod 9 enabled devices can profit it and enjoy features that would need -according to manufacturers- a brand new $600-phone. I’m not so sure about that.
The project is still in the development stage, so users could be waiting a little bit before things begin to roll out. However, there are dozens of fun features being worked on that will be integrated with at least CyanogenMod 9, as if it were supposed to be part of the phone. For project updates and more details, head on over to the original thread. Also, any developers who want to get involved, feel free to hit up the thread and ask if you can be of help.
[Thanks to XDA Recgonized Developers DooMLoRD and cdesai, and XDA Senior Member peterperfect for the tip!]
May 19, 2012 By: PoorCollegeGuy
Recently, we talked about the Google Play Music deauthorization issue. For those who aren’t aware, users of Google Music signed in randomly one day and could no longer deauthorize accounts on their Google Music. While this wouldn’t be a big deal for most unrooted users, for root users—and especially flashaholics like yours truly—this is was a pretty big deal, as users were finding that with every new ROM flash, Google would add a device to the authorization list. Once full, users used to be able to deauthorize the duplicate or unneeded devices. However, Google limited deathorization, much to the dismay of its active root users.
Much like Facebook a few weeks ago, Google realized that they upset many users and have since eased up on device deauthorization. This allows rooted users to use Google Music as they had before this policy took affect. While it’s not exactly clear why Google suddenly dropped the new policy after taking the time to explain it to so many angry users, one can only assume it was prompted by massive amounts of music disappearing from their servers and a whole bunch of angry yet-to-be-answered emails. In any case, this short, yet frustrating time in all our lives is over and Google has, presumably, learned its lesson.
Now, if only Motorola would learn from Google, then there’d be some real progress. For now, though, baby steps.
For anyone who wants to check out the discussion of the matter, head on over to the discussion thread.
[Thanks to XDA Senior Member bfspider and Google Plus user James Mason for the heads up!]
YouTube
Follow
Like
Google+
