Posts Tagged Unofficial

How to Install Unofficial CyanogenMod 10.1 on LG Optimus Me P350

440x330-lg-optimus-me

XDA Developers recently released the unofficial CyanogenMod 10.1 Android 4.2.1 Jelly Bean custom ROM for LG Optimus Me P350. While this could put owners to excitement, they should know that this is still a very early build and it has been released for testing purposes.

PecanCM, a senior member of XDA Developers forums, said in his thread that this is an Alpha release (3rd alpha release, actually), thus, there may still be a lot of features that don’t work. But the thing is, we know that someone is working on CM 10.1 Jelly Bean for Optimus Me P350. Perhaps, a week or two from now, the official build will be released.

Owners who wish flash this CM 10.1 mod into their devices should do it at their own risks; every tool and mod needed for this process is now available for download. But just so you know before you take the first step, there are a few things not working even after a successful flashing and Bluetooth is one of them. If that does not stop you, then continue with the step-by-step guide below.

Requirements 

  1. Fully charge your device if possible but if you have at least 75% battery, you can continue with the process.
  2. Make a backup of all your data just in case things go wrong during the update process.
  3. Enable USB Debugging.
  4. Disable antivirus and other security suites because sometimes they intervene with the process.
  5. Make sure your device is rooted and that you have installed either ClockworkMod 5 or ClockworkMod 6.
  6. Download this package as you will definitely be needing this: cm-10.1-20121221-UNOFFICIAL-p350.zip
  7. You also need to download Google Apps.

Step-by-Step Guide 

Step 1: Connect your device to your computer via USB cable and copy the unofficial CM 10.1 Jelly Bean package into your phone’s internal memory. But make sure you save it in the root directory because that’s what CWM Recovery can detect.

Step 2: You may now disconnect your device from your computer and boot it into ClockworkMod Recovery mode. You can do so by pressing and holding Power, Volume Down and Call buttons together. If your phone boots normally, try doing this step all over again.

Step 3: Perform a full data wipe and choose “flash zip from SD card.” Remember to confirm your every action.

Step 4: Now select “choose zip from sdcard” and browse through the directory in your device’s internal memory where you saved the package a while back and confirm your action. You also need to do this step for Google Apps only that you have to choose a different package.

Step 5: The final step would be to reboot your device and wait until the home screen shows and that’s it!

For this build, you may be able to encounter bugs every now and then. But know that the people behind this mod is doing all they can to make things better.

Credits go to XDA Developers and CyanogenMod team for releasing and making this build public.

[source: XDA]

, , , , , , , , , , , , ,

No Comments

Unofficial Samsung Galaxy S III WiFi roaming fix now available

Owners of some Android devices, in particular the Samsung Galaxy S III and Galaxy Nexus, may have noticed a bug that causes their device to have trouble transitioning between different WiFi access points when access points overlap. XDA Forum member felixchris has put together a hack that addresses one of three possible ways the bug manifests itself. According to felixchris, the three ways that users may experience the bug include:

  • Bug version 1: when connected to an access point (e.g. SSID_A), as you move to the area covered by a second access point (e.g. SSID_B), the phone never releases from the first point even though the signal gets very weak and the higher strength SSID_B is available. This particular version of the budget can be verified by turning off WiFi, then turning it back on again, at which point the device should associate with the second access point.
  • Bug version 2: very similar to version 1, but even after restarting WiFi, the phone still insists on connecting to the first access point, SSID_A.
  • Bug version 3: when connected to the first access point, SSID_A, as you move to the second access point, the signal strength seems to increase as the device searches for a stronger access point, but then drops the connection and after a short hiatus, re-establishes the connection. The easiest way to observe this is by the disappearance of the WiFi icon and an interruption in the connection.

Bug version 3 is the one for which felixchris has created a workaround. The fix is confirmed to work on Samsung Galaxy i9300 models and the Samsung Galaxy Nexus i9250. A couple different versions of the mod have been developed, one that requires a custom recovery and one that does not. However, both solutions require root access to the device.

If you are having trouble with your WiFi connection when moving between overlapping access points and you have one of the specified devices, you may want to give the fix a try by visiting the source link below. Just be sure to read the warnings and cautions related to rooting your device or flashing files.

source: XDA Forum WiFi Roaming Fix

, , , , , , , , , , , ,

No Comments

Unofficial Samsung Galaxy S III WiFi roaming fix now available

Owners of some Android devices, in particular the Samsung Galaxy S III and Galaxy Nexus, may have noticed a bug that causes their device to have trouble transitioning between different WiFi access points when access points overlap. XDA Forum member felixchris has put together a hack that addresses one of three possible ways the bug manifests itself. According to felixchris, the three ways that users may experience the bug include:

  • Bug version 1: when connected to an access point (e.g. SSID_A), as you move to the area covered by a second access point (e.g. SSID_B), the phone never releases from the first point even though the signal gets very weak and the higher strength SSID_B is available. This particular version of the budget can be verified by turning off WiFi, then turning it back on again, at which point the device should associate with the second access point.
  • Bug version 2: very similar to version 1, but even after restarting WiFi, the phone still insists on connecting to the first access point, SSID_A.
  • Bug version 3: when connected to the first access point, SSID_A, as you move to the second access point, the signal strength seems to increase as the device searches for a stronger access point, but then drops the connection and after a short hiatus, re-establishes the connection. The easiest way to observe this is by the disappearance of the WiFi icon and an interruption in the connection.

Bug version 3 is the one for which felixchris has created a workaround. The fix is confirmed to work on Samsung Galaxy i9300 models and the Samsung Galaxy Nexus i9250. A couple different versions of the mod have been developed, one that requires a custom recovery and one that does not. However, both solutions require root access to the device.

If you are having trouble with your WiFi connection when moving between overlapping access points and you have one of the specified devices, you may want to give the fix a try by visiting the source link below. Just be sure to read the warnings and cautions related to rooting your device or flashing files.

source: XDA Forum WiFi Roaming Fix

, , , , , , , , , , , ,

No Comments

Unofficial Samsung Galaxy S III WiFi roaming fix now available

Owners of some Android devices, in particular the Samsung Galaxy S III and Galaxy Nexus, may have noticed a bug that causes their device to have trouble transitioning between different WiFi access points when access points overlap. XDA Forum member felixchris has put together a hack that addresses one of three possible ways the bug manifests itself. According to felixchris, the three ways that users may experience the bug include:

  • Bug version 1: when connected to an access point (e.g. SSID_A), as you move to the area covered by a second access point (e.g. SSID_B), the phone never releases from the first point even though the signal gets very weak and the higher strength SSID_B is available. This particular version of the budget can be verified by turning off WiFi, then turning it back on again, at which point the device should associate with the second access point.
  • Bug version 2: very similar to version 1, but even after restarting WiFi, the phone still insists on connecting to the first access point, SSID_A.
  • Bug version 3: when connected to the first access point, SSID_A, as you move to the second access point, the signal strength seems to increase as the device searches for a stronger access point, but then drops the connection and after a short hiatus, re-establishes the connection. The easiest way to observe this is by the disappearance of the WiFi icon and an interruption in the connection.

Bug version 3 is the one for which felixchris has created a workaround. The fix is confirmed to work on Samsung Galaxy i9300 models and the Samsung Galaxy Nexus i9250. A couple different versions of the mod have been developed, one that requires a custom recovery and one that does not. However, both solutions require root access to the device.

If you are having trouble with your WiFi connection when moving between overlapping access points and you have one of the specified devices, you may want to give the fix a try by visiting the source link below. Just be sure to read the warnings and cautions related to rooting your device or flashing files.

source: XDA Forum WiFi Roaming Fix

, , , , , , , , , , , ,

No Comments

The Unofficial Sony “Yuga” Smartphone Gets Detailed Preview, Confirms Everything We Thought Previously About The Device

 

Another day, another tidbit of news regarding the suddenly not-so-secret Sony “Yuga” smartphone. After seeing some teaser photos of the superphone yesterday, we are now treated to a an actual preview of the device, complete with all the spec details you can handle. Thanks to our friends at Mobile Reviews, we now know the “Yuga” will come fully loaded with a 5-inch 1080p display, quad-core Snapdragon S4 Pro chip, 2 gigs of RAM, a microSD card slot, LTE and 12MP camera. In addition to the premium hardware features, the smartphone will come preloaded with Android 4.1 and Sony’s custom UI slapped on top.

So now that the cat is just about out of the bag, it’s just a matter of time before Sony comes out and gives up the deets. Q1 2013 can’t come here soon enough!

source: Mobile Reviews

, , , , , , , , , , , ,

No Comments

The Unofficial Sony “Yuga” Smartphone Gets Detailed Preview, Confirms Everything We Thought Previously About The Device

 

Another day, another tidbit of news regarding the suddenly not-so-secret Sony “Yuga” smartphone. After seeing some teaser photos of the superphone yesterday, we are now treated to a an actual preview of the device, complete with all the spec details you can handle. Thanks to our friends at Mobile Reviews, we now know the “Yuga” will come fully loaded with a 5-inch 1080p display, quad-core Snapdragon S4 Pro chip, 2 gigs of RAM, a microSD card slot, LTE and 12MP camera. In addition to the premium hardware features, the smartphone will come preloaded with Android 4.1 and Sony’s custom UI slapped on top.

So now that the cat is just about out of the bag, it’s just a matter of time before Sony comes out and gives up the deets. Q1 2013 can’t come here soon enough!

source: Mobile Reviews

, , , , , , , , , , , ,

No Comments

The Unofficial Sony “Yuga” Smartphone Gets Detailed Preview, Confirms Everything We Thought Previously About The Device

 

Another day, another tidbit of news regarding the suddenly not-so-secret Sony “Yuga” smartphone. After seeing some teaser photos of the superphone yesterday, we are now treated to a an actual preview of the device, complete with all the spec details you can handle. Thanks to our friends at Mobile Reviews, we now know the “Yuga” will come fully loaded with a 5-inch 1080p display, quad-core Snapdragon S4 Pro chip, 2 gigs of RAM, a microSD card slot, LTE and 12MP camera. In addition to the premium hardware features, the smartphone will come preloaded with Android 4.1 and Sony’s custom UI slapped on top.

So now that the cat is just about out of the bag, it’s just a matter of time before Sony comes out and gives up the deets. Q1 2013 can’t come here soon enough!

source: Mobile Reviews

, , , , , , , , , , , ,

No Comments

Official CyanogenMod Music Player ‘Apollo’ Arrives On The Play Store To Organize Your Musical Muses

apollotinyIn ancient Greece, Apollo was—among other things—the god of music. In ancient 2012, Apollo became the official music app for CyanogenMod. It was gorgeous, functional, and completely customizable, as you might expect from the world’s most popular ROM. At the time, we were told that this lovely bit of software would be coming to the Market “in the coming weeks.” That was back when we still called it the Market. Today, though, Apollo is available on the Play Store.

apollo1 apollo2 apollo3

The player comes in two flavors: regular, and +. Apollo+ removes ads and offers quicker updates for a mere $0.99.

Done With This Post? You Might Also Like These:

Official CyanogenMod Music Player ‘Apollo’ Arrives On The Play Store To Organize Your Musical Muses was written by the awesome team at Android Police.

, , , , , , , , , , , , ,

No Comments

Unofficial Galaxy Nexus Google+ Page Mentions Multiple Nexus Devices – Android Fans Go Nuts

This image has no alt text

Careful out there, folks. I know we’re all a bit excited, scouring the nets for any bit of info regarding the next Nexus device(s) but just like the world of Twitter, Google+ is full of unofficial accounts spreading hope (sometimes falsely). Take the “Galaxy Nexus” Google+ account which posted the following:

“Happy birthday +Galaxy Nexus, you were born one year ago, on October 19th. Soon you are going to meet your younger brother(s) ;)

This lead our Phantips inbox filling with, “ERMAHGERD!!! NERCKSERZ!!!!!” emails from excited Android-fanboys across the globe. Only one problem — the Galaxy Nexus Google+ page in question ISN’T OFFICIAL. Whoever runs it was merely commenting on current rumors and speculation that multiple Nexus devices could be announced on October 29th. We’ll still keep our fingers crossed but in the meantime, watch yourself out there. The net is a big strange place (especially those weird kids on Google+).

[Google+]


, , , , , , , , , , ,

No Comments

Unofficial CM10 Alpha 1 makes its way to the Barnes & Noble Nook Color

The Nook Color?? Anyone know what that is? It might seem a little old school and not like a top priority, and you might kind of be right. The fact that it was done and is being worked on is what is more important. The NookieDevs have been tirelessly working and building and squashing bugs to get the most current CM10 (Android 4.1.2) all loaded up and functioning on the Barnes & Noble Nook Color a.k.a the Encore.

They have done it. How and why? We aren’t sure, but they have proven it to be possible. The build they released super early this morning is up for those of you that are curious about the whole en-devour. It is still just an Alpha build and more so as a preview build, but they have a fairly short list of known issues.

WHAT DOESN’T YET WORK?

  • HD YouTube (regular SD is hardware-accelerated, however)
  • Netflix (we know *someone* will ask)
  • The home (aka “n”) button doesn’t wake the device from sleep. We’re working on it.
  • OpenGL rendering has been turned off (due to poor performance) – so any apps that need it (such as Chrome) may not take advantage of OpenGL..
  • A weird bug: Wall-power charging isn’t detected when the charger is plugged in while sleeping – so be sure to wake the device before plugging in your A/C charger (usb charging is fine)
  • Possibly other stuff.

Some of those might disappoint you, but at the same time, we are talking about an older tabletish device that was never meant to even be close to a powerhouse device of any kind. The fact that the team is working on it still and that it is said to run pretty well, is a great achievement.

The team has a rather lengthy thread running over at XDA currently with all the details you could possibly want to know. They offer up a little back story, how a lot of the Drivers had to be re-written to even get it this far and some other important aspects. It is a good read. If you want to know a few things they did and even grap the current preview build for yourself to try out, then head over to NookDevs 2012 XDA thread. As always, be sure to read everything at least once, but twice is recommended.

Thanks for the tip @krylon360 and nice work to the whole team.

, , , , , , , , , , ,

No Comments

Isis Mobile Wallet app for Android surfaces in Google Play, you probably can’t run it

Isis Mobile Wallet app for Android surfaces in Google Play, you probably can't run it

Unofficial rumblings have pointed to Isis Mobile Wallet’s trial getting close. If you’ve remained skeptical all the same, we’re pretty sure that seeing Isis’ Android app in Google Play will change your mind. The currently T-Mobile-only software confirms that pilot program members will tie their American Express, Capital One or Chase card (as well as a unique card) to Isis for paying through NFC at stores with a SmartTap terminal. We’re also promised streamlined loyalty cards and coupons. Before anyone rushes to try the app at the local shop, remember that it’s just one piece of the puzzle on top of the special SIM card, one of three NFC-equipped phones and that small matter of living in Austin or Salt Lake City when the service goes live. Having the official app at least lets those who qualify get a head start on what could soon be the only major alternative to Google Wallet in the US.

Filed under: ,

Isis Mobile Wallet app for Android surfaces in Google Play, you probably can’t run it originally appeared on Engadget on Tue, 16 Oct 2012 18:22:00 EDT. Please see our terms for use of feeds.

Permalink MobileBurn  |  sourceGoogle Play  | Email this | Comments

, , , , , , , , , , , , , , ,

No Comments

HTC One V Receives Unofficial CM10 Port

The HTC One V, the youngest sibliing in the HTC One series of Android devices, finally gets an Android 4.1 Jelly Bean-based Cyanogenmod 10 port. The CM10 nightlies port is available thanks to XDA Recognized Contributor jmztaylor for CDMA-based devices and XDA Recognized Contributor Lloir for GSM-based devices. Unlike most alpha and beta builds, the new build for both versions of the One V appear to be quite stable, with the exception of the LCD backlight never turning off and the camcorder not working. If you’re an HTC One V owner and feeling brave, hit up the source link and get flashing! But as always, it’s wise to take backups before proceeding.

Source: XDA


, , , , , , , , , , , ,

No Comments

Sony Xperia SL Live Photos Leaked, Confirm Rumored Specs

Photos of the rumored Sony Xperia SL have been leaked online by an anonymous tipster Thursday, August 2.While it wasn’t known if the photos were the official press shots of the device or not, it has been published by GSM Arena as an exclusive report claiming a tipster allegedly sent the photos to them.

Nevertheless, the shots look legit and confirmed previous reports that it would simply be a slight bump from Sony Xperia S.

Xperia SL Unofficial Specs

Specs-wise, Xperia SL is the same as with Xperia S only that it has a slightly overclocked processor. That said, here are the key specs of this device;

Processor. It would still sport the Qualcomm MSM8260 Snapdragon chipset, a dual-core CPU which is popularly known to come at 1.5 GHz clockspeed. A slight bump to this would give us 1.7GHz speed but that means overclocking it. The 200MHz may not be enough for many to notice a slight difference in processing, it is nonetheless an upgrade.

Memory. Xperia SL was previously rumored to come with 1GB RAM and that’s the highest memory Sony can give to its devices. Just like the previous version, it would also come with 32GB internal memory but without a microSD slot; upgrading is not an option here.

Display. A 4.3-incher LED-backlit LCD capacitive touchscreen, like that of Xperia S, will also be seen on this device. Other display features include 720 x 1280 pixels resolution plus Sony Mobile BRAVIA Engine and the Timescape user interface.

Camera. Xperia SL would also come with a 12-megapixel camera with LED flash as the primary while the front-facing cam has 1.3 megapixels. The rear-facing camera can record full HD video at 1080p@30fps with video stabilizer and video light features.

OS. Fortunately, Xperia SL will be sporting Android 4.0.4 Ice Cream Sandwich out of the box and not Gingerbread like the Xperia S.

Pricing & Availability. For now, there is no information as to when the release date of this device would be but tech enthusiasts believe this device will be offered at the same price as the Xperia S. While there is a little upgrade on the specs, they are not enough to make this handset more expensive than the one already released.

Basically, the clear differences between the previous model and the upcoming one are the processor and operating system. Other than these two, everything is the same. However, Sony is yet to confirm these specs, so until such time the company releases the official word, we can’t really be sure what’s to come. Here are the photos published on GSMArena.

Sony-Xperia-SL-1
Sony-Xperia-SL-2
Sony-Xperia-SL-3
Sony-Xperia-SL-4
Sony-Xperia-SL-5
Sony-Xperia-SL-6
Sony-Xperia-SL-7
Sony-Xperia-SL-8
Sony-Xperia-SL-9

Source: GSM Arena

, , , , , , , , , , , , , , , , ,

No Comments

Unofficial CM10 and AOKP Builds Release for Verizon Galaxy S III

Even though Verizon has kept the bootloader locked on their Galaxy S III, development from the ROM developers hasn’t stopped at all to this point. A couple weeks ago Verizon’s Galaxy S III saw a unofficial CyanogenMod 9 port, over the weekend though we saw the heat turn up with two more ports of AOKP and CyanogenMod 10. Know what that means? Android 4.1 Jelly Bean! Both AOKP and CM10 are as close to fully working as currently possible with a few minor bugs that should of been worked out by now.

I’m very curious as to how they were able to get the AOKP and CM 10 running on Verizon’s Galaxy S III without the bootloader unlocked. On the Motorola Atrix 2 people are having such trouble getting things on it like CM 10. It’d be be very interesting to know how they’ve done it. That aside, it’s great that we can depend on the community to what our carriers refuse to do for some odd reason.

The AOKP Milestone 6 is ready for its prime time and a daily drive. It currently has no known bugs so this may be a good one to look into first. CyanogenMod 10 on the other hand, is still be strictly referred to as an “alpha.” Aside from that, all of the most important features in the software is working and currently very stable. When I say that the “most important features” are working that also includes the data connection. So if you can get past a few bugs and the gritty feeling of an unfinished ROM this also might be a great one to download.

TouchWiz may be way too painful for you to use and the stock Android you may not like either. Either way, you should check out both of these ROMs and maybe even consider downloading one of them to your device. As a quick remind these ROMs are actually only possible to the kexec boot sequence created by CVPCS (this may be how they got past the bootloader). The boot sequence will apear twice during a bootup, that’s normal and is just the Kexec Boot Sequence doing it’s normal work.

All of this is interesting. Again I am curious as to how they were able to get past Verizon’s locked bootloader. It could be because of CVPCS’s bootloader, but that isn’t 100% confirmed. That aside, it’s great to hear that there are ROMs available for the Galaxy S III. Many were worried that it might end up the same way the Motorola Arix 2 has been.

Do you own one of Verizon’s Galaxy S III’s? Will you be looking into downloading one of these “unofficial” build releases for your device? If so, would you pick up CyanogenMod 10 or the AOKP Milestone 6? It’d be interesting to see what both are like but I have feeling they are both very similar. CyanogenMod 10 of course, is the more popular one. Let us know how all of that works out for you in the comments section below!

Happy ROMing!

source: Droid-Life

, , , , , , , , , , , ,

No Comments

Developer Ports Unofficial AOKP Build to the Nexus 7

  Developer nize2beme uploaded a port of AOKP for the Nexus 7 to the forums at RootzWiki last night. So far, this is a very early alpha build and in order to get it booted up and running, he says he needed to take pieces of code from the newest CM10 source. At the moment, the developer is looking [...]

Click through to continue reading…

, , , , , , , , , , , , ,

No Comments

Unofficial CM10 and AOKP Builds Released for Verizon’s Galaxy S III

Verizon’s locked bootloader on their Galaxy S III hasn’t stopped development at all to this point. Two unofficial ports of AOKP and CyanogenMod 10 popped up, with each either being as close to fully working as can be or with a couple of minor bugs that are currently being worked on.

AOKP Milestone 6 appears to be ready for release and a daily driver without any known bugs so far. CM10 is currently still being referred to as an “alpha”, however, data and all the other most important core features are working. You may just want to look into either one of these, especially CM10 as they always do a outstanding job and go beyond the call of duty.

These ROMs are only possible thanks to CVPCS’s kexec boot sequence and will appear to boot twice during the bootup process. That’s all normal and is just the kexec doing it’s work.

sources: RootzWiki, DroidHive
via: DroidLife


, , , , , , , , , , ,

No Comments

Unofficial CM10 and AOKP Builds Released for Verizon’s Galaxy S3

The locked bootloader on Verizon’s Galaxy S3 hasn’t stopped development much to this point. Last week, we saw the device receive an unofficial CM9 port, but over the weekend, things turned up another notch. Two unofficial ports of AOKP and CM10 popped up, with each either being as close to fully working as possible or [...]

Click through to continue reading…

, , , , , , , , , , ,

No Comments

ROM – @flappjaxxx AOSPxXx v1.0B2 Unofficial AOSP/CM9 Mashup “Vacation Edition” for Samsung Galaxy Note I717/ AT&T

flappjaxxx has released an update to AOSPxXx v1.0B2 Unofficial AOSP/CM9 Mashup “Vacation Edition”. The latest version is now 1.0B2.

This release is supported on the following Device(s):
- Samsung Galaxy Note I717: AT&T

Head over to flappjaxxx’s CommunityRelease Developer Homepage for more information and downloads.

Register now on Community Release and follow your favorites.

Get instant notifications for:

  • Single Releases
  • Device Releases
  • Developer Releases

    • It’s so simple and will give you access to new registered user features as they become available.
      Click HERE to complete your registration.

, , , , , , , , , , , ,

No Comments

ASUS Transformer, Transformer Prime and Motorola Xoom Receive CyanogenMod 10 Preview Builds

The other day we received the CyanogenMod 10 preview builds for both the international and U.S. versions of the Samsung Galaxy S III and now there’s more! The CM 10 preview builds are now available for the ASUS Transformer and Transformer Prime (tf101 and 201) and with Motorola’s Xoom. With all the excitement around Jelly Bean and CyanogenMod 10, a working build for tablets is wonderful news to hear.

These are only preview builds though, so they may not be very stable. Unofficial builds also carry no guarantee on support, assistance or updates.

The Transformer builds are currently functional with Wi-Fi, Bluetooth, sounds, camera, video acceleration, minor dock functionality and most sensors. The GPS and light sensor functionality isn’t in there just yet, but the device’s core functionality is stable and working.

Here’s a quick video of the Transformer Prime running CM10 on its current build in action:

Click here to view the embedded video.

The Xoom builds, on the other hand, are not quite as complete. In a post to Google+, Steve Hawkin notes that “A lot of the features and functions are still very much [a work in progress].” He also says that he has personally been using the builds as a daily driver, so they may just be worth taking a look at.

To get a early preview build of CyanogenMod 10, click the links below for your respective devices:

Downloads: Xoom (Wi-Fi), Xoom (VZW), TF101, TF201

source: Android Root, Google+
via: Android Police


, , , , , , , , , , , , , , , , , ,

No Comments

Unofficial CM10 ROM lands for Nexus S

Some of you Nexus S owners out there might remember a post we put up yesterday about a new Jelly Bean AOSP built ROM for your device. That was created by XDA member legolas93 and seemed to get some pretty great feedback. Since then he has been busy working his developer magic and has since pulled a functional CM10 build over to the Nexus S now. In this one you will find a few mods like Lock Screen Calendar and power menu. Things are progressing pretty quickly all across the boards for quite a few devices over the last few days.

He makes mention that CM10 is pretty close to a stock Jelly Bean at this point, but that as new features are added in and updated he will do the same for the Nexus S. If you gave yesterdays build a shot you might want to check out this new one. Head over legolas93′s XDA thread to join the discussion and give it a whirl. Looks like we might have to start getting these added to our CommunityRelease page soon.

, , , , , , , , , , , , , ,

No Comments

Unofficial Android 4.1.1 ROM for the Nexus S now available at XDA

android-4.1.1-nexus-s

The Jelly Bean ROM for Nexus S has been made available by a developer over at XDA Forums. The AOSP ROM was posted by a user named legolas93. The device has to be rooted, and the user needs to be well versed with flashing custom ROMs to be able to go on with the process. It must be noted that the ROM used here is the most recent release i.e. Android 4.1.1, which should make way officially to Nexus S smartphones in the coming days.

The Galaxy Nexus has already received the Jelly Bean update, while the Nexus S and the Motorola XOOM are in tow. The change log for the new release hardly gives out any details by merely mentioning that the tethering feature and camera have been fixed. The new ROM comes with the fix that Google rolled out to the Galaxy Nexus and Nexus 7 recently to avoid potential lawsuits.

The new ROM seems to be working fine with no issues, though I haven’t tested it out myself. This ROM isn’t the same as Google’s OTA version, so you might be better off waiting for the official release. So this basically is for the users who are curious to try out the new Jelly Bean update. One of the perks of owning a Nexus device is the fact that these devices get the updates first followed by the rest of the Android bandwagon. There are no details as to when Google will make the Jelly Bean update available for Nexus S and XOOM users, but it should be coming anytime soon now.

It is commendable how these developers manage to work on ROMs for the community and for free. While there is always a risk of damaging your device, the process is pretty breezy. Scrolling through the comments didn’t reveal any problems with the flashing, so it seems like everything is fine here. Some users are reportedly getting an installation error, which is reportedly due to not following the instructions carefully. So make sure you read everything properly before going forward.

Note: Head over only if you know what you’re doing as it can be pretty tricky for rookies.

Download the ROM from the XDA link provided below.

Source: XDA Forums
Via: Android Authority

, , , , , , , , , , , , , , , ,

No Comments

Unofficial factory image leaks for Verizon Samsung Galaxy S III

Many Verizon customers are starting to see their pre-ordered Samsung Galaxy S III show up on their door steps. The official launch of the device nationwide and in stores is still 4 more days away, but that doesn’t mean there aren’t some goodies already floating about. One of the more useful bits of software has already made its way to the web via Samsung-Updates. We are talking about the crucial factory image for the device. While this leak isn’t officially support or released by Samsung, near as everyone can tell it is the final build of the devices software. This news won’t mean a whole lot to the average user, but for the developers looking to jump-start the Verizon Galaxy S III into gear, it can be a life saver.

Direct your browser to Samsung-Updates if your interested in picking it up.

Source: Samsung-Updates Via Phandroid

, , , , , , , , , , , , ,

No Comments

ASUS Transformer TF101 Gets Update To Version 9.2.1.27 Bringing Bug Fixes, Not Much Else

image

Owners of ASUS’ original Eee Pad Transformer have something to be excited about, as reports of an update to software version 9.2.1.27 began to surface on XDA earlier today.

While the update isn’t too exciting (keeping the device at Android 4.0.3), it does bring a handful of fixes that Tf101 users have been waiting for for some time. Among them are fixes for video playback, Chrome performance, and various app performance issues. Unofficial user reports indicate that the update may also bring smoother performance overall. Here’s the full (official) change log:

9.2.1.27 Release Note

  • Fix Chrome browser and black screen issues
  • Fix "Mobile Dock Battery saving mode" bug
  • Fix movie playback hang issue
  • Enhance MyLibrary and Vibe performance
  • Enhance AppBackup stability
  • Enhance Email stability
  • Update translation for Settings

As usual, users looking to grab the update manually need only check for system updates in their device’s Settings menu.

Official Android Police t-shirts are now on sale, with over 25 designs to call yours.

Done With This Post? You Might Also Like These:

ASUS Transformer TF101 Gets Update To Version 9.2.1.27 Bringing Bug Fixes, Not Much Else was written by the awesome team at Android Police.

, , , , , , , , , , , , , , , ,

No Comments

ROM – @flappjaxxx AOSPxXx v0.6a Unofficial AOSP/CM9 Mashup “Hey Jerky!” for Samsung Galaxy Note I717/ AT&T

flappjaxxx has released an update to AOSPxXx v0.6a Unofficial AOSP/CM9 Mashup “Hey Jerky!”. The latest version is now 0.6a.

This release is supported on the following Device(s):
- Samsung Galaxy Note I717: AT&T

AOSPxXx v0.6A Changelog:

Compiled Fresh on 7/2/2012 AOSPxXx v0.6A
*NO Wipe Upgrade if coming from previous versions of AOSPxXx*
1 Merged all previous fixes from v0.5A

2. adb access is root by default again

3. Some more under the hood references removed

4. More of my own stuff integrated at compile time

5. Bumped Tools to v5.5

8. Synced latest AOSP/CM9 repos before compile time

9. Some minor under the hood bug fixes/code clean up and stuff I forget

Head over to flappjaxxx’s CommunityRelease Developer Homepage for more information and downloads.

Register now on Community Release and follow your favorites.

Get instant notifications for:

  • Single Releases
  • Device Releases
  • Developer Releases

    • It’s so simple and will give you access to new registered user features as they become available.
      Click HERE to complete your registration.

, , , , , , , , , , ,

No Comments

Iconia Tab A500 by Acer Gets Unofficial Android 4.1 Build

For users of the Acer Iconia A500 tablet who simply cannot wait until Google releases the Android 4.1 Jelly Bean source code, a developer has already released an unofficial build. This build still has many issues, but might be enough to satisfy the curiosity of some about the newest version of Android OS on the block.

This is believed to be the first-ever Android 4.1 Jelly Bean SDK port, at least according to the developer randomblame of the xda-developers forum, who has uploaded it. Among the issues identified on the port are the lack of audio and Wi-Fi connectivity.

The SD card reportedly is also not functioning, and the USB is unable to mount flash drives. Randomblame, however, has been hard at work on the SDK port and trying to address some of the bugs to provide a better Jelly Bean experience. Furthermore, there is a walkthrough accompanying the port for those who are interested.

Google, for its part, is expected to bring out the source code in just a few weeks, the schedule being mid-July. However, the over the air update will initially be brought to a very small set of devices including the Samsung Galaxy Nexus, Nexus S, and the Motorola Xoom.

A minor upgrade from Android 4.0 Ice Cream Sandwich, Jelly Bean offers a speedy and highly responsive system with minimal lagging thanks to technologies like triple buffering, touch anticipation, and better frame rates of 60fps. It moreover has new accessibility APIs, notifications that can be expanded, high-resolution images of contacts, added uses for the NFC-based Android Beam, and an enhanced way of getting updates for apps.

Google Voice Search and Google Now also offer comprehensive assistance. The camera likewise allows for smoother image capture. During image review, users may pinch on an image to see the set of all captured photos while a simple swipe erases an unwanted image. An undo button is also provided. Finally, the OS has a new user interface that is similar to that found on Android Ice Cream Sandwich, and generally believed to save battery life more efficiently.

via liliputing

Amazon Image

, , , , , , , , , , , , , , , , , ,

No Comments

Galaxy S III Battery Bug Discovered, Unofficial Fix Available

The bad news as you can see above is that there seems to be a bug in the battery stats on the Samsung Galaxy S III, which isn’t what you want to see from your brand new flagship phone.

The good news is twofold: (1) the bug is a reporting bug, not an actual battery usage bug, and (2) there’s a fix available already, albeit not from Samsung but from some crafty developers over at XDA.  

It seems a bug in the phone’s framework-res.apk file is causing the reported voltage of the “cell standby” process to be about 10x higher than it actually is, which throws off the reported battery stats.  Your phone isn’t using and more power than normal, and your battery isn’t running out any faster.  It’s simply a reporting error.

The good news is a modified power_profile.xml file is available to fix the problem if it really bothers you.  I’d expect to see a fix from Samsung, but as this isn’t a critical bug I doubt we’ll see a fix very quickly.

Head over to XDA to read more and grab the needed files.

source: XDA


, , , , , , , , , , , , ,

No Comments

DROID Bionic gets Unofficial ICS 4.0.4 ROM, must be flashed through Stock Recovery

DROID Bionic owners have been waiting since the announcement of ICS back in 2011 for their software upgrade. Everything’s going to get a whole lot better, as this morning P3Droid released a leaked version of Android 4.0.4 ICS for the DROID Bionic, which MUST be flashed through stock recovery, and you must be running the current firmware (.905) in order to flash it. Bionic owners who have already flashed the update have reported that the ROM runs pretty well, and that there are no major bugs in the firmware.

As Droid-Life points out, the new firmware is easily rooted using a previous DROID RAZR 4.0.4 method, although there is another method currently being developed for this specific Bionic build. If you love ICS as much as we do, and own a DROID Bionic, today might be your day. As always, however, we aren’t responsible if you mess anything up.

Source: Droid Hive

Via: Droid-Life

, , , , , , , , , , , ,

No Comments

Flipboard for Android to break free from the Galaxy S III officially

Android Central

Love it or hate it, Flipboard coming to Android is big news. We first took a look at it back at Earls Court in London during the Samsung Galaxy S III launch event. Initially at least, Flipboard is exclusive to the Galaxy S III, but as is often the way this didn't last very long at all. Unofficial versions were 'ported' from the Galaxy S III and hosted on the interwebs for all the world to download and use at their leisure. Word from Flipboard now though, is that the application will soon be available on all Android devices. 

The story goes that in concentrating on one device, with one screen size and resolution, Flipboard could ensure that their massively popular iOS offering wouldn't suck when it arrived on Android. That, and quite possibly the bazillion number of units Samsung were likely to — and eventually will be — shipping of the Galaxy S III. As far as a test bed goes, a device that ended up with 9 million pre-orders probably wasn't a bad choice. As it turns out, Flipboard is pretty close to having a beta version of the app ready for the rest of the Android world. 

The developers are planning to release it to a small amount of users initially under a strict beta tag, to help test it out, submit bug reports, and generally make sure that the app is as polished as it needs to be. Makes sense, after all, Flipboard is all about the visual, and a janky experience would be the quickest way to put users off. 

There is no mention of the magic date that Flipboard may start to make it into eager beta testers hands, but by all accounts it sounds like it's pretty close. Could it even appear before the Pebble Blue Galaxy S III perhaps? 

Source: Engadget

, , , , , , , , , , , , ,

No Comments

AT&T HTC One X Receives Unofficial Bootloader Unlock Method

This image has no alt text

You may remember awhile back when we told you about the extra effort AT&T went through to lock down the HTC One X’s bootloader for their network (vs the international model). Well, it didn’t take long for those wacky devs on XDA to crack it, opening up the device to custom ROMs and modding. They even provided a handy walkthrough and if you’re handy with command lines, shouldn’t be too difficult. The coolest part about this method is when you’re done tinkering around, you can finish unlocking the bootloader the official way using HTCDev’s online tool. Full instructions below.

You need ADB and an understanding of how to use it and have a rooted device (although I didn’t test this). You will also need a hex editor like HxD.

BACK UP YOUR DATA BEFORE DOING THIS!!!! WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!

1. Fire up your command prompt and go to the directory that you have ADB installed to. Type “adb shell” and hit enter.

2. Type “su” and hit enter. You now have root privileges.

3. Next type “dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4″ and hit enter. This will dump the partition to your sdcard.

4. Next type “exit”, hit enter, type “exit”, and hit enter again. This should take you back to a command prompt for your computer.

5. type “adb pull /sdcard/mmcblk0p4″ and hit enter.

6. Open the file (mmcblk0p4) with your hex editor.

7. Look for offset 00000210 and you should see CWS__001 with your IMEI number attached to it.

8. Change CWS__001 to ROGER001 and save the file as mmcblk0p4MOD.

9. Now go back to your command prompt and type “adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD” and hit enter.

10. Type “adb shell” and hit enter then type “su” and hit enter again. This will put you back into the android shell and give you root privileges.

11. Type “dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4″ and hit enter. To test if it worked restart the phone into fastboot (type “adb reboot bootloader” and hit enter) and once the bootloader screen comes up type “fastboot oem readcid” and hit enter. It should read “ROGER001″.

12. Next type “fastboot oem get_identifier_token” and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there.

Keep in mind, that method will erase everything on your device, so backup your personals accordingly. I don’t recommend anyone unlock their bootloaders unless they know full well what they’re getting themselves into. The world of flashing custom ROMs is dark and scary one. Don’t say I didn’t warn you…

[XDA]


, , , , , , , , , , , ,

No Comments

Unofficial Port Of Classic PC Game “Theme Hospital” Hits The Google Play Store

If you’re a huge fan of classic PC games then you’re in for a surprise.  Recently to surface in the Google Play Store is an unofficial port of the classic 1997 game Theme Hospital.  The game is available for download now and will run you $1.49.  The game can be played on smartphones and tablets alike.  The SIMs-esque game offers you the great task of running an entire hospital from nothing into a state of the art and up to date facility with full wards, standard operating rooms, offices and of course, staff members.  You’re the boss, so hire and fire as you see fit.  Some of the ailments from various patients are rather odd, but nevertheless, your job to cure them.  Ready to download?  Check out the Google Play Store link below or feel free to use the QR code as well.  Let us know what you think of the game in the comments below.

ThemeHospital_1
ThemeHospital_2
ThemeHospital_3
ThemeHospital_4

qrcode

Play Store Download Link


, , , , , , , , , , , , , , , , ,

No Comments