January 3, 2012 By: Joseph Hindy
One of the biggest pains of playing video games on a non-console platform is configuring your controller to work properly. Making sure everything works in every environment, testing and re-testing until everything seems right.
Well, if you’re a Sixaxis controller user and you play GTA III, then this is a pain you won’t need pills to fix. XDA Senior Member Jameslepable has taken the trouble to figure out the most optimal button configuration and has created a tutorial to help those who are having trouble doing it.
The instructions for use are relatively simple and noob friendly, so it doesn’t take a great deal of knowledge to get his configuration to work. His instructions:
1)Download sixaxis and GTA3 from market place (obviously)
2)Download profile from bottom of post.
3) From GTA3 menu go to options>controls>adjust on foot controls/adjust driving controls and make them look like the screenshot.
4)Then go to sixaxis controller settings>edit touch profiles>Load Profile>gta3 vx.x and ensure that they match the screenshots.
The file he mentions can be found, along with the screenshots needed, further instructions and the button mapping list in the original thread. So far, it’s confirmed working on the Samsung Galaxy Nexus since that’s where it’s posted, but the directions seem pretty universal and could possibly be used on other devices as well if they’re compatible with GTA III and Sixaxis.
Now, as Jameslepable puts it,
Go shoot some hookers!
December 27, 2011 By: Joseph Hindy
The port is working pretty well, with a very short list of things not working so far and it’s still, as fuss132 puts it,
like 70% CM7 and 30% MIUI.
So it’s not a pure MIUI release just yet and it is still in the testing stage. If you happen to check it out, the known issues are:
GPS not working
Sometimes Kernel anic (Just remove Battery and reboot)
Some Miui Apps not working: Miui Stats, Miui Settings (so CM7 Settings included)
Video recording with Camera in very bad quality
And, of course, here’s your list of things that does currently work:
HW Acc + GPU Support
Of course Touchscreen
MIUI Apps: Miui Notes, Miui Music, Miui Contacts, Miui Phone, Miui Talk, Miui Browser, Miui Camera
Miui Lockscreen (Please activate it in your Device´s Settings)
So if you’re up for a little MIUI fun and you happen to own Samsung Galaxy SL i9003, then you can check out the original thread for additional information and installation instructions. If you’ve tried it and want to chime in to let us know how it’s working, feel free to do so!
December 14, the deadline Senator Al Franken gave to answer his questions about Carrier IQ, came and went. Now the responses are public. Franken also questioned FBI director Robert Mueller in the Senate Judiciary Committee about the FBI’s collection of information specifically obtained from Carrier IQ’s software. Thankfully, Franken was not satisfied by the answers he received in either inquiry. From Franken’s press release, which includes companies’ responses,
“I appreciate the responses I received, but I’m still very troubled by what’s going on,” said Sen. Franken. “People have a fundamental right to control their private information. After reading the companies’ responses, I’m still concerned that this right is not being respected. The average user of any device equipped with Carrier IQ software has no way of knowing that this software is running, what information it is getting, and who it is giving it to—and that’s a problem.”
There’s a big problem of specificity in how the media reported Trevor Eckhart’s (XDA Recognized Developer, TrevE’s) research. And now, anyone who wants the issue minimized is exploiting that lack of specification of what people mean when they say “Carrier IQ” to avoid saying anything damning. For example, look for the clarity in Mueller’s initial response, where the FBI “neither sought nor obtained any information from Carrier IQ”–the company–in this video:
When Franken pressed on, trying to clarify the question, it was abundantly obvious how unpracticed Mueller was at using “Carrier IQ“ to mean the software. Of course, the assertion that the FBI never sought information from Carrier IQ, the company, isn’t true. Andrew Coward, Carrier IQ’s VP of Marketing, told The Associated Press that the FBI is the only law enforcement agency to contact them for data. It’s a discrepancy that will probably be excused by the semantic ambiguities of “sought”.
The EFF posted an article about the lack of clarity in reporting about Carrier IQ, identifying four different meanings of “Carrier IQ”. It should be standard reading for anyone making inquiries into the Carrier IQ issue. I personally feel that Carrier IQ themselves are responsible for much of the confusion. Instead of giving words like “IQ Agent”, which is their software’s name, they gave words like “metrics” and “profile”, which require a working understanding of their software. Eyes glaze over as people read technical explanations, and they give up, deciding to just say, “Carrier IQ”.
Responsibility is perpetually deferred using this ambiguity. Carrier IQ says the data belongs to the carriers. The carriers have the software installed by the manufacturers. The manufacturers say they’re simply following instructions from the carriers. The carriers say the data is aggregated by Carrier IQ. Carrier IQ says they send the data to the carriers. Nobody shares the information with anyone else. And the FBI never sought or obtained information from Carrier IQ. Except they did. And they didn’t. Maybe.
Examine Sprint’s response to Franken’s seventh question, “Has your company disclosed this data to federal or state law enforcement?”
Sprint has not disclosed Carrier IQ data to federal or state law enforcement.
The ambiguity even here is dangerous. Does this response mean they don’t share data collected by the software on individual phones? Does it mean they don’t share the aggregated data from Carrier IQ, the company? Does it mean they don’t share the kind of data collected by IQ Agent? Does it mean they don’t tell law enforcement what they know about Carrier IQ, the company?
Franken has every reason to be dissatisfied with these answers. I implore members of the media and their readers to do their part in clarifying the issue in their articles, and by demanding clarifications in their interviews.
Chainfire’s abilities know no bounds. The XDA Moderator and Recognized Developer now presents Mobile ODIN, allowing you to flash firmware from your device, itself. That’s right, you no longer need to connect your device to your computer.
All right, that’s not perfectly true–Mobile ODIN currently cannot flash PIT, bootloader, or EFS partitions. You still need your computer for those. For now. But if you want to flash a new kernel, system, DBData, data, cache, parameter, or modem partition, Mobile ODIN can do that. As the developer says,
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
Mobile ODIN Lite is exclusively available on XDA. You can find the pro version on the Android Market. Now, Mobile ODIN Pro has a few extra perks that the regular, old ODIN doesn’t have. For example, Chainfire includes EverRoot–an option that roots your ROM as you flash it. With that, you can also automatically flash Superuser, and Mobile ODIN itself, so you’re all ready to flash again when you reboot your new ROM.
Not every device is compatible. But Chainfire made eight new devices compatible in the second update, and he says he’s willing to work with Samsung phones. If you install the app on an incompatible device, the app will let you create a dump file, which you can post in the app’s thread. If you can, also post a PIT file for your device. Lastly, the developer says, he needs a kernel running ClockworkMod5, though it might work with CWM3 or 4.
To see if your device is compatible–or if there are plans for compatibility–and try it out, please carefully read the source thread.
XDA Recognized Developer pedrodh recently identified an exploit in Samsung devices running AccuWeather, and developed an app for demonstration. The app can poll your location without granting any permissions–not even Superuser permissions–using two lines of code.
As a system app, AccuWeather is automatically granted access to your GPS settings. There are two ways to avoid giving away your location. Under the AccuWeather settings you can set your location manually. The developer recommends some remote village in China. Unless, of course, you live in a remote Chinese village. The second way is to gain root access to your Samsung device and remove the widget entirely.
The developer provides those two lines of code if you want to create your own app, or you can use his. Hopefully this demonstration is enough to alert less enthusiastic Samsung users to where they are vulnerable.
Originally posted by pedrodh
The problem is even more serious than I first though, because you only need to have the widget on the launcher once, and that info will remain in the system informations when you remote it from the launcher, even across reboots or even if you clear the widget’s data and cache (pretty scary :S). Sometimes (I don’t know why exactly yet) the info goes away for good, but only if you don’t have this widget on your launcher!
Please see the development thread for more information.
October 6, 2011 By: egzthunder1
Over the last few months, you have likely seen a hard push by manufacturers in attempts to try and get closer to developer communities like ours. The effect that we have on their product sales is strong enough to create a tough situation for any company that decides to ignore this part of their consumer base. The best examples that you can see would be number of devices and users of Samsung and HTC products as compared to other brands that are not as developer friendly like Motorola and Sony. The effect is not a coincidence as our intervention in their “world” is not destructive but rather constructive and some companies decide to take advantage of this constructive criticism, which in turn makes their products better and more popular, increasing their sales in the process.
One such company is Samsung. A few months back, you can likely recall a xda user by the name of SamsungJohn who had what some would consider a “firery” entrance and exit from the xda scene. The original idea, unfortunately never worked out in the way it was expected with Samsung trying to establish a stronger presence on xda. However, over the last few months, we have been working together with John on a very interesting project that will likely help xda (and the Android community as a whole) to be closer and thus have the ability to get more stuff done that will ultimately benefit all of us, as we will get better quality products that will ultimately work out 100% of the box. As an added bonus, as we see a bigger push towards developers, we may see more openness in the platform as well.
John has been instrumental in the organization of an upcoming conference that was just announced via his Twitter account. Samsung Developer Conference or “DevCon” will be taking place in San Francisco one month from now on November 8th. The best part is that xda will participate in the event as a sponsor as well as being active in a few special activities of this mega event. If this wasn’t interesting enough, Samsung will invite 3 people from xda-developers to the conference. XDA User Experience Administrator svetius will be hand picking the people who will attend to this event, but it isn’t really fixed as to who will go at the moment. However, svetius could potentially choose anyone.
Here is the official announcement by SamsungJohn
Hello XDA’ers, I haven’t forgotten about you. In fact, I want to invite three of you guys for free to our very own conference…SA
MSUNG DEVCON!” Soon, Svetius will be selecting the three lucky people who will attend.
“The Journey Has Already Begun” – Converging TV, tablet computers, and mobile phones to create a “take anywhere” digital world for customers.
Time: Tuesday, November 8 8:00AM-8:00PM
[B]More big announcements to come [/B]
Follow me on Twitter: [URL="http://twitter.
com/#!/samsungj"]@SamsungJohn[ ohn /URL]
Special thanks to: Captainkrtek & Egzthunder1
Well, folks… there you have it! xda-developers will attend and will participate. The question is, will you?
John will be keeping this thread up to date for you to have the latest information available as well as having up to the minute updates via his Twitter.
Want something published in the Portal? Contact any News Writer.
A bricked phone. No JTAG. Modify hardware, upload a bootloader, and the phone lives. Pure development.
That’s what I think of the work of AdamOutler and Rebellos to breathe life into dead devices. A couple days ago, WillVerduzco wrote an article on Rebellos’ method of unbricking Hummingbird devices by uploading your very own custom bootloader to your device. A couple weeks ago, AdamOutler asked for help getting the official Samsung bootloader for Galaxy devices. Since then, the two teamed up to put Rebellos’ Resurrection Bootloader on devices modified according to AdamOutler’s UnBrickable Mod.
Now they’re finding the fun doesn’t stop at unbricking phones. They’re flashing bootloaders built for other operating systems. ”I used UnBrickable mod to install Bada OS bootloaders on my Captivate,” AdamOutler says. ”Totally bricked it. Messed up partition tables and everything. It assimilated my Captivate. I used UnBrickable mod to load up a secondary bootloader while holding the key combination, then flashed it.” He goes on, “I was worried for a bit because it would not download, but eventually we got it! It works!”
This means the months of hard work put into this project finally paid off. AdamOutler working on hardware, Rebellos working on software. Once the hardware side of development finished, Rebellos stepped in. ”You see,” AdamOutler says, “Rebellos is a developer working on a port of Android for Bada OS. He’s 18 years old, from Poland, just got his driver’s license, and he’s a badass behind the assembly language console.”
Samsung Galaxy devices normally boot using a primary bootloader to load a secondary bootloader that, in turn, loads the Linux kernel. Rebellos replaced the primary bootloader. That means they should be able to load non-Linux systems, like Windows Phone 7 or iOS. Rebellos says that will take, “tons of work in pure assembler, as they aren’t opensource.” He adds, “I’d say for SGS family you can count on Bada and any opensource OS, like Ubuntu.”
To put it clearly, the work these developers put into this project means the beginning of HD2-like development on any device with a CORTEX-A8 processor in it, including the iPhone 4 and Nexus S. And that’s exactly what AdamOutler and Rebellos plan to do. ”We basically created a whole new system for developers to use for developing and noobs to use for unbricking after playing with the big kids.” Pure development.
The developers are currently looking for bricked and broken CORTEX-A8 phone donations, such as these:
Samsung I9000 SGS
Samsung S8500 Wave
Samsung S8530 Wave II
Samsung SGH-i997 Infuse 4G
Samsung T959 Vibrant
Samsung SGH-T849 Galaxy Tab 7.0 inch
Samsung GT-P1000 Galaxy Tab
Samsung GT-i9010 Girogio Armani Galaxy
Samsung GT-i8350 Omnia 7
Google Nexus S
If you would like to help out with this historical work, please see the development thread.