As more devices come with multiple CPU cores, multi core-friendly CPU tweaking applications and modifications have shown up extensively in recent months. Now, there is an application to control the GPU and both CPU cores on the GSM HTC EVO 3D, as well as modify many other settings.
The application already has a number of features, but it is still under construction. Features that are currently working include:
Full CPU controll(single and dual-core devices)
Changing buttons backlight
Quickly force both cores online
Completly disabling second core
XDA Senior Member pedja1, who created the app, plans to add the following features in future releases.
Settings for ONDEMAND governor
Full quad core support
Apply settings on boot
While some important functionality is missing at this time, users can expect this to be added in future updates. For now, it is still a potentially useful application to tweak various CPU, GPU, and system settings.
For additional info, check out the original thread.
August 4, 2012 By: egzthunder1
So after months and months of waiting, kicking, and screaming from the user base, Sprint has finally decided to provide their EVO 3D customers with a brand spanking new base to play around with. The new official Sprint ROM (base number 2.89.651.2) has been fitted with ICS 4.0.3, Sense 3.6 (as promised), a new radio, HBOOT 1.58, and some new bits and pieces of firmware. As always, this is loaded (and I do mean loaded) with Sprint’s usual bloatware such as Sprint Zone, Nascar, and a few other unremovable (by regular means anyways) bits of Sprint love on the device. After all, nothing screams “we care about our customers” than the bundled Blockbuster app, embedded into the framework with an additional .jar. This rom is an OTA, which means that Sprint is distributing this wirelessly to roms that are capable of receiving the update.
Enough with the formalities about the ROM itself, and lets just go to the core of this article. This is a well known topic as we have covered it before in similar instances. You know, the usual dance where Google announces a new OS, everyone gets excited about promises and ideas and starts looking forward to a reason to hold off on dropping $500-$800 for a new phone (off contract) or for begging the carriers for an early upgrade. Here at XDA, we strive against the inability of the carriers to completely satisfy their customers (us). And because of that, we have had ICS with Sense 3.6 builds for a few months now. Which makes me wonder quite a bit about the entire update. Is it worth having your bootloader relocked just to have to flash buggy software? Yes, buggy software. As it turns out, this new ROM does not have the amount of quality control it should have had for having taken such a monumental amount of time to be released. One such somewhat major bug is Bluetooth, which was either not working or doing so very poorly. Thanks to XDA Forum Member mikeyxda, we now have a fix for this bug. You would think that something like this would have been caught after such a long wait. Lets face it, it was a rather big “opps” considering that Bluetooth is so widely used.
So, what exactly took HTC and Sprint so long? Why did they keep people waiting for this? In previous articles, we had stipulated that perhaps they hold off on upgrades for long enough to not have to explain themselves to the customers as to why they are purposely going against Google’s recommendation about the 18 month promised upgrade. This is not exactly rocket science, albeit you need a good set of skills to whip up a decent ROM. Having said that, developers on XDA probably have far fewer resources than HTC and Sprint, and certainly they don’t have access to most of their “private stuff.” That said, why is it that our site’s devs have the capability to put out better stuff in shorter amounts of time? Oh! I know! HTC has to spend monumental amounts of time and resources because the likes of Sprint and Verizon want them to “protect” the devices and as such, they put in new locked bootloaders so that people cannot fully utilize their devices. How did we arrive at this conclusion? Quite simple actually, we have had Sprint’s ICS with Sense 3.6 leaks on XDA for a few months already. The stock RUU was actually not half bad, and certainly something par to what we see in other stock roms. But aside from the official vs leak factor, there is a major difference between the leak and what we just received from Sprint: a new locked bootloader, which unlike previous bootloader versions, will make your device go on a bootloop if you try to flash the ROM without updating it. In other words, if you want to run Sprint’s latest and greatest, you must update your hboot. Is there any reason to believe that this is necessary for ICS or even for Sense 3.6 to run on the EVO3D? Considering that the leaked build runs perfectly well on ENG HBOOT, I am going to dare say no, there is not.
So, what conclusion do we arrive to from all this? EVO 3D owners just waited for well over a year not for ICS and a somewhat outdated version Sense, but for Sprint’s latest attempt to prevent users from using their devices. So, thank you Sprint for making HTC give us a brand new headache version number 1.58 as opposed to a bug free ICS rom with Sense 4.0. Oh, and just an FYI, Sense 4.0 works fantastically well on our EVO 3D.
Thanks for reading.
Want something published in the Portal? Contact any News Writer.
July 19, 2012 By: Former Writer
Not too long ago, we brought you news that allowed HTC EVO 4G LTE users to customize their bootloaders. The process was pretty cool, allowing users to make their bootloader look however they want—including making it look unhacked. After the initial project was released, users clamored for this to be made available to more devices. The requests were heard and responded to. Now, the plugin has been made available to make the bootloader customizer for a number of HTC devices.
The process for a developer to port this is not hard. XDA Recognized Contributor regaw_leinad, who developed the application and plugin, takes a time out from the stags (yes, that’s really him) to explain how:
it’s basically all written, they just need to fill in the values for their hboot, and embed the hboot.img into the exe. I already have a placeholder for the hboot.img and android-info.txt so a drag and drop over them should keep it embedded.
Regaw_leinad is also creating the application for the supported devices, but wanted to release the plugin first so users had a chance to get it sooner. The current list of supported HTC devices include:
While the list is quite large, one must keep in mind that not all of these devices have S-Off, and users must have S-Off in order to actually use this application. To get started, visit the original thread.
July 13, 2012 By: egzthunder1
If you enjoy gaming in this day and age, you have certainly come across a few FPS (first person shooter) games. In recent times, it seems like the idea of a post-apocalyptic zombie future is prime material for the genre. With this in mind, we now introduce to you Dead Trigger, which for all practical purposes is a game that features you trying to survive against the walking dead. This game was introduced as part of the marketing campaign to further promote Nvidia’s Tegra 3 processor, which is featured in several devices such as the One X, Asus Transformer Infinity, and a few others. The extra punch provided by the GPU enables an ultra-rich and nearly lag-free experience, resembling the closest thing to PC gaming with a mobile phone—or so they would have you (and I) believe.
XDA Forum Member sgaheer posted a link in the EVO 3D section with a work-around to enable the ultimate-rich graphics we described previously for this game. As it turns out, you do not need a Tegra 3 device to enjoy Tegra-specific games in their full glory, but the software is written in such a way that these details are hidden when non-Tegra 3 devices are used. Calling this a shady practice would be an understatement, but I guess that is a rant for a different article, for which we may want to invite Linus Torvalds to share his views.
In any case, the guide itself is relatively simple to follow. You will need to have a rooted device and some sort of file manager capable of gaining access to the root folder (Solid Explorer and ES File Explorer are good and free). Also, you will need to do some minor (and I do mean minor) editing of an .xml file.
It’s quite simple, and there are several reports in the thread that the “hack” works wonderfully well. Please provide your feedback and your game experience on your “unworthy” non-Tegra devices.
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.
The march of Jelly Bean across XDA has reached a fevered pitch since it was first announced at Google I/O 2012. With a number of devices receiving a port of the new version of Android on the rise and more expected in the future now that Jelly Bean source was released, Jelly Bean has certainly hit with a splash. For Samsung Galaxy S II I9100 and HTC EVO 3D users, there isn’t an AOSP version of Jelly Bean yet. However, there is a SDK port users can check out to preview JB.
The Galaxy S II port is a little rough as expected for an alpha release but it does have a number of things working. The list includes:
SD card (internal-only)
MTP (can’t copy files)
SM (courtesy of bpear96)
Network Data (courtesy of stormtroopercs)
logcat (courtesy of edint3000 & bpear96, again)
While the list of things that still need fixed include:
Google Now/Google Search
XDA Senior Member LastStandingDroid is spearheading the effort, but there are a lot of XDA members and developers working on the project. With the hardest part—getting it to boot—out of the way, it’s all a matter of fixing the individual problems until the ROM is stable. It is not ready for daily driver use yet, but a few fixes here and there and it will be.
For the EVO 3D, XDA Senior Member ognimnella is heading up the project which already has a number of contributors, developers, and testers helping out. There are a lot of problems with the ROM. For instance, it doesn’t boot yet. On the initial release, developers could get to a frozen boot animation but not far enough to get a logcat. The logcat problem has been fixed so far, and has allowed the developers to truly begin the process of making everything work. It should be noted that this ROM is for developers only at this point. Users should not flash unless they are looking to help in some way with the development. Nevertheless, Jelly Bean being ported is always good news.
Good news for EVO 3D users. The development team responsible for the EVO 3D Jelly Bean port have released a couple of updates bringing into the world of the living. The new list of things working are:
Bluetooth (turns on)
There’s still quite a few things that don’t work, but it is now stable enough to be considered an alpha release and not a developer-only release!
June 29, 2012 By: Former Writer
The journey of ICS to the HTC EVO 3D has been long and interesting. We brought you news of the first ICS leak, the problems with the ICS leak, and the solution to the problems. The last leak was for the Virgin Mobile-branded device, which ultimately was the cause of many issues. This time, though, it’s legit.
XDA Forum Member AcerExtensa has posted a guide that for users with the German or unbranded versions of the device to obtain the official ICS OTA. What’s more, the OTA has been modified so that users don’t have to upgrade their HBoot, recovery, or radio before updating.
The process is in 3 stages. First, users download the OTA in the form of a flashable update.zip. It is noted that users should use the 4EXT recovery, as that is the only recovery tested so far. Afterwards, users are to download a PG86IMG.zip to flash in the bootloader. This gives users unrooted ICS without losing any of the fun stuff. The last step is flashing root to the device.
It won’t be long until many derivative ROMs are updated with the fresh base, and many options based on this build appear. Here’s hoping the CDMA EVO 3D gets similar treatment soon.
For the download links and instructions, head over to the original thread.
Music and camera modifications have been popping up frequently in recent months. Camera modifications for the HTC Vivid and HTC Sensation, as well as the Samsung Galaxy S II and Galaxy S III have given users over a wide range of phones better cameras. Paired with the many available music modifications, many Android devices are being optimized for better media experiences.
The HTC EVO 3D now has a camera and music mod of its own. Released by XDA Recognized Developer coolexe, the modifications bring features that refresh the aging device’s camera and music experience including:
* For 1.13.652.2_R2 Base.
* HDR, Panorama
* 1250 ISO
* Fast Click
* Sharpness Mod (For Sharp Photos and Videos)
* GPU Effects Mod (Photo/Video Enhancement)
* Front Cam 720p Video Recording
* Front Cam Image Auto-Enhance
Some of the features of the music mod include:
* Buggy HTC Music Fix
* Video/Streaming Mod
–Working SRS, HTC 5.1 and Beats Audio Without Breaking 3D Video
* Audio Mod
–Working SRS, Dolby, EQ and Beats Audio
* Improved SRS Audio (More Bass and Surround) *Only For Wired & BT Headset*
While not everything is working 100% properly yet in either modification, the developer is trying to squelch bugs and add new features. For information on both mods, download links and instructions, go to the original thread for more details.
One of the most common questions here at XDA over the past several months has been, “When will my HTC device receive Ice Cream Sandwich?” Now, thanks to a tip from XDA Senior Member neoofoox we have our answer.
Although we previously mentioned the devices confirmed to get ICS from HTC’s blog back in March, it was only recently that HTC finally confirmed their timeline for this year’s releases. According to HTC:
What is the overall timeline of Android 4.0 updates?
The majority of devices will receive upgrades in June and July 2012 and we expect to finish upgrades in August 2012 for all announced devices.
When will my device get the Android 4.0 upgrade?
The target timeline for announced devices is below. Because of partner and network testing, and approval processes for device updates, it can take up to 45 days for all carriers and countries to get the update after a rollout has begun.
DROID Incredible 2 by HTC To be determined (by the end of August) HTC Amaze 4G May-June HTC Desire S June-July HTC Desire HD July-August HTC EVO 3D June-July HTC EVO 4G+ May-June HTC EVO Design 4G June-July HTC Incredible S June-July HTC Sensation March-June HTC Sensation 4G March-June HTC Sensation XE March-June HTC Sensation XL April-Jun HTC Rezound June-July HTC Rhyme June-July HTC Thunderbolt July-August HTC Velocity 4G March-June HTC Vivid March-June
Please note these dates are targets and may shift due to testing and approvals.
For a detailed look at when your specific device will be getting a taste of frosty Android goodness and several other questions answered, head on over the official page and salivate over your upcoming good fortune.
May 18, 2012 By: Former Writer
As our regular readers will tell you, we’ve been following the HTC EVO 3D closely. Not too long ago, it received an ICS leak and its associated problems. The leak wasn’t for the Sprint or GSM versions of the phone, but rather for the Virgin Mobile version of the phone, which hasn’t even been released yet. As you can imagine, early adopters who flashed the red hot leak had some serious problems—not least of which was being unable to revert back to factory firmware. Fortunately, those days have come to an end.
XDA Senior Member jlechner, with the help of other developers, has released a full method to downgrade the EVO 3D back to its Gingerbread roots. The process is a little complicated, and requires that users know how to flash RUU files in the bootloader as well as ADB commands, so this is definitely not for the faint of heart. Jlechner is kind enough to provide links for all downloads you’ll need. The whole process will take roughly half an hour once everything is in place. However, there is also a stern warning:
This works for some, others are having data issues after. YMMV.
WARNING: Some can’t activate now. Your risk.
So if you’re not confident your device can handle the return to Gingerbread, it’s probably best to skip this for right now. If you really want to revert to the older firmware, you do so at your own risk.
For additional information on what marks the end of the VM ICS leak experience, head on over to the original thread and get downgraded.
May 12, 2012 By: Former Writer
For owners of many HTC device such as the HTC Amaze 4G, EVO 3D, MyTouch 4G Slide, Sensation, and the Vivid/Raider/Velocity, this has been a long time coming. A fully functional method to restore a device from a full brick is a pretty big deal. This then gives users more confidence when performing potentially risky tasks such as HBoot updates, ROM flashes, or turning S On.
XDA Senior Member dexter93, along with a host of other developers, has finally released this project after several months of beta testing and waiting. This is great news for many HTC users who have bricked devices under certain circumstances, and is much better news for users who unintentionally—or even intentionally—brick theirs in the future.
The method is pretty complicated and requires a number of things on the user side. The method also requires the use of a Linux-based computer and the most up to date RUU for your device. Finally, the most important thing, according to dexter93 is as folllows:
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
In other words, this will not work for all kinds of bricks. Rather it will only work for devices bricked by setting S On with an unsigned HBoot or if your HBoot was somehow damaged. While this unfortunately doesn’t help those who may have bricked their devices through other means, it will undoubtedly help many previously helpless users. It should be mentioned, though, that dexter93 and crew are looking to find way to fix other bricks as well.
For all of the information—and there’s quite a bit—as well as download links, screen shots, the full instructions, and discussion, head on over to the appropriate thread to get unbricked:
Whenever a device gets a new leak, some brave soul has to flash it and figure out what works and what doesn’t. In many cases, there isn’t much wrong but often, the software is incomplete and there’s the occasional force close or signal issue. However, on some leaks—especially ones that aren’t really intended for your device—there are more numerous issues.
Those carrying the HTC EVO 3D may have noticed that on Sense 4 leaks, the camera doesn’t exactly work. While camera functionality is commonly lacking in ICS leaks, you don’t have to suffer from for long. XDA Recognized Developer JoelZ9614 has provided a fix that will get the shutterbugs out there back in action.
The fix, which comes packaged in a recovery-flashable update.zip, fixes some (but not all) of the camera problems. Specifically, users can expect their 2D camera and 2D camcorder to work again, but 3D functionality is still down for the time being. Additionally, you get some classic ICS transition animations. However, half a fix is better than having it broken, so users can expect this fix to be incorporated into various ROMs in the near future.
For additional information, check out the original thread.
May 9, 2012 By: pstevep
With Ice Cream Sandwich quickly spreading across Android devices like wildfire right now, new drivers for the Adreno 220 GPU found in the Qualcomm Snapdragon S3 have surfaced. These drivers can potentially lead to improved 2D UI rendering performance in ICS and, of course, increased benchmark scores.
XDA Senior Member gjcamp has produced recovery-flashable update.zip files that work across multiple devices with this hardware. Every phone running the Adreno 220 from the HTC Evo 3D to a couple variants of the Samsung Galaxy S2 may be able to benefit from these drivers, and there are currently seven different devices for which gjcamp has created threads. In his words:
…I have seen dramatically improved result on my Quadrant 3D scores with “Force 2D GPU rendering” UNCHECKED in the Setting->Develop Options Menu of this ICS Release. With this option checked I have seen improvements on both 2D and 3D. Although results are slightly degraded for 3D from post update the 2D results have doubled in value.
I can confirm this myself on my own Evo 3D that Quadrant scores were improved with these new drivers. Similarly, the 2D UI rendering does seem to be smoother, but this is always hard to measure objectively. As anyone who flashes bleeding edge tech to their phone knows, there could be side effects.
You can get started by visiting the threads in their respective sections listed below:
Even if your device isn’t explicitly, the drivers may potentially work on your device, provided that you’re running an Adreno 220 GPU and Android 4.0 Ice Cream Sandwich. However, if your phone’s not on the list, be extra careful and be sure to have a working backup to revert to.