Related
I got my first Vibrant on launch day with high hopes. Two weeks later I had a new one due the phone freezing EVERY time I opened Google Maps. I've held on to this one now waiting for a GPS fix and JI6 worked great for me....for about the first week. Now its just as bad as ever.
I get an initial fix much quicker, but after about five minutes it loses GPS signal completely and indefinitely. In the past week my phone has begun freezing AGAIN, including three times today alone. Two of the times I would go to unlock my phone and nothing would happen. The screen would remain off, softkeys wouldn't light up, and a long press on the power button does nothing. I have to pull the battery out and reboot.
This is incredibly frustrating because this phone takes nearly 5 minutes to boot (never actually timed it but I have to imagine somewhere close to that). So its a long wait before I can do what I intended to do. I did notice that Shopsavvy was sucking on the GPS signal when I rebooted the phone so perhaps that's what was secretly crashing it (Needless to say, ShopSavvy got the boot after the second freeze).
I've tried uninstalling and re-installing the Maps updates w/ no change. I would bring the phone back but T-Mo doesn't have any other phones I want. My Touch 4G is hideous and I don't want another QWERTY like the G2.
So did I just end up with another dud Vibrant or is there a fix? Would rooting fix my problems? This phone has never been rooted or hacked in any way.
Any ideas???
Short answer: Yes.
Short but longer answer: At least install a LagFix. I got back and forth between stock JI6 and Fusion 1.1 a lot. JI6 with a custom kernel and LagFix is butter. Fusion is even better.
You may have a dud though. I haven't had that many problems except for things I did myself.
atvman29 said:
I got my first Vibrant on launch day with high hopes. Two weeks later I had a new one due the phone freezing EVERY time I opened Google Maps. I've held on to this one now waiting for a GPS fix and JI6 worked great for me....for about the first week. Now its just as bad as ever.
I get an initial fix much quicker, but after about five minutes it loses GPS signal completely and indefinitely. In the past week my phone has begun freezing AGAIN, including three times today alone. Two of the times I would go to unlock my phone and nothing would happen. The screen would remain off, softkeys wouldn't light up, and a long press on the power button does nothing. I have to pull the battery out and reboot.
This is incredibly frustrating because this phone takes nearly 5 minutes to boot (never actually timed it but I have to imagine somewhere close to that). So its a long wait before I can do what I intended to do. I did notice that Shopsavvy was sucking on the GPS signal when I rebooted the phone so perhaps that's what was secretly crashing it (Needless to say, ShopSavvy got the boot after the second freeze).
I've tried uninstalling and re-installing the Maps updates w/ no change. I would bring the phone back but T-Mo doesn't have any other phones I want. My Touch 4G is hideous and I don't want another QWERTY like the G2.
So did I just end up with another dud Vibrant or is there a fix? Would rooting fix my problems? This phone has never been rooted or hacked in any way.
Any ideas???
Click to expand...
Click to collapse
I did not know what a real smartphone was supposed to be until I rooted and custom rom(ed) it.
For the first 3 months I had the phone... I was reluctant to root. But ofcourse... It was just another phone... laggy and slow...
Until I rooted and installed Bionix. Now its smooth as butter.
Good things in life are always free. I paid for a suffocated phone... xda developers free services released and refreshed my phone.
Well
I would install Fusion 1.1 with the Core kernel from Sombionix and see if that fixes it. Stock is totally unacceptable.
If it stills sucks, its likely a dud.
You must either be getting dud phones, or you're installing some app that's messing them up(?) I'm stock/unrooted, and very happy. Not that I doubt the happy results reported by folx like those above, but I don't have bothersome "lag" or freezing etc. -- no issues that even tempt me to ROM-swap (I wouldn't have kept the phone if I weren't satisfied w/it stock).
My GPS did used to lose signal as you report; haven't given it a good comparison test since JI6 update.
Well I've rooted using OCLF and also applied the lag fix. No change.
I still find the phone dead 2-3 times a day with no warning. I'll go to wake it up and nothing happens.
Some of you think installing a new ROM with help? How can I do that? The one time I tried using ODIN, it was never able to identify my phone.
Ugh, why can't this POS just work.
atvman29 said:
Well I've rooted using OCLF and also applied the lag fix. No change.
I still find the phone dead 2-3 times a day with no warning. I'll go to wake it up and nothing happens.
Some of you think installing a new ROM with help? How can I do that? The one time I tried using ODIN, it was never able to identify my phone.
Ugh, why can't this POS just work.
Click to expand...
Click to collapse
Did you make sure you had the Samsung USB Driver for the Vibrant? If you don't Odin won't recognize your phone. Also important to have a newer version of Odin. Like I have 1.7. And last as Odin is a little troublesome, you should have Odin up and running before you connect your phone. Read the Bible in the Dev section for links.
1) Could be a dud, it happens
2) When I first got my Vibrant, it boots up so fast. Its because there are hardly any apps installed that as part of the boot up process, go and check on. I think it has to do with the cache, because once you load it up with apps, the time it takes to get to the home screen is noticeably longer.
Also ShopSavvy is a bit wonky with the gps, so I disabled that setting in the app. But my though is you might have a bad app installed or something funky on the internal/sd memory that its fighting with. I'd say as something to just try for kicks, backup everything, copy memory to your pc, wipe the memory and do a factory reset(You could odin to stock, but you'll lose the Sims app). If things work, slowly add your apps back in.
As for gps, yes before the update it just wouldn't lock or would take forever, but still not be very accurate. After the update(but then also after alot of flashing different roms, then finally just going back to stock), gps works like a champ. But I would also point out that gps is vulnerable to several things. Don't place the phone near any large metal or magnetic object, this will throw the compass off. And always try to have a clear view of the sky, without being in a 'canyon' of buildings. The buildings distort the signal(which in the case of gps is just a signal that tells the time) and can throw off the reading(which is where the a in agps is supposed to come in).
Has anyone else noticed their MT4G being retardedly slow? Like to the point it takes 20 seconds to do anything? It was fast the other day. Became unbearably slow today. To the point it wouldn't recognize touch, lagged between screens, etc. I have pulled the battery and rebooted about 6 times now, in the last 12 hours.
I've done a factory reset 2 times since I bought it on Thursday. Not cool.
weird.. never happened to me.
go into setting/applications clear your browser data sometimes it gets really high and needs to be cleaned...just go thru your apps and clear some stuff maybe thats the problem
It's really odd. I pulled out the SIM. Booted up, and it was fast as hell.
Kinda odd. I also just put the SIM back in, ran it in GSM only mode, and its much quicker.
This happens a lot to me, when I talk on the phone and try to do anything. Mostly, I've noticed that Sense just seems to take a dump here and there with all of the background services running. LaucherPro is a lot faster for me, that much is certain.
The dreadful combination is:
Talk on phone
Scroll through something in Sense
Have Android sync with GMail
When that happens, you're toast.
Jon C said:
This happens a lot to me, when I talk on the phone and try to do anything. Mostly, I've noticed that Sense just seems to take a dump here and there with all of the background services running. LaucherPro is a lot faster for me, that much is certain.
The dreadful combination is:
Talk on phone
Scroll through something in Sense
Have Android sync with GMail
When that happens, you're toast.
Click to expand...
Click to collapse
How have you been speeding it back up once this happens? I did a few battery pulls and it was still slow, finally just pulled the sim and it worked. But there's gotta be a more definitive answer. Even if it means manually selecting networks.
I sped it up by ditching Sense and using LauncherPro instead. There is such a huge speed increase that it is insane.
Previous to that, I restarted the phone (which is like an actual shutdown) and turned it back on. Not ideal at all. The phone's software is pretty buggy. The ambient light sensor suffers from the same issues that the iPhone 4 launched with. The screen will sometimes stay on during a call (or flash on-off over and over) until your cheek hangs up the call by accident.
I love this phone, but T-Mo and HTC better be quick with the updates.
Phone has always been lag free for me. Are you on stock rom? Post all after market stuff that you downloaded. Something must be running in the background that's slowing you down. Mine has always been good, and when I flashed to iced glacier rom it flies
I have had problems viewing the photo gallery. It really slows down when I start scrolling through the pictures. I don't know if it is because of the memory card or maybe syncing with facebook. I have about 200 pictures on my card. I've had most of these same ones on my G1 and other phones without this problem.
Sent from my HTC Glacier using XDA App
you can install WatchDog to take a look at what may be eating your CPU. Also I am going to keep going back to it, make sure USB debug is checked. Helped me a lot!
Please post questions in the Q&A section.
Sometimes my phone will get very unresponsive such that any action takes many seconds to show up, and everything is very choppy. Often I see this when I wake up in the morning, but it happens often enough in general. It's so bad that I can't shut it down normally because it would take over 10 min (I've actually never waited to see exactly how long it would take). Thankfully I just found out about the three finger reset (volume up, camera, power), so I shouldn't have to pull the battery anymore, but it's still a problem.
I don't remember this happening before using custom roms. It happens with both DK28 roms I've tried - Bonsai and Viper. I believe it also occurred on the 2.1 Epic Experience, although I'm not sure. I guess I should try flashing to DK28 stock to see if that works, but it's a pain to set up everything each time. I figured I'd ask here to see if anyone else has had this problem and found a way to fix it. Also, I have a feeling this could be related to WiFi being turned on, but can't confirm yet.
My phone was stuttering yesterday.
But that was only after installing smartbench and using theonscreen keyboard.
However, since I've upgraded to dk28, the phone does take (relatively) forever to shutdown.
It'll go black but the bottom lights would still be on and then like a minute or two later it vibrates and actually cuts off
Sent from my SPH-D700 using XDA App
When my phone does this, it reminds me that I like to have SeePU installed. It's pretty useful in pointing out the apps that are hogging CPU and most likely slowing down your phone.
For me it's often Touchdown, and I kill it and things are back to normal.
I have found a few things that are useful. When I need to reboot my phone I use quick boot from the market. Works every time. In between I use fast reboot also from the market. Try them and see how they work.
Sent from my SPH-D700 using XDA App
Thanks for the app suggestions. I like the taskbar icons for SeePU. It's always been useful on my Mac (stats from iStat). Quick Boot makes things easier as well.
Next time my phone hangs, I'll see if some process is taking 100% CPU.
The phone hung again, and it seemed like something was taking 100% CPU, if the taskbar SeePU icon is to be trusted. I wasn't able to figure out what the culprit was though, because the phone pretty much stopped responding. Otherwise I would have loaded Android System Info to check.
can the epic 4g run this lag fix? if not, do we have any other ways to fix the lag?
http://forum.xda-developers.com/showthread.php?t=784691
edit: nvm
So I was able to view Android System Info while my phone was hanging, but it did now show any processes taking 100% CPU, although the total CPU usage was 100%. My guess then is that the Android 2.2 OS is buggy.
However, I did find people who said leaving USB debugging on would fix it, so I'm going to try that.
For reference:
http://forum.xda-developers.com/showthread.php?t=826507
http://androidforums.com/desire-hd-support-troubleshooting/244553-100-cpu.html#post2140890
My phone hasn't hung for a while, so apparently enabling USB debugging prevents the hang / lag / crash / 100% CPU. Weird but I'm glad it works
Now the only problem is kswapd0 eating CPU sometimes. I think this is caused by lack of memory, but I'm not sure what I can do about it.
Here's the rundown ...
Last night I was playing a little Nimble Quest before bed. I started to get tired so I quit out of the game and as I was turning the phone back into portrait mode the screen went black (still on) and seemingly froze. I let it chill for a bit, then it vibrated and I heard my notification sound. I let it go again and a few seconds later it did it again (vibrate/sound). This happened a couple more times before I decided to hold down the power button and attempt to shut it down. After holding the power down for about 5-6 seconds, the phone rebooted itself. It stayed on the CM boot screen for what seemed like 5 minutes--long enough for me to think it was bootlooping. Finally I saw the screen brightness lower and the lockscreen came up. My background was there but all of my homescreen icons were gone. All of my apps were there, but all of the data was gone. Rather than deal with it at 1AM, I put it on the charger and let it go.
This morning I did a full wipe and restored a nandroid backup from the 20th. Everything seemed back to normal. When I got to work I reflashed the CM10.1 stable that just came out and faux's mainline 16 kernel, effectively bringing my phone back to the state it was before last night's drama. I got up from my desk to get coffee and when I returned I noticed my phone was on with a yellow screen that read:
HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
There was some other stuff too but I decided to Google it before I did any of the things listed on the screen. I found a post in the Optimus G forum describing the same thing. One of the members said to hold down the power button until the phone shuts down, then restart and everything would be cool. No one else in the post seemed to see it as a big deal.
I went ahead and did what was recommended and my phone seems to be OK. Nothing weird has happened since then.
I guess my question is: what could've caused this? Is it my ROM/kernel combo or is it more likely the actual hardware? Should I be alarmed? My phone is less than a month old. Any help would be appreciated. Thanks!
I'm not an expert here, so I might not be the best source of advice, but I'll try.
The 'HW reset' message is kind of weird. I assume it means hardware reset. Out of curiosity, are you playing with the voltages or clock speed of your processor? Maybe it went out of the fringes of usability and crashed. Although if that happened, I'm not sure if the system would realize it and automatically recalibrate it (hence the 'HW reset').
You said you were playing a game called Nimble Quest when you first had issues? Is that a really resource-intensive game? Maybe your chip overheated, and the system freaked out and reset something. Then again, there was plenty of time between that and when you actually saw the screen so I doubt that.
I couldn't tell you, OP. That is very strange indeed. Did anyone in the thread you found about the Optimus G have any suggestions as to the cause?
Johmama said:
I'm not an expert here, so I might not be the best source of advice, but I'll try.
The 'HW reset' message is kind of weird. I assume it means hardware reset. Out of curiosity, are you playing with the voltages or clock speed of your processor? Maybe it went out of the fringes of usability and crashed. Although if that happened, I'm not sure if the system would realize it and automatically recalibrate it (hence the 'HW reset').
You said you were playing a game called Nimble Quest when you first had issues? Is that a really resource-intensive game? Maybe your chip overheated, and the system freaked out and reset something. Then again, there was plenty of time between that and when you actually saw the screen so I doubt that.
I couldn't tell you, OP. That is very strange indeed. Did anyone in the thread you found about the Optimus G have any suggestions as to the cause?
Click to expand...
Click to collapse
At the time I was using faux's kernel and his FauxClock app. Processor speeds were set to his recommended for good battery life (384 min 1512 high, intellidemand). Also, I can't imagine Nimble Quest being very demanding. It's a 2D, 16bit style snake-type game. No one in the Optimus G thread had another other suggestions than holding power down to restart.
So the night before last I had another episode with soft reboots. I couple in a row. No data loss, but still annoying. This morning I decided to ditch faux's kernel and flash the latest CM nightly (people have been saying the nightlies are pretty much just as stable as the RC/stables). Just about 15 minutes ago, I was playing Nimble Quest again and had the same problem. I quit out of the game and the screen went black, but still on. I felt a quick vibe and heard my notification sound. Count a few seconds and it happened again. I held down power for a few seconds and the phone shut down. I booted back up and everything seems to be there except for my wallpaper. I've tried setting a new wallpaper and it's not working. I just get a solid black background.
At this point I'm really worried that it's my hardware and not the ROM/kernel/software. How should I go about testing this? I assume the most foolproof way would be to flash the factory image and run it stock for a while to see if I have problems. Before I go that route should I try a full wipe, CM install and forego restoring my apps with TiBu? Could it be a corrupt app or data causing this issue?
Again, any help is appreciated.
I used to have it too when I was using Faux kernel. Turning off C3 and C4 in FauxClock fixed it for me.
daewond3r said:
At the time I was using faux's kernel and his FauxClock app. Processor speeds were set to his recommended for good battery life (384 min 1512 high, intellidemand). Also, I can't imagine Nimble Quest being very demanding. It's a 2D, 16bit style snake-type game. No one in the Optimus G thread had another other suggestions than holding power down to restart.
So the night before last I had another episode with soft reboots. I couple in a row. No data loss, but still annoying. This morning I decided to ditch faux's kernel and flash the latest CM nightly (people have been saying the nightlies are pretty much just as stable as the RC/stables). Just about 15 minutes ago, I was playing Nimble Quest again and had the same problem. I quit out of the game and the screen went black, but still on. I felt a quick vibe and heard my notification sound. Count a few seconds and it happened again. I held down power for a few seconds and the phone shut down. I booted back up and everything seems to be there except for my wallpaper. I've tried setting a new wallpaper and it's not working. I just get a solid black background.
At this point I'm really worried that it's my hardware and not the ROM/kernel/software. How should I go about testing this? I assume the most foolproof way would be to flash the factory image and run it stock for a while to see if I have problems. Before I go that route should I try a full wipe, CM install and forego restoring my apps with TiBu? Could it be a corrupt app or data causing this issue?
Again, any help is appreciated.
Click to expand...
Click to collapse
Hm, this is an interesting bug indeed. I guess first, I would try
illhangon said:
I used to have it too when I was using Faux kernel. Turning off C3 and C4 in FauxClock fixed it for me.
Click to expand...
Click to collapse
.
If that doesn't work, I would at least try a different kernel. If that does nothing, I would try changing ROM, and without restoring any apps or data. Is the only time you can get this problem with that specific game? If so, the game itself might be a faulty-coded game. If you get this problem elsewhere, try messing around on the newly-flashed ROM in the other areas you can replicate this. If you can't get it to soft-brick, try downloading that game and playing it on the fresh ROM/kernel. If you still get it, try flashing another kernel again. Basically, try 2 different ROMs, each with 2 different kernels, with and without Nimble Quest. Might seem like overkill, but I'm just trying to completely eliminated ROM/kernel problems, and any app problems. If none of that works, I really don't know what to say, maybe it really is a hardware issue.
Tonight, I'll try downloading Nimble Quest and playing it for a bit to replicate the issue. Is it just playing the game in general that crashes, or is it specific actions that you've found that really trigger it? From what I've read, the issue seems to pop up when you quit the game. I assume that just means hitting the Home key? I've read the reviews on the Play page and can't find one that complains about system-wide problems. I have a feeling it isn't the app, but it doesn't hurt for me to try and replicate the issue. If I get it, that means it's either the game, or specific settings both you and I share, and we will need to dig a little deeper to find out what it could be. Anyway, I'll mess with it a bit tonight and get back to you tomorrow if you haven't already found the cause/solution.
It happens every time the modem crashes. Earlier it just used to reboot without giving the message.
Sent from my Nexus 4 using xda premium
Hello,
Forever pretty much I've been experiencing issues with my nexus 6p. I got it second hand but it seemed fine when I got it. Now, however, after a little inactivity, I find that unlock my phone will cause it to crash or reboot instantly. Its right after it unlocks that it does this. It's not every time but it happens a lot. It also sometimes happens a little bit after unlocking the phone after inactivity. Its like when it needs to drain more power from the battery than its used to it will just crash on me.
The only real thing that prevents this is keeping the phone on charge. Then again, it has happened before where it will still die on me. I've replaced pretty much everything on the phone with the exception of the charging board and the main board. So stuff like the screen and battery have been replaced (+more). Not sure what is causing it. I've had this issue before on stock android but at the moment I'm running the final version of Resurrection Remix on Nougat.
How would I go about troubleshooting this?
Nexus Radical said:
Hello,
Forever pretty much I've been experiencing issues with my nexus 6p. I got it second hand but it seemed fine when I got it. Now, however, after a little inactivity, I find that unlock my phone will cause it to crash or reboot instantly. Its right after it unlocks that it does this. It's not every time but it happens a lot. It also sometimes happens a little bit after unlocking the phone after inactivity. Its like when it needs to drain more power from the battery than its used to it will just crash on me.
The only real thing that prevents this is keeping the phone on charge. Then again, it has happened before where it will still die on me. I've replaced pretty much everything on the phone with the exception of the charging board and the main board. So stuff like the screen and battery have been replaced (+more). Not sure what is causing it. I've had this issue before on stock android but at the moment I'm running the final version of Resurrection Remix on Nougat.
How would I go about troubleshooting this?
Click to expand...
Click to collapse
Good observation. It is true that the reboot happens because of higher performance. It is caused by the four higher performance cores of the CPU starting to work. There is a fix.
What it does is to shutdown those four cores and you will be able to use only four of the lower performance but power efficient cores.
Follow the link :
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
Sorry for my late reply...
Thanks for the solution, but it seems like a very drastic trade-off for a fix. Is there nothing I can try to fix this like a system or boot.img patch that does something other than disable cores?
Either way, thank you.
Nexus Radical said:
Hello,
Forever pretty much I've been experiencing issues with my nexus 6p. I got it second hand but it seemed fine when I got it. Now, however, after a little inactivity, I find that unlock my phone will cause it to crash or reboot instantly. Its right after it unlocks that it does this. It's not every time but it happens a lot. It also sometimes happens a little bit after unlocking the phone after inactivity. Its like when it needs to drain more power from the battery than its used to it will just crash on me.
The only real thing that prevents this is keeping the phone on charge. Then again, it has happened before where it will still die on me. I've replaced pretty much everything on the phone with the exception of the charging board and the main board. So stuff like the screen and battery have been replaced (+more). Not sure what is causing it. I've had this issue before on stock android but at the moment I'm running the final version of Resurrection Remix on Nougat.
How would I go about troubleshooting this?
Click to expand...
Click to collapse
My 6p just recently encountered the same symptoms as yours. Only way to keep it from rebooting is keeping it plugged in. I've found something that has worked for me so far, maybe it will work for you too. It seems like disabling the Doze feature has fixed this problem for me. I'm not rooted, so I used adb command to do so. Here is a link for the instructions. Hope this helps you too. In the instructions,
it show you how to enable, but can be used to disable with one simple change.
https://windroidwiz.wordpress.com/2017/06/02/android-noroot-force-enable-doze-to-extend-battery-life-of-your-phone/