Search the Community

Showing results for tags 'cyanogenmod'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • TeamUSCellular Blog


    • * -[READ THIS THREAD]- * Common Q&A and our Terms!
    • Shoutbox
  • Team US Cellular
    • Contests and Giveaways
    • Site News and Blog
    • Reviews
    • General Discussion
    • Suggestion Box
    • (¯`·.¸¸.-> °º Birthdays º°
    • Ask The Employees
  • US Cellular
    • News
    • Rumor Mill
    • Contract & Billing
  • Android
    • Android Discussion
    • Android Development
  • Google Pixel
    • Pixel & Pixel XL Discussion and Development
  • Nexus 6P
    • Nexus 6P Discussion
    • Nexus 6P Development
  • Nexus 5X
    • Nexus 5X Discussion
    • Nexus 5X Development
  • Nexus 6
    • Nexus 6 Discussion
    • Nexus 6 Development
  • Apple iPhone
    • General Discussion
    • Development Q&A
  • Ubuntu for Android
    • General Discussion
  • Windows Phone
  • LG V20
    • LG V20 Discussion
    • LG V20 Development
  • LG G3
    • LG G3 Discussion
    • LG G3 Development
  • LG G4
    • LG G4 Development
    • LG G4 Discussion
  • LG G5
    • LG G5 Discussion
    • LG G5 Development
  • LG G Flex 2
    • G Flex 2 Discussion
    • G Flex 2 Development
  • Motorola Electrify M
    • Electrify M Discussion
    • Electrify M Development
  • Motorola Moto X
    • Moto X General Discussion
    • Moto X Development
  • Motorola Moto X (2nd Gen)
    • Moto X (2nd Gen) Discussion
    • Moto X (2nd Gen) Development
  • Moto X Pure Edition 2015
    • Moto X Pure Edition Discussion
    • Moto X Pure Edition Development
  • Motorola Moto G
    • Moto G General Discussion
    • Moto G Development
  • Samsung Galaxy S8
    • Galaxy S8 Discussion
    • Galaxy S8 Development
    • Galaxy S8 Plus Discussion
    • Galaxy S8 Plus Development
  • Samsung Galaxy S7
    • Galaxy S7 Discussion
    • Galaxy S7 Development
    • Galaxy S7 Edge Discussion
    • Galaxy S7 Edge Development
  • Samsung Galaxy S6
    • Galaxy S6 Discussion
    • Galaxy S6 Development
    • Galaxy S6 Edge Discussion
    • Galaxy S6 Edge Development
  • Samsung Galaxy Note 5
    • Note 5 Discussion
    • Note 5 Development
  • Samsung Galaxy Note 4
    • Note 4 General Discussion
    • Note 4 Development
  • Samsung Galaxy Note 3
    • Note 3 General Discussion
    • Note 3 Development
  • Galaxy Note Edge
    • Note Edge Discussion
    • Note Edge Development
  • Samsung Galaxy Mega
    • Mega General Discussion
    • Mega Development
  • Legacy Devices
    • BlackBerry
    • Samsung Galaxy S5
    • HTC Desire
    • HTC Hero S
    • HTC Merge
    • HTC Pro 7
    • HTC Wildfire S
    • Huawei Ascend II
    • LG Apex
    • LG Genesis
    • LG Optimus F7
    • LG Optimus U
    • LG Splendor
    • Motorola Defy XT
    • Motorola Electrify
    • Samsung Acclaim
    • Samsung ATIV Odyssey
    • Motorola Electrify 2
    • Samsung Axiom
    • Samsung Galaxy Note 2
    • Samsung Galaxy S Aviator
    • Samsung Galaxy S II
    • Samsung Galaxy S III
    • Samsung Gem
    • Samsung Galaxy S4
    • Samsung Note 7
    • Samsung Galaxy S4 Mini
    • Samsung Mesmerize
  • Tablets
    • Windows Phone Discussion
    • Asus Eee Pad Transformer
    • Windows Phone Apps & Media
    • Asus Eee Pad Transformer Prime
    • Galaxy Note 10.1
    • Galaxy Tab 8.9
    • Galaxy Tab 10.1
    • Galaxy Tablet 2 7.0
    • Galaxy Tablet 2 10.1
    • HP TouchPad
    • HTC Flyer
    • Kindle Fire
    • LG G Pad 7.0
    • Motorola Xoom
    • Nexus 7
    • Tab S2
    • LG GPad 8.0 V2
  • Other
    • The Lounge
    • Buy/Sell/Trade
  • Trash
    • Trash Bin


  • Google Apps
  • Alcatel Shockwave
  • Blackberry 9350
  • Blackberry 9850
  • HTC Desire
  • HTC Hero
  • HTC Merge
  • HTC One V
  • HTC Wildfire
  • Huawei Ascend II
  • LG Splendor
  • Motorola Electrify
  • Motorola Electrify 2
  • Motorola Electrify M
  • Moto X
  • Odin 3.09/3.10
  • Samsung Aviator
  • Samsung Axiom
  • Samsung Galaxy Note II
  • Samsung Galaxy S II
  • Samsung Galaxy S III
  • Samsung Galaxy S4
  • Galaxy S5
  • Samsung Mesmerize
  • Samsung Metrix
  • Samsung Repp
  • Samsung Galaxy S6
  • Samsung Note III
  • Samsung Galaxy Note 4

Found 20 results

  1. It doesn't really make sense that there's a combining forum for LTE Note 2 phones on the CyanogenMod forums for the i605, l900, and the r950 when a CyanogenMod version called t0lte only combines the n7105, i317, and the t889; the r950 isn't considered a t0lte phone, yet the model number is technically t0lteusc. Furthermore, I don't see why the r950 is even included in the forum anymore if it's officially in a legacy build at this point with no sign of future updating. I read somewhere that CyanogenMod t0lte versions are only for GSM phones which is why they're different but it's not very specific. So, as a result, I did some research and changed a few verification things. Normally, t0lte would deny installation in a traditional TWRP flashing menu. Some people just used a recovery on their R950 for a different model number but that seemed like quite a bad idea in case anything went wrong. To fix it, I just replaced the N7105 verification with the R950 model numbers (SCH-R950 and t0lteusc) and it worked! Mislabeled some model numbers but it was easily fixed in the build.prop which is included in the ROM already. Introducing a highly experimental CyanogenMod 12.1 for the R950. Who knows how well it works, but, to give you an idea, it hasn't crashed at all while the official CM11 crashed a couple times in using it. I don't have service which is problematic because then I can't test if service even works. I doubt it will because the t0lte model number is for GSM phones which is why the r950 is in the CDMA forum along with the L900 and the i605. But in using Wi-Fi, the camera, compass, rotation, root, modding of system properties, GPS, etc, there have been no issues except Google Play services crashing which has come and gone, themes provider crashing but the actual saved theme still working, and the camera reboot issue. I'm not entirely sure that forum users are allowed to distribute their own modifications of CyanogenMod, but I don't see anywhere that says I can't, and, frankly, it almost seems it's encouraged. Just let me know if this is kind of illegal. Here is the modified CyanogenMod now with the modified build.prop incorporated in it and Gapps in one package: Extract it to get the flashable files, then push them over via adb. If anyone has suggestions (as in changes for the build.prop etc) for any future releases I might modify, by all means. I want to be more providing than the R950 team has been (shots fired) To install, just wipe data, dalvik, and cache (simply factory reset on TWRP, probably other recoveries too) and then flash the CM12 .zip (not the whole package) and then tk Gapps if you haven't installed a Gapps package already, then install Xposed; the build.prop should install automatically. I haven't tried updating to the latest nightly via settings but it'll probably fail again as it's still registed to the original t0lte database so I do not recommend it. My current one is working just fine anyway, which is why I didn't downgrade this to a snapshot (this is a nightly). The modded build.prop includes performance enhancements, slight battery improvements, and data and wifi speed enhancements as well as some changed model numbers. Optionally, you could also get an app on the Play Store called SPenCommand (it's paid) to get stylus features back plus the pop-up window from the later Notes. While writing this, it occured to me that, if service doesn't work on this version, it might be able to work on a CDMA version (not i605 as it's incredibly glitchy in my experience of trying it) Thoughts? Enjoy your glorious Android 5.1.1; I know I have.
  2. Root the device Download BMM 0.3.4 from here Reboot to BMM -> Recovery -> Full backup to tar. (dup seems to be broken) Now follow to Flash firmware -> back-up CID After the successful backup (double check !) erase CID. Reboot Enter fastboot mode (Vol+, Vol-, Power On) and pass the following line "fastboot flash boot boot.img" (see post attachment) BMM -> Recovery -> Install zip -> (choose the ROM you wanna try) After the system successfully installed - check if BMM auto installed to the new system. Reboot, Wipe Dalvik, wipe cache or Factory Reset. Normal boot.N.B. During the boot process you'll see CustomerID error msg. - just press and hold power btn for several secs. All the available ROMs for XT881 -…#dir/path=%252Fyangtze Currently I've tested CM4.4.2, MK4.2.2 The last one is the most stable and usable. Alternatively if the download is slow, you might visit my DB:
  3. note 3 CM Rom

    Hello, I was able to root phone and using a recovery flash the custom ROM. the rom itself works well, and I got google play on it and apps and wifi work great. But today, I took the gamble and got the phone activated with my number. The network keeps dropping and re connecting, over and over every few seconds. Cant really call or text this way. My main question is, is this ROM specific (such as, try a different rom)..or is this a common problem that can be fixed with (just go here and change this, or replace this file, ect) I do not see anything in the forum about this issue. Thank you The cyanogenmod rom I used was a "nightly" build, that was the newest on the list.
  4. Version Android 4.4.1(mixed with


    Translated from Chinese to English Aroma script, some modifications were made to fix hacked UDN Pro stop downloading bloatware. Cleaned some preinstalled chinese apps. Removed custom files for XT885, XT889. Use 4.2.2 gapps with this ROM. If you want to use newer one (eg 4.4+), you'll have to mess for a long time moving new files to /system/app folder in order to run them properly. Install via BMM 0.3.4 on main system with boot.img from chinese XT881 (more info
  5. Hello TUSC! For the last few months I have been running Cyanogenmod and keeping up with the latest nightlies for the Galaxy S4 (SCH-R970). Then, there was one nightly nightmare and I was stuck in a boot loop. Alright, no big deal, I'll just recovery boot and downgrade to the previous nightly. When I booted back up, I was roaming, and when I tried to make a call it said something along the lines of "you are roaming, if you would like to purchase....". That's no good! I did some research, changed the network settings around a bit (changed CDMA roaming mode to "home only"), and that got 4g LTE running. Meaning that I could go online, but still couldn't call or text anyone (it just says no mobile network available). Very strange. I changed the CDMA back to "automatic" and tried *228. The call would just hang (the lady would say to wait for a few seconds, an advertisement would play, then just silence until I eventually hung up). Alright, things are getting serious... I did a factory reset—still no luck. I flashed 4.4.2 stock touchwiz. Still doesn't work. Any ideas? Thanks!
  6. Happy New Year Folks - Here's a belated Christmas present... Presenting.... Electrify M - ROM Converter!! After months of "hand editing" every ROM I flash, I have finally decided to make a flash-able zip to do it. (Be nice, it's my first project like this.) What it does: -Installs USC specific "eri.xml" and "apns-conf.xml". -Installs USC specific "libs" to have a working voicemail notification. -Edits "build.prop" to have working SMS/MMS. (Tested with stock camera and messenger apps.) -Edits "build.prop" to have proper model number and carrier. -(Testing 01/03/14 , ver 0.3 should automatically set RUIM and CDMA/EvDo "stable 3g" - thanks to "ekylypse") -(More Testing 01/03/14 ver 0.4 - Now sets RUIM and CDMA/EvDo Before Or After initial boot-up.)-Version 0.5 - Added LTE version and cleaned up code. Installation: (new ver 0.5 installation) -Flash your favorite ROM made for the "unlocked" RAZR M / XT907 -Flash the EM ROM Converter - STD* or LTE** version see below (as of ver 0.4 this can be flashed before or after "trying" the ROM) -Flash the appropriate gapps. I am currently using "PhilZ touch recovery" and didn't have any issues. TWRP (tested) should also work fine. CWM may need "/data" and "/system" mounted prior to flashing. ROMS TESTED (as of 01/25/14): -CyanogenMOD 10.1 - Working MMS -CyanogenMOD 11 -SlimKat 4.4.2 -OSE ROM 4.4.2 BUGS: -In all my ROM flashing, I occasionally have RUIM and or CDMA/LTE not set. (Quick fix, but should be noted) -Working MMS varies per ROM. Thanks to user "cdiamond" for pointing out that CM 10.1 / AOSP 4.2 was working. THANKS: -User "ekylypse" for "LTE-Helper", code ideas, and testing. -All others for their testing and input. * This will provide "stable" 3G service. Do to incompatibilities with ROMS built for the "RAZR M - XT907", LTE / 4G is not stable. ** While LTE-Helper provides LTE service, users may notice higher battery usage.
  7. For those who care, CyanogenMod has brought the Mesmerize up to version 10.1 (i.e. version 4.2.1 of Jellybean):
  8. Hello all, After my semi-painful experience of having a handset for half a day that had the equivalent functionality of a paper-weight, I wanted to try to save others the trouble. So, let's get started... I was one of the few (perhaps many?) whom unknowingly went to Stock 4.3 and ended up locked into KNOX (thank you Samsung). The hazard this created is when I later wanted to go back to a Custom ROM, specifically CM 10.2 Stable, I would get the following line of code from the ROM pop up and the install subsequently fail. assert(getprop("ro.bootloader") == "R530UVXAMB1" || getprop("ro.bootloader") == "R530UVXAMD4" After a lot of researching here and on the web, I was able to find the way to fix this issue thanks to Lynkz83 ( I employed Lynkz83's recommendation to remove the above lines from the ROM itself; after doing so, I flashed with GREAT SUCCESS! (cue Borat voice)! To save everyone the hassle, I've uploaded the modded ROM file to my Dropbox and below is the link to get it; the file is in essence the same as what's on CM's website, just with the bad code removed. My thanks go out to the Cyanogenmod Team for the wonderful ROM (I love CM's stability), and to Lynkz83 for the awesome walkthrough on modding the updater script to make the ROM actually work. So far, so good for running the ROM (about a day in). I hope this helps out those who ran into the same problem that I did.
  9. You can flash it over your Cyanogenmod 10.1 ROM safely, make sure you get the gapps for 4.3 though. No bugs that I've run across so far aside from using Font Installer (don't use it, it'll break your ROM and you'll have to reflash.) IR Blaster, MMS, Camera, etc. etc works perfectly. Make sure you go into the Dev Options and go to Root Access and select App and ADB and you'll be good to go. Can't think of much else to tell you guys. All credit goes to the bloke over at XDA, my buddy Stephen, and the 2 cents I tossed in there to help things a long a little. So you will get nightlies over there, though it's an AT&T ROM he complies for many devices. When CM catches up, you can just use the CM updater. Anyway, enjoy, enjoy, enjoy!
  10. The RAZR M (Electrify M) has joined the official list of supported devices at along with a few other Motorola devices. Link: Of course an unlocked bootloader is necessary, and there are probably a few bugs. Hopefully being "official" will bring more dev support. PS - We should be seeing builds of 10.2 shortly too.
  11. I'v been doing some research, looking around all over the internet, and I have come across this app in the app store called Boot Menu Manager. Now, i know the Electrify 2 is locked by motorola, but I also read that the Electrify 2 is the same as the Razr V, Would it be possible to download a Razr V Custom ROM (Such as Cyanogenmod) onto the Electrify 2 and install it through Boot Menu Manager? Would like to work with someone on this, Help would be appreciated
  12. Source: Mod Type: ROM Difficulty: Easy Mod Status: Nightly Mod Base: Carrier: US Cellular Requires Root: Yes Apply In: CWM Recovery Optional: Optional: Android Version: 4.2.2 (JB) Credits/Thanks To: Bajee11 Description Dark RootBox is built straight from RootBox sources and always carries a very light installation with no extra/useless apps. This means, you can enjoy a pure Android experience combined with AOKP/CM features and some CM cherry-picks. Keep in mind Jelly Bean is only at the beginning stage of development and there will be minor bugs. Every RootBox releases are stable and always up to the challenge for a daily usage. I personally have a high standard when it comes to releases and this is why this project always meets the expectations of users. If you're wondering how this ROM differs from any other AOKP roms out there, I only have one thing to say: Try it yourself and choose the one that meets your requirements. Features Built from RootBox Sources AOKP Features CM Profiles Per App DPI Per App Tablet UI Per App Language Navigation Bar Colour Camera: Save to external memory Phone: Advance Phone Settings (Vibrate on Answer, Every 45 Seconds, On Hangup and On Call Waiting) Phone: Noise Suppression MMS: Fully Customizable MMS Theme MMS: Soft Keyboard Type (Emoji, Enter to Send, Enter for a New Line) Home button call answer (Accessibility Option) Variable size pattern lockscreen RootBox Settings Pie (Paranoid Android) LCD Density Changer Low Battery Warning (Pop-up & Sound, Pop-up only, Sound only, Off) Option to control cursor in text fields using volume keys Disable Fullscreen Keyboard (Landscape mode) Expanded Desktop Hold Back to Kill CRT Animation (Screen On/Screen Off) Lockscreen Shortcuts (Paranoid) Lockscreen Targets (CM) Screen Security Features (Unlock options: Quick Unlock, Delay Screen Lock, Menu Unlock, Home Unlock) cLock (Chronus) Option to disable sound when adjusting volume Launch Music app on Headset connection Hardware Keys Remapping Lockscreen Hardware Keys Remapping kernel update to 3.4.37 paranoid android settings Built using GCC version 4.7 -from google Aliasing fixes from linaro networking optimizations fix memory leaking Update translation Update Adreno driver Fix composition issues when framework rebooted in suspend don't clear wallpaper when SystemUI disconnects. Carbon power PhabletUI NavBar in landscape Bring some Swagger Back Add LongClick to FastCharge Toggle Moar style fixes Fix touch issue using 0% navbar fix stuck pixel on screen redraw Menu UI Overflow Toggle Set ringtone mode even if ringer is silent RootBox SquareMod Battery fix mobile data usage display for sim-less devices Enable car dock pie on lockscreen if lockscreen is secure Allow USB notification to show when primary SD allows UMS and MTP *optimized apps **lots of added language translations ------------------05/08--------------- HALO thanks PA
  13. Does anyone here have any experience with roaming and running a "non-stock" ROM (Cyanogenmod)? I recently went on a trip to Sioux City, which according to the map, is a roaming area. I was running "Arrakis / BareBack" ROM and had roaming 3G. For the heck of it, I restored a CM based ROM and had no service at all. I did check the settings, and everything was similar (Data enabled, Data roaming, CDMA, etc.) Just curious if anyone else had any input?
  14. i bit the bullet and installed CyanogenMod 10.1 with JellyBean 4.2. I like it, lots. However, I miss some of the stock ringtones that originally came with the phone. I have a complete backup with Titanium Backup Pro of my old rom apps and data. I also have access to a stock (non-rooted) phone. Is there any way I can pull the stock ringtones from my backup, from the other phone, or download from the Internet? As for the CyanogenMod, it is awesome. The ease of setting up a wireless tether is amazing! I am still a noobie with Android and expect I will be for some time. The installation of the new ROM and restoration of my apps took close to two days. I think next time it should be closer to 3-4 hours.
  15. DISCONTINUED Disclaimer: I take no responsibility for bad things that may occur as a result of flashing this. These are Unofficial CM10 builds for the U.S. Cellular Note 2 SCH-R950 built from source. All source code credits go to sbrissen. Github Source: Can be downloaded using ROM Manager! NEW! [Alpha 1]ROM: Changes: - Initial Release [Alpha 2] ROM: Changes: - Upstream CM changes - Fixed MMS receive - Orientation sensor is "better" (After a reboot, screen off/on and it will kick in) - Fix LPM (Charging while phone is off) - Fix Camera fw being copied (should fix camera issues) - Boost audio volumes [Alpha 3] ROM: Changes: - Built from source Instructions: - Download and copy rom to sdcard ( - Mirror: --------------------------------- - Download and copy gapps to sdcard ( - Reboot into recovery (i.e. CWM) - Flash ROM - Flash gapps - Flash optional add-ons - Wipe data/cache (if needed) - Reboot Optional Add-ons: - Center Clock ( - Inverted Messaging (Dark Theme) ( NEW (01/08) Known Bugs: - NFC might not work? - Orientation sensor is delayed in kicking on, can take a minute to start working. Credits: Team Hacksung CM TSM slick_rick sbrissen atronin Donations accepted! (:
  16. As much as i hate to be the bearer of bad news, I think this needed to be shared on here, and @sno ( if posting the article like this is prohibited, ill take it down and just have the link posted) Samsung loses some developer support for Exynos-based phones "Remember when many U.S. customers were thrilled that they would finally be able to enjoy the quad-core Exynos 4412 chipset together with LTE in the Galaxy Note 2? For most of Rootzwiki's readers, though, the first question we ask about a new superphone is "will it have developer support?" Unfortunately, the Galaxy Note 2 and other Exynos-based phones will not have the same developer support that the newest Snapdragon, TI OMAP, and Tegra 3-based devices enjoy. CyanogenMod/Team Hacksung developer codeworkx, among others, have withdrawn support for the international version of the Galaxy S III, citing a lack of developer support from Samsung for its signature chipset. Other Samsung Exynos-based devices facing decreasing support from developers include the international Galaxy S II, the international Galaxy Note and all versions of the Galaxy Note 2. In a conversation I had with Codeworkx, he pointed out that AOSP ROMs running on new and recent Exynos-based devices face a variety of bugs because of failure on Samsung's part to release source code for its Exynos chipsets. For example, bugs in the international Galaxy S3 (i9300) include certain camera features, broken Bluetooth and WiFi tethering, and unsupported TV Out. In the international Galaxy S2 (i9100), issues include incomplete Jelly Bean support from Hardware Composer (referring to the Mali GPU included in the Exynos chipset), broken camera recording, slow transfer of data over USB in Mass Storage mode, and TV Out (as in the i9300). The international Galaxy S3 hasn't completely lost CyanogenMod support though, as developer Xplodwild is still supporting the device at the moment. I’ll stay away from all exynos powered phones as long as there is no proper support from samsung in form of documentation and sourcecode (especially userspace) to get aosp properly working on it. - CyanogenMod/Team Hacksung developer codeworkx Both codeworkx and other developers I've talked to have said that Qualcomm, nVidia, and Texas Instruments all provide a greater measure of support for their system-on-a-chip (SOC) processors, thus devices with those chipsets will receive more support from the development community. While the Snapdragon series and the Tegra series come with more support than the Exynos series, Texas Instruments provides the most extensive support of all for its OMAP chipsets. Unfortunately, Texas Instruments announced that it is shifting its focus away from smartphones and tablets for its OMAP architecture. As codeworkx and others have also pointed out, Samsung is under no obligation to release documentation or source code for its Exynos chipsets, just as Qualcomm, nVidia, and Texas Instruments are under no obligation to do so. SOC-specific code is proprietary, and is regarded a trade secret, though Samsung is the most secretive of the four companies. It's also important to note that proprietary code is not covered by the General Public License requirements and is entirely different from device manufacturers (such as HTC, Motorola, and Samsung) releasing kernel source for their Android-based handsets and tablets."
  17. I just updated my phone to the latest nightly build, the one uploaded on the 21st (today), and I cannot get LTE or any mobile data at all. I can connect to wifi, and I get radio signal, but no mobile data. I have tried reinstalling the updated package multiple times, and I get the same issue. Anyone out there know how to fix this? I haven't found much using google, and what I did find didn't work.
  18. Hi everyone - long time lurker, first time poster. I got an S3 last month and really liked the experience after two years with an HTC Desire, which I had rooted and with CM 7 within the first two months. First thing I did was I blocked/disabled most automated internet-using functions of the phone, like Kies, etc, because I knew I might want to root someday and I didn't want updates being installed OTA that might make it harder to do that. (two years of iPod touch using before the Desire taught me to never trust manufacturer's updates until you've researched them!) This may have been my mistake Last week I decided it was time to see how CM10 was doing, so I rooted using the method which does not update the Odin flash counter (it's on TUSC here) and then bought TitaniumBackup Pro to back up the apps, and then Rom Manager to make the full .tar backups. I'm currently on Nightly 20120929. I've heard some people here on TUSC say that CM10 works better on a certain baseband then others. Oops. I checked my CM10 installer and found that I'm running R530UVXLG1. I've seen several posts that allude to CM10 working better on newer basebands (am I running one that is third oldest right now, with LG4 coming after LG1, then LL4 being released yesterday on October 3rd?) I'm having some trouble with certain aspects of CM10, although overall I like it a lot. Bluetooth seems to not work with Pandora and Google Music, although it works fine for Youtube (I use a jogger's headset). Battery usage seems pretty high, compared with stock Touchwiz. And Google Now doesn't "talk back" to me for some reason, it just displays the info I searched for (which is still great of course!) So, what do people around here think? Would I be better served by going back to stock, taking an update to LG4 or LL4 (or anything, really! I know roms, but not basebands, really) and then going back to CM10 or Blackbean or something? Thank you all for your comments and advice. You're a great community and I'm hoping to be a part of it.
  19. As someone that has only rooted one phone in their past (HTC Desire) I'm a little bit hesitant to do it again, but I'm growing very impatient with the lack of an ICS update. I've been hearing the praises of CM9 (from friends that have the SG2 on other carriers) and I had CM6 on my Desire for a time so I know what I'm getting myself into as far as CM is concerned. This build on the forum isn't the final build, but how close to 100% is it? I guess that's a silly question because if I didn't want bugs, I'd wait until the stable CM9 release, but I'm too impatient. CM9/ICS look too darn sexy to pass up for much longer, not to mention the speed and customization. Makes me regret getting the SG2 when I could've waited >3 months to get the SG3. PS: I had accidentally bricked my SG2 last week when my FF18 update didn't go as planned & due to this website, I learned how to unbrick and successfully returned to stock. You guys are fantastic.
  20. CM9

    I wonder how soon CM9 will be stable for the SIII. I'm really anxious to get it, I think this phone with that ROM on there will be cat's pajamas.