[Q] Nexus 4 Notification Delay - Nexus 4 Q&A, Help & Troubleshooting

This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.

ibrahim52 said:
This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.
Click to expand...
Click to collapse
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it

playya said:
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it
Click to expand...
Click to collapse
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.

Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app

QuackDuck said:
Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
any APP has the same issue. I use the following and in everything it is the same frustrating issue.
whatsapp
Talk.to
Email (Even if the settings are on 1 hour INBOX CHECK, it never works until i manually do the sync)
These are the only apps I always expect to notify me INSTANTLY. Also it was the same in Google talk and any other IM apps.

ibrahim52 said:
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.
Click to expand...
Click to collapse
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first

playya said:
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first
Click to expand...
Click to collapse
Thanks but it also happens in 2G because 3G I can't use due to my work environment where I can't keep charging my phone and in 3G this phone battery drains quickly. Well, two more weeks ill wait for 4.3 and if Google is still fooling then I will go ahead with ROOT and some KERNEL experiments. Thanks a load.

Related

[Q] Wifi Issue with LG-D802. Advice is very appreciated

[Q] Wifi Issue with LG-D802
Hi all
Few days ago i receive my G2 and quickly updated to android Kitkat (Never experiencing Jellybean on this phone before),
I started to have some issues with the wifi. The wifi appears to be connected but sometimes there is no data transfer and wifi automatically disconnect even in the strongest signal area (the router is just below my desk of my phone) and the wifi settings was still turned on.
This occurs with every router from normal to the strongest connection.
Besides the connection drops also occurs on this phone which there is no internet connection even when the wifi is connected
So is this the wireless hardware issue or anyone experienced this before? Would like some suggestion please, Thanks!
So... just to make sure, you are running the default/stock ROM with OTA update to Android KitKat right? I am currently running CM11 nightly, and sometimes it has issues with connectivity (wifi/LTE). Let me know.
ainstushar said:
So... just to make sure, you are running the default/stock ROM with OTA update to Android KitKat right? I am currently running CM11 nightly, and sometimes it has issues with connectivity (wifi/LTE). Let me know.
Click to expand...
Click to collapse
Yes it is running stock LG rom at 4.4.2
Here is what i would try:
1. Try resetting the phone to see if the errors go away. Maybe something went wrong while upgrading
2. If the problem still persists, and you are expert at ROMing - try installing a different ROM to see if this is related to LG's ROM.
3. Get a replacement if under warranty.
Just to let you know, KitKat does have some wifi issues. Some people are reporting issues with 4.4.2 and not with 4.2.2.
Hope that helps.
ainstushar said:
Here is what i would try:
1. Try resetting the phone to see if the errors go away. Maybe something went wrong while upgrading
2. If the problem still persists, and you are expert at ROMing - try installing a different ROM to see if this is related to LG's ROM.
3. Get a replacement if under warranty.
Just to let you know, KitKat does have some wifi issues. Some people are reporting issues with 4.4.2 and not with 4.2.2.
Hope that helps.
Click to expand...
Click to collapse
I have reset the phone after i face the problem after the first day of use. However it does still appear but not in a very frequent like minute or hour basis. The connection drop and wifi disconnects occurs randomly during normal browsing/playstore/ social apps activities. I guess it was very hard to get for replacement under warranty if the problem was not really significant (occurs 2-4 times per day) although it is still under warranty coverage.
Thanks for your advice, i am currently looking towards in accessing device debug log to try to proof them there is something wrong with the wifi on the phone.
For me the same problem happened and i found out the solution by lowering the band of rounter to 54mbps only
Sent from my LG-D802 using XDA Free mobile app

Cannot update PRL or Profile Error codes

So for a while now I have not been able to update my PRL or Profile. It hasn't bothered me because for the most part the phone has worked fine until recently. A friend texted me and said he was going to call me. He text back a few minutes later and ask why I didnt answer. Phone was next to me the whole time and it didnt ring or so any kind of notification that he had tried to call. Took him 3 calls before my phone rang and he got through.
I have applied for a few jobs within the past few weeks and have heard nothing from anyone which I am surprised because I was referred to one company by and friend who put in a good word for me and said that his supervisors were really impressed with my resume. So now I feel like this issue could possibly be costing me job opportunities and I want to get it figured out.
The errors are 6602 and 407. I've tried to do it over 4G and put my phone just in CDMA mode for 3G only and get the 407 code for 3G and the 6602 over 4G.
I am running Stock rooted/odexed MK2 and I just did a clean flash of the rom again clearing data/cache and dalvik seeing if that would help which it didn't. I have reflashed the modem seperately also with no help.
I have seen many threads of others having this issue but no answers on a fix. Has anyone experienced this and actually done something that has resolved the issue?
If you feel it may be costing you a job, why not flash a nand of a stock rom, assuming you have one
Sent from my SPH-L720 using XDA Free mobile app
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
tenaciousj said:
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
Click to expand...
Click to collapse
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
rsngfrce said:
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
Click to expand...
Click to collapse
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
tenaciousj said:
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
Click to expand...
Click to collapse
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
rsngfrce said:
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
Click to expand...
Click to collapse
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
rsngfrce said:
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
Click to expand...
Click to collapse
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
rsngfrce said:
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
Click to expand...
Click to collapse
Bootloader and software version both show up as NG2 on Device Info.
tenaciousj said:
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Click to expand...
Click to collapse
I'm not an EXPERT on this subject, but if you are on NG2 stock unrooted right now, I believe you can use: CF-Auto-Root to root it. Or, here is a stock rooted version of the NG2 ROM:
[ROM][NG2] Stock Rooted NG2 (which mentions that it has Knox removed).
As far as tripping stuff, I'm somewhat unsure about that to be honest. I have always used Triangle Away on my phone, but it has a warning now not to use it with a custom kernel (which I use). My counter is at 3, but I am out of warranty anyway.
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
rsngfrce said:
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
Click to expand...
Click to collapse
I got the phone I have now about a month after the GS4 came out so its non sparks. I stayed on MK2 for so long because I couldn't find a newer rom that looked to be stable and not have to jump through a bunch of hoops to install it. The Odin screen shows everything being zero and offical software so I should be good. I am going to sign out of all of my accounts before I bring it in being I have a lot of apps bought through the store that only work on rooted phones. I hope I can get a tri band to replace it. My friend has a triband GS4 and it gets much better data speeds than mine.
Yeah, I mentioned elsewhere here before that I actually didn't know of the existence of the "Sparks" version of the G4. I screwed up the USB port on my G4 before upgrade time, so I had to buy another G4 on Amazon. Upgrade time has come up, so I was just looking and saw my phone listed as "Non-Sprint Sparks", which I thought meant that they called it the "Sparks" model because I hadn't bought it from Sprint... took me a while to figure out what that actually meant... :laugh:
Sprint online nor the store could fix it so I got a new one.
No rooting but error 407
As titled, I've not rooted the phone. I'm getting error code 407 on attempts to update PRL and Update profile. Download updates manually does nothing. Note I'm on a Samsung Note 4, Sprint. Had updated to Marshmallow 6.0.1 late March but then above actions persist since then. I'm using Wi-Fi only, Sprint service disconnected as I couldn't pay bill when I lost job during a disabling illness.
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
00Lee said:
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
Click to expand...
Click to collapse
Have you done a factory reset via recovery? Or you might want to flash latest full stock

Android 5.0.1 Changes

While there are several threads announcing the release of Android 5.0.1, in regard to the Nexus 6, most of them seem to be filled with posts relating to the availability, instructions for sideloading, etc.
This thread is to discuss the CHANGES that you have noticed between 5.0 and 5.0.1, and as this is the Nexus 6 section, it should really relate to changes on that device only. You may list changes you've personally noticed, or published changes, but please indicate the source. I, like many of you, no doubt, am very curious to see what is new, fixed, broken, etc.
http://aosp.changelog.to/aosp-LRX21V-LRX22C.html
On 5.0 I kept having the cloud print service or whatever keep crashing, on 5.0.1 I had the Amazon kindle app keep showing a notification Amazon kindle stopped for about 12 hours and had to reboot my phone. (Kept throwing the notification up about every 20 minutes on 5.0.1)
My phone has also been unable to chromecast netflix for the last week and I have to use my gf's nexus 6 to chromecast netflix. Weird little problems with applications on both operating systems.
Edit: Finally re-installed netflix and it fixed chromecasting.
It would be nice to see a list of changes (In language a typical person speaks rather than the jumbled mess that those AOSP changes look like)
I agree. Those AOSP changes are not that easy to understand. Also, they are just to the Android Operating System but doesn't the OTA also contain a new Modem and possibly other driver updates that would fix other issues with our phones? Those fixes and changes would not be in the AOSP list.
On a second note, why does Google do this? They obviously know whats changed. How hard is it to publish a simple list?
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
agentfazexx said:
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
Click to expand...
Click to collapse
It doesn't.
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
I think I saw there is a new radio... Would be interested to know if signal reception is any better
Sent from my Nexus 6 using XDA Free mobile app
banzaiwolfe said:
It doesn't.
Click to expand...
Click to collapse
What does?
Sent from my Nexus 6 using XDA Free mobile app
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
fdan100 said:
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
Click to expand...
Click to collapse
sweet, thanks for letting me know that this works now.
digging in a little deeper
https://android.googlesource.com/platform/external/wpa_supplicant_8/+/1d13911
Work around AP misbehavior on EAPOL-Key descriptor version
It looks like some APs are incorrectly selecting descriptor version 3
(AES-128-CMAC) for EAPOL-Key frames when version 2 (HMAC-SHA1) was
expected to be used. This is likely triggered by an attempt to negotiate
PMF with SHA1-based AKM.
Since AES-128-CMAC is considered stronger than HMAC-SHA1, allow the
incorrect, but stronger, option to be used in these cases to avoid
interoperability issues with deployed APs.
This issue shows up with "WPA: CCMP is used, but EAPOL-Key descriptor
version (3) is not 2" in debug log. With the new workaround, this issue
is ignored and "WPA: Interoperability workaround: allow incorrect
(should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor
version to be used" is written to the log.
Bug: 18411110
Change-Id: I9ae12e8882adc9e785f6e4cef9f30b89bf72dcd2
Signed-off-by: Jouni Malinen <[email protected]>
Click to expand...
Click to collapse
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
The issue with the face unlock camera is fixed.
5.0 is had huge problems in dim rooms buy now no issues
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1
Click to expand...
Click to collapse
I was kinda seeing this too.
N6
land2634 said:
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
Click to expand...
Click to collapse
FWIW I'm on AT&T and have not had this happen to me even once.
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
Click to expand...
Click to collapse
Now that's more like it!
Not sure if it was 501 or the gplay music update, but my music sounds much more clear now. No more cloud print crashes.. Hoping my signal issue was fixed (sprint) but as im deployed right now i only use wifi.
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
cavalier11 said:
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
Click to expand...
Click to collapse
i am not having that issue with my exchange account and gmail app

Exclamation mark on Wifi/Signal icon

I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
tluley51 said:
I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
Click to expand...
Click to collapse
That's means your router has no Internet not the phone. It's your WiFi router losing its Internet connection. Without seeing your setup I can only speculate as to the exact issue.
Gizmoe said:
That's means your router has no Internet not the phone. It's your WiFi router losing its Internet connection. Without seeing your setup I can only speculate as to the exact issue.
Click to expand...
Click to collapse
There are 2 problems with that. All my computers and other phones in the house do not have this problem, so it definitely is not the router. Also, I am not always connected to my home router. I will be on my commute to work (no wifi) and it will happen. Hell, it will happen AT work and we have an enterprise network with update to date Cisco switches and APs.
tluley51 said:
There are 2 problems with that. All my computers and other phones in the house do not have this problem, so it definitely is not the router. Also, I am not always connected to my home router. I will be on my commute to work (no wifi) and it will happen. Hell, it will happen AT work and we have an enterprise network with update to date Cisco switches and APs.
Click to expand...
Click to collapse
Rma then. It's not normal.
Gizmoe said:
Rma then. It's not normal.
Click to expand...
Click to collapse
Funny thing is, I am back to unrooted stock and it instantly goes away. I was having the issue last night and into this morning on my home Wifi, on my way to work, then at work on LTE and when on the Wifi. I reverted the phone back to stock and now all is well. Why would a custom rom have something to do with not connecting to Google Services??
tluley51 said:
Funny thing is, I am back to unrooted stock and it instantly goes away. I was having the issue last night and into this morning on my home Wifi, on my way to work, then at work on LTE and when on the Wifi. I reverted the phone back to stock and now all is well. Why would a custom rom have something to do with not connecting to Google Services??
Click to expand...
Click to collapse
There could be many reasons. Custom Roms are modified and usually have custom kernels. Lots of stuff can go wrong. It's the risk of flashing custom Roms. I find with the 6p, stock rooted is the best. There isn't anything you can't do between xposed and root access. Each time I try a rom I have radio issues to be honest. I just stay stock.
That's a good call. Really the only thing I want root for is theming and double tap to wake, both can be achieved without custom rom (I believe)
Although I use Android Pay and even with systemless root, I am unable to get it to work....So maybe I should stay stock for awhile, but that is for another thread.
Appreciate your help, Gizmoe!
tluley51 said:
That's a good call. Really the only thing I want root for is theming and double tap to wake, both can be achieved without custom rom (I believe)
Although I use Android Pay and even with systemless root, I am unable to get it to work....So maybe I should stay stock for awhile, but that is for another thread.
Appreciate your help, Gizmoe!
Click to expand...
Click to collapse
I think Google has updated the safetynet API that prevents Android Pay working with Systemless root. I had it working until the latest update of Android Pay.
tluley51 said:
I cannot seem to fix it. I have searched threads here and on other forums, poked around the Google forums and I have tried everything mentioned and I cannot get it to go away. It comes and goes at random too. I have yet to flash an older radio, if anyone could provide me with one then I could give that a shot, but I cannot believe that I am in the minority here.
Oh and I have completely factory reset my phone and it does not help. Rooted running PureNexus.
Click to expand...
Click to collapse
I see you are running Pure Nexus, seems you are not the first to have an issue with wifi. Beans has suggested a potential fix.
SlimSnoopOS said:
I see you are running Pure Nexus, seems you are not the first to have an issue with wifi. Beans has suggested a potential fix.
Click to expand...
Click to collapse
Unfortunately, I had tried that. I am not even sure it is Wifi related though as I was getting the ! on my cell signal as well when I wasn't even on wifi.
tluley51 said:
Unfortunately, I had tried that. I am not even sure it is Wifi related though as I was getting the ! on my cell signal as well when I wasn't even on wifi.
Click to expand...
Click to collapse
Hmm, that is unusual. Is this all occurring with the matching Vendor.img to the Pure Nexus build you are using?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm, that is unusual. Is this all occurring with the matching Vendor.img to the Pure Nexus build you are using?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes, it was. I have reverted back to stock unrooted and I am no longer having the issue. I did not want to do this, but unfortunately I have to actually use my phone as a phone and need the basic functionality that I was losing with the continuous issue.
tluley51 said:
Yes, it was. I have reverted back to stock unrooted and I am no longer having the issue. I did not want to do this, but unfortunately I have to actually use my phone as a phone and need the basic functionality that I was losing with the continuous issue.
Click to expand...
Click to collapse
I suggest trying another rom and testing that out. May help you isolate the problem. Perhaps its has to do with 2.4 ghz vs. 5.0 ghz Wi-Fi networks, either can be forced in Wi-Fi settings. Or it may be a conflict with a mod in Pure Nexus if this does not occur on another rom.
Sent from my Nexus 5X using Tapatalk

sporadically losing data connection - reboot fixes temporarily - any ideas?

This has been happening for a couple months. Seems like a couple times a day I lose my data connection, and the only fix is to reboot. After that it's fine for a while, until it drops again...
Running rooted 6.0.1, radio version 3.61. Anything I can check? Or should I just flash a new image?
I have this issue, flashing different radios did nothing for me. The hardware is just going bad I think
Been having the same issue for a couple months now, going to my carrier for a new SIM and resetting APN did nothing. Thought it was my ROM at first and ended up flashing a few different ones along with kernels, it was never fixed. Data drops and comes back about 10 minutes later, every half hour or so. Seems to not effect calling or messaging, only data. Is this a confirmed hardware issue?
My wife and I both had our 6P's doing this as well. Seems like the device will get in a connection loop or something. the WiFi drops, then my 4g data signal, then both are out, then WiFi turns on, Data turns on, then repeats the process. I usually reboot, or toggle airplane mode off and on to stop it. Its periodic, but it doesn't last long on my end. I'm on T-Mobile BTW
UPDATE - REFER YOU TO THIS LINK. Looks like radio files from Android O Beta DP4 are confirmed to fix the T-Mobile Cell Signal Bug
Hopefully, this means our prayers have been answered
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637/page35
mikeygeer said:
UPDATE - REFER YOU TO THIS LINK. Looks like radio files from Android O Beta DP4 are confirmed to fix the T-Mobile Cell Signal Bug
Hopefully, this means our prayers have been answered
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637/page35
Click to expand...
Click to collapse
My radio didn't drop once on the way to work today, hell, it's still going right now. I actually think it's been fixed
is it ok to apply the updated radio without upgrading android (staying on 6.0.1)? i heard there have been some issues with 7.x on the Nexus?
mgoblue2005 said:
is it ok to apply the updated radio without upgrading android (staying on 6.0.1)? i heard there have been some issues with 7.x on the Nexus?
Click to expand...
Click to collapse
I do not know its comptibility with 6.0.1 - you could just make a backup and give it a try.
conversely I must say - Nougat on good ROMs is stable and gets good battery life. What are you concerns with just joining the party here on Nougat?
mikeygeer said:
I do not know its comptibility with 6.0.1 - you could just make a backup and give it a try.
conversely I must say - Nougat on good ROMs is stable and gets good battery life. What are you concerns with just joining the party here on Nougat?
Click to expand...
Click to collapse
-----------------------------------------------
I'm running rooted stock android. Haven't made the move to any custom ROMs yet. I recall when Nougat first landed people were reporting some issues with it on the 6P (battery life? instability?).
That being said I'm open to loading a Nougat ROM if it's gonna be stable. Is there any consensus on top ROM for the 6P (something close to stock android experience)?
Close to stock with aroma installable features, check superxe rom, you can choose between nougat or Android O.

Categories

Resources