Related
I am from Hong Kong, using vibrant.
I found that my vibrant will get easily hanged/not responding, occasionally.
No matter which rom I flashed, stock, roms from eugene. (Applied/not Applied lagfix)
When my vibrant is not responding, the back of vibrant near the camara or next to the camara, will get hot and hotter.
After a long press of the power button, for a hard reboot of the vibrant, the vibrant will be fine again. However, the situation repeat.
So, I want to figure out that is there anybody encountering the same situation.
Thanks.
I have not had this exact problem, but I have had mine randomly go black. It's done it 3 times in the 4 days I have had it. When it goes black, you can't turn it on, power does nothing, and you have to pull the battery to start it again. I have never let it sit long enough to see if it gets hot.
I have heard mixed thoughts, some people claim it's hardware problem, some say its a firmware problem =/
I've seen my screen turn black with just the key backlights remain on. The device becomes and remains hot to the touch as if working very hard (drawing heavily on the battery and CPU) but it never responds again. Holding down the power button for a full five seconds resets it.
In my case, I typically see this happen while I'm trying to use Google Navigate (GPS) while also running Pandora (streaming radio) in the background. Often it works, but often it doesn't, especially on days with warm weather. I've monitored battery temperatures around 114 degrees F after rebooting.
I suspect it is related to the problems with the GPS (fixed to use supl.google.com) and very much hope it will be fixed with the promised OTA upgrade. Although I may have seen it a few times (very few times) without GPS. My other suspicion turns toward a process called mmcqd which seems to run heavily at times. Perhaps the lagfix will help with this "Multimedia Card Queue Daemon" process. ::shrug::
Just offering this as notes to compare. I'm curious if others see the problem with GPS disabled? Or if you notice the mmcqd process maxing your CPU?
I've noticed that when using GPS, only when the GPS gets confused.. say for instance that I'm driving, get out of my car with a Navi program still running and walk inside of a building/house.. bam, phone is dead with the buttons lit.. I've decided to not bother with GPS.
If you're having those types of issues try avoiding background sync with the forever sluggish stock eMail app, and don't load up the internal memory with a lot of junk.
having the same prob... cant find the solution .. do u have any?
This happens to me on my stock vibrant everytime I try to use the maps program. On the off chance I get it to start working, as soon as it shifts orientation to landscape mode the whole thing will lock up. Usually I have to remove the battery to get it to reset. As was said, it appears to be caused by the faulty gps, so I usually just leave mine off.
However, I haven't noticed it happening while doing anything else and I'm hoping the upcoming ota update fixes these issues. (Don't want to bother with rooting stuff until I'm on stock 2.2)
The solution is to install the leaked update that we should be getting officially very soon. No freezing, no serious lag (installing apps will lag almost any Android device), no black screen freeze ups, much improved GPS, I'm lovin' it.
I installed Cyanogen Mod7 on samsung vibrant, after reboot the set not started, only samsung logo shows but not booted further, plz give the solution.
heygrl said:
The solution is to install the leaked update that we should be getting officially very soon. No freezing, no serious lag (installing apps will lag almost any Android device), no black screen freeze ups, much improved GPS, I'm lovin' it.
Click to expand...
Click to collapse
Hey, did u get the update or solution?
Good morning all. I have a small amount of knowledge about this device (I’ve read a fair bit) but would still classify myself as a novice user. I am able to flash my device and have had android running for a while now. I have a few issues, and just want confirmation that I’m not doing anything stupidly wrong.
Firstly, I have flashed to a number of winmo roms, all with varying degrees of usability. I found them to be slow compared to android. All my rom including the last two roms, chuckyrom tabtastic and chuckydroid, have given me a few issues of varying degrees. They freeze a lot and require a soft reset or to pull the battery. Sometimes, if I try and restart straight away, the red writing on the first screen doesn't come up and the phone vibrates 4 or 5 times. Further to this, they may restart midway through booting up, or if I am transferring a large amount of data or using my phone as a wireless hotspot the phone also resets after a while. I have noticed the phone gets quite warm during this. Best results for a reboot come after pulling the battery and leaving it for 15-20 minutes.
Secondly, I have used a number of different android builds (all HTC based) and whilst generally the phone does not freeze when it is in idle mode, it freezes up to 15-20 times a day when using applications such as facebook, internet explorer, music etc. Is this normal?? I don't get any force close notifications. When people say it is “relatively stable” what does this actually mean – no freezing, 5 freezes a day, 50 freezes a day?? The device also freezes when syncing all data. Sometimes when I am in a call, if a change occurs on the device (text message or other notification comes in, even when on the move which I’m guessing may be location changes in the system) the phone freezes and emits a “bzzzzzzzz”ing noise (well, I don't know how well the word “bzzzzzz” conveys what I’m trying to say, but you may get the picture). All this in turn leads to me needing to re-boot, which then brings into play the issues of rebooting above.
The other day, I noted that the micro-usb cable had what appeared to be small burn marks on it, and the contacts inside the micro-usb cable were a bit corroded/eroded. I do remember a few weeks ago where my phone froze in the middle of the night whilst on charge and the phone became quite hot, possibly resulting in the damage to the cable. Yesterday, I got a new cable and woke up this morning with the phone quite warm again (battery temp was at 39 degrees). This was all whilst using android.
I have tried a number of different winmo roms and android builds, flashed radio, task29, different micro sd cards, formatted sd card etc. I am thinking of reflashing back ot the original rom and if I still have the same issues then sending away to get it fixed. Problem with this is that Telstra here in Australia claim it will be a month and that no replacement phone will be given to me in the meantime. I think I am paying about $160 a month at the moment – surely this is a bit slack not to give me a replacement phone in the meantime? Can anyone share their experiences with Telstra and/or tips when dealing with them?
Any help with the above would be appreciated. Thanks a lot.
No, don't think you're doing anything wrong. Android builds shouldn't be freezing at all, as far as I know. I've tried many builds, and have never had one freeze on me. The current ones are arguably more stable than most Windows Mobile ROMs! Still, Windows Mobile shouldn't actually require pulling the battery that often either.
Based on what you mention it sounds like your phone might be overheating, which would probably be a hardware problem (at least really unlikely to be caused purely by user operation or software). It might be worth checking the battery pins, to make sure all of them make a firm connection to the battery. If not, it could be one is disconnecting as your phone gets warmer. Still, overheating itself is a more likely cause, especially because of what you mention about vibrating x times if you restart it without giving it time to cool down.
I'm no expert, but it might be time to send your phone in for repairs... (if you do, don't forget to remove HSPL & restore stock ROM)
thanks for that help. I think i will send it back, i had already checked the battery pins.
just got rid of HSPL, but now having trouble flashing back to original rom. it jsut gets stuck on the update screen at 0%.... any ideas? i tried via SD card too, and it just gave me the "loading" page....
THnaks!
Hi there.
Getting kind of worried and irritated at the same time. My phone has recently been turning itself off and it seems the only way I can get it back on is removing the battery and putting it back in. Lock button doesn't work to turn it on. This happened a few days ago when I was sitting by a fire so I thought it might be the heat, but even then, my phone heats up often if I'm playing games etc. it also happened just a moment ago when my phone was just laying on the floor.
Has anyone else had this problem?
Anyone..?
charlimit
And what ROM might you be using? Stock or a custom one? Giving a little info never hurts
Willbuh said:
Hi there.
Getting kind of worried and irritated at the same time. My phone has recently been turning itself off and it seems the only way I can get it back on is removing the battery and putting it back in. Lock button doesn't work to turn it on. This happened a few days ago when I was sitting by a fire so I thought it might be the heat, but even then, my phone heats up often if I'm playing games etc. it also happened just a moment ago when my phone was just laying on the floor.
Has anyone else had this problem?
Click to expand...
Click to collapse
Dunno what a lock button is, but when you say the phone turns itself off, are you sure it hasn't just frozen? Next time it happens, press and hold the power button for about 8 seconds. If there is something still alive in the phone it should turn off/reboot without having to remove the battery.
And yes, lots of others have seen this type of behaviour. I have personally seen this freeze, "slow" reboots and "fast" reboots. Lots of threads out there about this type of stuff. I have no idea why it happens. I don't even know if its a hardware or software (app or OS) problem. And I don't think anyone else knows either ...
My phone was returned for replacement 1 week ago and it now appears to have been sent for repair / investigation / lost (take your pick).
I'm on stock rom by the way
I have the same problem. It started a few weeks ago. I had about 4 reboots/shut offs per day.
About one week ago it just stopped.
I haveno idea why it started or stopped.
Sent from my GT-I9100 using XDA App
I am also on stock.
It occured on KE2 and KF3.
Sent from my GT-I9100 using XDA App
i have the same problem right now, at first i believe that because i havent set a lock, maybe my phone turn off in my pocket by accident, but today it happens again just over my desk..... curious????
As of yesterday I noticed that my 16gig white wifi running TASK650's 6.0 (now on 7.1)was having odd screen issues where all the colors became distorted (white-->purple) as well as an odd effect when opening the keyboard the keys were all "streaking" a purple trail. I think it has something to do with heat as when I tried sticking the tab into the freezer the issue went away but came back once it became warm again. I have no sleeve or case on the tab but even when i use it on my lap it immediately gets these issues. I did have Pershoot's OC kernel installed but I rarely go past 1.0ghz on SetCPU for more than 25 minutes at a time and usually much less.
I was wondering if anyone else had these problems? If so did you manage to fix it?
Currently running TASK650's 7.1 with no OC but I'm pretty sure this is a hardware issue.
I guess no one else had this issue. But in case anyone else did or if anyone comes across this in the future I am currently testing if the issue persists on unrooted, stock without CWM. I will report back findings as I come across them or the lack of them if not.
I've decided it is most likely broken crystals from the display or rather that they are damaged but not broken. To anyone reading this just send it back for an exchange from your store if you are still inside the return period or Samsung if you are not. Nothing will fix it aside from knowing 100% that it is the LCD and buying a replacement screen and repairing it yourself.
How did you manage to fix the issue? Thanks.
Okay first of all, I've scoured not only XDA but even Google for an answer to this problem to no avail. So if anyone has/knows of any thread that has the answer, please kindly reply or notify me so we can have this thread removed.
Here goes,
I'm experiencing a very unique (afaik) problem with my Galaxy S3. This started a few months back, when the phone started getting random reboots/ freezes and terrible battery life on ANY ROM/Kernel. I've tried CM, SlimBean/Kat, and even Stock and nothing worked. Finally I figured maybe the battery was shot. So a few days ago I went and got a new battery, and that's when it got weird.
I used the latest SlimKat after replacing the battery and after powering on the device, EVERYTHING seems perfect. It's really fast and responsive, battery drain while screen is on is extremely acceptable, things worked like new again. UNTIL I switched off the display, after 5 mins, I pulled out the phone and it was switched off. At first I thought maybe the initial charge wore down so I charged the phone to full, then powered it on. Again, everything went smoothly BUT, after switching off the display for more than 1 minute, the phone shuts off automatically.
I switched to the latest stock 4.3 ROM and restored everything to factory settings and it seems to have helped at first. As usual, everything is fast and battery doesn't drain so much BUT, after putting the phone to sleep, it takes 5-10 seconds for the screen to wake after pressing the power button, and even if it wakes up, it becomes EXTREMELY laggy and often freezes requiring a reboot. As usual, after a fresh reboot, everything becomes awesome again until I have to turn the display off for more than a minute.
I've tried everything, even installing an app that prevents deep sleep but the problem persists. It improved a little after flashing stock rom and reverting everything back so I'm really hoping this isn't a hardware issue. Is there maybe something else I can try, settings/software-wise? The phone is almost 2 years old and is already out of warranty.
I'm hoping it's not the sleep of death thing because the phone isn't exactly bricked. I can still use it for as long as it doesnt have to go into deep sleep (I turn it off before putting in my pocket and turn it on again when I need to browse/use the camera which is all it's good for in its current state.)
Also, the symptoms don't really fit the usual "Sleep of Death/Brickbug" Symptoms I've read about.
Hey, I remember having a similar problem. I formatted both my internal sd and external sd. Haven't had any problems ever since. Hope this helps.
Sent from my SM-N9005 using XDA Free mobile app
Already tried that. I did full wipes/formats on all my installs. I even tried not having an external SD inserted for the Odin installs. I tried not installing any app on the phone and it still gets messed up after going to sleep. As fresh installed AOSP or Pure Stock ROM. Odin flashes no problem so I'm really hoping nothing hardware-wise is messed up. I had to re-flash PIT after getting a new battery though, could I have messed something up there that would lead to this?
There is an app for that deep sleep syndrome, it's on playstore its calles brick check or something like that, if you cant find just google it.
And I dont think that could be software problem, BUT depends on what apps you used, flashes you made.
Hope it hepls
Well, i don't think its deith break, but i had the same essue with unofficial 4.3 and then at official 4.3 it worked well,
it may be a break in the motherboard or something.. as u tried every rome avilable it couldn't be softwear thing..
the app for emmc firmware is called 'eMMC check', you can find it on playstore
edit: does your phone heat up? or battery? did your display ever turned blue when waking up from sleep?
it could be also a short with your display/motherboard or other connectors or battery connector... and the protection kicks in
if you're good with tools and phone is not under warranty, you could disassemble it and reassemble/reseat the connectors
or, could be the power button shorting, if you decide to open it, examine the power button
@Eibram did you ever undervolt or overclock when using custom kernels or roms? Because it could be hardware damage.
Also, do as they tell you above, check if you have the insane f01 emmc chip. I know it's a common missconception going around that since 4.1.2 the SDS got fixed, but it didn't really get fixed since it's a firmware problem in the emmc patched through software which just makes it highly unlikely to happen (but not impossible).
I did some minor undervolting way back before JB came out but not since over half a year ago. I did the eMMc check and yes, I do have the inane chip.
Just an update, I re-flashed a PIT file and a rescue firmware and it seems to have helped a bit. It was running fine for over 12 hours aside from a random reboot just now.
I'm observing the phone right now to see wether the reboot was just coincidental. I really wish this is just a software thing.
Okay one more update, 2 days in and I've only experienced the one random reboot. It's still sometimes slow when waking up, but something around 2-5 secs sore not 5-15 seconds slow. I'm thinking that must be due to touchwiz bloat.