For those of you with a Samsung WP7 phone, it looks like there are some reports now about an update coming in 3 days to resolve this issue. This was posted on wpcentral: http://ow.ly/416NN
Related
My brother has a GNex. He is not as tech savvy as I am, so I try to help him out when I can (update his rom, troubleshoot issues, etc.). It's a bit difficult because I live in Texas and he goes to school in North Carolina. Long story short, he is having problems with his phone. He is having issues where the phone will not have any signal at all (literally can't make calls or text or anything). It is not the area he is in because I visited him and had zero issues with my GNex. His phone also says it is December 31, 1999. I found a few threads from a quick Google search describing similar issues, although it seems to be a variety of phones having the issue (I can't post links here yet because I am a 'new' user. If you want to see the threads I posted, this same message is posted at droidHive under Help/Galaxy Nexus and at DroidJunk under General Gnex Discussion). This must be some Samsung issue. He had the problem while running stock 4.0.2. Verizon sent him a ‘certified like new’ replacement and that was okay for a few days, then he had the issue again. I put him on Tranquil Ice 4.0.4 and that fixed the issue for a few days, then it came back. This has all been within the last couple of months.
Basically, I am wondering if anyone has previously heard of this and/or know how to fix it? All of the threads I noted above seem to have died and have not resolved the issue.
Thanks in advance for any feedback.
(in case you are wondering, I have a GNex running Junk with no serious issues and I'm loving it)
Just to update, my brother did a battery pull and everything seems to be working properly for the time being.
I'm still interested to know if anyone has more information about the problem described in the OP.
Hi
I've just bought a nexus 7 after returning my useless surface rt,I was a bit wary of getting one because of the various issues,like ghost touches etc.
But I took the dive and got one,I've checked the screen with yamtt and all seems OK,touchwood.
After using the nexus for an hour or so an update message popped up asking me to update to the latest version ,it doesn't give any details on the update,just that it will bring fixes and improvements etc.
I just keep thinking,if it ain't broke don't fix,I'm on build JWR66N,any advice on weather I should update would be appreciated,I've read a few posts about people updating then experiencing problems where there was none before.
Cheers in advance.
Not updating is never a good idea, just update I've had no problems with any of the updates
Sent from my HTC One using Tapatalk 4
Nope. We all buy nexus devices to stay on old defunct version of the Android OS...Never update. Everything gets better with age...
/Sarcasm
Well I updated my Nexus 7,it put build JSS15Q on my device,from having zero problems, I've now got the touchscreen issue.
Knew I shouldn't have updated
Hi, just got home from Best Buy with an 8.4 S. Got it for a decent price after price matching with Canada Computers. This is my first android tablet but I'm on my fourth android phone and I've rooted and played with roms before.
So we all know touchwiz lags right out of the box. I want to fix this. I'll replace the launcher regardless but I've got a couple questions:
1) People suggest waiting a bit before rooting in case the tablet is defective. Is this really necessary? Is there any way to run a diagnostic so I can figure out if there are hardware defects before rooting?
2) Does rooting really void hardware warranty coverage? This seems a little ridiculous. I've owned four android phones so far and not a single one has had a hardware issue that I didn't cause myself. Has anyone rooted and actually had issues that Samsung refused to fix?
3) Given that the official Samsung L build is coming to this tab soon, should I just wait until then before making any decision on rooting?
4) In the mean-time, I'll probably run the Debloater tool referenced here
I understand some of these are personal decisions but I'm curious what your opinions are!
This happened with me on Lollipop as well, I never got the OTA until after Xmas, still not a sniff of Marshmallow. May be it is just me, but in theory you think owning a Nexus device means you get updates sooner but for me anyway the reality is by the time you get the OTA other manufacturers already have it out. My S5 got Lollipop before my Nexus 7 2013.
Anyone else have this issue?
I wish I knew the answer to your question. A co-worker got LP with in days of release and my tablet didn't see the update come down until 5.1 was out. Then oddly enough I saw MM with in three days of release and the small update that came after it the day it was posted.
I'm sure Google has some weird plan that only makes sense to them on when and what get the updates but it sure isn't any forum of logic I can understand. I think part of is they push the update to some devices and wait to see the telemetric data come back for a few days to see if there is any major bugs before pushing it out to "everyone." It's not like Google doesn't have the resources to just pump the update out for all to get at once like iOS does.
I found this link to a class action lawsuit. I think that has to do with all the thread I have been reading about ever since my wife's Note 4 started to freeze, reboot and just die several times a day.
http://www.classlawdc.com/2017/04/25/investigation-samsung-galaxy-note-4-mmc_read-failed-defect/.
At first I thought it was a battery problem. When a fresh aftermarket battery and a factory reset didn't fix the problem, I thought it had to be the new OTA updated andriod 6.01. After reading many of the thread regarding the impossibility to downgrade from QG1 6.01 to any of stock older ROM on ATT SM-910A I resign to use the band-aid (wake-lock app) to keep us from buying a new phone. Then, out of curiosity, I sift through the Galaxy Note 4 forum and found this thread (https://forum.xda-developers.com/note-4/general/emmc-class-action-lawsuit-t3678249) and I now understand that this was a hardware problem that may have been intentional or at least overlooked manufacturing defact. That explains the reason this problem shows up different times beginning from late fall of last year to my problem last week. And why some of the people who took their phones to Samsung repair centers and had the motherboard replaced for about $70 had their phones fixed properly. I hope this answers many of the that was asked on many other thread.