Edit: renamed thread to more clarify what I'm after.
This is really just a follow-up for a poll to this original thread here in this forum.
I'm looking to see if definitive data can be collected as to whether or not the "reboot during a call" bug only started appearing after the 2.3.1 update or not.
Please don't answer the poll if you're not sure.
It's probably pointless, since Google's already working on it, but I'm curious.
Phone reboots during calls ONLY after 2.3.1 update
Phone reboots during calls BEFORE 2.3.1 update
Not sure if it rebooted on 2.3 or not, but it definitely reboots on 2.3.1
I am still on 2.3 and it reboots during calls
There's no option for me in the poll...
I'm still in 2.3 and without reboots. Yesterday I made a call of 27 minutes and everything was fine. I hope to continue without them.
Only a week ago that I have the Nexus...
I hope my contribution can be used to detect whether or not a software failure
nitsuajd said:
There's no option for me in the poll...
I'm still in 2.3 and without reboots. Yesterday I made a call of 27 minutes and everything was fine. I hope to continue without them.
Only a week ago that I have the Nexus...
I hope my contribution can be used to detect whether or not a software failure
Click to expand...
Click to collapse
Aw, nuts, I knew I forgot an option. /sigh
yup... i have not yet seen any reboot during a call
but maybe because my calls has not been long enough?
30 min was my longest thus far
So I should have added:
I'm on 2.3 and never reboot during a call
I'm on 2.3.1 and never reboot during a call
???
I was working under the assumption that the poll would be an idea to give those who are having the problem a way to say when it started; I think it can still be useful from that point of view.
I wasn't looking to rehash the thread I linked originally, just a tool to quantify when the problem started for those who have it.
I am also on 2.3.1 and have never had a reboot mid call, however i have had calls end randomly (and no its not a dropped call as i live in the UK, so no such thing)
Nexus S - 2.3.2
I just bought nexus s and today during my long call to a friend, it reboots 5 times...!!
Each reboot after different period range from 4-8 mins.
FYI, I was using speaker.
I have another nexus one for 1 year now and it never reboot during a call..
I never had a reboot during a call
how about a choice for:
'None of the above"
i still have yet to see a reboot on my phone
Related
My friend has the Nexus S and he says he has to reboot his phone DAILY.
Just wondering what other users' experience are before I take the plunge.
Neo3D said:
My friend has the Nexus S and he says he has to reboot his phone DAILY.
Just wondering what other users' experience are before I take the plunge.
Click to expand...
Click to collapse
I only ever reboot when I flash a new rom.
kenvan19 said:
I only ever reboot when I flash a new rom.
Click to expand...
Click to collapse
the same. only reboot to see a new bootanimation or when i do flashing/backup/restoring. other than that i dont see the need.
once a day to keep things under control
i never reboot but i do turn my phone off when im sleeping
I only reboot when new pics go missing in my Gallery or when Navigation crashes, which is about once a week.
depend
it depends...I only reboot if needed... hmm maybe 1 reboot every 2 days.
i started a thread called "what is your uptime" in the nexus one forums. at that time, my nexus one was running for 245 hours without a reboot (can see in the settings menu). that is about 11 days straight, and i regularly go longer, usually a few weeks between reboots. the other people who replied all had similar results and longer.
the android linux kernel is extremely solid and stable. without even trying, my phone runs for 3 weeeks or so without rebooting.
not sure about the nexus s, as gingerbread seems to have a few issues that froyo did not (when i started my thread).
as i type this post for example my up time is 230 hours. smooth as butter like always.
5 hours on mine
i usually only reboot when i flash something to my phone. that being said, generally im flashing things to my phone several times a day, every day. so im rebooting 2 or more times a day. there really isnt a need to reboot very often, but rebooting once a day will keep your phone on the quick side.
I reboot when i fix permissions, or flash rom or update or Kernel or whenever my phone does the random reboot bug.
I'd guess i never have reboot my phone because something went wrong, that i caused it to happen
I've never had to reboot because of a problem. Running stock 2.3.2.
My uptime is 25 hours at the moment as i updated the netarchy kernel to 1.2.7 yesterday (over stock 2.3.3)..
I had many reboots before the 2.3.3 update (not my choice the phone just did it often when on a call). But now its purely up all the time unless updating or playing about.
Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot
fix the a2dp on gb and i'll give you your first donation.
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..
Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.
So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium
ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?
No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?
After about one day of this GB update, what can we tell? Still any issues? Some people bricked their phones, so is there any idea why? Can we recap on what has been achieved this far? Are there any flashable ROMs with all good stuff?
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
aowendoff said:
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
Click to expand...
Click to collapse
Did you update the baseband?
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
For those who are still having problems after the update it might be wise just to do a factory reset because froyo and gbread is very different...
* GPS locks much faster now, often instantly, and indoors.
* Switching between 2G/4G seems to be smoother; doesn't lose the connection for a few seconds like it used to
htc2364 said:
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
Click to expand...
Click to collapse
I had reboot issues before and so far haven't had any, but to make a proper conclusion I'll have to wait, as even before the update sometimes I would make it days between reboots/shut offs and sometimes only hours.
GPS appears to be very good now, as for wifi/4g/2g I always turn off 2g and use only wcdma setting, and haven't had any issues with it, I leave my wifi and BT on at all times too even when not connected and don't have too bad battery strain.
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had, but there are a lot of camera apps (I love vignette) so that's not a huge issue, if anyone has the lg app I would love it back though.
I did have some sluggishness especially this morning, I downloaded some widgets though so it might be more of what I added than the update itself.
one surprise was that I thought it was supposed to wipe all data etc. from the phone, but everything was set up the same as I had it before with launcher pro, so I was happy I didn't have to start from scratch. Also I have been getting occasional force closes with launcher pro that I didn't have before.
as far as quadrant scores go I'm getting consistant 2600+ so that is good, I had Faux's kernal and OC to 1300 w/ pimpmycpu and was getting 2800-3000 so without OC I'm more than happy with 2600. Now if only netflix will make it's way to this phone as is, and hopefully we can root soon as i really want ROM Manager, pimpmycpu and a few other root only apps to work again! Love this community, everyone is so helpful and creative, keep up the good work.
GPS locks Faster
Google Music Beta offline feature does NOT work, won't download.
Android Market did not restore my previous apps.
Touch screen is still dodgy, sometimes requiring multiple touches.
Email, specifically @Live.com mail will not display junk mail. Other folders, yes, but not junk.
More frequent messages about Cannot connect to Server
Has anyone figured out why some people have bricks trying to update? To be honest I still hesitate to do the update because I still don't know why this happens
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
I think it's worth waiting for a rooted flashable version a day or two and to avoid any risks.
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
<nods head and ducks>
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
dmartin1976 said:
GPS appears to be very good now...
Click to expand...
Click to collapse
I wish that were true for me. As I've mentioned in other threads, I'm still getting 90-180 second TTFFs, which is about where I was with stock Froyo. I hope someone will reply to my question in the other thread about the system settings they have that give them such good results. I've fiddled with all of the ones in the hidden menu GPS Test section and haven't found a good combination (and I don't know what the factory settings are supposed to be any more); it's hard because of having to wait a few hours between tests to let the ephemeris data expire in the receiver so I won't just be getting a carryover hot fix.
dmartin1976 said:
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had...
Click to expand...
Click to collapse
Hmm, that's strange; I still have Gmail in the list of options for "Share" in the gallery.
As for the camera, I think I actually like this one better. At least, it seems to do a better job of taking close-ups with the flash. With the original LG camera, close-up flash photos were always blown-out and overexposed. I took a couple of test shots in a dark room with the flash, and they look great, about as good as you can get with an LED flash, I think.
JHaste said:
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
Click to expand...
Click to collapse
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
alodar1 said:
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
Click to expand...
Click to collapse
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
JHaste said:
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
Click to expand...
Click to collapse
So it seems some folks just had bad luck
krekabl said:
So it seems some folks just had bad luck
Click to expand...
Click to collapse
or the file they downloaded was corrupt? its not like we had an md5 to match...
JHaste said:
or the file they downloaded was corrupt? its not like we had an md5 to match...
Click to expand...
Click to collapse
well everybody updated the same source didn't they?
GPS locks on a lot faster...but still loses accuracy in middle of route.
Hi guys,
Right, so I've noticed that when making calls with the Sensation, if they are reaching the 10 minute mark, for absolutely no reason whatsoever the line will just go silent, before the call is dropped. The signal bar doesn't even change.
Has anyone else had this issue?
Cheers,
James
My phone also has dropped calls randomly but on random times I'm sure. Today it did it as well. I don't know why though. I hope to God its not a fault in the phone that can't be fixed with an update. I'd hate switching to s-on and stock recovery.
Sent from my HTC Sensation 4G using XDA App
random call dropping
Hi,
A complete n00b when it comes to Android and first post on this forum. Kindly excuse any inadvertant mistakes.
Thanks to the wonderful forum we have here, I managed to root and get the IC 2.5.3 ROM on my Sensation. And its working like a dream except for one small problem. Big problem really.
Calls keeps dropping, and there have been occassions where I was getting disconnected every 10 seconds. Patterns I noticed :-
1. Voice suddently drops. The call is still on and in about 3-5 seconds call gets disconnected.
2. This happens only in a wi-fi zone (mostly at home). When I am in a wi-fi off zone, this has never happened.
3. This was happening even BEFORE I flashed the custom ROM, (was hoping that the problem would be resolved), but no luck)
4. I suspect its because of an incompatible radio image in my country (India), but what do I know. Could a 4G enabled handset encounter such problems on a 3G network?
5. How can I get to know the best/most compatible radio image for my ROM . ( I searched, but nothing conclusive so far anywhere. I am not able to post in the developer thread because I am newbie )
Please help.
HTC Sensation
Insertcoin rom 2.5.3
Bricked kernel 1.5ghz
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Heuser1 said:
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Click to expand...
Click to collapse
Have never heard of that.... still have you tried a data and cache wipe in cmw? then install a rom on a fresh device? I know you will have to back up all your stuff but may be the answer.
Also try another modem may help. Im not sure since ive never experienced that but give it a try.
Heuser1 said:
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Click to expand...
Click to collapse
I can relate. I had the same exact issue a few days ago. I just flashed and didn't look back.. though I probably will eventually. Try Mitra, very good. I loved it. Experimenting with Caty's rom now. Good luck. Wipe/factory reset, wipe dalvik and fix permissions. Then flash. Let it sit for 10-15 before you start using it. Make sure it settles and gets used to, "it's native infuse guts," as EXPERIMENT put it.