Related
Firstly congrats. If you're seeing this post, you might have already done so or are trying to flash some custom ROM, which is absolutely ok.
Rather its fun and satisfaction that you keep your device up to date if not possible through official means. Also for some good changes.
Unfortunately, its not completely flawless. There might be some issues which are covered in the further updates of the ROMs.
Among oother small problems, one major problem I faceed when I flashed a custom ROM (actually three) is that the Android Market failed miserably when I initiated it. There were horrible search results. Also the categories were not showing the apps which would otherwise be placed under them.
Fortunately, the Android Market site was open for me which was the last option for me to go on with.
The only solution I could find to this problem was a bit of patience and some really basic info about market.
I tried to re install all the applications that were previously being shown as installed already. Though they showwed "Installed" status but you can install them again.
After a lapse of almost three days, I tried to access the Market app and it was actually accessible with all the search functionalities and EVERYTHING running smooth.
A thing I would like to advise on is try not to wipe out all the data (the 4 wipe out options while flashing) from your device. It might, might help you not to lose data and possibly, the Android Market too.
Have fun.
I've been on a custom rom for greater than a month now and have not experienced any market issues. The only problem that I've ever had was wifi stopped connecting for me. But it was an easy fix. Sorry you've had problems... Perhaps something else is to blame?
Sent from my PC36100 using Tapatalk
antjmon said:
I've been on a custom rom for greater than a month now and have not experienced any market issues. The only problem that I've ever had was wifi stopped connecting for me. But it was an easy fix. Sorry you've had problems... Perhaps something else is to blame?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yes, as I have solved the problem anyways.
DawoodMunir said:
Yes, as I have solved the problem anyways.
Click to expand...
Click to collapse
عزيزي منير
Please let me know how did you fixed this issue?
I really need to know because i have the same issue.
Hi Guys,
I bought a Nexus 4 on Ebay. The listing said the phone was stuck in "download mode" and the guy couldn't fix it. I bought it cheap, received it, and used a thread here (http://forum.xda-developers.com/showthread.php?t=2347060) to get it up and running. The phone is now booting and working well enough.
Unfortunately there are 2 problems that seem to persist.
1) Rotation doesn't work at all. The sensor reports no data back when I use various testing applications. I know that the phone has some issues if you mix radios between versions. I assure you that I've tried various combinations, including the correct ones, to no avail. I also have checked the "auto rotate" settings in the normal menus and they are turned on. Also, in looking into the rotation issues I found that the other sensors (light, proximity, gravity, etc...) are not functioning.
2) When I install the 4.3 OTA rom the system hangs. Based on some troubleshooting it appears to be the .84 radio that's causing the system to fail to boot, though I haven't gotten the 4.3 rom to boot at all.
I've run a logcat and there are error messages that seem to report problems with the sensors. I googled for them and found them in other logcats where people did not report the problems that I'm having. I'd be happy to post a logcat if it would help.
I believe that this is a software issue, but it is possible that it is hardware. I just get the feeling that it is software.
Can anybody contribute or point me in a direction for more information.
you have tried reflashing the factory img?
simms22 said:
you have tried reflashing the factory img?
Click to expand...
Click to collapse
(Sorry, I have this issue posted as a similar question in another thread and thought this response was there. My bad. That's why the reference to the other post. It isn't really that big a deal though...)
I have. In fact, from the post just before mine I tried flashing the "newer" image. I also made an (unsuccessful) attempt to use the LG flash tool mentioned in that post. I was hoping that using a DLL that was specifically for the N4 might yield better results. I couldn't make it work though and eventually gave up.
I'm drawn towards the idea that there is initialization, configuration, or driver issues that are causing this problem. I wonder if, like the bluetooth and wifi MAC issue, there is a similar bit of config magic that must be done for the sensors as well. With that said though, if that were the case, I'd expect there to be somebody else out there who is having the same problem. Given the unknown history of the phone too, it is entirely possible that the hardware is bad.
I'm open to suggestions and certainly willing to post a logcat or whatever may help.
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
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Loopy Frog said:
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Click to expand...
Click to collapse
My N4 had a broken mic out of the box brand new lol. It was the latest batch, made in October 2013
I fixed it by getting a new mic because i diagnosed it wasn't a software issue
I ended up flashing "LRX08 B15.5S" from [L][5.0] Android L-pv N4 [B15.1 updated 10-27-2014] and I also put the "91u-a9: AOSP/L" Kernel from [KERNEL] [4.4.4/CM/(L)] [Bleeding Edge] Unleashed Kernel Series [91u-a9] [10/28/2014] Thinking there might be a chance it would fix my problem bringing it to 5.0 instead of 4.4.4.
I thought it worked all day yesterday without the data cable needing to be plugged in, I ran tests all day and it worked fine. Today is a different story though. I guess the data cable creates some form of initial connection the phone needs for my mic to work, and leaving it long enough it looses that connectivity. I'm not sure.
I don't have any intentions sending the phone in to get fixed, or repaired, as I'll be upgrading my nexus soon enough. I guess at this stage my fix is too cut the very end off of an old cable and have it in my pocket for incoming and outgoing calls. Anyone else have another solution?
Best Regards.
Loopy
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I believe that's what I did in the very very beginning of the problem, however on the possibly note that I didn't I'll do that just before Nov 3rd, if the official L is update is available then. Thanks ark
Yup...
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
flashed stock. Problem still persists.
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