- 5,050,000
REGISTERED - 43,882
ONLINE NOW
April 3, 2012 By: Adam Outler
Heimdall Suite, an Open-Source Cross-Platform set of tools designed to flash firmware to Samsung devices, has received an incremental update to version 1.3.2. This latest update supports Galaxy S II GT-I9100, Galaxy Player, Captivate, Vibrant, Fascinate, Mesmerize, Epic 4G, Galaxy S 4G, Infuse 4G, GT-I9000T, Galaxy Tab (7 and 10.1 inches) and of course the Galaxy S GT-i9000. If your Samsung device is not listed here, testing is required.
Heimdall has always been a favorite among kernel developers and those who frequently flash the latest kernels because no flashable update.zip or Odin packaging is required. A Heimdall user can simply put their device into Download Mode, and click a button to flash a new zImage directly. XDA Recognized Developer Benjamin Dobell‘s latest release improves compatibility with Loke (the flash receiver on the device) and expands comparability to several new devices.
In the words of the developer:
Version 1.3.2 addresses some compatibility issues with several devices i.e. the Galaxy Player 5.0 and Galaxy S II. In particular the “Failed to confirm end of file transfer sequence!” error should no longer occur under regular use. This was fixed by mapping a previously unknown protocol parameter, which I’ve now called “chip identifier”, to information in a device’s PIT file. A big thanks goes out to XDA developers user ambrice, who helped identify the cause of the issue.
Head on over to the original thread , get the source code , and check out the official product page.
March 28, 2012 By: Conan Troutman
A few days ago some users of certain Samsung Galaxy devices began to notice that within the pending updates in the Play Store (that name still feels wrong), was a strange app that they had not installed and the description of which was entirely in Russian. The application was entitled МТС Мобильная Почта, and has since been removed. What’s more, users were unable to actually find this app on their device to uninstall it. Understandably those affected were somewhat concerned about this, fearing that they had fallen victim to some kind of malware. Thankfully it wasn’t, and the MTC application itself is nothing more than an E Mail client for Russia’s Mobile Telecom Systems published by the developers OJSC.
Shortly after the issue was reported, it was discovered that uninstalling certain Samsung specific apps would prevent this MTC application from being listed under “My Apps” or the pending updates.
As identified by the nice folks at The Verge, it turns out that the E Mail application included in stock Samsung firmwares was given the “unique” application name com.seven.Z7—the same unique name as the MTC app. Apparently Seven, who used to develop E Mail services for WinMo but now offer their applications as white labels to third parties, made the mistake of giving the two applications the same name and certificate, thereby confusing the Play Store. Obviously the Samsung Mail client was not listed on Google Play, whereas the MTC app was. This caused many users to see this fictitious update for an app they did not have installed.
Anyone who was affected by this issue should already have seen it resolve itself thanks to action taken by Google, however if for any reason you are still seeing this app then the simplest solution seems to be simply clearing the Google Play’s cache and/or data. There is no longer any need to remove your Samsung specific applications, as the root of the issue is now resolved.
This does of course bring to light a possible hole in the security of the Play Store. Although this has happened before, it was not on such a large or widely reported scale. I would certainly imagine that Google will be looking to make some adjustments and make sure that this kind of error is no longer possible. Although reproducing it with malicious intent would not be easy, as the same unique app identifier and matching certificate would be required. And to be fair to Google, considering that the Samsung Mail client was not actually listed on the Play Store, technically there was no duplication of the unique ID that they could have been aware of. It still seems that there’s room for improvement here though, as Google’s rather lax policy of app screening has repeatedly come under close scrutiny. While they are not at fault here, that wouldn’t really matter if this were a malicious app rather than a simple mix up.
March 20, 2012 By: Joseph Hindy
Hardware mods can be tricky business. Modifying software is one thing, because if it messes up you can always restore that back up that all our rooted readers should have by now. Then it’s back to normal to try something different another day. With hardware mods, though, there’s a much bigger risk because if you mess up it is the end of the line for whatever you’re hardware modding. So, with that in mind, be careful when doing hardware mods because if it gets messed up, that’s the end of the road.
Depressing consequences aside, XDA Recognized Developer TRusselo has posted a way to modify cheap aftermarket rapid AC chargers to perform like OEM Samsung AC chargers do. This would provide users with the full charging capacity of the Samsung branded AC chargers at a cheaper price.
The modification is pretty self explanatory and involves simply bending and connecting a few pins within the charger itself to fool the Samsung Android phone into believing it’s using a real Samsung charger. As TRusselo explains:
The theory behind it is with samsung galaxy phones and “official chargers”:
if the middle 2 data pins on the usb, while getting 5v to the outer 2 pins it tells the phone that it is an *official samsung* charger and enables full speed charging.without the middle 2 pins connected (with or without data flow) will not charge at full speed. even if you supply 800mA it will only charge around 350mA.
This mod fixes that 350mA problem and charges the phone at the full capacity it supports. It is highly recommended that you not try this if it’s your only charger, as breaking it will leave you charging via USB and nobody likes to charge via USB.
For anyone who’s interesting in turning their chargers into Samsung chargers, check out the modification thread for photos of how it works and a complete explanation on how and why it works. Additionally, for those carrying the Samsung Galaxy Nexus, check out your local kernel devs to see if they’ve implemented the force AC charge kernel mod for theoretically similar, but without the hardware modification.
March 16, 2012 By: Ian Stacy
Samsung Epic 4G Touch owners, begin celebrating! XDA Senior Member Calkulin has posted the leaked FC14 4.0.3 firmware, stock and rooted with busybox installed, along with a de-odexed version and the FC14 modem.
The developer warns that users installing the update must flash both the firmware file and the FC14 modem in the same ClockworkMod recovery session because after installation and rebooting you will no longer have CWM recovery. The developer also notes that a factory reset and data wipe is recommended, and he has included a flashable zip that will guarantee all partitions are formatted properly.
Shortly after Calkulin‘s original post, XDA Senior Member qbking77 posted two youtube videos regarding the update—an installation guide and a review of the update. If that sounds like something you’d like to take advantage of, you can check them out here.
All the downloads and information can be found in the original post here. Best of luck to those who attempt to install it!
March 8, 2012 By: Joseph Hindy
Sometimes bad things happen and you don’t even know it. Flashing modules can wreck your WiFi, kernels can bork your camera and, and flashing some ROMs can mess with your EFS folder—and thus your IMEI—on Samsung devices including the popular Galaxy S II I9100.
XDA Forum Member vaskodogamagmail has posted about a method that may help users restore their IMEI if the all-important EFS folder is modified by accident. In a nut shell, restoring your backed up IMEI involves deleting the corrupted EFS folder, creating a new one, and doing a few file modifications with a root-enabled file explorer. In the words of the developer:
so I researched. searched all the forums and didn’t find anything that could cure my phone’s IMEI and set it to the original IMEI number. so I experimented and after some hours, I fixed my IMEI.
one thing that led me to the conclusion that ” .nv_data ” file is the thing that I need to fix the IMEI is that they share a very look alike name, and they have the same 2MB size.
While the guide was written with the Galaxy S II in mind, the method should work on all Samsung devices with EFS folders. Those looking to restore their IMEI should visit the original thread for additional information and the full method. Just be sure to back up your device, including the contents of your EFS folder, before getting started.
March 5, 2012 By: Pulser_G2
After shipping 300 million handsets in 2011, Samsung is arguably the biggest and most important handset manufacturer at present. HTC seeks to challenge this with devices in its new One series, and Samsung is still seen by many to fall behind HTC when it comes to third party development.
While we at XDA don’t tend to cover petitions on the portal, it was felt that this one could potentially result in some major benefits for device users if it gains more traction. The petition came about as a result of XDA Recognized Developer, and CyanogenMod Device Maintainer, Codeworkx, and his detailed post detailing what is holding back traction of custom ROMs on the Samsung Galaxy S2.
It is hoped that this petition will gather enough weight that it can be presented to Samsung Mobile, in the hope of greater future cooperation with third party developers on all their devices. To read more about the petition, and sign it for yourself, click here.
February 19, 2012 By: orb3000
Finally we got to the third and final part of this interesting interview:
If you missed previous parts, you can find them in here for Pt. 1, and here for Pt. 2
orb3000: What would you recommend to anyone interested in entering the
high-level hardware mod world?
AdamOutler: I would recommend getting a hold of some tools and hardware, get
on google and do it!
I’d choose the standard $60 Radio Shack temperature controlled soldering
iron, some breadboards, leds, 1kohm resistors, and a microcontroller. Any
open-hardware development board will teach you how to work with inputs and
outputs. One of my favorite development boards is the Arduino series. Some people may say, “hey, Arduino is not real hardware development, it’s too easy…BlaBlaBla… Whatever, they’re cheap and
work well. let me ask you, if you’re trying to prototype or learn
something, should it be easy or convoluted?. I’ve managed to make several
devices which solve real-world problems using my Arduinos including EMF
detection for locating a source of interference at work and UART processing
for developing Unbrickable Mod.
To really get into digital communications, you’ll want some additional tools
like the Bus Pirate. The Bus Pirate is a universal serial interface used to
communicate with just about anything at low speeds. It’s open-hardware and
known as The Hacker’s Multi-tool.
For troubleshooting and circuit identification, you’ll want something like
the Logic Sniffer. It can record digital highs and lows then display them on your desktop screen where you can run filters and detect logical patterns.
While I’m at it… I don’t think I can hammer this point enough; Use
Open-Hardware.
With Open-Hardware(like OMAP44xx) you can get all the information you need.
With proprietary hardware (like Qualcrapp processors) you have nothing to
work with.
orb3000: Why is your adamoutler.com main site generally down?
AdamOutler: My main webserver is a Texas Instruments EvalBot.
This is a Texas Instruments Development Board with an ARMv3 processor. Its
form-factor is designed to roll around the floor, bounce off walls, turn 90
degrees and keep going. For some reason it came with an Ethernet port, so I
re purposed the device to serve web pages. It does not do a very good job
and it locks up all the time. I could probably use a real web-server instead
of a development board on wheels.
orb3000: Finally, please tell us a bit of the Adam outside the hardware world, what do you do for a living? What is your current device?
AdamOutler: Heh, the funny thing is that what I do for a living is in the
hardware world… I’m an electronics tech. I have been working in
electronics for 13 years. In 1999, I joined the Army as a Radar Repairer
and my job was to keep multi-million dollar Artillery, Rocket and Missile
Radars operational at all costs. I changed jobs to be a Biomedical
Equipment Technician after working with Radars in Iraq.
I’m currently in the Civil Service, but I’m still performing Inspection, PM,
calibration, and rebuilding medical equipment (like infusion pumps, x-rays
and ultrasounds) in a hospital as my daily job. Being a biomed and keeping
things in-line with regulations is a stark contrast to modifying radars.
When I’m at work, non-manufacturer authorized modifications can kill
someone. When I get home and work on mobile devices, I can kinda “let
loose”. The worst that can happen with mobile devices is it breaks. At
work, I could face much worse. 
My current daily phone is an Infuse 4G. My current Dev phone is a Samsung Captivate. My current development tablet is Nook Tablet.
orb3000: Thanks a lot for your time, any final comments you want to make?
AdamOutler: Yes. Since this will be on the XDA Portal and many
manufacturers will see this..
I believe Google chose OMAP4460 because it is the only truly open-hardware
processor available. Open-Hardware means device manufacturers can be
self-sufficient and modders can get the information they need.
Closed-Hardware means it has a relatively short life-cycle.
Samsung: Your Exynos 4210 processor without datasheets is now obsolete
because you chose to keep 1/2 of the datasheets private. I don’t know of a
single person who, with any sort of planning, would say “hey, I want that
processor because of ${Maintainability, Ease of use, Cost Effectiveness}”
All of these qualities are missing when you lock down your datasheets.
Qualcomm: Is there any benefeit to using a Qualcomm processor? Can you
prove it? As far as I can tell, they’re the Celerons of the ARM world.
About the only benefeit to using a Qualcomm processor is integral call
processor. However if the device manufacturers actually cared about the
device and its ability to work through upgrades they would never use
Qualcomm. Here’s a factoid, Qualcomm does not even let the manufacturers
have access to bootloaders. You do realize that the only reason people are
using your chips in their devices is because they think you might know
something they can learn from right?
NVidia: Sure TEGRA extensions are great, but we can’t program them into the
latest versions of Android without knowledge of how they work. You’ve closed
your hardware and thereby stifled development.
Texas Instruments: Good Job! Other processor manufacturers take note. Texas
Instruments is on the rise in the ARM industry because of decisions made by
all other processor manufacturers. We need more Open-Hardware to work with.
BTW… If anyone has access to Samsung Exynos 4210 Chapter 19, entitled
“Boot Sequence” or similar, I need it. The manual I have stops at Chapter
18.
Thats a lot of knowledge!. Hope you all have enjoyed the interview, if so please share it, want someone to be interviewed? Let us know!
Thanks for reading.
February 18, 2012 By: orb3000
Welcome to the second part of the interview with Recognized Developer AdamOutler:
Here you can find the first part in case you missed it.
orb3000: We know you have the longest bash script ever written, what is made for exactly?
AdamOutler: Mythical Librarian was a
project I created over the course of 6 months. At the time, my daughter was
3, could not read and liked TV Shows like Dora the Explorer, Sesame Street
and others. I found a way to make it so she could point to the show she
wanted to watch, with proper naming convention, XBMC could assign pictures
to each episode and she could select which TV Show she wanted to watch. The
idea behind this project was to automate the process of recording a video,
looking up the season and episode numbers, then renaming. Sounds simple
right?
I began with BASHSEXX(Bash SeasonXX, EpisodeXX). It evolved to support
MythTV’s database and was renamed MythSEXX. Eventually it got a small
following, people started reporting bugs, the script was supporting a large
number of functions and databases and was “thinking” on its own, so it was
renamed mythicalLibrarian.
Long story short, it takes a recording, references an online database,
parses, creates a local textual database, looks TVShows up based on
SeriesID, Original Airdate, Show Title and Episode Title, utilizes standard
and fuzzy logic, grades its performance, makes decisions if its going to
redo the lookup at a later time, maintains filesystem symlinks and manages
metadata. It talks to GNOME desktop, XBMC and MythTV. mythicalLibrarian
generates RSS feeds upon each action via Apache web server.
mythicalLibrarian also has the ability to update itself from the latest SVN
or Stable version.
The end result is the user can use XBMC as a better front-end for MythTV.
XBMC uses mythicalLibrarian to get information which downloads cover-art,
fan-art, episode-art, and displays detailed information about the episode,
while MythTV handles disk-space issues and recording.
I believe it’s main portion is now the longest BASH script in existence.
orb3000: Regarding your current projects such as Unsecure boot on the Nook Tablet, running Ubuntu on Nook tablet, Exynos4120 UnBrickable Mod, what is the actual status and what users can expect from those amazing tools?
AdamOutler: While I did put in a lot of research into Unsecure Boot on the
Nook Tablet and even prototyped Nook Tablet ModChips, XDA Junior Member
Bauwks came up with a total software solution. This solution is now the
defacto standard used in all custom Nook Table booting including Ubuntu.
As for Ubuntu booting, there is considerable work going into a Nook Tablet
3.0 Kernel. This is required for proper operation of Ubuntu. The older 2.6
kernel will boot Ubuntu just fine, but there are problems which cannot be
corrected without proper underlying datastructures. The Ubuntu Recovery
system I came up with works well and will recover a dead Nook Tablet from
any known cause of bricking. I will continue this project as soon as I get my hands on a 3.0 kernel.
The Exynos4210 UnBrickable Mod is complete. We are now researching firmware
solutions. I have worked with Rebellos via Internet and it would appear
that the most logical solution would be to simply send it to him. He will
attempt to write new bootloaders and make GS2 UnBrickable Mod a reality.
Believe me, I want this badly as I receive several PMs per week asking about
the status of GS2 UBM.
orb3000: You have opened a thread called Do you want to help out
developers? Got a broken device? How the project is going, and what would
you like to ask/advice the donors?. We would like to take this opportunity
to remind everyone participating to help us to keep thread clean.
AdamOutler: A broken device may be something most people throw away.
However, to myself and others, they are research tools.
I stated devices in which I am interested at the top of the thread. Many members have posted
other devices which they are willing to part with. I would like to
encourage other developers and hardware hackers to take advantage of this
and use it as a resource for their projects.
Expect the third and last part soon. Thanks for reading.
February 17, 2012 By: orb3000
Finally we are back on the XDA Interview series! For those of you too new to XDA, you may find the previous ones in this links: Interview With XDA Developer pof, Interview with User Experience Admin svetius, Interview with XDA forum Admin mikechannon, etc.
This time we will talk with XDA Recognized Developer AdamOutler. It´s hard to find where to start when you have the pleasure to interview such a versatile Developer with so many active projects.
orb3000: Hi Adam, thanks for taking this time to talk. I will start asking how do you started to work in Unbrickable Mod?
AdamOutler: When I switched from iPhone to Android, I had a feeling of
immense freedom. I could do anything I want with an Android! So I did…
I did something and bricked my phone within about 1 hour of owning it.
I searched for ways to recover bricks and JTAG was the only option for my
device. It required soldering 8 tiny wires and purchasing a very expensive
box. I felt that was unacceptable and there should be another way to reload
firmware so I began research and was pulled into the thread Lets save some
bricks. After locating the hardware modification, I called it UnBrickable Mod because I
knew it had potential to make a device totally UnBrickable.
Cool factoid: The B in UnBrickable is always capitalized because it bypasses
Auto-Correct on Android devices.
orb3000: How Unbrickable Mod works?, can you explain us what is all about?
AdamOutler: That is a very broad question… UnBrickable Mod is a hardware
modification which enables USB upload of bootloaders. I think everyone
wants the reassurance that no matter what they flash on their device it can
be recovered. All CORTEX A8 processors have the ability to boot from USB.
Most modern devices support this and at the same time, most manufacturers
tend to lock this ability down. While UnBrickable Mod is technically a
hardware hack/exploit, it functions to increase device maintainability and
thereby increases device value. Personally, I view UnBrickable Mod as the
way devices should come from the factory.
Here’s a video which explains most of it.
(Note to readers, ignore this paragraph if you’re not a geek) While most
devices have a default failover mode to boot from USB, this is ineffective
if the device locks up on a bootloader. Each device has its own unique boot
mode. Most GalaxyS1 devices use a boot code of 0×9(OneNAND>UART>USB). By
modifying the value from 0×9 to 0×29(UART>USB>OneNAND), the device will
reverse its boot order and thereby cause the device to swap its boot mode
from the default boot first from OneNAND to booting first from UART, then
USB, then OneNAND. It’s not always the same value we’re searching for
though.. Each device has its own unique configuration and processor. A
booting code of 0×9 on a Hummingbird processor does not mean the same on any
other processor, nor is it guaranteed that the boot modes can be swapped,
also memory locations are different per processor.
For example, I’ve just finished locating the modification required on the
Exynos4120 GalaxyS2. As far as I can tell, it will not be possible to
simply swap the boot modes. On the Exynos4120, a temporary connection must
be made in order to make the device attempt to boot from an alternate source
and failover into the USB mode. I chose a switch to make this temporary
connection. See XDA-TV GalaxyS2 Unboxing for more.
orb3000: For a regular user sometimes so many tools is kind of confusing, please tell us about the supporting software like UnBrickable Resurrector, ModeDetect, and Heimdall One-Click?
AdamOutler: These tools each serve different purposes. Lets start with
Heimdall One-Click
Heimdall One-Click is a cross-platform, all-dependencies-included, single
executable file, firmware packaging and distribution tool. It is superior
to the Windows-only Odin3. Its purpose is to allow users on Linux, Windows
and Mac to use the exact same file to flash firmware onto their device. The
advantages of using Heimdall One-Click over Odin3:
*Utilzing a much safer flashing method
*Allowing those with Windows, Mac and Linux to flash your firmware
*Increasing user-awareness of what is being flashed
*Packing your firmware into a much easier to use One-Click
*Supporting the work of other Open-Source developers
Heimdall One-Click is based on Heimdall by Benjamin Dobell. Heimdall is
actually safer to use than Odin, and Heimdall One-Click adds 6 points of
safety to standard flashing with Odin. I’ve also created a tool to make
Heimdall One-Clicks from Heimdall Tar.GZ packages.
The UnBrickable Resurrector is the firmware/software component to
UnBrickable Mod.
The UnBrickable Resurrector will tell you when you’ve connected a device
which has been properly modified. It also can recognize several other modes
like ADB, Media Player, Mass Storage and many others. By connecting an
UnBrickable Modded device and clicking the “Download Mode” button, you’re
activating a process of uploading customized bootloaders directly into
specific memory locations where they are executed and perform initialization
tasks designed to put your device into Download Mode or Fastboot Mode. The
Resurrector was created as a team effort by Rebellos and Myself.
I designed the high-level Java app and hardware mod while he designed the
HIBL(Hummingbird Interceptor BootLoader) and modified SBL.
ModeDetect was discontinued. It has been replaced and absorbed by the
UnBrickable Resurrector.
Basically, we’ve got Heimdall One-Click which makes loading software easy
and the UnBrickable Resurrector which gets you to the point where you can
load software. The reason for having them be totally separate entities:
Not everyone needs or can use the Resurrector and not everyone needs or can
use Heimdall One-Click. Although they work together to form a total
recovery system, they are separate in that developers may not need a full
300meg firmware flash to put their device into download mode and test a
kernel, and people flashing firmware would be confused by inoperative
buttons and extra status icons.
In short, UnBrickable Resurrector supports several devices and provides
hard-brick recovery to a soft-bricked state. Heimdall One-Click provides
soft-brick recovery to an operational state.
This brings me to my work-in-progress… Why don’t we have any
cross-platform tools which work with every single Android device out there?
CASUAL (Cross-platform ADB Scripting, Unified Android Loader), like the Unbrickable resurrector, will support several devices. Since it only requires 6 commands, it is intended to be an easy-to-learn, Cross-Platform, light-weight scripting language for deploying binaries over ADB with a Graphical User Interface. If you’re a developer who wants to deploy a new root script over ADB, put out a kernel for multiple devices or install applications via adb, CASUAL will be your
application of choice. It works on Linux, Windows and Mac. A basic script can be created by simply putting all of your binaries into a zip file then typing in a few adb commands without the word “adb” and replace file
references with $ZIPFILEfilename.ext. For example:
[code]
Shell mkdir /data/tmp
push $ZIPFILEzergRush /data/tmp
shell /data/temp/zergRush
remount
push $ZIPFILEzergRush /system/bin
[/code]
The end-user of a CASUAL application will not see the script. They will see
a GUI. User will simply plug in their Android Debug Bridge enabled device,
select the operation from a drop-down box, then click the big button. It
will also provide a great way to easily root an Android Virtual Device from
Linux as well. CASUAL will support every single Operating System and every
single Android Device.
Here we end the first part of the interview, stay tuned for the following two parts.
Thanks for reading.
February 7, 2012 By: Will Verduzco
It’s no secret that ROM development is considerably more cumbersome on Microsoft’s closed source Windows Phone 7 operating system than on its open source competition. Despite the difficulties, developers on our site such as -=Barin=- have made outstanding progress with releases such as a fully functioning kitchen for HTC devices.
Unfortunately, however, this is little consolation for Samsung device owners. The sad reality is that in the fourteen months since the Samsung Focus and Omnia 7 were released, not a single custom ROM has been cooked. However, thanks to hard work by XDA forum members Cotulla and mwang, this is no longer the case. Based off Windows Phone 7.5 Mango build 8107, the Freedom series of ROMs gives first generation Samsung device owners what they’ve wanted from the very beginning.
As with any major OS modification, users should proceed with caution and read all available documentation. Those interested in loading up custom Mango goodness on your Samsung First Generation device should proceed to the Sammy Rainbow thread to get started with the MAGLDR. Once this has been done, fast forward to the Focus Rev1.3, Focus Rev1.4, and Omnia 7 ROM threads.
[Thank you very much to XDA forum moderator Ceesheim for the help and heads up!]
February 4, 2012 By: Joseph Hindy
Thanks to a tip from XDA Senior Member dr.ketan, users of the Samsung Galaxy Note, and presumably other Samsung devices as well, can use a free service from Samsung to remotely track and control their devices from a web browser.
The directions are very simple and present no danger to your device whatsoever. Says dr.ketan:
First Go here
http://samsungdive.com
and register your account(free)
- Now on mobile go to setting-Location n security – Find My mobile
1.check SIM card change alert
2.click on alert msg recipient – Now login with credential, you have register on above mentioned samsung site. – and add recipient mobile number (your other number / family number) on which you will get notification, if SIM will changed.
3.check Remote control
Then upon logging into Samsung’s website for it, you simply click on your device and from there you can do anything from remote wiping the device to making it ring in case you dropped it in your couch and you can’t find it.
The uses are plentiful. For more information, you can check out dr.ketan’s thread where you can also find directions for use and a feature list.
January 12, 2012 By: liwen
This is the MetroPCS Samsung SCH-R920, an LTE Android smartphone that has yet to be released on the carrier. We don’t know much about the R920 except that it will act as the successor to the Galaxy Indulge, which is also known as the Samsung SCH-R910. The R920 is likely to come with Android 2.3, a WVGA screen (around 3.7-4.0″), and a 1GHz single-core CPU with 512MB of RAM.
(Thanks jzelaya)
January 11, 2012 By: Will Verduzco
It’s hardly a secret that here on XDA, we really love it when developers accomplish the impossible. Throughout the forums, this takes the shape of custom kernels that push the boundaries of performance and clocks, apps that accomplish previously unheard of tasks, and—perhaps most importantly—ROM updates for the devices of yesteryear.
Enter the Samsung Galaxy 5—a phone that even upon release, was never destined to be considered a flagship device. And now that this device is approaching two years of age, it seems as if first party support is all but extinct. Thankfully, developers such as XDA forum member subpsyke, have worked hard to keep the Galaxy 5 running modern builds of the platform.
Today, thanks to the hard work of XDA forum member myshu, we have an early Ice Cream Sandwich-flavored build of CyanogenMod 9. While the ROM isn’t quite ready to serve as your daily driver, it’s an excellent step in the right direction.
This is a port of Cyanogen 9 (based on Android 4.0.3 Ice Cream Sandwich) for the Samsung Galaxy 5 I5500 (Europa) phone. The current port status is unstable - NOT SUITABLE FOR DAILY USE.
Special Thanks to: psyke83, squadzone, dhalham, people that helped with hotfixes and rooting and ofcourse all of you for Testing
Working:
- Hardware Acceleration (Some Parts)
- Touchscreen
- WiFi
Broken:
- Telephony
- 3G
- Audio
- GPS
- Sensors
- Bluetooth
- Market
- USB Mounting
- WiFi Hotspot
- Tethering
- JIT is Disabled (So, the ROM is slightly slow)
- Keyboard (Doesn’t appear completely on the Screen)
If you’re interested in giving this a shot on your own Galaxy 5, continue on to the ROM thread. Just be sure to create a nandroid backup before doing so, as you’re going to need to revert in order to actually use your phone as a phone… or anything else, for that matter.
YouTube
Follow
Like
Google+
