Database Develop

Signal Problems on Custom Rom

Alright,
First, Here is what im using currently:
My Own Rom
-Cooked with Dsixda's kitchen
-Based on rdannar's Barebones 10e froyo rom
-With my own custom bootanimation
-Go Launcher instead of SonyErricsson
-some various build.prop tweaks [hsupa cat.,lcd density(changing quite often so i can use a lower density and still use the market... ugh!)]
-And bedwa's thrillz v3 kernel cooked in
And my issue is:
At random times i will have a complete loss of service. Usually what happens is, im texting someone back and forth and when i go to text them back, my text wont send! so, i retry sending... doesnt work. Usually the only way i can make it work is to reboot, however a few times putting it into airplane mode and then back out has worked.
Now, i know what your thinking, its probably my rom... But i am fairly certain i had this issue when i was using just the barebones 10e rom, and i cant remeber exactly but i think i had the problem once back when i was on gtg465x's thriller v1.1.0 rom with my own OC kernel.
So, basically im just curious if anyone else has had this problem as well, or if anyone has a fix for me?
anybody who wants to post their:
-APN settings
-build.prop network categories
-and other build.prop settings
-or anything else
would be appreciated.
thanks

Had that problem
On every rom
Sent from my GT-I9100 using xda premium

Sounds like it could be many possible things... Myself I'm on Roadrunner and whatever beta kernel I'm tweaking with my Thrillz line (Currently on BetaV4.) and I haven't had any issues. Then again I'm not sending SMS/MMS. I do all of that through Google Voice as I have SMS blocked. (old UNL Data FTW)
Is it primarily when sending SMS or MMS?

Were you able to fix it ever rdannar?
I do a lot of texting so typically yeah it is when im using messaging but I'm pretty sure that a few of the times it has just been when trying to use the browser...
Usually happens once the screen has been off for a while, then I turn it on, try and use an app that uses data, and then it it just never connects... until I restart.
Sent from my LG-P925 using xda premium

Another question is have you guys tried one of the 920h basebands as well. I have a signal drop on rare occasion, but nothing truly affecting service. It has to be one of 3 factors. Kernel, Baseband, Rom.

I have tried everything except 920h... people have always reported signal drop with this device. The hard part is it only uses hspa + so it doesn't usually catch 3g signals much.... at least that's what I've read about... try and take out hspa and network tweaks out of the build prop to see if that helps
Sent from my GT-I9100 using xda premium

Hspa+ is nothing more than a network improvement on UMTS (Standard 3G). It almost sounds like the radio.

Yeah I don't know why, but every custom rom I've tried on this phone has crap signal.

Dec 14
On the 14th (wednesday) im gonna start chasing down the cause of my signal problems using some of your suggestions. I have to take my finals and finish up some final papers then i'm going to dive back in to trying to help make the thrill awesome.

bzlmnop said:
On the 14th (wednesday) im gonna start chasing down the cause of my signal problems using some of your suggestions. I have to take my finals and finish up some final papers then i'm going to dive back in to trying to help make the thrill awesome.
Click to expand...
Click to collapse
Good luck with finals and we'll be here

I think i figured it out!
So, finals went well... (i think), I still havent gotten my grades back...
But, i wiped data/factory reset, wiped cache, and wiped dalvik. Then flashed the latest Doomed froyo w/ OC (thanks Urabewe) just to have a fresh start. Finally, i started playing with the build.prop network tweaks and almost everything i did had a negative effect on network speed and consistency of the connection. [also, im pretty sure the doomed build.prop did not include any of the common network speed tweaks, i.e. hsdpa cat, etc.]
So, in short, i am pretty sure the build.prop stuff was my problem.
However, i am going to continue testing various ro.ril build.prop tweaks and various apn settings; to hopefully find out what build.prop tweaks will have a negative effect and if any will have a positive effect, and what apn setup works best. I will post anything significant i discover in this thread...
Thanks for the build.prop suggestion, i had suspected that was my problem...

Anything not work in the new leak?

Since upgrading will take you off the upgrade path, I was just wondering if there is something on the new build that isn't working.
Like camera, video, data etc.

Honestly, I wouldn't jump on it unless you really need it (I've heard it makes GSM work a lot better). AFAIK, it hasn't even been rooted yet, which means you are giving up a LOT just to get ICS, which you can do from the stock rom and safestrap.

If you root just before flashing and use voodoo rootkeeper you can keep root. I unfortunately forgot to re-root after I needed to flash SBF (wouldn't update). So far everything works for me. Well except root that is. But to tell you the truth. I only used root to change the build.prop and have write access to system (notifications etc). Owh and freeze apps. But thats it.
So far so good! The battery won't last as long as on 219. But by how much I'll have to test. On 219 I ran in 2G mode all the time. So it isn't a real fair comparison. Yesterday I turned off all sync and push and disabled some applications. So we'll see how long it will last today.. I took it off the charger around 07:50 AM. So don't expect an update 'till tomorrow. It's only 08:50 AM where I live .

For the gsm users i recommend this update if you can go with no root
The rom is actually more responsive and most importantly, it dun drop the line that often
And ics with WORKING camera & video, not much is missing actually

According to this, you can keep root if you install OTA Rootkeeper, back up root, temp unroot, restore root, and THEN apply the update.

I updated and kept root and am very impressed with every aspect of performance on this build.
Battery life the first day was excellent, above average considering I was playing with the phone a lot.
Radio performance on VZW's network with this new baseband is exceptional.
Data throughput and transitions from cellular to WiFi and maintaining data connection were all distinctly improved. I am in a marginal 3g only area where I live and work 90% of the time, but I can go a few miles away to get LTE coverage.
While I cannot openly recommend flashing non revertable leaks to anyone, I cannot say enough about how much I am enjoying this build right now. I have yet to find any downside beyond the fact that we have no full firmware files for this build yet.
This is a superlative build and anyone willing to accept the risk should not be disappointed.

25 hours later there's 30% battery remaining. Made 5 1-minute phone calls. Played about 20 minutes of 3D games. Used internet a couple of times (checked email, whatsapp, some internet apps) and I would say at 90% 3G connection. So that's not so bad I would say.

Stuff not Working
For me, my Facebook app (built-in) is not working, and constantly crashes. I finally disabled the app completely to stop getting the crash pop-ups.
Also, built-in MotoCast disappeared, and it does not show up for me in the Play Store (probably because they have not released an ICS version of the app for non-tablets yet in the Store).
Other than those 2 so far, everything I have tested and checked works like a dream come true.

Everything is working great for me. The ota rootkeeper worked as well. Im running the leak with root.. the facebook app that came on the leak needs update. Its an older version. May be the reason
Sent from my DROID4 using xda premium

Anyone else have problems with the headphone jack not working?

Everything seems to work fine for me so far.
Motocast is built in to "My Files", "My Gallery", and "My Music" now. I just installed it and seems to work fine.

Negative. Just drove 20 hours with headphones on.
Sent from my DROID4 using xda premium

What's the battery like for GSM users on 3G with the new leak?
Sent from my XT860 running ICS

I also am having problems with the headphone jack. Is there a fix for this?

mcochon said:
I also am having problems with the headphone jack. Is there a fix for this?
Click to expand...
Click to collapse
Please be more specific about the headphones.
I haven't had any issues with Klipsch X10 headphones at all, but mine is only a 2 prong headset, without microphone or call control features.

I've had some odd headphone issues and I am NOT on the leak.
I'll plug in headphones, but the phone won't switch from the loudspeaker to the headphones. Unplugging and replugging the headphones in usually fixes the issue. Kind of annoying, but I use headphones so infrequently on my phone anyway that I haven't done any hard investigating on whether it is a software or hardware issue.
I'm leaning towards hardware though, because IIRC it happens on stock and the GB-ICS frankenbuilds.

This may be a stupid question but does anyone know if there is going to be a way to reverse being taken off the upgrade path? Im new to the forums and I just started getting into rooting and flashing roms. Im running a nightly build of the aokp ics with cm9. Im happy with it so far but would love to use my camcorder again lol. Are there any other issues with this version of ics?

I dont know about reversing the upgrade path but i do know that everything works really great on my d4 running the leaked ics.
Sent from my DROID4 using xda premium

anon117 said:
This may be a stupid question but does anyone know if there is going to be a way to reverse being taken off the upgrade path? Im new to the forums and I just started getting into rooting and flashing roms. Im running a nightly build of the aokp ics with cm9. Im happy with it so far but would love to use my camcorder again lol. Are there any other issues with this version of ics?
Click to expand...
Click to collapse
You SHOULD be able to get back on the upgrade path using the same method others have used to go from the .200 ICS leak to the .206 ICS leak. That involves a partial flash of the .219 fastboot file to essentially trick the update into thinking you are still on .219. But there are no guarantees.

I see. Thank you for your input. One more thing does anyone know if the gummy rom has been updated? I was using it for a few days but decided to go to the aokp for better 4g functionality.

[Q] Noob with unanswered questions

I've just ditched the BB (hooray!), have rooted and flashed CM9 and working out what to tweak next... I HAVE read loads of posts but still have a few questions.
1. Modem.bin files : there doesn't seem to be a list of differences, and people says some are better than others. I flashed XXKB3 and it works well. Better than others, I don't know. Does anybody know what differs in the versions?
2. GPS - Is there any way to fix the poor reception (have Fasterfix). Anyone modded the aerial or similar?? Otherwise can recommend a good GPS puck for the car
3. Supercharger V6 - yes or no? I only get redraw a bit, but always with Firefox Beta so maybe it's just that app. I understand the principles behind it, just not whether it is worth bothering on the I9000
Thanks so much (in advance) and to everyone keeping the I9000 alive and up-to-date. Still a fantastic bit of kit even if 2 years old!
H.

1. The difference is that some modems have better/worse signal in certain locations. E.g i live in Europe and i might get 1-2 bars with one modem and full 4 bars with another.. so just test them out to find an optimal one.
2. Dont know anything bout this, i think it varies between different roms. But i dont personally use gps that much that i have a need to figuree it out.
3. Definately install V6! I got to a point that i had constant redraws and the phone started to lag, etc. Installed V6 and working sooo smooth now also the dev has made an additional 3g booster script, this worked good for me also, though the speed increase wasnt very big but even an slight speed increase isnt bad , eh?

[Q] Trouble with no calls or text

My girlfriends D3 has gradually been getting worse with poor reception, dropping calls, not being able to make/receive calls or texts.
Data seems to work fine. This weekend it just finally stopped being able to make calls or send texts from our home.
If i drive a few miles down the road or to a higher elevation i was barely able to call *228 to update roaming.
I can still use the browser over 3G and Wifi, just no tethering, phone or text.
The phone shows 3G and a full signal, but as soon as i initiate a call it drops to 1 bar.
Another thing we noticed this morning is that when calling the phone it goes straight to voicemail.
I had tried changing the Network mode from Global to CDMA yesterday and at one point got an error message saying "No CDMA networks were found. Would you like to switch to Global Mode?"
Phone has been rebooted and battery pulled along with some other diagnostic tests that the verizon techs did over the phone yesterday.
The only thing i had done to this phone was i applied the TBH tethering hack without root over a year ago. It worked fine up until now.
The phone has the latest System version 5.7.906.XT862 and the latest Baseband N_03.18.32P.
Im thinking of reverting the TBH Tethering hack back using the instructions in this post
I spoke to Verizon tech support yesterday and they said there was some trouble in our area, but my Droid X is still able to connect so i doubt thats the issue.
Does anyone think that an OTA update from Verizon may have screwed something up due to the TBH hack being applied?
The GF is frantic about getting her phone back. I can take out insurance for 6.99 pr/month and pay $100 to get her a new phone, but if reverting the TBH hack and maybe rooting and installing a new ROM might help, im all for it.
Any thoughts? ROM advice? Was reading up about the AOKP Build 40 ROM, but wondering if all the hoop jumping will help or if the D3 has a hardware issue that has just got progressively worse.
Wont you help a poor guy keep the peace with his lady please?

I don't think it's that. It's possible that the 3G in the area is good but 1x is crap. 3G is just used for data while calls/texts are used on 1x. What is the PRL versions your phone and her phone have?

MrObvious said:
I don't think it's that. It's possible that the 3G in the area is good but 1x is crap. 3G is just used for data while calls/texts are used on 1x. What is the PRL versions your phone and her phone have?
Click to expand...
Click to collapse
My Droid X running on VXLR V2.2.0: PRL 53018
Her Droid 3 Stock w/TBH Tethering Hack: PRL 52996
Just tried updating them both and the PRL's stayed the same.
About an hour ago i was in the middle of backing up her phone and it started ringing. I was able to answer the call and now im able to make and receive texts and calls. There must have been a tower issue. The signal still drops to 2 bars when i initiate a call, but at least its working again.
She says its been flaky for quite a while with dropping calls and texts not getting sent. Im all backed up and was thinking of rooting and trying a ROM on this. Not sure if itll help with signal issues, dropped calls or texts not being sent or received.
She was also complaining about the thing pocket dialing, and other random stuff happening like her browser launching and texts being sent etc. I saw it this morning. I picked up her phone to bring it downstairs and saw that there was a text reply box open with a bunch of jibberish typed in it. She says that sort of thing happens all the time.
Think maybe a good stable ROM might help?
After a little more research i came across Minimoto here at XDA. Minimoto Link
Seems to be the way to go if im sticking to a GB ROM. I see you contributed some to it. Would you happen to know where some step by step instructions for getting it installed on a non rooted D3 might be?

1) Root it.
2) Install Safestrap 3.05.
3) Reboot to it, create ROM-Slot 1.
4) Factory reset and wipe cache and delvik.
5) Flash the ROM.
6) Set her up with goodness.
Though if random crap is popping up, I suspect the digitizer is flaky.

MrObvious said:
1) Root it.
2) Install Safestrap 3.05.
3) Reboot to it, create ROM-Slot 1.
4) Factory reset and wipe cache and delvik.
5) Flash the ROM.
6) Set her up with goodness.
Though if random crap is popping up, I suspect the digitizer is flaky.
Click to expand...
Click to collapse
Have you heard of digitizer issues with D3's before?
Any recommendations on which rooting method to use?
Do i have to remove the TBH Tether hack before rooting, installing Safestrap or Flashing the ROM?
So i take it your in agreement that this would be a good choice for a stable no frills GB ROM?

the random stuff can be from from a bad digitizer, dirt/grime on digitizer/edge or a software conflict
try cleaning screen around the edge, and/or flash rom/sbf
you need to remove bootstrap before safestrap, tbh hack should be fine
i haven't use minmo, but many have, also you could look at
http://forum.xda-developers.com/showthread.php?t=2106722
use the Deodexed ROM (Courtesy of thingonaspring) link

sd_shadow said:
the random stuff can be from from a bad digitizer, dirt/grime on digitizer/edge or a software conflict
try cleaning screen around the edge, and/or flash rom/sbf
you need to remove bootstrap before safestrap, tbh hack should be fine
i haven't use minmo, but many have, also you could look at
http://forum.xda-developers.com/showthread.php?t=2106722
use the Deodexed ROM (Courtesy of thingonaspring) link
Click to expand...
Click to collapse
Thanks sd_shadow I think ill stick with minimo most likely. Too many dam ROMS to choose from!.
Ok so from the hours of reading i did yesterday, i found a working link for motofail. It appears it is the best (or only) way to root the D3 if on 906.
From there i thought i could just install Safestrap 3.05 which i managed to track down as well.
I never installed Bootstrap, so does this even apply? Is there a factory bootstrap included with the D3?
I believe i read that minimoto has its own tethering feature included. So are we sure i dont have to revert the TBH tethering hack?
Some great links in your signature by the way. If the digitizer keeps acting up, i may try replacing it. I did clean it last night and will see if things improve.

LOTL said:
Thanks sd_shadow I think ill stick with minimo most likely. Too many dam ROMS to choose from!.
I think your the only person to say that for the d3 lol. Most of us are flash- a-holics and we love lots of roms to chose from.
Ok so from the hours of reading i did yesterday, i found a working link for motofail. It appears it is the best (or only) way to root the D3 if on 906.
From there i thought i could just install Safestrap 3.05 which i managed to track down as well.
I never installed Bootstrap, so does this even apply?
Just install safestrap on your safe system after root don't worry about bootstrap.
Is there a factory bootstrap included with the D3?
No
I believe i read that minimoto has its own tethering feature included. So are we sure i dont have to revert the TBH tethering hack?
No you do not have to undo the tether hack it is a hardwear hack not a software hack and will work on any rom no matter if the rom already has tethering in it.
Some great links in your signature by the way. If the digitizer keeps acting up, i may try replacing it. I did clean it last night and will see if things improve.
Click to expand...
Click to collapse
Sent from my DROID3 using XDA

replacing the digitizer is a pain
some [how to] links in my list

[Q] No 3g with CM 10.1 plus some other less severe issues

Greetings,
Just a few days ago I installed the most recent CM 10.1 nightly, first 20130319 and now updated to 20130323. For the most part, my phone is working well, but I do not have any 3g data service nor have I had it since installing CM 10.1.
I have a Droid 3 XT862 being used in the US on Verizon's CDMA network and placing and receiving calls works. I *can* send and receive SMS as well, although in a test I did toay I sent very short 25 character text from my Droid 3 on the Verizon network to another Android device on the Sprint network and it arrived a mere 2h15m later.
I have read many messages on this forum and others, but either the problem addressed is too far removed or the ideas/changes suggested are offered with little explantion as to why, so I am unsure if making any of these changes would be a good idea. I did read through the build.prop on my device and it certainly appears that it is more or less configured and ready for CDMA usage. I have performed a *228 PRL update, but it did not appear to help. CM 10.1 makes available, unlike the stock ROM, a menu/page full of mobile network settings. I have tried to work with some of these settings, toggles, preferred network types, and so on, but again none of these changes seems to have had an effect on my 3g data connection.
Am I doing something wrong? Does anybody know how to fix this? Or perhaps it is a new/temporary bug in CM 10.1?
As for the operation of everything else under CM 10.1, I like it very much. It is a very big step up from before, when I was first using stock Android 2.3.4 followed by the Maverick ROM, which, while better, sure liked to crash/reboot when under memory pressure. I do have a few issues that I hope others might be able to help with:
* The hardware keyboard's ALT key does not appear to work anymore which rules out half the symbols on the keyboard, making it far less useful. I also cannot use it any longer with VX ConnectBot as some of the mappings do not seem to work. For example, the "OK" key used to work as a CTRL key. Maybe these are related? Any idea how to fix this?
* The backlight on the hard buttons and on the keyboard was, previously, triggered by a light sensor (I think). Now the backlight comes on when there is any tapping, swiping, or button/key activity. That's fine, except that the timeout for the light is extremely short, on the order of about two seconds. In a dark environment, this can be annoying.
* It's slow... my god is it slow! I think this is due almost entirely to a severe lack of free RAM on the device, but I don't know what to do about it. Some programs, like GMail, take forever to start, while many others are just very slow to use/respond. I see the "Not Responding" popup appear *much* more than ever before, but, as I know these apps are just slow and not dead, I always just tap on "wait" and go on with what I was doing.
I really don't think I have that much running in the background or foreground to use all of this RAM. I have replaced Trebuchet with NemusLauncher in hopes of freeing some memory. I have three widgets only: a clock/weather widget, the standard calendar widget, and the Google Voice inbox widget. In the background, besides whatever Android and CM run, I have Google Voice and imo (the instant messanger) running. I believe that is it. Is there *anything* I can do to improve the speed issue? I understand how Android handles memory, so it is clearly not about just increasing the "free RAM" value. That said, however, it seems that if there were fewer apps trying to use the limited memory then this would naturally be higher to begin with.
I have a decent collection of apps, but the number is much smaller than in the past and most all of them should remain dormant unless I actually run them... or so I believe.
Okay, so those are the issues. I could add battery life and the camera to that list, but I have read on the forum that, no thanks to Motorola, the camera is unlikely to be available anytime soon, and I have also read that the battery issues should be resolved soon.
So, um... please help! And great many thanks to all of the hard working devs who bring us better software and especially to those who help those of us with devices that are practically *new* and yet abandoned by the carriers. Extra kudos to those finding ways to work around locked bootloaders and proprietary binary blobs.
--John Gruenenfelder

Can you force it to EVDO only? And what happens in a stock ROM?

In the mobile network settings page, as mentioned above, I can, and have, tried many of the options. Among them is the preferred network type.
It defaults to 'global' which actually sets it to LTE/CDMA, though this is not an LTE device. I have tried all of the options that make sense (i.e. nothing GSM related). I have tried Evdo-only and currently have it set to 'CDMA/Evdo auto'.
None of these settings has changed anything. To test, I disable WiFi and see if I have a Net connection.
With the stock ROM, as well as the Maverick ROM, when I have 3g, the letters '3g' appear in the status bar next to the mobile signal strength icon and there are two small arrows to indicate I/O. This is what I expected to happen with CM.
-Sent from my XT862 using xda app-developers app

I have a 3g update, but no solution yet.
In the mobile net settings page I have the network set to 'CDMA/EvDo auto'. Then I turn on airplane mode to force the radio off, then turn airplane mode back off.
The radio comes back and as it does I can see the network strength icon briefly add an R, presumably meaning reconnecting, followed by a 1x, and finally by a 3g. Then the 3g disappears. This entire sequence takes only about 3 to 5 seconds. If I do this while viewing Settings->About->Phone, I can see the current radio/network states change. Of course, I do all of this with my local wifi connection off.
Also, I did try a network type of 'EvDo only' and the above sequence still occurred but without the 1x step. However, this sequence didn't seem to occur as reliably as when the network is set to 'CDMA/EvDo auto'. For reference, the phone info page under settings indicates that this phone or network is 'CDMA - EvDo rev. A:6'.
So, it would seem 3g is at least possible, if fleeting. What should I do now? I really don't want to stop using CM 10.1.
--John Gruenenfelder

Same issue here. No 3g. In the system status, it will briefly show the mobile network status as "connecting" then drop back to disconnected.

If you reboot into stock it works right?

MrObvious said:
If you reboot into stock it works right?
Click to expand...
Click to collapse
Me or rocksolid99?
In my case, I, well, did not follow the correct Safestrap update procedure when I went from 1.x to 3.05. As such, I *think* my stock ROM may be slightly hosed. I *do* have a complete backup of the original stock that I created with Safestrap 1.x, but 3.05 does not "see" it when I tap on the "Restore" button in recovery. So, I have it, I'm just not sure what I should do if I really need to restore that backup.
However, I have installed the Minimoto 1.7 ROM into slot 2 in Safestrap 3.05 and if I use that ROM (which is a super stripped down Droid 3 stock) then 3g works just fine. I did not have any network/connection issues and did not need to take any extra steps to get 3g to work.
--John Gruenenfelder

I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium

Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Click to expand...
Click to collapse
Really? Good to know. Thanks for the info.
If I might reiterate on my other CM 10.1 problem, they keyboard? Right now, the ALT key does not work which means that I cannot access most of the punctuation keys. Strangely, in many apps when I press ALT I will see the cursor change with the upside down triangle at the top of the cursor bar indicating that ALT has been pressed. Good, but if I press any other key it is not recognized. It is as though I had not pressed anything. The ALT indicator doesn't even change or go away. The only thing I can do is continue to press the ALT key to cycle through its states (off, one-key, locked). Could this also be a bug in CM 10.1?
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Thanks again!
--John Gruenenfelder

JetpackJohn said:
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Click to expand...
Click to collapse
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Click to expand...
Click to collapse
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.

doogald said:
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.
Click to expand...
Click to collapse
+1 anything above gingerbread is not stable. Some people manage to use them for daily drivers but they have to deal with the bugs. Myself, I need a camera and I need my phone to work all day, I use it for my job. As such, I run minimoto, as it is quite stable, and any bugs that do arise can be dealt with as it's based on gingerbread, which is stable on our devices. Liberty is also a good rom to use, it's based on an older system version but it's quite stable and has lots of features, as opposed to Minimotos minimalist goal.
Sent from my XT860 using xda premium

has anyone tried making a swap partition for cm10.1 ?
I made it and it seems to be much much faster or the latest nightly (04/07/2013) is quicker.
anyhow I have it up only for about an hour it remains to be seen during the day how it's reacting
regards

Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Have you (or has anyone) successfully booted CM10.1 on the XT860? I just get bootloops after install. MiniMoto has been working great for me though.