Related
Hi guys, haven't been here since my WIN MOB days. Glad the place is hopping as usual.
Bionic users seem to be experiencing a total lockup on sleeping handsets. There is a rather extensive thread over Moto support and the mod seems to be paying attention.
Just popped in to ask your experiences and the frequency with which you guys are seeing this and any possible remedies.
I've seen a couple of very short threads here, but nothing with any follow-up.
Thanks,
RMD
I have had this happen on multiple occasions, the power/wake-up button stops working and the only way to get the phone back is pulling the battery. The last time it happened was last night, and even after the battery was pulled it wouldn't come back up. I only got my phone back after switching out the battery with my extended battery.
Does anyone have a link to the thread at Moto support?
Seems like it happens more often when the phone has been sleeping for longer than 30 mins for me. Go for a run, come back and can't wake the phone up. Or go to sleep and wake up in the morning with it blacked out.
This happened to me for the first time today, but it happened twice within about 2 hours. Pulling the battery was the only way to get it back.
This has been happening to me for the last few days, only things is Im rooted, I was considering unrooting until customer roms and kernels come out.... but seeing that you guys are having this issue with the phone stock.... quite weird, hopefully a firmware update will come out for this soon
I've got mine rooted and have never had this issue before. I have not removed or frozen any apps though.
Also I leave my system on performance mode in the battery profile.
In fact, I left it on my nightstand last night without plugging it in. Woke up a few times and checked the time each time and the phone always woke right up.
So, I want to say mine started locking up when I selected "in pocket detection."
I just now thought about it reading one of the post here talking about going for a jog. I just turned it off and will see if that makes a difference. I get a lock at least once a day.
I have been rooted since day 1 and have had Bloat removed since day 2 and "knock on wood" have never had this issue.
I've been getting this too. It only seems to happen at home where I have only 3g available. Are you guys that are having this happen in a 4g area or is it just 3g as well?
I had this issue on the second day and never since, but being how "lucky" I am as I post this I will have the issue...
Had this happen once to me today while i was severely multitasking then hit the power button by mistake. I gave up after about 5 seconds and pulled the battery
I have had this happen to me about 3 times now. Once during texting, once after breakfast, and once after movie. I think this is pretty damn unacceptable for a $600 device that was delayed so much.
Never had the black screen. However after long standby times the pattern screen doesn't register correctly the first few times. Unrooted.
Sent from my DROID BIONIC using XDA App
Luckily Chicago and the suburbs are 4g so im it all the time. So far inly in 4g has it happen to me
Sent from my DROID BIONIC using Tapatalk
Second day it happened but nothing since this and the huge 3G drop error is big on the moto site maybe an update soon
Sent from my DROID BIONIC
mine did it once, but after i rooted i havent had it happen since.
Chbimmer said:
So, I want to say mine started locking up when I selected "in pocket detection."
I just now thought about it reading one of the post here talking about going for a jog. I just turned it off and will see if that makes a difference. I get a lock at least once a day.
Click to expand...
Click to collapse
I had this same issue on Day 2 of having my blessid Bionic... Didn't realize why my screen kept going to sleep every 5 seconds. So after taking my phone to VZW to have it looked at (and the rep had no clue what was going on)--I realized that my in-pocket detection setting may have been the culprit.
Not happening to mine. However I do notice apps deleting themselves when transferred to my SD card. Rumor is they are prepping an update soon... I sure hope so. But the good news is the screen is growing on me, and I love the phone. It reminds me when I first bought My Samsung LED TV w/240 refresh rate. My eyes took forever to adjust, now I cant watch tv any other way.
Rip Syntaxx said:
I had this same issue on Day 2 of having my blessid Bionic... Didn't realize why my screen kept going to sleep every 5 seconds. So after taking my phone to VZW to have it looked at (and the rep had no clue what was going on)--I realized that my in-pocket detection setting may have been the culprit.
Click to expand...
Click to collapse
So, I turned in pocket detection off and it has not had an issue since I posted last.
Chbimmer said:
So, I turned in pocket detection off and it has not had an issue since I posted last.
Click to expand...
Click to collapse
Good deal... Glad to hear it. It was gonna drive me nuts. This was my first time being an "early adopter". I usually wait about 3-6 months before buying a popular phone to allow all the bugs to be worked out. So getting this phone 2 days after its debut--you can see why I was nervous to have a fully-functioning phone!
I have been through 2 phones already, this one here is the worst yet. Within the 1st hour of use it had rebooted 3 times. Now it seems to happen at random.. the phone can be sitting idle on the table and it will randomly reboot.
Anyone else having issues this bad?
Chr0nicDreamz said:
I have been through 2 phones already, this one here is the worst yet. Within the 1st hour of use it had rebooted 3 times. Now it seems to happen at random.. the phone can be sitting idle on the table and it will randomly reboot.
Anyone else having issues this bad?
Click to expand...
Click to collapse
Mine's done it about 3 or 4 times in the month I've owned it... perfectly acceptable and better than my previous Android device... or my iPhone before that as a matter of fact.
I have to wonder if it is due to some piece of software you have installed.
The new phone was received today. I had only added my gmail account to it and not restored anything on it yet. it was bone stock with the exception of the account. and it rebooted now 5 times in the last 1.5 hours. The last 2 times were done AFTER a factory reset
Mine reboots maybe once or twice a week, which while annoying, I can live with.
<Removed>
Youssarian said:
That bad no, but mine had the occasional reboot as well and that was completely stock. It did it after resetting the vivid. The next logical thing was to back off the stock bloatware / spyware one at a time and of course the stock app uninstall is very limited, but I did what I could and it still did it. I blamed Carrier IQ, which may, or may not be true, but I blame it anyway. <G>
Click to expand...
Click to collapse
What I have come down to is returning it to amazon. After speaking to a very polite and helpful rep he had state they have been getting lots of returns for locked bootloaders as the main reason but also random reboots. So he gave me the skyrocket for free i just have to make sure that upon delivery I hand the vivid to UPS. I really Hate to leave HTC but this is something I cannot deal with as I need a phone that works since it is tied to my business.
I've had mine for a couple weeks now and it has done it once. Freaked me out though. It was just sitting on the car seat when I happened to look over, it shut off briefly and went to the splash. I thought about returning it at that momnet... and still am. If It wasn't so new, I probably wouldn't care.
Mine did this while charging and went away with new battery. I called HTC and they sent one out.
Bad batch of phones?
There is another, older thread on this same issue. I have experienced reboots three times in this first month, but not in the past week or so. Based on your experience, and some other issues in other threads, I think there must have been a bad batch of phones. It's too bad a replacement did not make things better.
I used to have random reebots, but for the past couple weeks it hasn't happened. Not worried about it anymore.
I don't really get random reboots anymore but it freezes sometimes while trying to lock/unlock the phone. Just emailed HTC to see if my device is faulty or if its a known issue.
Sent from my HTC PH39100 using XDA App
travisxcore said:
I don't really get random reboots anymore but it freezes sometimes while trying to lock/unlock the phone. Just emailed HTC to see if my device is faulty or if its a known issue.
Sent from my HTC PH39100 using XDA App
Click to expand...
Click to collapse
I just got a call from HTC regarding a failure to help resolve an issue and the bad review i gave them via their survey lol.
I've had a strange bug since I got the phone that I'm wondering if anyone else has seen (don't think it is hardware).
I can reproduce it every morning after I wake up. Conditions are as follows:
Phone is on the clock daydream while charging. I use Sleep As Android as my alarm. Every morning when my alarm is going off and I reach for my phone half of the screen is not working and or black.
I just had a recurrence of this in the xda app after I lost wifi connection and was exciting a thread (pressing the back button) during the handoff to LTE. Easy fix is to just hit the power button to turn the screen off then turn it back on. Works right away.
Anyone seen or read about anything similar?
Thanks!
I made a post earlier about screen touch issues and this is one of mine as well. I can't reproduce it like you can but the right half of the screen just drops off to touch.
Have you seen the half (or third) of the screen go completely black? Seriously Wtf. I've only had it happen probably 4 times.... Comes back on immediately and worms as expected if I press the power button twice.
EmperorX said:
Have you seen the half (or third) of the screen go completely black? Seriously Wtf. I've only had it happen probably 4 times.... Comes back on immediately and worms as expected if I press the power button twice.
Click to expand...
Click to collapse
Sounds like you have the ATT model which was recalled for that very reason.
http://www.droid-life.com/2014/11/2...p-nexus-6-inventory-back-due-to-software-bug/
hsj1906 said:
Sounds like you have the ATT model which was recalled for that very reason.
http://www.droid-life.com/2014/11/2...p-nexus-6-inventory-back-due-to-software-bug/
Click to expand...
Click to collapse
Picked it up from tmobile on Wed morning.
Also, those issues seem different from what I read.. Screen is *completely* black and they get stuck. Mine works fine 100% except when I wake up with the prior conditions (over night, phone is on clock daydream, dimmed and I am woke up with Sleep As Android alarm). It has only happened once in any other circumstance. Also, my phone updated to LRX21O upon first boot.
At this point I can't tell if it is software or hardware... Not sure how tmobile handles this as I bought directly from them (no insurance as of yet) or if I go straight to Motorola?
I just wish I could conclusively rule out a hardware issue.
I'm having a similar issue. It seems to definitely be intermittent though. Also, I've only experienced it when my phone is in landscape mode. It goes back to normal when I flip it to portrait mode.
Did you ever find anything else out about the issue OP?
trustinhate said:
I'm having a similar issue. It seems to definitely be intermittent though. Also, I've only experienced it when my phone is in landscape mode. It goes back to normal when I flip it to portrait mode.
Did you ever find anything else out about the issue OP?
Click to expand...
Click to collapse
Nothing other than what is in here. Still happens to me, though much less frequently. Hoping the 5.1 update rumored for Feb solves some of the quirks.
I honestly think this is a hardware issue of some sort. I had my original Nexus 6 for weeks and throughout heavy usage, I never had any issues. The first day I received a replacement device from Google, half of my screen would freeze/go black when in landscape watching videos, playing games, and sometimes even browsing the web. This was with 100% stock ROM and kernel without root (which rules out that being an issue). I tried reflashing the stock image and the issue still persists.
I contacted the GPS customer service last night and ordered another replacement device. This is issue is certainly specific to this phone, my first device was used heavily and this never happened even once.
I am convinced it is hardware as well.
I am experiencing the same issue with my phone and opened a ticket with Google yesterday and I want mine replaced. It's not just the Nexus 6 that's suffering from this as some Droid Turbo users are experiencing it as well.
lianw said:
I am convinced it is hardware as well.
I am experiencing the same issue with my phone and opened a ticket with Google yesterday and I want mine replaced. It's not just the Nexus 6 that's suffering from this as some Droid Turbo users are experiencing it as well.
Click to expand...
Click to collapse
Same thing here. Tmobile 64 GB nexus 6. Bought mine from T Mobile, but they don't have a replacement to send me, so I contacted Motorola, and they sent me a new one that arrives tomorrow. I hope the same thing doesn't happen with this one.
Sent from my Nexus 6 using XDA Free mobile app
Look on the positive side of things, 50% less battery drain due to screen usage...
I still think this is, in my case, specifically software. Other people have reported different issues that are most likely hardware, don't think mine is. Also it has only happened two or three times in the past month, seems to with screen on and rotation occurring at the same time, though I can't confirm or repro reliably.
Well, just had my replacement processed over the phone. Only potential issue is that they said it may be a refurbished device. Anyone know how/if there is a way to tell??
I am not sure if this is somehow related-but my first Nexus 6 I got from t-mobile was working fine and on the second day of owning it the touch screen stopped working! I mean it won't register any touch whatsoever! The phone was just charging and I just used it like 30min ago....tried rebooting, resetting-nothing helped-went to a t-mobile store and replaced with a new one. The second one works...for now. The strange part is that they were no issues-it worked flawlessly and all of a sudden just stopped responding to touch.
I have never experienced issues like this with any smartphone in my life-I have owned android smartphones ever since the G1 was released...
Sleeepy2 said:
Well, just had my replacement processed over the phone. Only potential issue is that they said it may be a refurbished device. Anyone know how/if there is a way to tell??
Click to expand...
Click to collapse
T mobile didn't have any available devices to send me, so I contacted Moto. Moto sent me a brand new phone.Build date is December 16th. So far no problems, but I just got it today. I'll report back if anything goes wrong.
Sent from my Nexus 6 using XDA Free mobile app
NastyNeil said:
T mobile didn't have any available devices to send me, so I contacted Moto. Moto sent me a brand new phone.Build date is December 16th. So far no problems, but I just got it today. I'll report back if anything goes wrong.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do you see the Build date?
Sleeepy2 said:
Where do you see the Build date?
Click to expand...
Click to collapse
On the box. Under the barcodes.
Sent from my Nexus 6 using XDA Free mobile app
NastyNeil said:
On the box. Under the barcodes.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanx :good:
NastyNeil said:
On the box. Under the barcodes.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Can you post a picture of where? I don't see any dates listed on the box.
On the bottom right just before SeQ#
But a better way to check is to boot into the bootloader/fastboot hit valume down until you see barcode then push power.
For me the date it shows is 1 day before the date on the box. The box says 2014-11-16 bootloader says 2014-11-15.
I am currently wearing my 4th OG Pebble.
4th.
I have had the screen tearing issue come up on every one, and every one was faithfully replaced by Pebble, which is nice. My first three I wore in the shower and in the pool, per the various ads I saw where people showered and swam with it, and my wife was like dude, quit wearing it in the water. So my latest warranty replacement has never been wet. The last two days, I've had the screen thing again.
Again.
I can't afford a Pebble Time at the moment, or I would go that direction in the hopes that they figured it out.
I know that there is a solution involving taking the watch apart and placing a small plastic shim inside; has anyone done this successfully, did it work, how difficult is it REALLY, and what kind/size shim did you use?
Sent from my XT1254 using Tapatalk
OMG! I hate this problem. Happens on mine all the time. I had a friend tell me it doesn't happen if you use the stock watchfaces. I've notice it actually does happen more on certain watchfaces for some reason. I've never tried the repair trick. Switching watchfaces HAS helped a bit though. Which makes me think, is it really a software issue?
I don't know about inevitable, but given that the reason is a hardware connector, that's probably likely. Water has nothing to do with it at all. All four of the Pebbles we own with the old style connector have been wet numerous times with no harm.
I can't speak for everyone's use but my wife and I have 1 OG Pebble and 3 Pebble Steels between us.
I only use the OG Pebble for working out and I turn it off between workouts. It has never had a screen tearing issue. It's the screwback later model of the OG.
My wife's Brushed Silver Pebble Steel, which was pre-ordered on announcement day, has never had a screen tearing issue.
My original Matte Black Pebble Steel, ordered on announcement day as well, did have the screen tearing issue and Pebble quickly RMA'd it and told me to keep it as well as the new one. The warranty replacement (I was actually a couple of months out of warranty) has never had the screen tearing issue.
Since it was already broken/spare I did attempt the business card shim fix on my original Matte Black and it has worked beautifully. Since my brother wanted to see if he would use a smartwatch, I lent the repaired one to him to wear during his paramedic clinicals and he hasn't seen any screen tearing at all while exposing it to God knows what. It was an extremely easy fix. I followed this youtube tutorial https://youtu.be/c-3pfh-bx_w and it was spot on.
If you have the screwback version of the OG Pebble then the fix is pretty straightforward. If you have the glued together version then you're probably better off buying another one if you want to keep using Pebble.
If any of our other three watches did start having screen tearing I feel 100% confident the shim fix would correct the issue entirely.
Worked like a charm! Thanks,
Sent from my XT1254 using Tapatalk
arizonaomnia said:
Worked like a charm! Thanks,
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Glad that worked for you. Pebble has always been great at RMAing my messed up Pebbles. I too had the 4th one start to go so I emailed them. They said they'd replace it but I inquired about testing a beta with new hardware or seeing if there was something else they could do. I also asked for a phone number to speak to someone about it. They replied that they do not have a phone system and there are no betas of the OG Pebble but did offer me a Pebble Time. I took their offer even though I liked the OG Pebble firmware. Its worth a try if you are still having troubles down the road. Good luck.
danbest82 said:
Glad that worked for you. Pebble has always been great at RMAing my messed up Pebbles. I too had the 4th one start to go so I emailed them. They said they'd replace it but I inquired about testing a beta with new hardware or seeing if there was something else they could do. I also asked for a phone number to speak to someone about it. They replied that they do not have a phone system and there are no betas of the OG Pebble but did offer me a Pebble Time. I took their offer even though I liked the OG Pebble firmware. Its worth a try if you are still having troubles down the road. Good luck.
Click to expand...
Click to collapse
Thanks. Unfortunately, my Pebble (which is my third) was rejected by them recently as being out of warranty.
Sent from my XT1254 using Tapatalk
I'll just re-iterate that they took back my used Pebble Steel (RMA) and sent me brand new one and it hasn't torn yet. So, great support and us early folk have that tearing a possibility at any time
Side note-I can't get it to pair with my vs985 any more (kinda makes it useless). It's likely something with the new CM13-based ROM AND my phone (same Rom - OctM pairs fine with my Nexus 7). I'm now seeing the LE radio and the standard from the Pebble and CM13 doesn't like to pair with the regular. I'm going to do some searching today to see if there's a fix.
Pebbles!
FWIW, my Kickstarter Edition Pebble is still holding up just fine after daily use for close to two years now (I got it used). That said, a Pebble Steel I was recently working on from 2015 did have the issue. Seems like they got it right at first and then forgot how.
jimbob_sf said:
I'll just re-iterate that they took back my used Pebble Steel (RMA) and sent me brand new one and it hasn't torn yet. So, great support and us early folk have that tearing a possibility at any time
Side note-I can't get it to pair with my vs985 any more (kinda makes it useless). It's likely something with the new CM13-based ROM AND my phone (same Rom - OctM pairs fine with my Nexus 7). I'm now seeing the LE radio and the standard from the Pebble and CM13 doesn't like to pair with the regular. I'm going to do some searching today to see if there's a fix.
Click to expand...
Click to collapse
Cyanogenmod Roms used to have issues with being finicky when it comes to Bluetooth, so that kind of behavior wouldn't necessarily surprise me.
I didn't think it was the Pebble. Thanks for noting it for others!
Sent from my HTC6545LVW using XDA Labs
My OG Pebble Steel has been running fine for about nearly a year now, screen tearing started showing up but been super minimal....
Hay guys,
Edited: on 07/07/2016: Problems First; My AT&T Galaxy S6, reboots randomly, dies instantly and some times freezes, doesn't matter what app i am on. The full story is here if interested, please read below;
I bought a used AT&T Galaxy S 6, 64 GB Black sapphire, Now running 6.0.1 (i sideloaded it) and it has a problem which you guys call it deep sleep problem (I call it, dying phone with no reason) when i bought it, it was running 5.1.1 then (probably BOJ7), and the second day i noticed that it was dead, (i remember i was taking some selfies, pictures, i locked it and after more or less 15 or 20 minutes i wanted to take some more pics, i saw it was not waking up). And to my surprise, I have checked it, when i call the number which is in that phone, the call goes and i can listen on my other phone that the bill is ringing but actually my device doesn't ring at all (while dead) (I have also seen once that the notification LED was blinking Blue, yet the phone was off, itself)
So, story short when i saw the device was unexpectedly off i tried to switch it on by the following methods;
i pressed all the button many times but it didn't respond until, i pressed and kept holding recovery boot combination i.e. volume down + volume up + Power buttons and it booted.
Later on it was good, after two days, it did it again.
Now my concern was rising about Galaxy S6's sudden deaths, (I still don't know whether i should call it a deep sleep and awake problem or it is something related to hardware) so, i thought lets find a way and upgrade it to MM. I searched the xda and found this
Updating to Android 6.0.1 G920AUCU3CPD6 Step by Step {http://forum.xda-developers.com/att-galaxy-s6/general/updating-to-android-6-0-1-g920aucu3cpd6-t3371884}
I upgraded my phone and thought it's fine now, but to my surprise, the phone went off while it was in my pocket with almost 70% battery charged. I was shocked, yet started it with the buttons combo, and yesterday when i left it charging while the battery was about 87% charged, I thought let it go to 100% but when i picked it up after 15 minutes and pushed the home button to see the status the phone was dead again with a RED LED light on while the screen was off, when i pressed the home OR power button the screen showed a big green battery with 100 % Charge (which was indicating as i powered it off and kept charging)
Now my question is that " What the hell is going on?"
If it was a rooting problem? Then, I did an odin flash of BOJ7 with all four files AP, CP, CSC and his child. which should have removed the rooting, and to confirm it whether my device is rooted or the KNOX tripped or not, i have checked the knox it is 00000 which means the KNOX is not tripped.
Please help me guys, this was my dream phone, i can't buy a new one with warranty, and i can't loose it or live it with this problem, my days suck.
please help me,
And today I've seen a new thing may be it's the real problem but I really got it today. I was surfing the net and twitter my AT&T Galaxy S6 suddenly went off and I had to force start it.
Hay guys, i need your help, am i missing you all?
Hay guys, Talvigi back,
As far as no body is interested in my post and may be no one has faced such problem before, so, i am back with some updated information;
Day before Last night, I was very much worried about my phone's behaviour, even i was thinking to show it's way out. But when i was a bit asleep yet awaken i thought way not try to factory reset the device from recovery, formate system devlock and cache partitions?
And i did it while i was half asleep and let the device update it's builtin softwares and WOLLA, it's second day my beloved AT&T specific Galaxy S6 hadn't misbehaved yet, (till now, may be it will make me lying just now)
Edit: (Third Day):
Third Day guys its third day and still my phone has not misbehaved after the above mentioned factory reset, and i hope this will continue to work like that.
Edit: Fifth day:
Sorry Sammy boy but you are a sucking OEM, after two good days my AT&T Galaxy S6 is again misbehaving with me, it again deep slept, just after seconds when i was surfing the facebook and i got lock my device for some seconds. As soon as i wanted to unlock it again i saw that the device was once again not waking up hence i had to push both volume and power buttons to start it.
And it did the same thing while it was kept on my table for a couple of hours.
It's now making me crazy to sell it again and go for a galaxy S5, it least i haven't seen this problem, i actually haven't listened this kinda problem in them from any where.
Edit; Now after a lot of days of sudden deaths and instant restarts, it has started to freeze now, I have not seen this before. I mean when I am using facebook it freezes but doesn't restart as far as I have seen it twice with freeze problem. Now I can say that it is indeed a software problem may be we can suggest it to be a kernel related problem.
So is it because I might have used a 32 GB specific ROM on a 64 GB device?
Is there a real difference between 64 GB and 32 GB ROM.
Hell with the AT&T Galaxy S6.
talvigi said:
Hay guys, Talvigi back,
As far as no body is interested in my post and may be no one has faced such problem before, so, i am back with some updated information;
Day before Last night, I was very much worried about my phone's behaviour, even i was thinking to show it's way out. But when i was a bit asleep yet awaken i thought way not try to factory reset the device from recovery, formate system devlock and cache partitions?
And i did it while i was half asleep and let the device update it's builtin softwares and WOLLA, it's second day my beloved AT&T specific Galaxy S6 hadn't misbehaved yet, (till now, may be it will make me lying just now)
Edit: (Third Day):
Third Day guys its third day and still my phone has not misbehaved after the above mentioned factory reset, and i hope this will continue to work like that.
Edit: Fifth day:
Sorry Sammy boy but you are a sucking OEM, after two good days my AT&T Galaxy S6 is again misbehaving with me, it again deep slept, just after seconds when i was surfing the facebook and i got lock my device for some seconds. As soon as i wanted to unlock it again i saw that the device was once again not waking up hence i had to push both volume and power buttons to start it.
And it did the same thing while it was kept on my table for a couple of hours.
It's now making me crazy to sell it again and go for a galaxy S5, it least i haven't seen this problem, i actually haven't listened this kinda problem in them from any where.
Hell with the AT&T Galaxy S6.
Click to expand...
Click to collapse
May I ask, Why am I tagged in this?
hyelton said:
May I ask, Why am I tagged in this?
Click to expand...
Click to collapse
Sorry man, @hyelton: but you are the great hero for me,
You have been so much helpful to me as well as to many others i have seen,
And to tell the truth, i didn't tag you to help me specifically on this problem,
but i knew you will be the only one to notice me in this crap.
And i believe you have read my problem and have at least thought once, about my situation, haven't you?
And i also know you can off course guide me, or lead me a way through.
Please don't be rude, i beg your kind honour to please suggest me a way out there, any way out! :crying::fingers-crossed::crying::fingers-crossed:
Because there are many people in this forum but you can see no one, no one even noticed my problem.
Hello, I was tagged in your threads and received the notification while I was sleeping. First of all my Galaxy S6 was bought by me on May 6 2015 at an Official AT&T Store, the same Store were, nine years ago, I open a contract account for mobile service. Before Android phones I was a Blackberry user. Never root a phone, never side loaded a Google Platform Upgrade, never bought a used phone. The only time I bought a phone outside an Official AT&T Store was when I bought a brand NEW Google Nexus 5 at Amazon and God knows that my former Nexus 5 was the best phone I ever owned. I always owned the top of the line Blackberry, the Bold series. And all my formers Android phones bought at AT&T were Flagships phones at the moment I bought them. OK now, I read all your threads and when you applied a Factory Data Reset you do, in my humble opinion, the right thing . Unfortunately the problem at your phone is beyond a Factory Data Reset. My advise is that you must go to an AT&T Official Store and ask for a new Nano Sim Card. If that's not work go to an Official Samsung Repair Store or Center. If that's not work, then my friend, take out the Nano Sim Card of your Galaxy S6 and bought a NEW Google Nexus 6p directly from Google or Amazon and push the Nano Sim Card in. You are going to have peace on earth running a Google Nexus phone at AT&T. Remember my fried, NEVER AGAIN buy an used phone and by the way don't side loaded Google Platform Upgrade. Just wait for the OTA regarding Platform Upgrade. I'm really sorry for the bad experience with your Galaxy S6.
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
emilioaponte said:
Hello, I was tagged in your threads and received the notification while I was sleeping. First of all my Galaxy S6 was bought by me on May 6 2015 at an Official AT&T Store, the same Store were, nine years ago, I open a contract account for mobile service. Before Android phones I was a Blackberry user. Never root a phone, never side loaded a Google Platform Upgrade, never bought a used phone. The only time I bought a phone outside an Official AT&T Store was when I bought a brand NEW Google Nexus 5 at Amazon and God knows that my former Nexus 5 was the best phone I ever owned. I always owned the top of the line Blackberry, the Bold series. And all my formers Android phones bought at AT&T were Flagships phones at the moment I bought them. OK now, I read all your threads and when you applied a Factory Data Reset you do, in my humble opinion, the right thing . Unfortunately the problem at your phone is beyond a Factory Data Reset. My advise is that you must go to an AT&T Official Store and ask for a new Nano Sim Card. If that's not work go to an Official Samsung Repair Store or Center. If that's not work, then my friend, take out the Nano Sim Card of your Galaxy S6 and bought a NEW Google Nexus 6p directly from Google or Amazon and push the Nano Sim Card in. You are going to have peace on earth running a Google Nexus phone at AT&T. Remember my fried, NEVER AGAIN buy an used phone and by the way don't side loaded Google Platform Upgrade. Just wait for the OTA regarding Platform Upgrade. I'm really sorry for the bad experience with your Galaxy S6.
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank You sir for such a detailed reply, my bad luck with S6 is that I love it so much but when it comes to your life you will better lose your eyes. I think I will somehow sell it back and will not buy any second hand phone again.
Sent from my SAMSUNG-SM-G920A using Tapatalk
talvigi said:
Thank You sir for such a detailed reply, my bad luck with S6 is that I love it so much but when it comes to your life you will better lose your eyes. I think I will somehow sell it back and will not buy any second hand phone again.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
My friend please don't lose your eye and work hard so you can buy a brand new Samsung Flagship, Galaxy S7 or a Note 6. Don't forget, far beyond the Manufacturers Flagships, far beyond your worst nightmare is the Google Nexus Phone .
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
Well thanks for the suggestion but do you know, I will have to work 8 hours a day for five month and save 50% of that earnings, if I want to buy a brand new Galaxy S7, and for you my dear, that would be not more then 15 days half earning or 8 days full. So, to buy a flagship, in my dreams! Yet I will try to manage on a Huawei X5 or oppo F1
Sent from my SAMSUNG-SM-G920A using Tapatalk
emilioaponte said:
My friend please don't lose your eye and work hard so you can buy a brand new Samsung Flagship, Galaxy S7 or a Note 6. Don't forget, far beyond the Manufacturers Flagships, far beyond your worst nightmare is the Google Nexus Phone .
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
Click to expand...
Click to collapse
talvigi said:
well thanks for the sugg estion but do you know I will have to work 8 hours a day for five month and save 50% of that earnings, if I want to buy a brand new Galaxy S7, and for you my dear that would be not more then 15 days half earning or 8 days full. So, to buy a flagship, in my dreams! Yet I will try to manage on a Huawei X5 or oppo F1
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Sent from my SAMSUNG-SM-G920A using Tapatalk
talvigi said:
Well thanks for the suggestion but do you know, I will have to work 8 hours a day for five month and save 50% of that earnings, if I want to buy a brand new Galaxy S7, and for you my dear, that would be not more then 15 days half earning or 8 days full. So, to buy a flagship, in my dreams! Yet I will try to manage on a Huawei X5 or oppo F1
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
My dear friend at 16 years old I left my parents house and work hard and studied hard. Now I'm 60 years old and still work hard. That's the way life goes, don't fight it. You are a good person , work hard and enjoy your life and all the Android phones you are going to have.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Somebody, help me, please. My system is really unsustainable and doesn't tell me when to stop working and when to restart.
Edit; Now after a lot of days of sudden deaths and instant restarts, it has started to freeze now, I have not seen this before. I mean when I am using facebook it freezes but doesn't restart as far as I have seen it twice with freeze problem. Now I can say that it is indeed a software problem may be we can suggest it to be a kernel related problem.
So is it because I might have used a 32 GB specific ROM on a 64 GB device?
Is there a real difference between 64 GB and 32 GB ROM.
Sent from my LG-V410 using Tapatalk
Well, guys i somehow have been able to maintain my device to keep away from all those misbehavings which it had to do all the time. But i don't want to exaggeratedly lie that they are gone now, they are here, and they also sometimes show there faces but rarely, very rarely indeed. It all could happen after a couple of factory resets and keeping the device away from auto updates mostly from googleplaystore.
Well I have ODIN back and now i'm back on 5.1.1 BOJ7. And surprisingly the reboots are still here, I think, will have to kill my wish of being on Galaxy S6 for some more months and I will have to go back to the market and buy a LG G4 or Galaxy S5 may be?
People say their experience with Marshmallow has not been good but i would mine was the worst with S 6.
I think this device has a factory fault, but as far as i have bought it in used condition and the device is an AT&T device, that too out of the US, so samsung would surely won't help me, neither i have any warranty here.
I hat you Samsung/AT&T for making such a piece of crap.
Any body in this world has the same kind of problem with the Galaxy S6 AT&T 64 GB, or I am alone?