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?
Related
I don't know what the heck is going on with my HTC HD2, but the reboots are getting quite annoying.
Furthermore i noticed it happens when i utilize the cpu heavily.
Mostly with streaming video or playing games.
Have done multiple hard resets, rom updates and even custom roms but nothing seems to work.
Sometimes my phone even reboots(soft resets) after watching 5 whole seconds of youtube
So even directly after a hard reset the problem persists.
I'm totally confused right now(because i have tried everything i could do to fix this problem).
I am thinking could it be the battery not giving enough juice for the task? overheating ? or just faulty hardware?
what do you guys think?
because i noticed that the problem is happening more frequently over time.
Edit: it rebooted even in idle a moment ago (1th time) ???
Similar issue with youtube freeze and reset
I can validate your frustration. I am having problems with my HD2 freezing up as well and doing a soft reset on it's own. So the YouTube app opens up the HTC player and then it will play a few seconds and then freeze up. I also opened an MP4 movie file and view it with the HTC player and that also froze it. Last but not least, I have TomTom and that froze it after 15 minutes last night.
I have seen some postings that Tmobile and HTC will be releasing a new rom to fix some memory leaking issues so perhaps that might be it.
It started happening about a week ago for me. Please post any solutions you might find.
I am on:
OS v.5.2.21889
Mania v.2.5.20121412.1
ROM v.2.10.531.1 WWE
Radio v. 2.08.50.08.2
I have done some trail and error, played around with coreplayer and i noticed that when i set the video quality to FLV medium quality in the buildin youtube app in coreplayer i won't reboot that quick anymore, but after a couple of seconds it will eventually still reboot. If i set quality to high quality/high bandwidth i will reboot much faster (so this let's me think about some kind of memory leak/buffer overflow).
Furthermore luckly i don't have any problems with playing mp4 videos in coreplayer, i have tested this especially because of the youtube reboots, and it will keep playing for 1,5 hour without any problems, so maybe you could try coreplayer and see if that's a solution for your mp4 problem ?
But eventually it would be nice if these problems where sorted out so that the device will work like it is supossed to be
Already tried a TASK29 and a flashing a stock ROM from your SD card?
Ye, have tried task 29 (between each roms, i do use task to make sure that the phone is empty.) and when i went back to my 1.72 stock rom i did flash it from SD, but still no luck.
this happened to me today as i was logging onto the net. it did a full master reset.
Same thing happened to me after the unit froze. I pulled the battery, put it back in an it went into this continuous loop of starting up, going through the first couple of screens and then rebooting. What I eventually found to be the problem was that I had inadvertently bent one of the battery pins when I put the battery back in, not much but just enough to where it wasn't making contact. After I carefully straightened it out the issue was gone and it fired up as usual. I love simple fixes, of course this was after I task 29'd and reflashed which didnt correct the problem.
dfhgjkhgfeghjn
lemonspeakers said:
dfhgjkhgfeghjn
Click to expand...
Click to collapse
lol ? xD frustrated ?
thompsd said:
Same thing happened to me after the unit froze. I pulled the battery, put it back in an it went into this continuous loop of starting up, going through the first couple of screens and then rebooting. What I eventually found to be the problem was that I had inadvertently bent one of the battery pins when I put the battery back in, not much but just enough to where it wasn't making contact. After I carefully straightened it out the issue was gone and it fired up as usual. I love simple fixes, of course this was after I task 29'd and reflashed which didnt correct the problem.
Click to expand...
Click to collapse
hmm i only got the problem while i'm watching streaming video through 3g and on usb > active sync > pc data connection / some (cpu intensive) games
with wifi no problems at all, it plays youtube for more then a hour without a reboot, and i tested it multiple times to make sure), and booting is just fine without a single hickup
thompsd said:
Same thing happened to me after the unit froze. I pulled the battery, put it back in an it went into this continuous loop of starting up, going through the first couple of screens and then rebooting. What I eventually found to be the problem was that I had inadvertently bent one of the battery pins when I put the battery back in, not much but just enough to where it wasn't making contact. After I carefully straightened it out the issue was gone and it fired up as usual. I love simple fixes, of course this was after I task 29'd and reflashed which didnt correct the problem.
Click to expand...
Click to collapse
Hey, thank you @thompsd. This was driving me crazy on my phone. I finally took it back to a TMobile store for replacement and they put me on the phone with support before they would issue a replacement. Of course I was bewildered when they had me take out the battery and put it back in (which I had done a zillion times) and the phone suddenly worked. The person on the phone told me that it was fixed because I had to keep the battery out for at least 90 seconds. This made absolutely no sense, but it was hard to argue with success. I walked out of the store with my head hung low in shame.
Tonight, sitting in an airport lounge waiting for a flight, I noticed that my phone was hung so I pulled the battery to reset it. When I put the battery back in and started it, the phone went into the reboot loop -- displaying the boot screen for a couple of seconds and then shutting down and rebooting. I pulled the battery for 90 seconds. 120 seconds, 5 minutes. No joy. Realizing that this solution made absolutely no sense in the first place, I decided to search around again.
I found your reply in this thread and looked at my battery contacts. One of them was bent. I straightened it out, put the battery back in and the phone booted right up. Now I realize that when I was on the phone with TMobile, I must have put the battery back in that one time in such a way that inadvertently straightened the pin.
Hi all,
I have (maybe) the same problem with my HD2 i.e. when it is "doing something", well not idle, it sometimes restarts itself and then usually will not get out of the cycle of crash/reboot untill I remove the battery and wait for a few minutes before starting it again.
This is always more frequent if I am using a serious application such as sat nav. It also has only happened when the unit is connected to power, either on my desk or in the car (different power sources), but disconnecting it from the power after the cycle has started doesn't help.
I have assumed from the symptoms that it is caused by overheating and so leaving it switched off for a period allows it to cool.
I have got a return packet from Vodafone to send it for repair but I am loath to do this as it is likely to take 10 days and I suspect I might either get a recon unit back or "no fault found".
Does anyone think this could be battery related? If so I would buy a 2nd battery and test it.
Cheers, Gordon
I can confirm having the same problem.
Using BattClock (which shows a.o. the battery temperature) I was able to establish that the resets and reset loops happen once the battery temperature exceeds 31-32°C.
Contacted HTC support and received reply that the phone qualifies for repair.
PS. My wife just suggested providing me with a cooler bag, so I can enjoy reset-free phone during summer heatwave...
I had similar behavior, but it was due to the new ROM release (4/28/10). I loaded the official T-Mobile release date ROM (2/19/10) and the problem went away.
L.B.
Yesterday my battery charge got very low and shut the phone down. When I turned the phone back on without charging it kept rebooting time after time. I tried plugging the charger in but that didn't help. I took out the battery and put it back in and that still didn't help. I finally caught it when it was rebooting and pressed volume down and got the phone in bootloader to at least stop the constant rebooting. I left the phone on the charger and after about 1/2 hour I pulled the battery and put it back in and the phone was fine.
I am not wanting this to happen again. Maybe I will go back to an older ROM.
if i have some luck i will receive my phone tomorrow or the day after tomorrow.
i will let you know what has been repaired and if this solved the reboot problem.
today i received my phone back from the repair center.
The repair letter says that the display has being changed because it was not functioning anymore? (but when i sent the phone in the display was working like it should).
And the youtube problem is still there
Im having the same problem! i figure it was the battery overheating...or the rom or even probably a not compatible radio.....try to change all of these and is still restarting when ever it tries to connect to any data or internet usage. Ex. youtube, downloading of files from the internet, Remote Desktop even Microsoft My Phone still restarts.
even when i used to make/receive phone calls it would restart as soon as i picked it up to talk. but for this i had a solution witch as of now is working fine with out a problem.
if anybody else has this problem with the Receiving/making calls this should work.
1. Go to: Start/Settings/Connections
2. is the "TASK" tab choose "Manage Existing Connections"
3. In the "Modem Tab" has for options to choose from, normally is on "Auto", this was the problem. you would want to get it OFF AUTO.
4. Try all the other " voice Stream options Shown" and see witch one works for you without giving problems, and save. Im currently using "wap.voicestream.com." witch is the second option after Auto.
Well i hope this works for you guys if ur having similar problems, its actually work for me. GooD luck! hope this helps.
bitbank said:
I had similar behavior, but it was due to the new ROM release (4/28/10). I loaded the official T-Mobile release date ROM (2/19/10) and the problem went away.
L.B.
Click to expand...
Click to collapse
is it possible for me to know where can i get this ROM??
(official T-Mobile release date ROM (2/19/10).
this week i will receive my phone back for the 2th time.
Hopefully they have found the faulty component of the phone.
I will keep you informed
Just doing a reliability poll to see how everyone else is getting on with their phone so far. if you vote other please specify the problem so it can be added to the poll.
No way to delete emails from am IMAP emailaccount with stock samsung software. Emails always just reappear after next sync.
Random reboots
I voted 'Other'.
I get very occasional reboots. I've only had 3 or 4. Thinking about it, they seem to happen mainly after installing apps. It's not really a problem as the phone seems to works flawlessly after the reboot.
I also voted other. Wifi seems unreliable, often dropping out when selecting links in web pages. To gte it to work requires the wifi to be turned off and back on again. It's not browser specific as I've had it happen with both the stock browser and Dolphin HD. My router is set to G and the signal is strong enough according to Wifi analyser. I've tried changing channels but it seems to have made no difference.
Other than that the phone has exceeded my expectations.
My Sms and 3g crashed out the other night, but the phone gave no indication of it happening. This is unnerving as I'm a system administrator and rely upon sms to know when our servers are down.
Sent from my GT-I9100 using XDA Premium App
I've had a few lockups and phone reboots.
I also had the phone get very hot due to SyncmIDS taking 96% CPU and running the battery down quickly...
Finally the audio keeps disappearing - no sounds of any sort and the only way to get it working again is to reboot...
This is the latest ROM (as of today) running TouchWiz and no attempts at root.
I also have occasional wifi problems where it sticks at getting an IP, so you have a wifi symbol but it doesn't connect, stays using 3G.
Apart from when it got hot, the battery life is no worse than the Galaxy S... but the hot battery run down has happened a few times now.
So it's not bad for beta software shame it's claimed to be release software
USB OTG is a nice feature.
Much faster than my Galaxy S though and brilliant screen.
More issues...
Must have crashed and shutdown (black screen - had to press and hold the power button).
It just decided to reboot while it was sitting on the desk (screen off), as I heard the boot music.
My phone occasionally turns off on its own. Very annoying. I'm thinking of getting a replacement in case it's a bad apple.
Mine's fine - great in fact. I've only had it a week though
My phone is a week old tomorrow. It is bone stockTmobile and has been having force close/ freeze issues. Nothing specific that I can recall doing at the time. I have a moderate amount of apps and games I play on it. When calling or just using in general it freezes which I then have to restart or pull the battery if completely frozen. I have wiped the phone and went back to factory setting. It seems to make no difference. What have you guys done to fix this issue?? A guy I work with has the exact same phone and his works flawless. I normally close the apps when done and I regularly clear the memory in the ram tab to help keep things running good. My S2 also started getting force close and freezing issues after updating to ICS. While I was waiting for Tmobile to warranty the S2 I bought the S3. Now have similar issues. Plus this phone seems to be blessed with wifi dropout issues, complete signal loss (comes back after restart), cant disable the led, and takes a screen shot on its own without having to push home + power. Just wait long enough and viola Nice phone but a little bigger screen, and a little faster processor. Starting to wonder if I should just take back and enjoy the S2 till something better comes out. Is it possible I just received a LEMON??
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.
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Do you remember when were the times when the screen was unresponsive?
I've read somewhere that sometimes when the screen is woken up and is under some pressure this will happen, and the only way is to do what you did. It's not uncommon in touchscreen phones though, so I wouldn't worry about it.
The verge app was broken until the most recent app update. Also, the s5 seems to refuse allowing Dashlane's accessibility service from working properly. So no more auto filling passwords for me. Ugh. I hoped rooting might help but it didn't. Now I really can't wait for custom ROMs to start appearing. Samsung, you make great hardware (like amoled displays) but your software sucks. Even the software on my Samsung TV is stupid.
Yes on two out of three!
finotti said:
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Click to expand...
Click to collapse
The unresponsive screen is more than a little issue, it is being reported all over the web, and get's more severe over time. I'm thinking that it is a bad proximity sensor defect, either firmware, hardware or software. Some people are reporting along with myself that sometimes for no apparent reason, the screen will not turn on even though the phone is completely operational! This has happened to me four times now and I am stock with very few apps on my phone, five total games and Pandora. I do use a substitute launcher that I've used for years but I don't believe that would be the issue since others report the same issue with stock launcher.
The pop or skipping you speak of in sound happens to many of us who stream music in our automobiles. It even happens on the note3. The fix is simple for that one though! Turn the screen on. I was told that with many of the streaming software music programs that the phones CPU goes to sleep and does not offer enough processing power to the music program. I stream all day via bluetooth to my Auto's sound system and it will usually start to skip, click or whatever after the phone has been untouched for about twenty minutes. The second I turn the screen on the problem alleviates itself. You can find even more information by googling that one, in fact both of those! The heat one I have not had, both with stock battery and zero lemon high capacity battery. The phone very rarely get's warm. However, when I was using wireless charging it would get warm even after charging was complete but I believe that is a normal event with QI type tech.