Database Info

Possible Bluetooth Fix G2x - Works so far

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?

Let's recap the new update

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.

[Q] Phone turning off randomly twice a day using Android Revolution 1.1.7

Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!

Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8

adam_deluxe said:
Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!
Click to expand...
Click to collapse
Hi,
This is a kernel issue.
Try flashing the kernel in my sig using CWM.

Dacoit said:
Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8
Click to expand...
Click to collapse
I did. Thing is, I'm still a Junior Member, so I'm not allowed to post the experience I had or ask questions about it. I know, it's a ROM-specific question which belongs in the thread of the aforementioned ROM, but asking someone out of the to post it for me would have been about just as much annoying. Still, I'm sorry.
Still, it seemed somehow that no one reported the exact situation, as there were different solutions proposed. But - as I said - I couldn't even add anything to the discussion, since I'm not allowed.
I hope, it didn't disturb you too much.
Regards

Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
EDIT: The UI runs pretty smoothly now and my WIFI and mobile data are not lagging anymore. It MUST have been the kernel.

adam_deluxe said:
Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
Click to expand...
Click to collapse
Hi,
It worked for me,and I've had no black screens since.

Yes, reverting to RC Mix 2.3 solves many glitches IMO. Should do the trick while waiting for a better version.

[Q] Delayed Emails

I sometimes see mail arrive at my Gmail Apps account and it doesn't get delivered to the phone for more than an hour. Nomally it's pretty much "push". Is this just 'how it works'? :-(
Stock T-Mobile UK ROM: 1.47.110.3
Connected via WiFi (good signal and on 30Mbps cable connection)
Using stock GMail (not HTC) app on the phone

Hmm can't say I've any probs ...they mostly hit my phone before the PC even notifies me of them

WibblyW said:
I sometimes see mail arrive at my Gmail Apps account and it doesn't get delivered to the phone for more than an hour. Nomally it's pretty much "push". Is this just 'how it works'? :-(
Stock T-Mobile UK ROM: 1.47.110.3
Connected via WiFi (good signal and on 30Mbps cable connection)
Using stock GMail (not HTC) app on the phone
Click to expand...
Click to collapse
No, mine's near enough instant! (just tested it again to prove it)
although I'm on a lower build than you (1.36), although should be moving up soon.
with Gmail version 2.3.5 2549Kb
That was also on wifi.

Ah. Was on 2.3.4.1, having updated it from the market a while back, Market 'forgot' to tell me there was a further update. Gawd this phone is soooo unreliable in sooo many areas. I just never know what's going to stop working next requiring another restart. All-time longest uptime before requiring a restart to fox something or other I've discovered by accident isn't working properly is a little over 5 days. Complete poo, not really fit for purpose IMHO, and big mistake I'm now stuck with :-(
Anyway, thanks, will try that and thanks for the pointer

WibblyW said:
Ah. Was on 2.3.4.1, having updated it from the market a while back, Market 'forgot' to tell me there was a further update. Gawd this phone is soooo unreliable in sooo many areas. I just never know what's going to stop working next requiring another restart. All-time longest uptime before requiring a restart to fox something or other I've discovered by accident isn't working properly is a little over 5 days. Complete poo, not really fit for purpose IMHO, and big mistake I'm now stuck with :-(
Anyway, thanks, will try that and thanks for the pointer
Click to expand...
Click to collapse
Either you have a massive dud unit, or it's about time that you took the chance and moved to a custom ROM.
I've has this phone since April and have the exact opposite opinion! I've used LBC Mod since it was first available after I S-OFF'd and rooted my phone, I have tried the other ROMS all of which offer different things, depending on what you're looking for, but, for me coming from a WM Sense background I'm very happy with a "working" close to stock ROM that's stable reliable and ideal for daily use.
I'm also on T-mobile UK. Happy to point you in the right direction - if needed.

det66 said:
Hmm can't say I've any probs ...they mostly hit my phone before the PC even notifies me of them
Click to expand...
Click to collapse
Ah, now there's an idea. I'm going to try that. With a hammer!

In summary, this thread is trolling at its weakest.
WibblyW, please stop trolling.

zeekiz said:
In summary, this thread is trolling at its weakest.
WibblyW, please stop trolling.
Click to expand...
Click to collapse
Really, trolling? I have a genuine problem and got some genuinely good advice that may lead to solving it. Good on this forum!
... and I genuinely feel like hitting this phone with a hammer once in a while. So that comment was an attempt at some humour to lighten the mood. Sorry you were not amused.
I do find it interesting when some people find it offending in some way when someone is negative about their fav product - that's the whole "Apple fanboy" mentality isn't it? In another thread entiled "Lucky to have the Desire S" others have said I've just been very unluckly with this phone - and maybe that's the case...

When one has a problem, simply think OH NOTHING CAN BE DONE TO SOLVE MY PROBLEM, STORY OF MY LIFE, WHAT A WORLD, NOTHING EEEEHHHH-VERRRR GOES RIGHT FOR ME.
When some simple steps and questions could be bring upon the holy grail.
1. When was the last time my application was working properly?
2. What has changed since said period of time the email was working properly?
3. Is there a way I can go back to said period of configuration and see if it will work efficiently?
3a. After reverting back to said period of time, has this resolved my problem?
4. Is it a software modification that was made that could be causing this problem?
5. Is it a external source that could be causing my problem?
6. Is it a network issue with my service provider?
7. Is it a issue with my modem that I am connecting to?
The list could go on and on, but my eyes are rather dry, and I need to do a few things for tomorrow.

[Q] Problem with Samsung phone performance

Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.

What firmware are you running?
Is it the same firmware on both phones?
What is the launcher?
Have you tried a different modem?
Are you using a battery saver like juice defender?
Are you using an ad blocker?
Are you using a specific kernel? Oc? Uv?
Need for specific info

ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
You know, for the rather lengthy post, you really have not explained any detail about your issue.. You have a generic 'I have an issue, the Infuse sucks' post and its not going to help anyone resolve your issue. I find it EXTREMELY hard to believe that you have 2 infuses having the SAME EXACT ISSUE. Yes, there will be times when you get a defective phone or it isnt working up to your standards, but to have 2 defective phones with the same defect? You need to play the lottery. Also, i suggest you send the phones back. It sounds like youve already made your mind up and have pretty much bashed the samsung infuse in that entire post. The same samsung infuse that myself, and plenty of other people live with day to day and have absolutely 0 complaints.

I will give you $20.00 a piece for them!!!!

ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
Simple . Hack it and put cm7 on it if you really need speed. Maybe its your screen protecter. Wipe the screen off. Cm9 can be sluggish, for speed go to miui on gingerbread or cm7

Id be willing to buy one of the infuses
Trust me...sounds like you got two defective units...which like Scott, I find hard to believe...but hey its possible-idk when you got hem.but if it hasn't been a year then put them back to stock with gtgs unbrick and file a warranty claim with Samsung...the infuse is a great phone and I never had the problem you described...I do have a question though...did you get them both at the same time? Cause I don't see why you would get a second if your first was having problems
Anyways...if you wanna sell one hmu...I may buy one depending on the price and if I can get the money (I think I already may have one lined up for $170 just need to get the money)
Sent from my HTC PH39100 using xda app-developers app

Never really had any problems with samsungs beside the only issue I have ever had with ALL Samsung phones .. They have the worst RF signal/strength out of any company! I miss the days of my old Nokia RF ..
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Android Law #1: Costum ROMs are ALWAYS 10x better than stock.

Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium

Prometh1216 said:
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hehehe, what ROM u running?
Sent from my SAMSUNG-SGH-I997 using xda premium

qkster said:
What firmware are you running?
Click to expand...
Click to collapse
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
qkster said:
Is it the same firmware on both phones?
Click to expand...
Click to collapse
No
qkster said:
What is the launcher?
Click to expand...
Click to collapse
Both stock
qkster said:
Have you tried a different modem?
Click to expand...
Click to collapse
No, thought never occurred to me that I should look at this as a solution.
qkster said:
Are you using a battery saver like juice defender?
Click to expand...
Click to collapse
Neither.
qkster said:
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope
qkster said:
Are you using a specific kernel? Oc? Uv?
Click to expand...
Click to collapse
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
qkster said:
Need for specific info
Click to expand...
Click to collapse
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).

are you completely wiping before every flash youve done? have you tried a complete wipe and start from fresh?

ssa2204 said:
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
No
Both stock
No, thought never occurred to me that I should look at this as a solution.
Neither.
Nope
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
Click to expand...
Click to collapse
Task manager is NOT the best app to tell you what is running in the background.
Maps and other location apps may not be listed but will consume resourse that can be the cause of your lag.
The fact that stopping wallpaper or live wall paper off alleviate the condition may suggest that the phone is running at max capacity. Steps to reduce the load improves it. Live wp, facebook, maps, stock email and other device manager from stock att was one of the first @#$% I took out on any rom I run.
Having a large amount of apps installed can also cause this lag. The OS may only be able to handle so many.
Have a poor signal at the time of the call may also be an issue, especially if both of your phones have this issue occasionally but not consistently.
Lock screen can also be a factor. Some sleep setting may also cause the phone to wake up poorly. I get around this by turning off my lock screen. On the call settings, you can also change the answering options so that it will override others and make it easy to answer.
On any firmware - stock or modded, after you have the phone running for an extended period of time without a reboot, you may start to see some lags. This may be across all devices. You may need to reboot it occasionally or boot into recovery and wipe the cache.
These issues may or not go away once you have a device with more power or resources..ex: dual or quad core, 1gb or 2gb ram etc..my guess is when a device has more power, programmers will come up with more resourse intensive apps that may hinder the phone as well.
Lastly, pay attention to your battery meter. As the power dips below 30%, there are steps taken by the OS to conserve the battery. This may give you lags as well..possibly one of the reason why it seems random also.
If you wanted to test out the lag issue due to background apps, go to settings/account and sync. turn off background data. You will retain the (radio) phone and text but there will be no email/facebook, weather, widgets/market/amazon etc updates unless you manually update them. If this runs smoothly but lags when you turn it back on, you can start the process of narrowing down your culprit.
gl