What Would You Like to See Added/Removed

  • Remove Rom Manager

    Votes: 14 37.8%
  • Keep Rom Manager

    Votes: 21 56.8%
  • Remove Fun & Games

    Votes: 28 75.7%
  • Keep Fun & Games

    Votes: 8 21.6%
  • Add ConnectBot

    Votes: 5 13.5%
  • Do Not Add ConnectBot

    Votes: 21 56.8%
  • Add Dolphin Browser HD

    Votes: 7 18.9%
  • Do Not Add Dolphin Browser HD

    Votes: 25 67.6%
  • Add exDialer w/ ICS Theme AC

    Votes: 8 21.6%
  • Do Not Add exDialer w/ ICS Theme AC

    Votes: 18 48.6%
  • Add Play Music

    Votes: 21 56.8%
  • Do Not Add Play Music

    Votes: 11 29.7%
  • Add SuperSU

    Votes: 21 56.8%
  • Do Not Add SuperSU

    Votes: 10 27.0%
  • Add OpenExplorer Beta

    Votes: 7 18.9%
  • Do Not Add OpenExplorer Beta

    Votes: 21 56.8%
  • Add Alarm Clock Plus

    Votes: 12 32.4%
  • Do Not Add Alarm Clock Plus

    Votes: 19 51.4%

  • Total voters
    37
  • Poll closed .
Search This thread

216Monster

Senior Member
Oct 17, 2011
1,233
363
Ohio
How did you get the touchpads working on the game?

Thanks to 216Monster we now have a fix to the network name being T-CDMA<network number>

If you hop over to the first post & check the main download folder, it's there (and it's cross-version, so it'll work with both cm7/9)

Now if only 216 would share how the flip he got shadowgun to work, it'd be fantastic ;)

The touch pads worked out the first time I was able to get the game to run in the first place :)

By editing these two build prop lines:

ro.product.device=zeus (changed from ro.product.device=zeusc)

ro.cm.device=zeus (changed from ro.cm.device=zeusc)
 
  • Like
Reactions: Schwabie64
I kinda feel like I should at least say I didn't mean anything by it :(
but I honestly liked the apps that were included in the build, minus rom manager and the get apps/get games apk. To each his own right :D

Doesn't matter much either way. Most of what I like is what people don't want from the poll. My ideas were simply recommendations based on the criteria of "more options than stock".
 

crono141

Senior Member
Jan 4, 2011
505
35
West Columbia, SC
I know I"m late the the whole "battery drain is now awesome" party but:

I just updated my kernel and rom 2 days ago. Today, after 2 hours unplugged I've only lost 5% (without any use). I'd be down 20% before. Good work, KeiranFTW!
 
  • Like
Reactions: KeiranFTW

KeiranFTW

Inactive Recognized Developer
Nov 17, 2011
2,637
2,692
28
Sunderland
There won't be a new kernel update until either:
Sony push new sources out.
FreeXperia update current source.
I feel that it is the most stable CM9 kernel, because of new sources.
The reason why FreeXperia won't merge new sources is because it breaks the mogami board stuff, which is for Arc and co.

Here is an update on my Battery Bar app:
5c29fbc8-097e-aa2a.jpg


Will have preset colours, maybe a colour wheel in the Pro version, when I get it out on the store.
Of course I'll push releases here for testing before I push them to Google Play. Just need a Google Play dev account now, $25 :)

Sent from my Sony Xperia™ PLAY using Tapatalk 2
 
  • Like
Reactions: 216Monster

T3mpr1x

Senior Member
Sep 16, 2007
101
10
Santa Clarita
x51v.info
I know I"m late the the whole "battery drain is now awesome" party but:

I just updated my kernel and rom 2 days ago. Today, after 2 hours unplugged I've only lost 5% (without any use). I'd be down 20% before. Good work, KeiranFTW!

Same here! I was experiencing horrible battery drain until this latest build. My steps:

  1. Flash kernel.
  2. Clear cache and dalvik cache.
  3. Install update zip.
  4. Install GApps.
  5. Reboot.

This also keeps my Google Apps data, so I don't have to add my multiple accounts again. Facebook integration still isn't working, and while it was cool to have it's definitely not a dealbreaker. My phone went over two hours before finally dipping 1 percentage point! Incredible stuff.
 

Schwabie64

Senior Member
Mar 1, 2012
199
26
30
Armada, MI
The touch pads worked out the first time I was able to get the game to run in the first place :)

By editing these two build prop lines:

ro.product.device=zeus (changed from ro.product.device=zeusc)

ro.cm.device=zeus (changed from ro.cm.device=zeusc)

I changed these in the building prop and am still having many problems with games in general.

Nova 2 starts but no menu is displayed. Shadowgun downloads to 50 percent then closes. Modern combat 3 won't start. Mupen64 the anologs don't work. And analog doesn't work in any games.

However emulators work great!!

Sent from my R800x using xda premium
 

216Monster

Senior Member
Oct 17, 2011
1,233
363
Ohio
I changed these in the building prop and am still having many problems with games in general.

Nova 2 starts but no menu is displayed. Shadowgun downloads to 50 percent then closes. Modern combat 3 won't start. Mupen64 the anologs don't work. And analog doesn't work in any games.

However emulators work great!!

Sent from my R800x using xda premium

I had Nova 2 running ok but It worked before I edited those lines and I haven't opened it since, I will try that when I get home, and ShadowGun gave me download problems on this rom before I even had it running, I had to keep restarting it. Once it finally downloaded it didn't load a game until I stumbled upon editing those lines, now ShadowGun works fine for me, and the analog works in ShadowGun and Blood and Glory just fine, I will test Analog in Nova 2 once I redownload the data also. I don't use mupen64 though :/.

Im not sure but maybe only one of those lines needs edited? Maybe someone smarter then me would know... but when I get home (30mins away) I'll test the things above and I'll edit one line back an forth to see if that makes a difference!

Sent from my R800x
 
  • Like
Reactions: Schwabie64

Schwabie64

Senior Member
Mar 1, 2012
199
26
30
Armada, MI
I had Nova 2 running ok but It worked before I edited those lines and I haven't opened it since, I will try that when I get home, and ShadowGun gave me download problems on this rom before I even had it running, I had to keep restarting it. Once it finally downloaded it didn't load a game until I stumbled upon editing those lines, now ShadowGun works fine for me, and the analog works in ShadowGun and Blood and Glory just fine, I will test Analog in Nova 2 once I redownload the data also. I don't use mupen64 though :/.

Im not sure but maybe only one of those lines needs edited? Maybe someone smarter then me would know... but when I get home (30mins away) I'll test the things above and I'll edit one line back an forth to see if that makes a difference!

Sent from my R800x

Thanks.

I'll play around with it when I get home as well. About 6 hours to go.

Sent from my R800x using xda premium
 

216Monster

Senior Member
Oct 17, 2011
1,233
363
Ohio
Thanks.

I'll play around with it when I get home as well. About 6 hours to go.

Sent from my R800x using xda premium

So, Im ending up with the same problem on Nova2, loads up to menu but nothing is displayed except exit and info. The download took about 25 attempts of it just stopping and having to close and restart, with that, did you try restarting and/or force close and restarting ShadowGun ? I didnt have that issue with SG just Nova, maybe it will work in your case?..

I dont have MC3 however..

I changed ro.cm.device=zues back to saying =zuesc

ShadowGun still works with analog :)
Blood and Glory the analogs work but the key mappings are off now

Edit : Im changing ro.cm.device.=zuesc back to say =zeus to see if key mappings are still off in Blood and Glory

Edit 2 : having it =zues gives me everything except the O key correct. Im gonna mess with the emulators now using the original fix posted (how I have it setup now) And Nova2 hasn't worked either way, but after I check the emulators Ill remove the fix entirely and see if N2 works again!

Edit 3 : All the emulators work for me Nesoid, Gameboid, SNesoid, N64oid, Gensoid , all of them except N64oid have lag in each game I played, Maybe I should update my emulators?... Moving on to Nova2 NVm I see you reply below!
 
Last edited:

Schwabie64

Senior Member
Mar 1, 2012
199
26
30
Armada, MI
So, Im ending up with the same problem on Nova2, loads up to menu but nothing is displayed except exit and info. The download took about 25 attempts of it just stopping and having to close and restart, with that, did you try restarting and/or force close and restarting ShadowGun ? I didnt have that issue with SG just Nova, maybe it will work in your case?..

I dont have MC3 however..

I changed ro.cm.device=zues back to saying =zuesc

ShadowGun still works with analog :)
Blood and Glory the analogs work but the key mappings are off now

Edit : Im changing ro.cm.device.=zuesc back to say =zeus to see if key mappings are still off in Blood and Glory


Nova 2 downloaded on the first try for me without changing the build.prop and if you push x while on the menu screen the game will load.
As for shadowgun I played around with it for about 30 minutes last night without the build.prop edited and it always stopped at 50 percent. I will be able to play with more when I get home.
Sent from my R800x using xda premium
 
  • Like
Reactions: 216Monster

216Monster

Senior Member
Oct 17, 2011
1,233
363
Ohio
Nova 2 downloaded on the first try for me without changing the build.prop and if you push x while on the menu screen the game will load.
As for shadowgun I played around with it for about 30 minutes last night without the build.prop edited and it always stopped at 50 percent. I will be able to play with more when I get home.
Sent from my R800x using xda premium

How are the touch pads for you? They dont work in Nova2 with or without build.prop edits , for me.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    FIRST OFF: THIS IS FOR UNLOCKED BOOTLOADERS. IF YOU TRY TO INSTALL THIS WITH A LOCKED BOOTLOADER, YOU WILL BRICK YOUR PHONE.

    As aGraceful has been mentioning, Here is the CM9 thread dedicated to the R800x.

    What it is:
    We (myself, aGraceful or anybody else who's interested) will port FXP with every new release that comes out.

    I (or if anybody else is interested) will be building & uploading a new version (from source) about mid-week (between FXP release) with the newest CM9 updates.

    What it is not:
    Neither myself, aGraceful, or anybody else who contributes claim any thing special about the code. Either FXP built it (if it's a port) or it's code from Cyangenmod/Koush/freexperia or anybody else who has contributed to the CM9/Android repos.
    Starting 2012 June 06 -- I am using my own device tree and vendor tree to build this, so it should work better with wifi than FXP's builds.

    Now, onto the good stuff.
    What Works:
    Data
    Calls
    Wifi
    GPS
    SMS
    Accelerometer
    MMS (thanks chrono!)


    What Doesn't Work:
    Bluetooth Media Audio (Thanks chrono!)
    Video Recording (Thanks Neoandgeo for pointing that one out)
    Facebook account syncing (Thanks DoubleByte) -- Note facebook account syncing looks like it's a problem within 4.0 framework...

    Anything else that doesn't work, lemme know, I'll add it to the list.

    FXP Changelog: changelog for fxp


    Link to All Downloads
    What's in it:

    1) agraceful's port of FXP 115 116 117 (Current as of 04/22) I'm gonna stop hosting FXP ports through my mediafire, look to agraceful for those
    2) mega_fix.zip -- contains Atarii's wifi/gamepad fix & 216monster's mms/carrier name fix
    3) My latest build from source (newest date in the title)
    4) Older builds
    5) Copy of the libs I use for porting, If you're interested in trying to bring another ROM to our phone, these cover mostly everything) dev corner with some libs if you're interested in porting something.

    Steps to do a install:
    1) Download & copy to sdcard
    2) reboot recovery,
    3) MAKE A NANDROID!
    4) wipe dalvik/cache
    5) install from sdcard.

    Steps to do a 100% clean install (we're talking if all else fails try this option)
    1) Reboot into recovery, MAKE A NANDROID, wipe the 3 major things (data/cache/dalvik)
    2) Turn off your phone & connect it in fastboot mode.
    3) enter this fastboot erase system (this will erase the /system partition, insuring a clean install)
    4) boot into recovery
    5) install from zip.

    Thanks to Ridder215215, a complete guide on how to install CM9 (just replace the link in line 2 with the link above)

    As everybody knows, Flashing roms can lead to issues with your phone. When you decide to flash something, you are taking the responsibility for your phone working into your own hands.


    Google apps: http://goo.im/gapps
    or goo.im market app: https://play.google.com/store/apps/details?id=com.s0up.goomanager

    Rom Update: 2012 April 11

    1) Latest CM9 fixes.
    2) Gamepad fix added in.
    3) Wifi fix is included
    4) Kernel is included in the zip this time, so no need to download two separate things :p

    Test update: 2012 April 11

    Uploaded a xLoud test version for y'all to try out. Please tell me how well it works for you guys! (If it makes a big enough difference, I'll change out dspmanager for it)
    1) Added in xLoud framework (kinda, I think we're missing stuff from framework.jar/framework-res.apk so it doesn't show up in menu-> sound settings) ALSO: It's having an issue with wrong UID (settingsProvider.apk issue) so when I get around to it, i'll tear apart some things and see if it can't be ported.
    2) Removed DSP manager

    Kernel Update; 2012 April 14
    Uploaded a new kernel for people to test out
    Enabled governors:
    Conservative
    MinMax
    SavagedZen
    SmartAssv2
    InteractiveX

    Enabled IO Schedulers:
    Anticipatory
    Deadline
    CFQ
    V(R)

    Disabled ALS (Thank Keiran)

    Sources are FXP's (https://github.com/freexperia/semc-kernel-msm7x30-ics/tree/ics) All I did was tweak some minor stuff

    Rom Update 2012 April 15
    1) Latest CM Sources
    2) No xLoud tweaks
    3) Wifi fix built in (will be from now on)
    4) Gamepad fix built in (will be from now on)
    5) Set mmc to "12" in apns-conf.xml (should fix any mms issues, if it doesn't I'll change it to 5)

    Kernel uploaded yesterday will still work (am using it right now)

    Kernel Update (2012 April 18)
    Uploaded a new kernel built from DooMLoRD's Sources (see links above) with wifi modules included (so you won't have to flash 'em) -- NOTE: THIS ONE WILL BREAK H/W DECODING.

    Rom Update (2012 April 19)
    Uploaded a new version.
    1) Latest cm9 fixes
    2) Tried adding some of the info from brainard52's post into the apns-conf.xml it it doesn't work, follow the instruction in his post (thanks brainard52!)

    Rom Update (2012 April 21)
    Uploaded a new version
    1) Latest cm9 fixes
    {in case mms is still not fixed 2) Tried adding some of the info from brainard52's post into the apns-conf.xml it it doesn't work, follow the instruction in his post (thanks brainard52!)
    }
    Why? Because 8 hours and still no upload from FXP, so I felt like uploading one :p

    Rom Update (2012 April 25)
    Uploaded a new version
    1) Latest cm9 fixes
    2) Included KeiranFTW's latest DFK-CM9 kernel in the zip, because well, it works. best. way to go keiran!
    3) Made sure that ro.board is zeus, not zeusc (once again, thanks Keiran!)

    Rom Update (2012 April 29)
    1) Latest CM9 Fixes
    2) zipalign in /system/xbin
    3) OI File Manager From OpenIntents
    4) Network Name fix from 216Monster!

    Rom Update (2012 May 03)
    1) Latest CM9 fixes
    2) Change in baseband libs to .57.
    Sorry, not too much this time, I got distracted with the 2.3.4 update & got to it late :D

    Rom Update (2012 May 05)
    Added Codename-Android to the download list. If you like tweaks, enjoy. Codename Android has it's own thread

    Rom Update (2012 May 06)
    1) Latest CM9 fixes... including theme manager! (but no themes, yet)

    Rom Update (2012 May 09)
    1) Latest CM9 fixes

    Rom Update (2012 May 12)
    1) Latest CM9 Fixes (sorry, nothing big this update, busy)
    2) Also packaged latest DFK in zip
    3) DO NOT USE FXP KERNEL WITH THIS ROM, I HAD MASSIVE FC ISSUES.

    Rom Update (2012 June 6)
    1) Been a little while hasn't it :D
    2) Latest CM9 fixes
    3) Kernel included was built from source as part of CM's new "inline kernel building" (FXP's kernel)
    6
    Added Codename Android Port to the downloads.

    NOTE: IT IS A COMPLETELY SEPARATE VERSION OF CM9 SIMILAR TO AOKP, IT WILL WIPE SYSTEM & WILL RESET YOUR HOMESCREEN ICONS. On the other hand, it's another flavor of CM9 available to us (and for a change, not available to the R800i first *sticks out tongue at R800i users*)

    Pax
    6
    Building an update, soon as it's done, i'll test, upload & update OP

    Pax
    5
    As Brainard52 Suggested,
    Resources:

    HOW TO FLASH A KERNEL:
    1) Download a working kernel for CM9 (it's in download links, included with FXP zip & stand-alone (will be fixed next update))
    2) extract kernel from where ever you downloaded it to where ever fastboot is (unless you add fastboot to $path in windows or /bin||/usr/bin||etc in linux)
    3) type the following command "fastboot -i 0x0fce flash boot <name of boot.img>
    4) NEVER FLASH RECOVERY.IMG.

    Linux users:
    If you create a file, 51.android.rules, put this in it
    Code:
    SUBSYSTEM=="usb", ATTR(idVendor)=="0fce", mode=="0666", GROUP="plugdev",
    chmod it to 644 (r+w) & copy it to /etc/udev/rules.d/ you never need to use -i again! (for your play)

    Links:
    Flashtool:
    http://xdaforums.com/showthread.php?t=1351299

    Original FXP Thread:
    http://xdaforums.com/showthread.php?t=1447542

    Team Darkforest CM9 Kernel:
    http://xdaforums.com/showthread.php?t=1541482

    Recovery:
    http://xdaforums.com/showthread.php?t=1130639


    In case you want to try out building from source, read this link:
    http://xdaforums.com/showthread.php?t=1556971

    Note: KeiranFTW forgets one major thing in his post, he assumes that somebody will only do it once! If you plan on doing it more than once, then for every git clone you do (msm-7x30, zeus, zeus-common in device/semc/ & vendor/semc/) you should go through and do a git pull everytime you wanna rebuild source (knowing Keiran, he probably just made a script for it :p )

    If you want to build a kernel from source download this text file:
    Kernel Tutorial! (Note: In it I use FXP sources, if you wanna Doom/Keiran just change the git url inside to their kernel sources)

    Courtesy of CrimsonKnight13, Here is a list of apps that are a good addition to CM9
    Here's my list of preferred apps over stock CM9/ICS

    ConnectBot > Terminal Emulator
    Dolphin Browser HD (newest has an ICS-ish look) > Browser (Chrome)
    exDialer w/ ICS Theme AC > Phone
    Play Music > Music
    SuperSU > Superuser
    APEX Launcher > Trebuchet
    Swiftkey 3 Beta (has a very ICS look) > Default keyboard
    OpenExplorer Beta > File Explorer (from any ICS/CM9 iteration)
    Alarm Clock Plus > Clock

    I'm adding a poll on top to see what people want included. If an app is a paid app, then don't even think about asking for it to be added.


    LOGCAT
    For future reference, I'm going to include here how to use logcat (android debugging tool.)
    There are two main ways to do a logcat, within android and through adb.
    Logcat within android can be installed by a logcat app:
    Two good examples are either: aLogcat or Catlog
    I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging.

    On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)

    The code for logcat is
    Code:
    adb logcat > name of problem.txt
    you can also do
    Code:
    adb logcat -f name of problem.txt
    how I prefer to do it is this way:
    Code:
    adb logcat -v long > name of problem.txt
    with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)

    Here's where using logcat (via adb makes life really easy)
    Lets say you find a problem you're having after looking at a logcat.

    For example:
    When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)

    So if you search for an error in the logcat file (it's always e/ for error, f/ for fatal. those are the two main things that matter to me.)

    Code:
    D/dalvikvm(  871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
    V/AmazonAppstore.DiskInspectorServiceImpl(  871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
    D/AmazonAppstore.UpdateService(  871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
    W/AmazonAppstore.UpdateService(  871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
    D/dalvikvm(  890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
    V/AmazonAppstore.ReferenceCounter(  871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
    E/WifiStateMachine(  203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon 
    V/AmazonAppstore.UpdateService(  871): runUpdateCommand doInBackground started.
    V/AmazonAppstore.UpdateService(  871): Running UpdateCommand: digitalLocker
    V/AmazonAppstore.UpdateCommand(  871): Not updating key: digitalLocker from: 1334228488057
    V/AmazonAppstore.UpdateService(  871): Finished UpdateCommand: digitalLocker
    V/AmazonAppstore.UpdateService(  871): Running UpdateCommand: serviceConfig
    V/AmazonAppstore.MASLoggerDB(  871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
    V/AmazonAppstore.MASLoggerDB(  871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
    W/CommandListener(  118): Failed to retrieve HW addr for eth0 (No such device)
    D/CommandListener(  118): Setting iface cfg
    D/NetworkManagementService(  203): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
    D/NetworkManagementService(  203): flags <[down]>
    E/WifiStateMachine(  203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
    W/PackageParser(  203): Unknown element under <manifest>: supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
    D/wpa_supplicant(  930): wpa_supplicant v0.8.x
    D/wpa_supplicant(  930): random: Trying to read entropy from /dev/random
    D/wpa_supplicant(  930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
    D/wpa_supplicant(  930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
    D/wpa_supplicant(  930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
    D/wpa_supplicant(  930): ctrl_interface='eth0'
    D/wpa_supplicant(  930): update_config=1
    D/wpa_supplicant(  930): Line: 4 - start of a new network block
    D/wpa_supplicant(  930): key_mgmt: 0x4
    (mind you, that's 29 lines out of 1300ish, just for example)

    I then could do the following with logcat:
    Code:
    adb logcat WifiStateMachine:E -v long > name of problem.txt

    and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!

    How this relates to xLoud. (or any other problem we have with future updates.)
    Now, since xLoud is apparently causing all sorts of havoc including not granting root , screwing up volume & messing with equalizers, a logcat done the following way will help me immensely with figuring out how to go about fixing it:
    Code:
    adb logcat *:E -v long > name of problem.txt
    will print out all errors, fatal exceptions (what causes android to crash) that happen with the xLoud (or any other risky) update.

    my email (for sending me logcats): nielson.peter@gmail.com
    Complaints, requests for add-ons, stupid questions, or anything else I feel like will be deleted upon receiving it. Logcats will not.
    (If you wanna complain, request something or ask a stupid questions, that's why this thread is here)


    Regarding Nightlies:

    UPDATE:
    Everybody: Head on over here -- http://xdaforums.com/show....php?t=1661091

    It's the nightly build for R800 :D
    Pax

    UPDATE: Here is an update.zip file to automatically change any CM9 (AOSP ICS) based R800i download to work with the R800x (all thanks to KeiranFTW & Atarii for the fix)
    5
    saved for future use