Database Info

[Q] Mango Data Problems

Didn't seem to have this problem when I first put Mango on but now it seems to be happening everyday. What's basically happening is my data connection just seems to disappear. 3G shows fine and SMS's come through, but I can't get on the internet, Twitter or Facebook at all.
The only way of fixing it is to pull the battery for a few seconds and then boot it back up. Flight mode doesn't fix it, nor does trying to change the carrier.
Anyone else had the same issue? Can see myself going back to NoDo unfortunately

Same issues here. Everytime the phone goes to 3G (or even G) it seems to loose data connection. Means no browsing, no bing maps, no syncing whatsoever...the same thing happened to me with NoDo, so I'm going to stay with Mango beta. Switching to flight mode and back usually fixes the conncetion though.

Reverted back to NoDo and data seems to be fine again (fingers crossed). It started to get worse, to the point where I'd only be able to get data for a few hours before needing to pull the battery.

DagsJT said:
Didn't seem to have this problem when I first put Mango on but now it seems to be happening everyday. What's basically happening is my data connection just seems to disappear. 3G shows fine and SMS's come through, but I can't get on the internet, Twitter or Facebook at all.
The only way of fixing it is to pull the battery for a few seconds and then boot it back up. Flight mode doesn't fix it, nor does trying to change the carrier.
Anyone else had the same issue? Can see myself going back to NoDo unfortunately
Click to expand...
Click to collapse
I had this on mine. Worked out that you have to select your phone provider's network explicitly in 'Settings' - Cellular' or 'Mobile Network' (if in Europe). If you use 'Automatic', it looses the data connection quite a lot...
Hope this helps!!!!

Just updated to Mango a week ago - Official via Zune.
Hadn't noticed it till today but I went on a long trip today and saw that after 20 mins or so my emails had stopped syncing. Only thing to get the connection back was a soft reset.
Seems after an hour or so it drops the data connection, and even though it is displaying a G/E/3G/H the connection isn't actually active.
This is a major issue... I can't be resetting my phone every hour!
I wonder if it is an issue with the roaming switch between Orange and T-Mobile because from what i've read it only really seems to be happening to people on Orange or T-mobile with the Omnia 7.
Another reason this is going to be my first and last Samsung device! Roll on Nokia.

Upgraded to official Mango and still getting the same problem, needing to pull the battery and boot it back up to get data running again.
Will try geddeeee's suggestion.

DagsJT said:
Upgraded to official Mango and still getting the same problem, needing to pull the battery and boot it back up to get data running again.
Will try geddeeee's suggestion.
Click to expand...
Click to collapse
I tried this but it didn't seem to help. I'd be curious to see if it fixed the problem for you though.
I now know of at least 4 people on Orange with the Omnia 7 now suffering this problem.

Nope, doesn't work. This is ridiculous and kinda makes the phone useless as a smartphone if it keeps losing its data connection every hour. Not very happy at all.

DagsJT said:
Nope, doesn't work. This is ridiculous and kinda makes the phone useless as a smartphone if it keeps losing its data connection every hour. Not very happy at all.
Click to expand...
Click to collapse
Likewise. It renders the phone more or less useless. May as well have a dumb phone.
I hard reset mine 2 days ago and haven't installed or changed anything on it yet to see if it happens. I haven't been to an area where i'd lose reception yet though so i'll see if it helps.
As an aside some other problems i was having with mango have been solved with a hard reset. Improved battery life, voice to text is putting punctuation in properly now (before it would put spaces like "don ' t"). My lock screen doesn't have lag displaying the time and calendar info any more. That's what i've noticed so far at least.
May be worth trying as it seems that the update didn't seem to install properly for me.

Freypal said:
Likewise. It renders the phone more or less useless. May as well have a dumb phone.
I hard reset mine 2 days ago and haven't installed or changed anything on it yet to see if it happens. I haven't been to an area where i'd lose reception yet though so i'll see if it helps.
As an aside some other problems i was having with mango have been solved with a hard reset. Improved battery life, voice to text is putting punctuation in properly now (before it would put spaces like "don ' t"). My lock screen doesn't have lag displaying the time and calendar info any more. That's what i've noticed so far at least.
May be worth trying as it seems that the update didn't seem to install properly for me.
Click to expand...
Click to collapse
I'll do a reset on mine now and see how it goes.
Edit: Still got the time lag when turning the phone on.

DagsJT said:
I'll do a reset on mine now and see how it goes.
Edit: Still got the time lag when turning the phone on.
Click to expand...
Click to collapse
After updating to mango mine was taking an age to boot up. sometimes as much as 2 minutes and it happened several times where it actually just froze completely with a black screen and just the battery indicator displaying.
I havent had a reason to reboot it yet so not sure if thats changed.
I was suffering the disappearing keyboard as well but so far touch wood. that hasn't happened yet either.

Well, tonight I went off for a run through the forest where i knew i would lose reception.
Sure enough when i got back to my car my data connection had died "email last update 39 minutes ago" or whatever.
Needed a soft-reset to get working again. So hard-resetting the phone hasn't solved this. I'm getting stupid battery level problems too, had this for a while now. When the phone is on it will show around 30% battery, after a soft reset it comes up with battery critically low.
Getting fed up with this now. If i return the phone I'm pretty sure that the same problem will be present as it's software related. All it means is my phone is more or less useless now.

Well I thought the hard reset had done the trick. Had emails coming through right up until I went to bed and turned on flight mode. Just trying to access data now and it's not working again.
Nokia's phone announcement and release can't come soon enough.

DagsJT said:
Well I thought the hard reset had done the trick. Had emails coming through right up until I went to bed and turned on flight mode. Just trying to access data now and it's not working again.
Nokia's phone announcement and release can't come soon enough.
Click to expand...
Click to collapse
I was genuinely gutted when i saw it wasn't working. It lasted two days and I thought it was fixed too. I don't know if it may have made it slightly better though...
I'm due an upgrade the start of next year. Like you say it can't come soon enough. I really love the OS, Mango is great but it seems Samsung have managed to ruin it again.
Nokia for me for sure.
I'm convinced this is an issue between the Software and the Orange network. Something either Samsung or Orange should have picked up during the testing phase so I can't see a replacement device being any better.

I can either sell it and get around £160 or so towards a new phone, or change supplier. I could go back to GiffGaff but O2 doesn't give 3G in my workplace and the other suppliers are too expensive for what I'm after.
The problem waiting for Nokia's phone is that I'm not going to have the money to buy a brand new Nokia outright and I don't want to get tied into a 18/24 month contract as I'm quite happy on my 30-day rolling contract.
Decisions...

DagsJT said:
I can either sell it and get around £160 or so towards a new phone, or change supplier. I could go back to GiffGaff but O2 doesn't give 3G in my workplace and the other suppliers are too expensive for what I'm after.
The problem waiting for Nokia's phone is that I'm not going to have the money to buy a brand new Nokia outright and I don't want to get tied into a 18/24 month contract as I'm quite happy on my 30-day rolling contract.
Decisions...
Click to expand...
Click to collapse
Tough call. There is always the possibility that a "Samsung Update" will be pushed out in the near future that could solve this. Between Nov 2010 and now i've had 5 updates to this phone so it's at a rate of around 1 every 2 months. And one of those was a firmware update only. It could be that it is simply a radio software issue and a new rev. could resolve it.
For my part i have insurance with Orange so they have already agreed to take the phone back and replace it. I know from past experience if i have the same fault with the phone 3 or 4 times they offer a different hand set in exchange. So conceivably if i keep sending them back i could get a Mozart or Radar i would guess.
The problem with that would be that i'd have to keep re-setting up new phones at a rate of around once a week and that's a whole world of hassle

Just out of interest, did your Omnia 7 have any Samsung apps prior to upgrading to Mango?
I've forced my Omnia 7 to upgrade to Mango via the Zune trick so I'm not sure I'll get any Samsung updates as I'm using a stock Microsoft rom as opposed to a Samsung version. Samsung haven't even released their version of Mango yet, have they?

DagsJT said:
Just out of interest, did your Omnia 7 have any Samsung apps prior to upgrading to Mango?
I've forced my Omnia 7 to upgrade to Mango via the Zune trick so I'm not sure I'll get any Samsung updates as I'm using a stock Microsoft rom as opposed to a Samsung version. Samsung haven't even released their version of Mango yet, have they?
Click to expand...
Click to collapse
Well mine wasn't forced - i updated when zune prompted me to. I did have some Samsung stuff installed prior. Now app is broken but that's affecting everyone.
When i hard reset none of them were pre-installed though.
Out of interest has your device been working better in any way since hard resetting like mine has?

Freypal said:
Well mine wasn't forced - i updated when zune prompted me to. I did have some Samsung stuff installed prior. Now app is broken but that's affecting everyone.
When i hard reset none of them were pre-installed though.
Out of interest has your device been working better in any way since hard resetting like mine has?
Click to expand...
Click to collapse
It kinda feels like it is actually running better, to be honest. Internet (when it works) seems to draw the pages quicker as well as loading quicker, it feels smoother between transitions of apps so I think the hard reset has helped to some degree.
I've also got a "Help+How-to" app on there which I didn't have before the hard reset.
It'd be nice to have constant data access though I'm not holding out much hope for any updates to the OS from Samsung or Orange to fix anything up either.

DagsJT said:
It kinda feels like it is actually running better, to be honest. Internet (when it works) seems to draw the pages quicker as well as loading quicker, it feels smoother between transitions of apps so I think the hard reset has helped to some degree.
I've also got a "Help+How-to" app on there which I didn't have before the hard reset.
It'd be nice to have constant data access though I'm not holding out much hope for any updates to the OS from Samsung or Orange to fix anything up either.
Click to expand...
Click to collapse
I'd noticed that Help and How to app as well.
Yeh I'm not really hopeful One question... are you signed up for Orange's Everything Everywhere thing? IE does your phone occasionaly switch to Orange-T-Mobile ?

Flash always lit?

Anyone else have their flash led always dimly lit? Even when the phone is off my camera flash is dimly lit.

This is most likely the heart rate monitor. There is currently an issue with Google Fit and the S6 which causes the heart rate monitor to stay on. The only solution st this point is to uninstall Google Fit until Google releases an update that fixes the app.
Sent from my SM-G900W8 using Tapatalk

msavic6 said:
This is most likely the heart rate monitor. There is currently an issue with Google Fit and the S6 which causes the heart rate monitor to stay on. The only solution st this point is to uninstall Google Fit until Google releases an update that fixes the app.
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
I'm not sure Google Fit is the only possible source for this problem.
I have the same problem as OP. I got my S6 (non-edge, 32GB) about 24 hours ago and last night noticed the faint yellow glow on the back of the unit. I haven't been impressed by the battery life (admittedly a very limited time with it so far) - but this could explain the less than stellar battery life so far.
I don't have Google Fit installed (in fact if I go to the play store, I get a message saying that it's not compatible with this version"). S-Health is disabled too.
One other thing, when I use the flashlight feature, I notice that the light isn't nearly as bright as on the S3 - not sure if this is relevant, it is the same LED.
I rebooted the system, and even turned it off, the faint light stays on. If the unit wasn't sealed I'd pull out the battery just to confirm this light can go out :-/

I have this issue on mine as well. I first noticed it when I went to charge my phone over night next to my bed. I lay the phone on its face so the LED notification doesn't show. I noticed a slight glow from the flash diode. I thought at first it only happened when I was charging my phone. Today, while at work, I powered down my phone and again noticed the light. For me, its always on. I just got off the phone with T-Mobile and they are going to over night me a replacement. I mention this thread to the T-Mobile support rep and she looked it up while I was on the phone with her. My friend's S6 does not have this issue, so not all of them are having this. I encourage everyone to go into a dark room and check your flash diode.

verboten said:
I have this issue on mine as well. I first noticed it when I went to charge my phone over night next to my bed. I lay the phone on its face so the LED notification doesn't show. I noticed a slight glow from the flash diode. I thought at first it only happened when I was charging my phone. Today, while at work, I powered down my phone and again noticed the light. For me, its always on. I just got off the phone with T-Mobile and they are going to over night me a replacement. I mention this thread to the T-Mobile support rep and she looked it up while I was on the phone with her. My friend's S6 does not have this issue, so not all of them are having this. I encourage everyone to go into a dark room and check your flash diode.
Click to expand...
Click to collapse
Just dropping into say I also have the issue . 32GB, Standard S6, T-Mobile. I will call them and get a new one overnighted as well.

Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now

demmo81 said:
Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now
Click to expand...
Click to collapse
I know I've done that on both of my s6s and still occurs.

demmo81 said:
Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now
Click to expand...
Click to collapse
No disrespect taken, man those are hard to get off (thanks for confirming this, it looked like there were).
However, that might explain the flashlight function being a bit dimmer than on the S3, but it wouldn't explain the constant light source itself.

How can we possibly check this in store where there is substantial amount of light anywhere. I'd definitely check my S6 in store for this.

Mine doesn't have this dim light at all I checked and I closed all the lights to make sure nothing is coming out . I don't know I wish I can help

KristianKenneth said:
How can we possibly check this in store where there is substantial amount of light anywhere. I'd definitely check my S6 in store for this.
Click to expand...
Click to collapse
I think it would be difficult to see unless you ask them to let you into a dark storage room without windows That's how I can verify mine is still doing that during the day, though at night when I wake up with the phone next to me, the glow is comparatively quite substantial.
Plus, you'll have to wait about a week before you can see them in the store.

I have two S6's and can confirm both of mine has this dim lit light only noticeable in the very dark.
The problem with us getting the device early is we don't know if this is hardware or software problem., that might get noticed and fixed with an update. Many say after the actual launch Samsung/Tmobile pushes an update. We can assume they at least will to fix the cell standby draining battery with VOLTE issue. Plus how many will we have to get shipped to us before we get one that doesn't do this, very different than being able to have the associate check it in the back office with lights off.
Can anyone that did get a replacement comment on this.

tenxo said:
I have two S6's and can confirm both of mine has this dim lit light only noticeable in the very dark.
The problem with us getting the device early is we don't know if this is hardware or software problem., that might get noticed and fixed with an update. Many say after the actual launch Samsung/Tmobile pushes an update. We can assume they at least will to fix the cell standby draining battery with VOLTE issue. Plus how many will we have to get shipped to us before we get one that doesn't do this, very different than being able to have the associate check it in the back office with lights off.
Can anyone that did get a replacement comment on this.
Click to expand...
Click to collapse
Mine is doing it too. If it is indeed the case that not all GS6s are doing this, that does make me concerned that somehow my unit is defective. I'm wondering if I should just hold onto it hoping that Samsung will fix it with a software update or if I should try yo exchange it.

poweroutlet said:
Mine is doing it too. If it is indeed the case that not all GS6s are doing this, that does make me concerned that somehow my unit is defective. I'm wondering if I should just hold onto it hoping that Samsung will fix it with a software update or if I should try yo exchange it.
Click to expand...
Click to collapse
I spoke with a tmobile rep. He said online orders get 20 days return exchange from the day of delivery not purchase. He also said there should be an update on a day or two after the official April 10th launch. I told him to document my account that I called about this issue. He said I could get another (two) overnight to me, but there's no way to guarantee if the new ones won't have this.
How come more people are not jumping in here to say theirs is doing it too. If its just us few maybe we do have a problem. But giving it's only noticeable in the dark maybe they haven't seen it on theirs?
Sent from my SM-G900T using AllianceR(●)m

tenxo said:
I spoke with a tmobile rep. He said online orders get 20 days return exchange from the day of delivery not purchase. He also said there should be an update on a day or two after the official April 10th launch. I told him to document my account that I called about this issue. He said I could get another (two) overnight to me, but there's no way to guarantee if the new ones won't have this.
How come more people are not jumping in here to say theirs is doing it too. If its just us few maybe we do have a problem. But giving it's only noticeable in the dark maybe they haven't seen it on theirs?
Sent from my SM-G900T using AllianceR(●)m
Click to expand...
Click to collapse
I think you are right, unless you have the phone next to you at night you probably won't notice it., still odd, I would have expected others to notice it too. And, even as dim it is, it can't help with battery life. I hope it's a software issue and can be easily patched that way.

Edit: just noticed tonight that my phone does in fact have the LED issue. It's odd because I spent some time yesterday in the dark looking for the problem and it was no where to be found. Been laying in bed messing with my phone while it's charging, decided to flip it over and low and behold, dimly lit flash on :/.
-Matt

Roflwafflez said:
Mine does not seem to be having this issue. I checked it out last night in a completely dark room and couldn't see anything. To see if I could get an idea of what it looked like though, I turned on the torch for about 20 seconds, then turned it off and looked again and it did replicate the faint glow that it seems most people are speaking of, however it faded away in about 30 seconds.
-Matt
Click to expand...
Click to collapse
This is making me think some S6s just have this defect where the LED never turns off and some don't. I think it might be best just to return my S6 and repurchase the phone after its official release date. I think these earlier phones might be more prone to defects. My gut feeling is that this is something that won't be fixed via software. I don't think exchanging the phone for a new one will help too much given that so many other S6s also have the issue, you have a good chance that the new phone you get will also be defective.

poweroutlet said:
This is making me think some S6s just have this defect where the LED never turns off and some don't..
Click to expand...
Click to collapse
My guess is it's a hardware issue (perhaps they used a different supplier/component for this part) since all of the phones are presumably running the same software (some with the OTA update that was waiting from T-Mobile - like myself, others perhaps without it). If it can be patched with software is another issue.
Actually, perhaps it would be useful to know if those experiencing the problem have applied the OTA update and those without haven't. My hunch is it won't be a factor, but curious, so people reporting should state their situation.
For my non-edge S6 (black 32 GB) I have the OTA and my flash stays on dimly all the time.

I noticed this last night and I thought it could have just been some sort of burn in from using the flashlight. (64gb regular tmo S6)
It's basically impossible to tell with any sort light around whether or not this is happening, even just with residual light, but mine does seem to be dimly lit in a pitch black room.
Could it have something to do with the selfie feature on the camera? Using the heart rate monitor as a picture button, that is.

I have a 64 GB T mobile regular GS6 with the OTA and I do have the issue.

Nexus 5 and various issues, anything that can be done?

Alright,
Phone: Nexus 5 2013
Android: 5.1.1
Country: Canada
So I've started to get a lot of issues on my Nexus 5 that I ordered back in November 2013 (when it was released) and they are too big to be left alone. If I cannot fix them, I'll have to buy a new cellphone and there's none that interest me right now, nor that I want to change my current Nexus 5.
Issues:
My Nexus 5 doesn't connect to my cellular network anymore. I'll stay on "No service" and refuse to connect to any Operator Network stating that the network is unavailable at the moment, even thought it is. Sometimes, it'll connect to the network for 15 to 30 minutes, before losing it for the next 8 hours.
It becomes hot really, really quick randomly. The upper back part of it becomes hot, and according to the Nexus 5 architecture, the battery isn't even located there so I don't know what could make it heat up like that. This happens even without it being charged, and without me using it a lot (games, apps, etc.)
The phone will randomly restart for no reason, and sometimes stay stuck on a "boot loop" (Starting apps X of Y... before restarting).
The vibrate mode is messed up. It'll vibrate every 30 seconds for a notification (email, Facebook, SMS, etc.) despite the fact that there's nothing, absolutely nothing. Right now I disabled the vibration/sound mode to avoid that issue.
The battery gets drained really, really fast. Like overnight, while not being used it'll fall from 100% to 5%. It never used to do that. When I don't use it overnight, it would lose maybe 20%, even less than that. It started recently as well.
All these issues were present in past versions of Android, starting at 4.4 so I doubt the version is in cause here, but it's still a possibility I guess.
I got my SIM card changed for a brand a new one, troubleshooted the phone with everything I could find online before giving up and restoring it to it's default settings, but the issues are still present. I don't know what I should check anymore. If you have any comments, experiences or solutions I could try to solve my issues, please let me know since at this point I'll most likely try all of them. Also, if you need more information on my phone, system, etc. let me know as well.
Thank you.

Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk

There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.

firemaned said:
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It used to be rooted, but it's not anymore. Any way I can make sure that it's rooted or not? When I used the SuperSU app back then I realized at some point that it wasn't rooted anymore (it was telling me that this app can only be used on rooted devices). I think the bootloader is unlocked because when I open my device, it shows me the little lock icon, but it's open (unlocked). Also, it's freshly reset to factory default (from yesterday).

dahawthorne said:
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
Click to expand...
Click to collapse
I already did a Factory Reset on my phone yesterday, so I guess I don't have to do another one? Right now, if I follow what you just told me, I should wait until the release of Android 6.0 (M) and upgrade to it then see if it solves my issues. I just hope that it won't take a long time to be pushed to my phone like it was with Android 5.0. Or your other solution is to flash the latest preview for Android 6.0 (M) on my phone and see how it goes, right?

If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.

dahawthorne said:
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
Click to expand...
Click to collapse
That was my original plan. I called the Play Store support this week and they told me that my phone was elligible for a replacement till April of 2016. I found that weird because it would make it a 2 years and a half guarantee but at least I had my backup plan in mind. Then I called today to order a replacement and the guy told me that my guarantee expired back in November 2014 (1 year after I bought my Nexus 5, which made sense) so now I'm stuck with this one. I don't know why, but since this morning (after creating this thread), the cellular network cameback. It still drops sometimes but only for a few seconds and if not, I enable/disable the Plane mode to make it connect again. However, the battery drain, phone heat, random restart and messed up vibration issues are still present. I can deal with them however until Android 6.0 (M) gets released. The most important thing was the cellular network. We'll see tomorrow how it goes. Still awaiting tips and tricks for my other issues if anyone have some.
For the battery draining issue, I think I have the paid version of Greenify somewhere and was thinking of using it to see if it helps, even though I didn't have that issue at the beginning.

Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app

CalculatedRisk said:
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
And I imagine that the factory image is still present on the device? This is what I find weird, because when I "reset" my factory to defaults, it restores it to Android 5.1.1 even though the device came with 4.x. I come from the computer field, and a Factory Reset on a computer uses the manufacturer's image present on the CD, DVD, USB or partition given with the computer to reinstall the original OS that was present on it and the OEM software as well. If the computer was eventually upgraded to Windows 8.1 and came with Windows 7, Windows 7 will be restored, not Windows 8.1. So I can understand now that a "Factory Reset" doesn't really return the device to its factory state, right?

I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.

dahawthorne said:
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
Click to expand...
Click to collapse
I did have an OTA update to 5.1.1, yes.
And I talked to one of my friend who's really into phones (used to work for Bell and he's usually the person I go to whenever I have issues with my cellphone), and he suggested me to wait until Android 6.0 comes out, and then to fastboot it on my Nexus 5 since OTA updates can be buggy sometimes. I could actually fastboot the phone right now (well tonight) with Android 5.1.1, but if Android 6.0 is to come out next week (or the one after), it might worth the wait, depending on whether or not I can keep the cellular network working. Otherwise I would have to go through 2 flashboots in 2 weeks and I can't really be bothered to do that
And I don't know where the CPU is in the Nexus 5 (I could look it up) but the zone where the heat is isn't where the battery is so there's that. However, my friend told me that the fact that my cellular network isn't working could explain why the battery is being drained so fast, but can't explain the vibrate mode and random restarts issues.

I was having battery issues on Stock ROM, but now I am using CM12.1 so battery is not draining very fast.
When I am inside my home or in some other house or building, the network disconnects very often. However, if I am outside, the network works pretty well.
The notification LED, when being configured using CM12.1 settings, shows blue color on green color selection and green color on blue color selection.

I had some of the same problems with my phone, it would reboot randomly throughout the day. With mine if I charged it overnight with it off when I turned it on in the morning it would only be at 85%. I ended up contacting LG and I paid $170 to get it fixed, they have replaced the mainboard twice so far. After the second time it had no issues, and that lasted a couple months but I have sent it back again to be fixed. If you bought the phone on a credit card they usually extend the warranty by a year, that's what I did, filed a claim and they sent a cheque for the repair cost, very simple actually. But I suspect it might be the same problem as mine, some hardware issue, especially if you've reset the phone.

Just for info, the CPU is indeed at the top rear of the phone, so this is undoubtedly where the heat is coming from.
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016 - see step 11 saying "The Quad-core, 2.26 GHz Snapdragon 800 SoC is layered beneath the RAM".
I reckon it's a rogue app, which I hope isn't a system app, running wild - a system app will be hard to cure.
A ROM refresh is probably a good place to start, and if you can wait for Android 6.0 then why settle for less...

Wiped my os on nexus 5 trying to install nethunter only comes on in twrp. very new to this be easy on me ive previously installed a vm lab with kali linux.
I have downloaded adb and fastboot
Using winace . Before this my pc would not recognize my device, "no drivers". But now it shows up on the pc control panel as active and found
However snap pea still cant find drivers although now it says are you fornatting your phone with only one option "yes" then it just dissappear. ... but before I downloaded adb, fast boot ... snap pea was simply saying no drivers found.... Please help. ..thank you.
Sent from my GT-I8190 using XDA Free mobile app

Here's an update on my situation: the cellular network is back at both my house and my workplace. The way it works, it seems that it takes it a day to "adapt" itself to the location and then gives me network. So at first after the Factory Reset, I didn't have network at my house, the day after I did. Now, when I went to work on Monday I didn't have network, but when I did on Tuesday, I did. My job is an hour of road away too, and at some places on the road I don't get any network, but it happens less and less as I travel back and forth.
The random restart and overheating issue are still present however. I didn't test the notifications (on vibrate) but I will soon. As long as I have my cellular network, I don't care about the other issues, until Android 6.0 (M) gets released and I fastboot it on my phone.
Now, since I bought my Nexus 5 using a MasterCard, I remembered that they have a promotion which double the guarantee on electronics (up to a 1 year), which means that I have a 2 years guarantee on my phone. So I called LG, and they have a promotion right now, $150 to get my phone repaired by their tech center IF it can be repaired. If they can't, they send it back and gives me a 50% refund (around that number).
My current plan of action is to wait for Android 6.0 (M) to get released, flashboot it on my phone and see how it goes from there.
Thank you for all the replies so far, they really helped me and still help me today

Good luck man. Keep us updated.
Sent from my Nexus 4 using XDA Free mobile app

Alright so, I fastbooted Android 6.0 on my Nexus 5, and it seems to have done the trick. I have network everywhere now, even on the road. I still lose it from times to times (a few seconds only), but this is a "normal" behavior considering the carrier I have. The notification issue is also gone, and so does the restart issue since I didn't have it once so far. But I only fastbooted it yesterday evening so it might be too soon to say that.
Now, I still have the "overheating" issue, but it could be from me playing Fallout Shelter, I really don't know. I used to play Clash of Clans alot, and graphically speaking, I think it's more demanding than FS, but I never had that overheating effect before. One thing I noticed however is that after fastbooting Android 6.0, my battery drops real fast, even when idle. I thought that Android 6.0 was supposed to improve the battery life. I'll try to see what process, app or activity is taking the most juice out of it, but I'm sure this isn't normal.

Alright so it took me an hour to go from my house to my workplace, and my battery went from 34% to 12%, while being on standby. This isn't normal I guess. I'll need to charge it to 100% once, and then use the Battery setting to see what's taking all the juice.

Might have spoke too soon. When going to work today, I went in a room where there's usually no signal (or the signal is very weak), and lost the network. It's normal in that room so I didn't pay much attention to it, but now I'm not able to get back on the network. Even searching for the Network Operator fails. Sigh, it really looks like I'll have to send it to LG for repair. I guess I need to fastboot it first to erase all my data, because they need to use my phone to test the repairs they make?

What's the best rooted user experience for a G930V?

Hi everyone,
I have a Verizon S7 flat (G930V). I bought it sometime mid-2016 and it's rooted with the eng kernel on 6.0.1. The baseband is G930VVRU4API3. The bootloader is locked and obviously that's very limiting.
I really enjoy the added functionality that comes rooting, but sometimes the phone hangs randomly and becomes unresponsive seemingly for no reason. I was wondering if there's a better experience to be had by updating to 7.0+, preferably with root.
What are my options now in Q4 of 2017? What's the deal with the "U" firmware? Is there a non-eng way of rooting or any one that doesn't bog down the phone so much, or is non-rooted the only way to go? Can I go from where I am now to where I want to be without wiping my phone, or is that needed/recommended?
Sorry for all the questions. For my past Android devices this info was pretty cut and dry, but it's hard figuring out what's the latest or more well received methods for this device. I love the phone, but going forward I don't think I'll choose Samsung if I want any sort of freedom (basically stuck with Verizon US, though).
Thank you for any direction you might be able to provide me.

I tried rooting with eng.boot kernel on my 930U but didn't like it - too much lag, very noticeable. And battery life was also worse, so I returned to stock.
I guess Verizon debloated hybrid ROM (or something like that can't remember exactly) would be good variant for you to go if you decide upgrading to nougat. I personally tried it hoping I would get 6 hrs SOT but got only very small positive difference in terms of battery life - "android system" is always on top positions in battery stats.

Looking for an OREO replacement

My Galaxy S7 (AT&T SM-G930A) was recently updated to Android 8 (Oreo). Since the update I am having issues with the volume. I plug my phone into a stereo receiver at work and we listen all day 12 - 14 hours. Nougat would often reset my volume after about 10 hrs of playing and display a warning about the dangers of listening to high volumes for extended periods. Since updating to Oreo the volume will reset randomly. It will not display a warning or reason it just resets. At first I thought it was because I was receiving a call or text or email but the random volume resets do not correspond to any notifications. This happens three or four times a day since the update.
The volume issues are just a minor issue compared to my battery life. I have a 33% reduction to battery life. Prior to the update I would plug in (to the stereo) my phone in the morning and after a 12 hr shift I would have about 20-25% left. Since the update I plug in (to the stereo) and after about 10 hrs I'm at 10-15%. I have not installed any new apps since the Oreo update and there are no other causes for the change in battery life.
The other main issue I have is speed. The phone is noticeably slower. Apps take longer to open and there is definite lag. Earlier today it took me a little over three minutes to pull up my navigation app and get directions. Prior to the update it would take around 30 seconds.
Here are my questions.
1) CAN I INSTALL A CUSTOM ROM? I had Cyanogenmod on my S4 and really liked it over the stock ROM. I think I would like to give Lineage a try but I still can't get a definite answer as to whether or not this can be done. Obviously I have the Snapdragon processor. Most of the information I'm finding is telling me that we can't install a custom recovery on Snapdragons yet, which means, no custom ROM. If I am wrong please provide me some current links.
2) If I can't install a custom recovery/ROM; CAN I REVERT TO NOUGAT OR MARSHMALLOW?
3) If I can't revert; WHAT CAN I DO THAT WILL PROVIDE ME WITH MORE IMMEDIATE SATISFACTION THAN WAITING FOR AT&T OR SAMSUNG TO FIX THIS CRAP?

1) No, US model S7's have locked bootloaders preventing custom firmware/recovery. You'll need an international G930F/FD to do anything custom.
2) No, the bootloader being locked prevents OS downgrades. You can only sidestep or upgrade.
3) Unfortunately your hands are pretty tied. All I can suggest is backup anything important and do a full clean flash, which may resolve some of the anomalies.

Beanvee7 said:
1) No, US model S7's have locked bootloaders preventing custom firmware/recovery. You'll need an international G930F/FD to do anything custom.
2) No, the bootloader being locked prevents OS downgrades. You can only sidestep or upgrade.
3) Unfortunately your hands are pretty tied. All I can suggest is backup anything important and do a full clean flash, which may resolve some of the anomalies.
Click to expand...
Click to collapse
Beanvee,
Thanks for the quick and concise reply. I just wanted to offer a belated but brief follow up. I backed up and restored Android. It took a little while to get everything back where I wanted it but most things seem better now. The only complaint I have at this time is that my streaming music app(s) seem to drop the connections too often when running on WiFi. If I turn off the WiFi and use mobile data there aren't any issues. The WiFi issues happen at home, at work and when connected at my mother's home and friend's homes. I rarely have mobile data over-runs so it isn't an issue per se; it just bugs me a little.
Once again, thanks for the help.

I'm afraid that's something I've not experienced and wouldn't know where to look. Best I can think of is check battery saving options, and under WiFi > advanced, make sure Keep WiFi on during sleep is set to Always