Related
Hi All,
Im having a very frustrating time with my back button, this doesnt seem to be Rom or Kernal caused so im just wanting to see if it is a common Mez prob or if i might have a hardware glitch? My back button just seems to randomly start activating, no set pattern sometimes just one step sometimes several. I thought for awhile that i just had an over sensitive screen response but it will do it occasionally when im not even holding the phone. Not app dependent either. I am currently running EF 3.4.1 with the EC01 radio, but it has done the same thing on EC10 PNP and SFC 2.9. Any info would be greatly appreciated.
BTW: have tried FR and Reboots many times to no avail, prob with haptic?
I give up I,m stumped
I have been putting up with the same problem for about a month now. Doesnt matter what Rom/Kernel/whatever I am on, even happens in stock. Thinking about just returning it, but this is the one they gave me last time I did, hate to see what is next.
Note: I have noticed this happens a lot more on 3g than WiFi. Something to do with spotty reception?
Have you cleaned your phone around the Back button? If you've got gunk on your phone it can cause issues with these touch displays and soft keys.
Yeah I thought about that and did clean it unfortunately still happens. Thx for the response thou. I'm beginning to think I have a hardware problem, if not I will just have to live with it.
Sent from my SCH-I500 using XDA Premium App
I too have this problem. It does get annoying every once and a while but It doesn't happen to often.
I have had an otterbox case on so my buttons are clean I thought it might have been the screen protector on my case casing it but now that i hear other people have the same problem idk.
Yeah, it happens to me sometimes too. Usually when I'm at the home screen, and I try to lock it it takes a screen shot. If I just tap the back button a couple times or seems to stop. Its annoying, but it doesn't happen very often.
Sent from my SCH-I500 using XDA App
Talked to uscc cs (nicest people I've ever had the pleasure of talking too) yesterday and I don't know if it is a known prob or if its just a company that likes to keep long time customers but they r sending a replacement out Monday.
Ill tell you one thing, not bad mouthing any other carrier but short of free phones and free service for life as long as I live in uscc coverage area nothing could get me to switch!
Sent from my SCH-I500 using XDA Premium App
Yeah, got my replacement coming also. Second phone in about a month, no questions asked, great customer service!
This has happened to me for a while. In trying to discern any sort of pattern I've noticed it happens the most in my web browser (Miren), but that by no means is it restricted to that app. I've also been unable to narrow down any triggering factor - it seems to be totally at the phone's whim.
I can also say that this is my second Mesmerize with this issue, so I suspect it's simply something about the Mes's hardware that causes this problem. Must be something about the way it's designed.
Very annoying.
I have had this problem from day one with this phone. I have since gone to many different roms and kernels and never have had an improvement, even with USCC stock updates they came out with. My brother and 3 of his friends and 1 of mine that have this phone also have the same issue and half of them are stock and untouched 1 or 2 even running 2.1 still. My girlfriends son has a Fascinate with verizon with the same issues. I was just on vacation this weekend with some friends and one running another touch screen phone from Samsung on USCC network with also the same issue and his is not even a Mes. I think this is a samsung issue and it sounds like they may have used similar if not the same hardware in different phones.
First off I want to start by saying I have flashed my rom to Bamf 1.5 remix. I do not overclock my phone however I have tried limiting my clockspeed hoping to prevent a reboot. The phone did not start the random reboot until I flashed to said rom. I have tried reflashing but no improvements, any ideas?
Sent from my ADR6400L using XDA App
It has happened to me but I believe it just me OCing, flashing back to the kernel that I was using before when my phone was stable and testing it out. If not, I will just go back to 1.5
Also, does anyone know how to edit the power control widgets in the pulldown? I can't find any options. Thanks.
Did you flash the new radio when you loaded up BAMF 1.5?
If so, there's your problem
Happened to me with BAMF 1.6 and leankernel 192X, but only when I set it to ondemandX thru SETCPU. Other than that I've had no reboots.
sent from my BAMF Thunderbolt!
eschelon said:
Did you flash the new radio when you loaded up BAMF 1.5?
If so, there's your problem
Click to expand...
Click to collapse
^^
yeah its pretty common for people who flashed the new radio to have reboots. i have had some of those issues, i found that using different kernels at different clocking speeds made my phone more stable. NOTE: i am not a pro, just something i noticed.
What's really behind all the random reboots?
OK... So I've tried just about every rom on the dev thread, I purchased the TB on launch date and had it rooted as soon as Jcase posted S-off instructions... I am now on the new radio and until today, I haven't had a single random reboot. Then all of a sudden, just about an hour ago, as I'm backing out of Tapatalk, bam... Phone rebooted itself...
Now I've been reading on just about every rom thread where people have been experiencing random reboots. Some think the new radio is the cause, but some people are on the new radio and have not experienced this. Others on the old radio still get random reboots.
Others think its the rom but people have noted this issue on most If not all of the rom threads.
Others think its the kernel that's causing it, but again, there doesn't seem to be any pattern to nail it down to a single kernel. Furthermore, some of these people are not OCing, myself included.
Which leads me to the strangest part of all this. My wife also has the TB. Her phone is totally stock and is not rooted. I got it for her day after launch and for the last few weeks, her phone has also been randomly rebooting. Not constantly, mind you. Just enough to be a nuisance. She has still not updated to OTA... The only suspect to this is that this appears to have started after the 4G outage a few weeks ago... And we are in a 3G only area but there was a day or so we could only connect to 1x...
So what's really causing these random reboots? I'm no expert, never claimed to be one, but is it possible that something going on between our phones and the Verizon network is causing this?
Thoughts... Ideas...?
Sent from my Thunderbolt using Tapatalk
Great post. It's good to know even non rooted users are having reboots.
non-rooted.... Updated yesterday... and got a reboot today.
Sent from my ADR6400L using XDA App
I've had about six lock ups and reboots today since ehrpd has been back up
Sent from my ADR6400L using XDA Premium App
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
toebee76 said:
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
Click to expand...
Click to collapse
GPS was also on when my phone rebooted... Google Maps was running.
Sent from my ADR6400L using XDA App
stock rom, not rooted, has had multiple random reboots
I have had no random reboots, or none that I have personally experienced. I figured if my phone was randomly rebooting I would have noticed a considerable battery drain. I have not noticed that yet. I honestly think that this might be an issue for people with little to no 4g coverage. I am bothered that this has not been addressed yet by verizon as I have seen so many people complain about this.
Hopefully I dont get these either, who knows may it is just phones that are may be defective hardware wise.
Well i just wanted to drop my $.02
I am Rooted and have been just about the same time the OP has been rooted.
I USED to have reboots. I install the full RUU and had reboots i also installed just the RADIO file and had reboots. I also reverted back to stock by the RUU provided by JCase. I Then flashed 1.6 followed 1.6.3 and have not had any problems. I assume that those 2 already had the radio file in them and i didn't not have to flash anything additional. Since being on 1.6 then 1.6.3 i have experienced not 1 reboot. Unless i did it myself.
I did notice then before when i did have the reboots (when i manually flashed RUU or just the RADIO file). I had reboots 3 different ways. I would either get a reboot when my phone had been sitting next to me for a while i would notice the white screen and know it was a reboot. Also the 2 other times was backing out of TapaTalk or native browser/dolphin HD.
So i don't know if that is in a way related. I just don't have them anymore.
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
toebee76 said:
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
Click to expand...
Click to collapse
This is a possibility... But if that's the case this will be the first Android device I've owned that has rebooted itself randomly due to GPS. Even the Samsung Vibrant, which had horrible GPS right out of the box, didn't reboot itself when it was turned on...
However, if this is the case, why has this only become a recent issue.. now my memory isn't so good... But I don't remember seeing much about this issue on rom threads until recently... I.e the past few weeks... Neither my wife's nor my phone randomly rebooted until just a few weeks ago, and we both have our GPS turned on everyday, all day...
Sent from my Thunderbolt using Tapatalk
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
I live in a strong 3G area and my phone has never re-booted itself as far as I know. I'm doing the update tomorrow and will be interested to see if the problem starts.....I hope not.
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
Unfortunately, I had a solid signal when my phone rebooted this afternoon. I was a stone's throw from Philadelphia on I-95. I've never had signal issues along I-95 between New York and Philadelphia. I'm running the released update.
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
This as well is a possibility... Although I am in an area where 3g is strong... I have seen on my and my wife's phone... Even when standing still... That the 3g icon will vanish and come back seconds later...I am in a decent sized college town, population of about 70000... I couldn't say how strong 3g actually is but its everywhere in the city limits... And most of the countryside...
I have traveled to cities with strong 4g but I didnt stand around long enough in a single place to really watch the phone to see if it was dropping data...
Thanks for the constructive input, everyone... Lets keep the corroboration going and see if we can find a pattern..
Sent from my Thunderbolt using Tapatalk
The only time I had reboot was on the leaked ruu which is now the OTA.
Once I went to BAMF 1.5 with new radio and new base no reboot. About a week ago I flashed back to stock radio just to compare after being on the new one for a while. I see nothing different between them really.
Okay so how many of you were thinking this was the update that would make the Thunderbolt better? Let me know of any issues you have been having since the update yesterday. I am speaking of the official non rooted update for the phone fyi.. So far I have compiled a list below of the issues I have experienced personally on my phone.
1. Randomly rebooting
2. Dropped calls and random reboots during calls
3. Gps issues still prevalent
4. Freezes while opening text messages or closing them
5. Noticeable lag when in app menu
If you guys have any other issues please post them and if there is a way to rollback the update without root please post.
Just updated last night and right away I notice I get no GPS lock at all (unless it takes 15+ min). No reboots yet.
Sent from my ADR6400L using XDA App
Yes I have noticed too that gps searches forever..
Yea, mine has rebooted twice since yesterday also. I'll have to try GPS later today. As for the rest of those complaints, I'm not sure. Weren't they supposed to fix the car mode thing? There's still no way to get to car mode unless you use the one search function.
I updated last night and had a few reboots this morning while using the hotspot. I just tested the gps with the GPS Status app and got a lock in my livingroom in 11secs. My gps has always worked good, but it seems to be locking a good bit quicker.
Sent from my HTC Thunderbolt
I'm also getting reboots and during calls also and GPS is no longer locking. Anything i can do about this?
I just used GPS Status and got a lock almost instantly. W/o it I wasn't able to get a lock at all.
Edit: GPS Status did not fix my lock problem. Worked once however I can't get a lock anymore :/
Sent from my ADR6400L using XDA App
For anyone who is not rooted and getting random reboots, please call VZW support and voice your problem.
They obviously were not reading this forum when half the people with the leaked RUU were getting reboots.
VZW won't issue a hotfix unless people call up and complain and/or start returning phones.
My problem is with phone being idle the battery drains quicker. Before I would lose between 1-3% every hour, now its more like 6-7%. When I check battery use details Android system uses between 60-70% when prior to update it was in single digits.
Tapatalked from Thunderbolt
bunklung said:
For anyone who is not rooted and getting random reboots, please call VZW support and voice your problem.
They obviously were not reading this forum when half the people with the leaked RUU were getting reboots.
VZW won't issue a hotfix unless people call up and complain and/or start returning phones.
Click to expand...
Click to collapse
I talked to tech. support and was told a small percentage of Thunderbolts were experiencing these problems. As w/ every problem I'm being sent another "like-new" phone.
Sent from my ADR6400L using XDA App
From what I have read, the issue is not with Thunderbolts, It's with the towers you're communicating with. The towers need their software fixed to work correctly with the new RUU. If you guys can, I'd wait it out and see if it gets better. I understand that a random reboot can be a huge deal (I came from a Storm 1) but if it is not wrecking your day or costing you business/clients/money etc., wait a week and see. It can be easier than trying to go through all of the set-up again to get your "new" phone the way you want.
6 reboots yestsrday. 10% battery drain each. Do the math kids. My tb isn't much more than a land line now because it's always plugged in. Returning it for sure. And they just sent me a new battery because I was only getting 5 hours max out of it.
I have had the update for a few hours now and non stop use on the phone so far no crashes or reboots. Phone is not rooted and not using any custom roms. So far so good
Sent from my ADR6400L using XDA App
xeene said:
My problem is with phone being idle the battery drains quicker. Before I would lose between 1-3% every hour, now its more like 6-7%. When I check battery use details Android system uses between 60-70% when prior to update it was in single digits.
Tapatalked from Thunderbolt
Click to expand...
Click to collapse
Fixed this problem by pulling battery.
Tapatalked from Thunderbolt
Mine reboots 2-3 times every hour.some freeze issues but not too many. Am thinking it would have been better to wait.. hope they get the tower software fixed also...
Sent from my ADR6400L using XDA App
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
So, I don't know what happened. I didn't touch a thing on this phone, haven't changed any settings or installed any apps for weeks. However, just now, my phone has decided to start acting up in a bad way.
I'm on Paranoid Android 2.52, and I have been for many months now, with no stability issues of any kind. However, without any warning or cause on my part, something got reset. The first thing I noticed was that all of my settings reset to the default Android settings. I had to go through and change all my settings back to how I want them. Then I discovered that there's nothing I can do to get my lockscreen to work again. I have it enabled, I've tried every variation of lockscreen on this ROM, with delay, without delay, but the lockscreen just won't show.
Then I noticed that my notification bar won't display any notifications. It'll show the time, battery, Wi-Fi and other small logos. But the alarm, timer, text, e-mail, etc. notifications will not show on the bar at all. My phone will vibrate when receiving and e-mail or text, but no notification will appear.
Then I noticed that in SMS Popup, which I use, I can't un-hide the message on the popup. I have the privacy set such that I have to tap the little eye logo to display the message. But now that logo no longer responds. It will change color on press, but will not un-hide the message. All I can do is close the popup with the message unseen.
Then I noticed that my home button doesn't work. Either short- or long-press. Short-press should take me to my home screen, long-press should take me to recent apps. It does neither. My phone will vibrate when I touch the home button, but it does nothing. I've checked my settings, and they are as they should be. The button just won't do anything.
I'm sure there's many, many more issues I'm yet to discover. What on Earth happened to my phone and how do I fix this?
Sent from my SGH-I997 using xda app-developers app
I've tried rebooting, turning it off, pulling the battery for a few minutes. Had no effect. And I have no idea what else to do.
Sent from my SGH-I997 using xda app-developers app
Titanium just reported to me that my phone's ID somehow changed. This indicates a factory reset, but I certainly didn't do that.
dstarr3 said:
I've tried rebooting, turning it off, pulling the battery for a few minutes. Had no effect. And I have no idea what else to do.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
When all else fails I personally start completely over using this thread http://forum.xda-developers.com/showthread.php?t=1524081 ,boot into completely stock GB go through setup,reboot into stock GB,then reboot into download mode, flash Zen's A16 kerrnel with recovery,reboot,then follow directions for installing whatever ROM you desire.My two personal favorites(YMMV)are 2.3.6 GB deodexed,zip-aligned,debloated and BeanStalk
elbscorp said:
When all else fails I personally start completely over using this thread http://forum.xda-developers.com/showthread.php?t=1524081 ,boot into completely stock GB go through setup,reboot into stock GB,then reboot into download mode, flash Zen's A16 kerrnel with recovery,reboot,then follow directions for installing whatever ROM you desire.My two personal favorites(YMMV)are 2.3.6 GB deodexed,zip-aligned,debloated and BeanStalk
Click to expand...
Click to collapse
Yeah, I ultimately decided that the only thing I could do is just go back to stock and work my way up to BeanStalk. I enjoyed PA for a while, but all the BeanStalk discussion piqued my interest.
Anyway, I just wish I knew what happened to cause my phone to spontaneously fail so completely. It's seriously of a case of it working before I put it in my pocket, and it being completely ruined when it came out.
dstarr3 said:
Yeah, I ultimately decided that the only thing I could do is just go back to stock and work my way up to BeanStalk. I enjoyed PA for a while, but all the BeanStalk discussion piqued my interest.
Anyway, I just wish I knew what happened to cause my phone to spontaneously fail so completely. It's seriously of a case of it working before I put it in my pocket, and it being completely ruined when it came out.
Click to expand...
Click to collapse
If you go back stock and run it for a day or two should let you know if it is a hardware issue.
elbscorp said:
If you go back stock and run it for a day or two should let you know if it is a hardware issue.
Click to expand...
Click to collapse
Yeah. As soon as I went back to stock, everything was immediately back to normal. But, my past three phones have all lasted anywhere between 21-24 months without any problem, and then suddenly falling apart like the Blues Brothers car and becoming completely unusable overnight, just in time for me to upgrade to new phone with a discount. And, since my contract is up in a couple months, I wouldn't be shocked if my phone's about to have its end-of-term breakdown.
I'd really like to avoid the introductory prices on the S4, though... If I could keep this phone going until about June, I'd love that.
dstarr3 said:
Yeah. As soon as I went back to stock, everything was immediately back to normal. But, my past three phones have all lasted anywhere between 21-24 months without any problem, and then suddenly falling apart like the Blues Brothers car and becoming completely unusable overnight, just in time for me to upgrade to new phone with a discount. And, since my contract is up in a couple months, I wouldn't be shocked if my phone's about to have its end-of-term breakdown.
I'd really like to avoid the introductory prices on the S4, though... If I could keep this phone going until about June, I'd love that.
Click to expand...
Click to collapse
I don't have contracts and I've had phones with faster,newer,better hardware and I come back to and enjoy my Infuse more. As long as there is this kind of active development for it I will keep picking up cheap Infuse.
elbscorp said:
I don't have contracts and I've had phones with faster,newer,better hardware and I come back to and enjoy my Infuse more. As long as there is this kind of active development for it I will keep picking up cheap Infuse.
Click to expand...
Click to collapse
Yeah, I'll admit Scott's solely responsible for keeping my interest in this phone. A year ago, I was still on Froyo and I was getting bored with it and wanting a new phone, but I stumbled across PA somehow and thought I'd give it a shot. Three PA roms and Bean Stalk later, I'm still loving my Infuse.
The problem is that the hardware's just not holding up anymore. I'm having the famous power button issue. I'm going to try to gut my phone and clean the button myself, but beyond that, there's not a lot that can be done about it. I'd really love to dedicate the Infuse to an alarm clock/media player when I get my new phone, so I can still have something to mod. But I just don't know how I'm going to adjust to the sudden lack of customizability when I get the S4 with a stock release of Android.