Related
Didn't notice this before, but according to http://stats.cyanogenmod.com/ , there are two installs for 'daytona' (codename for Droid X2).
Also, cvpcs recently tweeted "i'll see what i can muster together. need to get some DX and X2 stuff posted".
Good news? Old news?
I didn't know they had even started on the X2, I knew the X1 already had it, or an RC at least.
cvpcs, who I believe ported CM4DX, just recently got the X2, but has been busy with life.
Also, the Droid X is becoming, or already is, an official CM supported device.
Before my brother got his X2, I was trying to get the CM7 build on it, but couldn't find the correct one on their site, this was almost 2 months ago though.
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
drapp said:
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Do tell plz
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
drapp said:
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
Click to expand...
Click to collapse
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
ericerk said:
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
Click to expand...
Click to collapse
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
drapp said:
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Yup yup xDD
---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
If you still have time to give it (X2) back i'd recommend it,Get a Bionic or something or the droid 3, something thats more popular, d3 has cm7 booting same with the bionic, don't lock your self in a crap phone if you don't absolutely have to...
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
2nd init for the x2 was created on GB. I believe our ATRIX ports use 2nd init. Naven and dragon just made them flashable in CWM by including the 2nd init hack in the flash.
drapp said:
Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Click to expand...
Click to collapse
the posted 2nd-INIT in dev section for us works on gb if that is what you are referring to.
About CM7 & 2nd-init
the 2nd init that is used for all motorola devices (except the ATRIX) for cyanogenmod is designed for both froyo and gb. It has a check in there to see if the executable bit exists and figure out what to do from there. that way any motorola device could (in theory) use it. I know that this version of 2nd init works for the X2 and will pretty much be used when it comes to porting over cm7. We're going to have to use GB as our base (not Froyo) simply because of the requirements of our kernel (which we can't change).
About my involvement
now i know that I was original one who was trying to crank out cm7 and that it kinda died out. that doesn't mean that i don't play around with it from time to time. I'm starting from scratch, but if naven and/or cvcps or whomever get it running before I do, more power to them. I have little to no time to work with this, but I know what approach i'm taking this time. It is to simply base it off the ATRIX (obviously) but then work in the 2nd-init and edify scripts that the X uses. I kinda did that the first time, but got too mixed up in all of the details.
I don't want anyone to think that because I'm working on it that any results will arise. I'm merely trying to say that someone is working on it. Just maybe not as fast or with as much time as you guys will like. I want to have CM7, too. But we don't have a team or anything so it takes a lot of work.
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
Here's a link to cvpcs blog entry regarding 2nd-init when he was porting CM to Droid X.
http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
2nd-init allows us to have a new init.rc script, not just scripts in general and in reality has no affect on init.d unless the init.rc script is told to do so. Basically 2nd-init kills the init process (and all spawned processes) that uses the stock init.rc and uses a new one which we copy during hijacking the boot process and starts the init process again.
The root directory (where init.rc lies) of our phone is writable, but is reflashed every time the phone boots up, thus erasing any changes we might have made to init.rc (kinda defeats the purpose of having a custom script). This script is the script that gets everything set up during the boot sequence starting roughly around the time the motorola logo first shows up and all through the boot animation. We need to have a custom init.rc to get our phone's environment setup for CM7.
Our problem arises when we have to have the script satisfy both the OS and the kernel. Motorola's kernel expects certain criteria to be fulfilled within the phone to allow it to do it's thing. If these aren't satisfied, the kernel panics and reboots the phone (hence why we get bootloops). We can use logging (a rather tedious, slow, and painful method) of finding out where the kernel panics, and adjust as needed. But we need to have the environment ready for CM7 also, so those changes need to be in there without causing a kernel panic.
"Heavily modified" is a bad way to put it, more like "non-BLUR." If we could get CM7 working we can use the init and build files/setup/etc to allow us to have more ROMs based of AOSP. MIUI is based off of AOSP and in theory if we figure out CM7 we can even have AOSP ourselves. In fact the ATRIX recently got a port of AOSP (albeit buggy, but still).
The link above to cvpcs's blog goes into the details about it. It's really good read.
dragonzkiller said:
The link above to cvpcs's blog goes into the details about it. It's really good read.
Click to expand...
Click to collapse
It is also written in a '2nd init for dummies' fashion. Don't be afraid to read it!
Sent from my DROID X2 using XDA App
I agree this phone is one big piece of poo!
SE7EN- said:
I agree this phone is one big piece of poo!
Click to expand...
Click to collapse
I don't remember seeing anyone in this thread say that. Who are you agreeing with?
Hi,
i took a look in the 2 custom rom (artic and FTS) and i can't find any kernel file (system/lib) is it because the bootloader is still locked?
Then i guess CM7 can't be ported without kernel file?
Yes, that's exactly what a locked bootloader entails.
Sent from my XT910 using xda premium
Ok thank you for the answer.
onslaught86 only answered part of that question.
The bootloader is locked, but that does not mean that CM7 can't be loaded.
You DO NOT need a custom kernel to load CM7. I have loaded CM7 onto 2x DroidX's and 1x Droid2Global that all had locked bootloaders.
There is no one currently working on developing CM7 for the RAZR though, so you probably will never see a port of CM7 for RAZR. What you will see very soon, is a CM9 port onto the RAZR.
CM9 is not "official" yet, so you probably won't see it for about a month at least.
To be honest, the implementation of GB on this phone is good enough, I have rooted my phone, frozen the bloatware with Titanium Back up, and loaded ADW launcher, and I haven't noticed much of a difference between CM7 on my old D2G and my current RAZR load.
Try that out, and you may be surprised. There are a couple of minor differences, no performance enhancements on the clock speed, no auto recovery reboot....etc, but to be honest, this phone is so fast, and with safeboot, I don't know that you really need it.
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Troider said:
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Click to expand...
Click to collapse
Bricking is pretty tough on this phone. I haven't heard of full on bricking yet.
Also haven't heard of a warranty being voided just for flashing ROM's, at least for HTC.
There is a Chrome APK in the Themes forum. Sideload it as the very first thing you do once you flash an ICS rom. After that you are golden.
Good Luck.
Anyone know when ICS is out for Motorola Razr?
What? You aren't going to find to many people in this forum that actually care about an ICS release for the Razr.
http://lmgtfy.com/?q=motorola+razr+ics+release
Kalger said:
Anyone know when ICS is out for Motorola Razr?
Click to expand...
Click to collapse
Try here... http://forum.xda-developers.com/forumdisplay.php?f=1361
Troider said:
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Click to expand...
Click to collapse
I am a almost 3 year Motorola user using that root/flashing/sbf process. I haven't went back to unrooting yet on my Rezound, but I can tell you it's a little more difficult to get rooted than the original Motorola Droid and the Motorola Droid X2 (which is what i upgraded from).
First you have unlock the bootloader. I did it the slow way step-by-step through HTCDev.com becuase the noob method wasn't working for me. After you get the files you need from the SDK Android app it's pretty much easy from there to unlock the bastard.
Flashing new roms is pretty similiar, but there's a hitch. Usually when you flash a ROM you have to flash a kernal that is compabitable with the ROM. Which means you have to do it in the bootloader instead of in Recovery. The only time you don't have to do this is when the ROM has a built in kernal (boot.img) and it almost flashes it for you automatically.
I'm very happy with my upgrade from the X2, but then again the original X had a lot more variety as far as development. The X2 wasn't very popular even though for a short while it was the best specced pure 3G device on Verizon when 4G LTE came out.
I've tried a couple ICS ROMs and for the most part they're pretty damn stable with a few bugs in them. Personally I like ROMs very polished with literally almost no bugs so I'm sticking with GB ROMs until something pretty polished comes out. I will be totally happy with my Rezound if we get a full or pretty close to a full AOSP ROM released under Ice Cream Sandwich.
If you have any other questions private message me. I've owned the Rezound for about a week now and have been happy with it.
Chrome shows in the market for ics running rezounds, no need to side load.
Sent from my Rezound using Tapatalk
Hello,
Not new to messing with the X2, but just recently started testing out the A5 of CM9 and had a question that I couldn't seem to find the answer to by searching.
I realize this is an Alpha release, but in coming from CM7 to CM9, BT Audio is no longer working the same. I can no longer use my car audio controls to skip tracks and the metadata is no longer being displayed, well actually it did once, then never again. The only thing that works is play/pause. Was just wondering if anyone else has noticed this, or if it is already in the works to be fixed. I would have posted this in the thread on the development section, but this is a new account, need 10 posts I believe. If anyone has any knowledge on the subject I'd be happy to hear it, otherwise I'll just wait for the next update and see if it works.
In the main thread, some people have had issues with audio players. You may want to try and download some other players and see if they give you the same trouble. Myself and many others haven't had any trouble at all. Kind of hit or miss.
I believe I saw in the thread for CM9 on the X2 that the cam corder was still not working correctly... has anyone tried using LG Camera for the cam corder? I had a Droid X which is now funct and was on CM9 for it and I could get the cam corder to work using LG Camera. I would post this question on that thread but apparently I cant since I don't have 10 posts yet...
Since I can't post in the thread I want to cause I don't have 10 posts yet I am wondering a couple things about getting CM9 on the X2 when it arrives. The OP for CM9 Alpha5 is sort of misleading... I have flashed a ton of roms on my X but the X2 seems like there is an extra step or two. Will I need to be on 2.3.4 or 2.3.5 before flashing CM9? I already downloaded BSR for X2, I see something about a patched BSR for CM9; will I need this if I coming from Gingerbread or just the BSR?
wolfballz said:
Will I need to be on 2.3.4 or 2.3.5 before flashing CM9?
Click to expand...
Click to collapse
You will need to be on 2.3.4
wolfballz said:
I already downloaded BSR for X2, I see something about a patched BSR for CM9; will I need this if I coming from Gingerbread or just the BSR?
Click to expand...
Click to collapse
When you are on stock 2.3.4 you need to use the original BSR for the X2 to flash CM9. AFTER you have installed CM9 you need to install the PATCHED CM7 BSR as the regular BSR will not work with CM9 (or CM7). I had this same confusion and what I did was make 2 folders on my external SD card labeled "Step 1 BSR" and "Step 2 BSR" to differentiate the two.
Hey guys, just jumped ship from Sprint and put an X2 on PagePlus. I'm on day 2 with this phone and it's not bad... I'm coming from an EVO 3d and was running MIUI latest.. I'm seeing with all the roms posted here they all have querks. I'm wondering if there are any stable roms that have fully working MMS, camera, vid cam, FM, sleep, etc? I'll keep reading on my own but just curious what you guys might recommend?
I'd love to be on a stable ICS build if there is one floating around.
This really belongs in Q&A. As far as REALLY stable stuff, your best bet is a GB rom like eclipse or CM7. Everything works really nicely on those roms. The CM10 rom that Dragonzkiller ported over isn't bad, but it's got its issues. Just check out his thread.
CM7 is VERY stable. I never ran Eclipse. I will say that I have ran CM7, 9, and 10 and also ran ParanoidAndroid on CM9 and CM7 is by far the most stable and snappiest. Unfortunately I do believe this phone is starting to become obsolete and work is starting to cease on making CM9 and 10 fully stable.
Eclipse 1.3 is rock solid and I get almost 2 days of battery use out of it with a few tweaks.
Agreed, Eclipse is the most stable and all-around polished ROM for the X2. CM7 is nice, but I use my HDMI from time to time and it isn't supported.
I think I have tried them all and for me Eclipse is the best. or stock. even those have some issues. Eclipse does a reboot occasionally say once a day or two, and it has a quirk about wifi that sometimes it just goes away until i open the settings then it connects again.
I have tried eclipse 2.3, cm7 and cm10. I had wifi issues with both cm7 and cm10. I have never had a problem with eclipse 2.3. Fully functionable. Fm, mms, camera, camcorder. They all work. As for issues with wifi. Never had any. Haven't experienced any random reboots. There are also plenty of themes via adw or Holo. It just takes time searching for what you like. I'd highly recommend eclipse 2.3 though.
Sent from my Eclipsed Droid X2 using Tapatalk 2
I just wanted to echo the votes above for Eclipse.
Personally, I think the older versions were slightly faster and better on battery life, but you really can't go wrong with Eclipse. v 2.3 has some very nice features, and I doubt you'll have many (if any) quirks with it. All the features work fine for me, with no problems. That includes all those mentioned (fully working MMS, camera, vid cam, FM, sleep) as well as HDMI, application install and storage on SD cards, etc. It's truly a wonderfully built ROM, and a lot of time has been put into making it fast, clean, and functional.
As several mentioned above, there are some other very nice ROMs out there, based on AOSP. These definitely DO have merit, but I'm not really sure if the people posting them actually read and understood the OP's question. "Stability" might be a subjective term, and in many respects those ROMS could be considered more stable than Blur or Blur-based ROMs, But it's misleading to say that those ROMs don't have glitches. AOSP ROMs have issues with MMS, camcorder, HDMI, etc. There are imperfect fixes and workarounds for some of these issues, but certainly not all.
I don't want to discourage you from trying CM7, 9, 10, AOKP or Paranoid Android ROMS. These are each amazing in their own rights. I just installed AOKP and it is absolutely beautiful!! It's smooth, and has many of the options I've always been looking for on this phone. The flip-side is that there are SO many things that just do not work or that have "quirks". Each of these roms lists the known issues, but with AOKP, I've found that there are pretty significant problems with all of the following: MMS, Google Now, input (keyboard) glitches, voice recognition/voice dialing, HDMI, SD-card apps (and SD-storage in general--don't expect backed-up app-data to be recognized by most programs), tethering (wifi-AP), camera, video camera, many apps have "texturing" that causes crashes (e.g. chrome), etc.
But I think it's important to note that DESPITE all these significant problems, the OS is so amazing and fast and beautiful, that it is really hard to decide whether or not to switch back to Eclipse, especially since it doesn't seem to have been updated in a while (at least based on the xda post...not sure about twitter and nitro's eclipse website)
Good luck flashing (ROMs) and have fun!
I've tried them all and suggest that you do the same and find out what suits you best for me it's cm7 but I do keep nanos of them all in case I start having flash withdrawals or find a new mod to try
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
ive tried most of them and cm7 is probably the most stable. Im running cm10 right now and it runs pretty good considering the circumstances. yes the x2 is becoming obsolete but its still a good phone with good hardware, unfortunately its true potential is locked in a cage.
Thanks for all the replies guys, I flashed Ecplise and played with it for a bit and not bad. I played around with SBF which is a new concept to me coming from yeaaaars of HTC devices.
I can't get CM10 to install I think I need to SBF to 2.3.4 before BSR. In recovery it says the zip is invalid.. I even tried downloading it again. I'll keep messing with it but yeah, trying every rom I can that looks promising.
Right now I'm back on stock rooted (nandroid backup) of 2.3.5
Last question, does data tether work if rooted?
Most roms have it baked in so yep
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
Hurry take it back!!!
Sent from my Nexus 7 using xda premium
sledwrecker said:
Thanks for all the replies guys, I flashed Ecplise and played with it for a bit and not bad. I played around with SBF which is a new concept to me coming from yeaaaars of HTC devices.
I can't get CM10 to install I think I need to SBF to 2.3.4 before BSR. In recovery it says the zip is invalid.. I even tried downloading it again. I'll keep messing with it but yeah, trying every rom I can that looks promising.
Right now I'm back on stock rooted (nandroid backup) of 2.3.5
Last question, does data tether work if rooted?
Click to expand...
Click to collapse
You must be on 2.3.4 for cm10 to work. Eclipse is the only rom out there that requires you to be on 2.3.5.
Sent from my Eclipsed Droid X2 using Tapatalk 2
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
Also tethering does work if you're rooted.
Sent from my Eclipsed Droid X2 using Tapatalk 2