Related
I am the happy owner of a newly Galaxy Tab
and am subject to a rather annoying problem!
Once my tab in hands, I undertake a full exploration of the unit
and all tests relating thereto (installation of
various programs, GPS, ...) Everything seems to be perfect!
But ...
I continue my tests and installs a game, known as
compatible with Tab (Angry Birds), the installation
goes without problems.
The problem arises when opening the game, screen
remains as frozen (freeze?) and reboot th Tab after
few seconds ....
It happens the same way on all the games
I have tested!
In wanting to see my pictures taken with the camera,
unable to open the gallery! The screen also freezes the Tab
!
I fear a hardware problem on my tab and can already imagine
having to return to the SAV
Has anyone ever encountered a similar problem with
Tab or its there a suggestion to solve this problem?
Any help would be greatly appreciated .
That both sounds very annoying as well as a problem I haven't personally heard before. I'm not sure, but you may have a faulty unit.
I'd try a factory reset. Go to Settings>Privacy>Factory reset and wipe the data. It will NOT touch your sdcard. See if it works. If not its the Tab it self.
that problem my friend, you are 1 of 25 lucky people out there with Hardware Faulty chipset. Some friends works for Best Buy and local cellular shops, are getting similar problems. No one know exactly why the problem happens.
I would just bring it back to shop you purchased and ask for refund NOT exchange. Cause exchange are likely to get one of few similar problem devices.
First of all, thank you for helping me to solve this problem.
At begining of story, when i first have my unit and discover this issue, i've tried to do a factory reset and a data wipe but nothing better ..
Then i attempt some flashings on the unit, i tried different firmware (JJ3, JJ4, JJ7, Roto JME, Roto JMI) but problem remains the same.
Like Chainfire, i think of a faulty unit.
I'm currently under JJ4 and don't know what was the initial firmware on the unit when i bought it, do you know i will have some problems if i bring it back with another firmware to the shop ?
Don't know aout your particular shop, but when i had a problem with my first unit here in the UK, i took it back to tesco on RotoJMEv4
Got another new unit and walked right out of there with no probs
Yeah just tell your problem then leave it there, they don't really check.
I had a similar problem with my I9000, it was rooted with custom ROM but they just took and it and fixed the problem... well in your case they will just replace it most probably...
You right, spandsbab ,
i decided to bring it back to my shop and they gave me just another, working one.
All is working great on this one
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different firmware(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Update:
I found sth strange about the call issue by chance: when I lock the screen maybe for more than 5 mins,then wake it up and make a phone call soon,the receiver can't work every times.However, when I put it into use(light the screen) for more than 3 or 4 mins,and then the receiver works again during calls.
What I want to say is: maybe there are sth wrong with the cpu setting or the power management?
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
takooo said:
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different framekworks(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Click to expand...
Click to collapse
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Product F(RED) said:
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Click to expand...
Click to collapse
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Magik_Breezy said:
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yep!! Last time I had flashed the ripper rom and then I found this issue.First I thought it was the problems that come from the rom,but after several tries then I thought it probably due to the hardware issue that I cant solve....
Anyway,thanks for your suggestions!!
takooo said:
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Click to expand...
Click to collapse
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Product F(RED) said:
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Click to expand...
Click to collapse
Ok,thanks a lot for telling me these!!! I've sent a email to the customer service and hope to get respond soon.Anything news i will update it.
My earpiece stopped working today. This is the second time the earpiece of my Xperia T died. The first time was in October when I had the phone replaced as it was within the one month period. The very same thing has happened again with me within a few months of getting my replacement handset. I was able to locate another person who had the very same problem on some forums. I definitely think that the build quality of this phone is not as it ought to be as it cannot be a coincidence that I got the same issue twice with two separate brand new handsets!
Have just booked a repair with Sony's authorised repairer (SBE limited in UK). Has anyone else faced the same problem here?
sshariff said:
My earpiece stopped working today. This is the second time the earpiece of my Xperia T died. The first time was in October when I had the phone replaced as it was within the one month period. The very same thing has happened again with me within a few months of getting my replacement handset. I was able to locate another person who had the very same problem on some forums. I definitely think that the build quality of this phone is not as it ought to be as it cannot be a coincidence that I got the same issue twice with two separate brand new handsets!
Have just booked a repair with Sony's authorised repairer (SBE limited in UK). Has anyone else faced the same problem here?
Click to expand...
Click to collapse
I had issues of people finding it hard to hear me..meaning mic volume isnt enough. Got it replaced within the one month period to a brand new one.
Issue seemed to have reduced then but now its there many times, thus I have to speak louder than usual. Yet couldnt be bothered to go for a repair.
Not many users seem to have this issue. When did you get your first handset? I got mine on end of Sept (more or less release day in uk..) I have a feeling its to do with a specific batch (similar to the peeling issue)
ruwsoft said:
I had issues of people finding it hard to hear me..meaning mic volume isnt enough. Got it replaced within the one month period to a brand new one.
Issue seemed to have reduced then but now its there many times, thus I have to speak louder than usual. Yet couldnt be bothered to go for a repair.
Not many users seem to have this issue. When did you get your first handset? I got mine on end of Sept (more or less release day in uk..) I have a feeling its to do with a specific batch (similar to the peeling issue)
Click to expand...
Click to collapse
I got mine at the release date as well! Then had it replaced after 3 weeks...
Solved the issue!
The exact details of this issue can be seen at talkDOTsonymobileDOTcomDASHthreadDASH56851?start=0&tstart=0
(Sorry for that bad URL as I am too new to copy links)
I did a factory reset, flashed ICS from JB Europe generic, then updated to UK generic JB via PC Companion. Still the problem did not go. Then just out of curiosity I checked if I could hear sound from my Sony supplied headphones, and I could. I then removed the headphones and bingo everything is back to normal.
I think there is an inherent software bug with the Sony software for this phone where under some odd scenario sound gets disabled. Maybe if anyone else gets into a similar situation they can take heed of the resolution. Saved a couple of weeks at the repair shop at least!
Same Problem
I had the same problem on more than one occasion in past plugging in handfree and unplugging would work but over the weekend i ended up doing a factory reset but still didnt work but strangly somebody rung me and ear piece now working! im still in warrenty should i send away?
sshariff said:
Solved the issue!
The exact details of this issue can be seen at talkDOTsonymobileDOTcomDASHthreadDASH56851?start=0&tstart=0
(Sorry for that bad URL as I am too new to copy links)
I did a factory reset, flashed ICS from JB Europe generic, then updated to UK generic JB via PC Companion. Still the problem did not go. Then just out of curiosity I checked if I could hear sound from my Sony supplied headphones, and I could. I then removed the headphones and bingo everything is back to normal.
I think there is an inherent software bug with the Sony software for this phone where under some odd scenario sound gets disabled. Maybe if anyone else gets into a similar situation they can take heed of the resolution. Saved a couple of weeks at the repair shop at least!
Click to expand...
Click to collapse
Had my Nexus 6 for 4 months now - originally had it on stock for a couple of months, it would constantly power off, usually when battery was less than 20% or when trying to access the stock camera or random apps.
So to try and resolve the issue I rooted the device and have now tried practically every ROM available and still have the same problem
Currently running SaberMod 5.1 with Vindicator kernel and the problem still happens.
Tried PA, CM12, PAC, Vanir, Chroma, Euphoria, LiquidSmooth, Terminus....you name it I've tried it.
Will probably be returning it to supplier but before I do would like to know if anyone has had similar issues - is this because of a bad batch of Nexus 6 phones? I guess it's hardware/battery related - but wondered if any software fixes were available?
I have started to face the same problem, mine shuts off usually below 10% but it's only a month old, so disappointed with nexus 6,not only was it effing expensive, it's not the premium device that Google boasted about with so many bugs, which include the speaker crackles and random shutdowns
Totally agree, why pay for a premium device to be plagued with problems?
I was going to try and find if there was a fix but might just return the device.
Really disappointed I expected a lot better for such a high end device.
FWIW, I've had the 6 since November 26th and don't have any issues. I'm sorry you've had issues but that doesn't mean the whole lot is bad. RMA and get a new one. There are issues with every device after it's launched, go to any forum and you'll see what I mean. You can't label the whole line defective just because of a few isolated problems.
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
thx1971 said:
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
Click to expand...
Click to collapse
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Diocat said:
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Click to expand...
Click to collapse
Thanks for getting back to me with this - I guessed there was an issue but didn't want to return the phone unless I was totally sure, so thank you again for clarifying this.
I am not happy to be returning it but looks like this is my only option.
I have the very same problem with my N6 bought in December 2014. Have tried factory reset multiple times without luck. I just gave it for service. The guy there said they would try reflashing the firmware and if that doesn't work I'll be given a replacement. I'm from India btw.
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
drkboze said:
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
Click to expand...
Click to collapse
Almost exactly what happened to mine: http://forum.xda-developers.com/nexus-6/help/refused-repair-moto-uk-device-rooted-t3077271/page2
TL;DR:
Dear xxx,
Thank you for contacting Motorola.
I have now heard back regarding your Nexus 6 unit. After carrying out the initial repair the engineers at our repair centre then discovered a more serious fault with the battery on the phone as it started to swell during their testing.
Click to expand...
Click to collapse
So if your phone is randomly shutting down when their is plenty of battery, and/or does the optimising 0/xxx apps at start up - get ready to RMA because you don't want a swelling battery and a possible explosion/fire...
I've submitted the device to their service centre and awaiting replacement.
Sent from my iPhone using Tapatalk
My device has been returned and will be replaced, no questions asked, as it is a recognised faulty phone.
So to re-iterate, all I was wanting to clarify was if there was a bad batch of Nexus 6 phones and whether or not mine could be one of them - and it looks like that seems to be the case.
I wasn't in any way saying the whole line of phones are bad but it's good to clarify that there is a bad batch out there and the suppliers are willing to replace them
Same exact symptoms
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
rocket808 said:
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
Click to expand...
Click to collapse
Yes on all points there. The random turn off when doing anything, app optimisation (very long) wifi passwords gone (very annoying) and restart again while optimising. And the resultant swelling battery..
It seems very few of us have experienced this, thankfully, but very worrying, I certainly wouldn't get another moto device after this.
Sounds like the very common battery calibration problem, which can be reset by following a set of instructions in the bootloader. Look around for them.
Bumping this as I think I've found the root cause of this problem. Are you guys using Google Fit? The replacement that I got was working fine till two days ago when I initialized/started using Google Fit. Device turned off twice. Then I disabled the app and the shutdown hasn't happened till now. If you guys are using Google Fit, try disabling the app and monitor it for a couple of days.
Well I managed to get a replacement phone from GiffGaff and guess what - same issue again!
Battery overheats, crashes on Camera App, resets WiFi, random app crashes
Have tried several ROMS including Android M to see if there is an improvement but unfortunately not - will try disabling Google Fit now and see if that helps but so far I'm really disappointed.
This device is supposed to be top of the range flagship Google model but for me it is a resounding fail.
I have got the same problem , but i cracked the top of my screen when i had the phone after a month , when i called Motorola they said they could take to repair but would cost £120 to fix screen as they cant send back with screen damage. Really frustrating as i know the screen isn't the fault. Anyone got any ideas ?
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
goinovr said:
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
Click to expand...
Click to collapse
Boot into fastboot, find bootloader logs and hold power for ~10seconds (till it resets by itself), best done on full battery, may help, if not you can try to calibrate the battery (requires root tho). If all this fails only thing left is to change the battery. Takes about 20mins and costs like 20-25usd (easy to do by yourself
Hey guys, hopefully someone here can point me in the right direction. Looks like i got screwed with my Tab S2. I bought a 9.7" cellular version from someone on Kijiji (Equivalent to Craigslist in Canada) and it was working just fine. I installed some apps and was just playing around with it. About two days later it started freezing and restarting when i would play a game or watch a video. Since then it has gotten progressively worse. I boot it up and 30 seconds to a minute later it turns off on its own. I thought it may be a software issue so i did a hard reset but the problem still persists. I took it into a Samsung repair center and they said that it is a pre-production model (IMEI is 00000000000000) and they cannot help. Any ideas what i can do to repair it. I just hate the idea of having a $400 paper weight