Need some info regarding WiFi on Nougat 7.1 - Nexus 5X Q&A, Help & Troubleshooting

Hey people.
I was thinking of buying a second hand Nexus 5X.
Found and offer with the 16GB version, tempered glass, Dbrand case and full accessories.
The seller says it is running Android 7.1.1 and WiFi doesn't work (it turns on, but doesn't find networks) due to driver problems.
Before committing to anything I'd like to know if this problem is actually real, and not just a hardware issue on that particular device, and if there is any workaround or fix yet.
I'm gonna put a custom ROM on it anyway, but I wanna be sure that this issue won't cause problems across ROMs.

Pwnycorn said:
Hey people.
I was thinking of buying a second hand Nexus 5X.
Found and offer with the 16GB version, tempered glass, Dbrand case and full accessories.
The seller says it is running Android 7.1.1 and WiFi doesn't work (it turns on, but doesn't find networks) due to driver problems.
Before committing to anything I'd like to know if this problem is actually real, and not just a hardware issue on that particular device, and if there is any workaround or fix yet.
I'm gonna put a custom ROM on it anyway, but I wanna be sure that this issue won't cause problems across ROMs.
Click to expand...
Click to collapse
I guess this is a hardware issue specific to that device. Do you know if this was tested on different routers, i.e. work WiFi vs. publicly accessible college WiFi vs. home WiFi? I haven't noticed widespread WiFi reports on our forum. On Nougat 7.0+, some people initially had issues with specific WiFi. On Marshmallow 6.0, it helped to enable "Legacy DHCP" in Developer Options however this has been removed in Nougat 7.0+.
FYI, make sure the seller removes their account while booted in Android prior to performing a factory reset. Android 6.0+ introduced Factory Reset Protection which requires signing into the previous account on the phone if a factory reset is performed while still signed into that account. Failure to do so means you will be locked out of the device upon arrival and people have already fallen victim to this. There is no help provided on XDA to circumvent this security feature built into Android 6.0 and newer.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
I guess this is a hardware issue specific to that device. Do you know if this was tested on different routers, i.e. work WiFi vs. publicly accessible college WiFi vs. home WiFi? I haven't noticed widespread WiFi reports on our forum. On Nougat 7.0+, some people initially had issues with specific WiFi. On Marshmallow 6.0, it helped to enable "Legacy DHCP" in Developer Options however this has been removed in Nougat 7.0+.
FYI, make sure the seller removes their account while booted in Android prior to performing a factory reset. Android 6.0+ introduced Factory Reset Protection which requires signing into the previous account on the phone if a factory reset is performed while still signed into that account. Failure to do so means you will be locked out of the device upon arrival and people have already fallen victim to this. There is no help provided on XDA to circumvent this security feature built into Android 6.0 and newer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
There isn't much info in his description of the device and I have not talked to him yet.
He mentioned looking through the Google support forums. So I assume that's how he figured it must be software problem.
But I'm starting have second thoughts on this. The reason being the various reports of 5Xs going into bootloops due to some hardware issue.
Thanks for the reply.

OP, why not (and, you should) ask the seller/previous owner to factory restore or clean flash a stock ROM, whether it's 6.x or 7.x - assuming s/he knew what to do/done it - assumed it's out of warranty too ??
If that's all in working order, WiFi should not be an issue - you can then root and/or unlock the bootloader, etc. and choose your own OEM or custom Rom.
Running PureNexus on Nougat 7.0 (security level to Nov. 2016) on mine and I don't have any WiFi issues whatsoever.
Good luck but it doesn't feel right - keep looking, no matter how attractive the price/bundle can be. Is this seller a local source, eBay and have you look at Swappa offering for competitive comparison ?

WiFi works on the 7.1 beta.

Fcks work
7.1.1 work for some days
It's not hardware is software
Sent from my Nexus 5X using XDA-Developers mobile app

FYI:
WiFi of my Nexus 5X does not work on stock 7.1.1 rom.
But it works on stock 6.0.1 rom.

I haven't noticed any Wi-Fi problems on 7.1.1. But bear in mind Wi-Fi is a very tricky technology, there's literally tens of external factors which make Wi-Fi association and signal quality vary. Also, Android switches the Wi-Fi antenna to various (power saving) modes depending on battery level etc.
Not to mention some really stupid "problems" like the seller is an inexperienced person who doesn't know how to setup a router or that he could be testing it in, say, Facebook app which just happened to be unresponsive.

Related

[Q] Nexus 7 owners...... problems, fixed or not?

Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.
I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.
Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app
GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.
Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app
sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!
Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.
New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2
Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.
Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4
To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"
My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4
Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.
I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app
madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.

Touch "gets stuck" on letters while typing

Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.

For thouse, who run stock 5.0.x-5.1.x, why to risk the device?

I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk
The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.
5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.
donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.
^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.
I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.
Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.

Question Random reboot

Been using my phone consistently for 24 hours. No root. Set it down after a messenger message, and couple seconds later, random rebooted. When it came back up, the gesture pill was flashing. Rebooted properly, and no more flashing. Weird. Anyone been having this?
There are several threads on the topic, and yes it seems to be quite the widespread issue. Some where able to fix this by doing a factory reset WITHOUT a backup from another device, some (like me) needed a replacement device.
We still do not know if its a software or hardware issue, or if these are two separate issues that are similar in symptoms but differ in cause (hardware failure/bug caused reboot & software/backup problem).
I'd suggest you either contact Google and get a replacement immediately or try a factory reset and manual setup (I assume you copied over your files from another phone?).
Wow, that is unsettling. Yes, I copied from an S21U backup. I've only seen this once so far, how extreme does it get? I searched before posting but did not see any discussions. I will look more. Thank you.
Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!
Have you tried a factory reset, then not restoring from backup (or if you did a cable backup/restore, try a cloud restore instead)?
I hate to suggest it because I restored my Note 10+ cloud backup with no issue, but enough other folks have suggested factory reset and not restoring a backup at all. Worth a shot. Good luck, whatever route you take.
pre4speed said:
Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!
Click to expand...
Click to collapse
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
Ugh, I am not liking hearing that. First pixel phone.
pre4speed said:
Ugh, I am not liking hearing that. First pixel phone.
Click to expand...
Click to collapse
That is some bad luck. Sorry to hear that. But the Packers won today so that's good
TrustAugustus said:
That is some bad luck. Sorry to hear that. But the Packers won today so that's good
Click to expand...
Click to collapse
Is what it is. I should know better than to adopt a new release anything lol. And GO PACK GO!
Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
I am on beta One UI 4 on my s21u currently, and the bugs on that are not the same bugs as the pixel, that's for sure. At least not the random reboots. But Samsung so heavily skins android, that is not a surprise. One of the main reasons I want to go pixel. Tired of Samsung putting their trash over vanilla Android

Firmware advice - SM-N975U - Note 10+

Hi All,
Been a while on here - please be gentle!
I have spent the last 6 hours looking into updating my firmware from Android 10!
I have done this on previous phones, but my current phone is proving a little more difficult. For the life of me, I cannot find the correct ROM to flash. Whenever I come to something I think I have found I seem to have another issue.
I've tried using various tools (Bitfrost) but got errors.
I'm in the UK, and as far as I can tell, my phone is “XAA”, “USA unbranded (default)”. I'm not bothered about changing the region code (unless it can be done easily).
Details::
SW ver.: SAOMC_SM-N975U_OYN_XAA_PP_0001
XAA/XAA/ATT
I would really appreciate some help from you guys who are way more informed and cleverer than me!
Thanks guys and gals!
Simon
EDIT: I have found a bit more informstion - I think I would be ok using SM-N975U1 - is this correct?
That's the umlocked Snapdragon variant...
I have two N10+'s; N975U/Pie, N975U1/Android 10. I would stay on Android 10 unless you want cpu cycle sucking scoped storage in all its glory.
Personally I prefer Pie to 10, better functionality and usability. With 11 you lose even more and 12 is fubar... in my opinion.
The best way to trash a stock N10+ is to mess with its firmware.
Rule #1 if a OS is fulfilling its mission, let it be!
Upgrades/updates can and do break things.
blackhawk said:
That's the umlocked Snapdragon variant...
I have two N10+'s; N975U/Pie, N975U1/Android 10. I would stay on Android 10 unless you want cpu cycle sucking scoped storage in all its glory.
Personally I prefer Pie to 10, better functionality and usability. With 11 you lose even more and 12 is fubar... in my opinion.
The best way to trash a stock N10+ is to mess with its firmware.
Rule #1 if a OS is fulfilling its mission, let it be!
Upgrades/updates can and do break things.
Click to expand...
Click to collapse
Thanks for that info ... I actually have no beef with A10 other than one issue which I thought maybe a firmware issue.
My NFC works (I can transfer files between phones) however, I cannot use Google Pay, or Samsung Pay. I have read somewhere that this was a firmware issue, hence my desire to update.
I have tried literally everything to get it working (cleared cache, re-booted). NFC Tools confirms it works, but it just does nothing at the checkout.
If I can fix this issue, I'll be happier!
Ratzz2 said:
Thanks for that info ... I actually have no beef with A10 other than one issue which I thought maybe a firmware issue.
My NFC works (I can transfer files between phones) however, I cannot use Google Pay, or Samsung Pay. I have read somewhere that this was a firmware issue, hence my desire to update.
I have tried literally everything to get it working (cleared cache, re-booted). NFC Tools confirms it works, but it just does nothing at the checkout.
If I can fix this issue, I'll be happier!
Click to expand...
Click to collapse
You're welcome. It may be doing that because big sister Google thinks you need to upgrade to be secure. May have to do with the region you're using it in. I don't know. I never use those features and don't want them on the phone. Don't want anything to back door in using that route.
Depends how hell bent you are on having those features. You could easily lose more than you gain by upgrading, worse it may not resolve the issue. The N10+ is a valuable and reliable work horse that will run for years... just as it is. If it's running well otherwise I would try to find the root cause of this issue or simply use other workarounds rather than the shotgun approach.
Yeah, I was wondering about being in the UK with a phone registered in the US. But NFC doesn't read my credit card either. Would have thought that would be an option.
I'm not necessarily a huge NFC user, but the other day I forgot my wallet at the petrol station after filling my car. If I'd have had my NFC working, I'd have been able to fire it up and avoid the embarrassment!
Anyway, thanks for your help!
Be glad you have the Snapdragon variant. They are very reliable and run well stock when optimized. If you do upgrade to 11 a rollback to 10 isn't possible if you upgrade the boot loader.
There's always at least a small risk when flashing firmware which can trash the device. The only time I would flash a N10+ is if the rom was corrupted which barring a hardware failure is a very rare SUE, single upset event.
I never tried mine to see if Pay works nor have I ever set a screen lock. The fingerprint scanner could be dead for all I know.
The flip side to that is never being locked out* of my own device, no data lose, and double tap on/off. The device is glued to me as physical security is the only real security. I realize this may seem extreme to some, but it works well in the real world.
*a SEU or partial hardware can lock you out of your device. Had no lock been set, no lockout would have occurred. Got locked out of a PC bios like that. The password -was- correct
That caused a mountain of trouble...
Thank you my friend. Wise words indeed and duly noted...

Categories

Resources