Good for Enterprise causing wakelock - X Style (Pure) Q&A, Help & Troubleshooting

Anyone else using Good for Enterprise and experiencing a wakelock? Since I got the software activated by our IT shop yesterday, the phone is wakelocked 75%+ of the time.
This is similar to what happened with my 2014 Moto X after the 5.0 update, but I did NOT experience the same behavior on a Nexus 6 that I had been using for the past six months or so.
Thanks in advance for any insight or suggestions.

Related

[Q] Possible quality issues N4 bought in MediaMarkt DE

Dear N4 fans,
I just bought a Nexus 4 yesterday from MediaMarkt Germany in Rheine. The phone is absolutely great and works perfect but I have some doubts. Maybe I am just paranoid but as a big geek I want to have the best hardware.
My issues are the following:
1) The haptic feedback acts different than call vibration. It makes a strange sound but it's quite strong. I can imagine that the "engine" is bigger but the frequency of rotation is lower. I have experienced haptic feedback on Galaxy S & SII and the feeling was better in my opinion. It might be broken or that's the way it is?
2) The phone came with Android 4.2 build on 8th Nov 2012 and had the date setted on 20 Jan. In the check for updates section it was saying that it checked for updates on 1st of January (19 days ago). The phone was turn on in the past and somebody check it or is just standard? Do you think my phone is one of the old lots which was built before launch?
Thanks in advance for the feeback. I can't wait to arrive home from office to flash some custom kernels and ROMS. Cheers!

Switched to Moto X

I have switched to Moto X. Although have not sold my grand yet but will update the thread with the price.
Had a fully satisfied experience for a year. But in the last couple of weeks the phone started giving me a lot of problems. Huge amounts of lag and hang. It got so terrible that i had to switch. But after a factory reset it seems to work fine. Good luck to everyone still using the phone. Dont give up any hope for official kitkat.
Let me know how much.
Sent from my SM-N900W8 using Xparent Green Tapatalk 2

Can't see old phone on restore screen

Hi,
I owned a Nexus 5 and managed to return it to Google some days before the new Nexus came out. I got my 6P today and, in the meantime, I used a Moto X 2013 borrowed by a friend. Today I tried to restore apps from the Moto X but the device does not show up on the drop down menu. All that it's there is my Nexus 5 from almost two months ago. Any idea on how to solve this? I still have the Moto X so I'm able to do whatever I need on it.
--EDIT--
Nvm, fixed it. Backup option was turned off on the Moto X. I'm stoopid facepalm.

June Security Update

since receiving the June security update a few days ago i am noticing significant improvement in battery life. At the end of my 8 hour shift I am at 70%. Anybody else noticing this?
What does the June security update consist of? I haven't updated yet in case we get root soon and requires to be on an older version. If it's not that important I'd rather not update.
still haven't received the June security patch. When did you get it?
still waiting on this for my s7 Active...cmon ATT
jerseyboy51 said:
since receiving the June security update a few days ago i am noticing significant improvement in battery life. At the end of my 8 hour shift I am at 70%. Anybody else noticing this?
Click to expand...
Click to collapse
Are you still seeing great battery life or has it tailed off?

Nougat bootloop issue is fixed by replacing motherboard with new IMEI no.

After installing January update on my nexus 6p, my phone stuck in bootloop. I approached Huawei service center last Thursday (01/12/2017) for further actions and gave my device for inspection. Today i got my phone back, though i expected a new or refurbished device, i just got my mother board replaced with new IMEI no.
When i contacted Google regarding the issue, the representative asked me to downgrade the OS from 7.1.1 to 6.0.1. Surprisingly my device came with Marshmallow version of android installed as suggested by the Google employee.
I'm a flashaholic kinda person who loves to test different ROMs. Since Marshmallow has many stable/battery efficient ROMs and stable Xposed support, I decided to go with RR 6.0.1 with Xposed and any custom kernel.
Now my concern is to whether update my device to 7.1.1 based custom ROM or stick with MM. I'm also worried to try even MM ROMs as I have just few days left with my device warranty, I'm like cat on the wall thinking to flash and try ROMs or stick to stock RR until Google rolls out fix for the mysterious bootloop issue.
NOTE: I have searched for similar thread for answers but couldn't find one. So kindly navigate me to the respective thread if the issue is already under discussion.
jagadeeshkumar5793 said:
....Now my concern is to whether update my device to 7.1.1 based custom ROM or stick with MM. I'm also worried to try even MM ROMs as I have just few days left with my device warranty, I'm like cat on the wall thinking to flash and try ROMs or stick to stock RR until Google rolls out fix for the mysterious bootloop issue. [/B]
Click to expand...
Click to collapse
There are multiple instances/threads with MM devices bootlooping- both stock unrooted and custom roms. So far there is no link whatsoever to N, but quite a few people sitting on MM waiting for the miracle update to come down from Mt. Olympus. Don't get me wrong... there are a couple of valid reasons for some to stay with MM for the time being (eg. Xposed support), but IMO hard bricking or bootlooping are not valid reasons to fear updating to N.
jagadeeshkumar5793 said:
After installing January update on my nexus 6p, my phone stuck in bootloop. I approached Huawei service center last Thursday (01/12/2017) for further actions and gave my device for inspection. Today i got my phone back, though i expected a new or refurbished device, i just got my mother board replaced with new IMEI no.
When i contacted Google regarding the issue, the representative asked me to downgrade the OS from 7.1.1 to 6.0.1. Surprisingly my device came with Marshmallow version of android installed as suggested by the Google employee.
I'm a flashaholic kinda person who loves to test different ROMs. Since Marshmallow has many stable/battery efficient ROMs and stable Xposed support, I decided to go with RR 6.0.1 with Xposed and any custom kernel.
Now my concern is to whether update my device to 7.1.1 based custom ROM or stick with MM. I'm also worried to try even MM ROMs as I have just few days left with my device warranty, I'm like cat on the wall thinking to flash and try ROMs or stick to stock RR until Google rolls out fix for the mysterious bootloop issue.
NOTE: I have searched for similar thread for answers but couldn't find one. So kindly navigate me to the respective thread if the issue is already under discussion.
Click to expand...
Click to collapse
Did the Google rep say why to downgrade from Nougat to Marshmallow? I've never heard Google admit that Nougat causes boot loop problems so it seems like a strange thing for a Google rep to say.
The Google rep admitted that they have quite a few customers affected after the recent security patch update and he also stated that their engineers are working closely with OEM in fixing the issue permanently.
And regarding the downgrade to MM, the employee said that this issue is only after Nougat update and also said that not all the devices are affected but quite more devices which are updated to Nougat. So the suggestion to downgrade is for temporary fix till Google rolls out the miracle update.
@v12xke - Google did admit that the issue is received at their end and they are being fixed in a reddit thread.
https://www.reddit.com/r/Nexus/comments/4zhx53/never_ending_boot_loop_with_android_7_nougat/d7ppndx/
jagadeeshkumar5793 said:
The Google rep admitted that they have quite a few customers affected after the recent security patch update and he also stated that their engineers are working closely with OEM in fixing the issue permanently.
And regarding the downgrade to MM, the employee said that this issue is only after Nougat update and also said that not all the devices are affected but quite more devices which are updated to Nougat. So the suggestion to downgrade is for temporary fix till Google rolls out the miracle update.
@v12xke - Google did admit that the issue is received at their end and they are being fixed in a reddit thread.
https://www.reddit.com/r/Nexus/comments/4zhx53/never_ending_boot_loop_with_android_7_nougat/d7ppndx/
Click to expand...
Click to collapse
I read the link you provided before. In it Google says it's strictly a hardware issue, which is what they've been insisting all the time. That's why the Google employee asking you to downgrade to Marshmellow struck me as being strange.
jhs39 said:
I read the link you provided before. In it Google says it's strictly a hardware issue, which is what they've been insisting all the time. That's why the Google employee asking you to downgrade to Marshmellow struck me as being strange.
Click to expand...
Click to collapse
Yes, nougat badly does something to hardware especially motherboard, so my device's motherboard got replaced with new IMEI no. and I stick with RR MM rom with xposed and it is working great so far. Hope Google rolls out the miracle updatennsoon for the bootloop issue and fix it permanently.
Mine died today stuck at google screen 1 month out of warranty and never rooted. I'm basically out 500 bucks after one year. Unless they will fix it for a fee.
Contact them anyway. Tell them it is the problem that hundreds of people all over the internet are having. There are many reports that they are working with people.
Sent from my Nexus 6P using XDA-Developers Legacy app
jagadeeshkumar5793 said:
Yes, nougat badly does something to hardware especially motherboard, so my device's motherboard got replaced with new IMEI no. and I stick with RR MM rom with xposed and it is working great so far. Hope Google rolls out the miracle updatennsoon for the bootloop issue and fix it permanently.
Click to expand...
Click to collapse
There's a rumor around that if you downgrade your N6P to KitKat and stay there the problem will never appear again. KitKat does something really good to the hardware, especially the motherboard. :good:
kenhicg said:
Mine died today stuck at google screen 1 month out of warranty and never rooted. I'm basically out 500 bucks after one year. Unless they will fix it for a fee.
Click to expand...
Click to collapse
You can probably contact the service center and get a replacement if you bought from Google play store coz in India the service is undertaken by Huawei and not Google. When I had a chat with Google rep he sounded like the faulty device can be replaced freely even if out of warranty. And surprisingly mine was only like oddly 15 days warranty left when i gave my mobile to service center but now when i check the warranty, they have extended will April 21, 2017.
CyberpodS2 said:
Contact them anyway. Tell them it is the problem that hundreds of people all over the internet are having. There are many reports that they are working with people.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
You are right. Google sounded like the issue is taken care freely without cost even if the handset is out of warranty. When I spoke with the Google representative, I asked him why the customers has to pay money even if the handset is out of warranty when the issue is from manufacturer side and not the customer side. He stated and clearly explained that the issue is occurring only after the update and many devices are affected, but the customer also have to understand that not all the devices are affected by the update but specific handsets only. So Google is working closely with Huawei to fix the issue and he also stated that a team is working specifically for this issue.
jagadeeshkumar5793 said:
You are right. Google sounded like the issue is taken care freely without cost even if the handset is out of warranty. When I spoke with the Google representative, I asked him why the customers has to pay money even if the handset is out of warranty when the issue is from manufacturer side and not the customer side. He stated and clearly explained that the issue is occurring only after the update and many devices are affected, but the customer also have to understand that not all the devices are affected by the update but specific handsets only. So Google is working closely with Huawei to fix the issue and he also stated that a team is working specifically for this issue.
Click to expand...
Click to collapse
bumping this up..
any updates regarding this issue ?
i sent my phone to the huawei service centre here, they gave me an estimate of almost 400 USD for replacement of the motherboard (im out of warranty), which is crazy !
I can still access my bootloader and recovery (both stock and twrp, if needed), so ive hope that maybe i can fix this problem myself. Or maybe i mightve to just replace the motherboard myself.
My 6P died today. NitrogenOS, same issue.
I have quite a bit of data from the last time I backed up, that is on this phone. The data loss concerns me a lot more than the phone. Is there any way to recover it?
And no, I can't boot into recovery. Only fastboot.
greydelta38 said:
My 6P died today. NitrogenOS, same issue.
I have quite a bit of data from the last time I backed up, that is on this phone. The data loss concerns me a lot more than the phone. Is there any way to recover it?
And no, I can't boot into recovery. Only fastboot.
Click to expand...
Click to collapse
I'm my experience and probably hundreds more by now, no recovery access indicates your done. No way to recover your data. Sorry...
Sent from my Nexus 6P using XDA-Developers Legacy app
greydelta38 said:
My 6P died today. NitrogenOS, same issue.
I have quite a bit of data from the last time I backed up, that is on this phone. The data loss concerns me a lot more than the phone. Is there any way to recover it?
And no, I can't boot into recovery. Only fastboot.
Click to expand...
Click to collapse
I have fixed a handful of G4's bootloops(very, very comnon) by reflowing the processor and northbridge ram. You can youtube G4 bootloop fix. The solder underneath becomes weak and cracks, same thing that causes red ring of death on 360 and yellow light of death on ps3, the dreaded lead free solder that the EPA mandates manufactures use. Unfortunately reflowing is usually a temporary fix, but at least long enough to get your data back.
I suspect since the 810 runs even hotter than the 808 in the G4, that the same thing is happening here. Plus Huawei used terrible thermal compound to dissipate the heat. I have yet to get my hands on a 6p to test my theory on, and hopefully I won't have to do it to mine. If you're tech savvy or know someone who is it might be worth a shot at saving your data. Or PM me and I'll give it a shot.
hawkswind1 said:
I have fixed a handful of G4's bootloops(very, very comnon) by reflowing the processor and northbridge ram. You can youtube G4 bootloop fix. The solder underneath becomes weak and cracks, same thing that causes red ring of death on 360 and yellow light of death on ps3, the dreaded lead free solder that the EPA mandates manufactures use. Unfortunately reflowing is usually a temporary fix, but at least long enough to get your data back.
I suspect since the 810 runs even hotter than the 808 in the G4, that the same thing is happening here. Plus Huawei used terrible thermal compound to dissipate the heat. I have yet to get my hands on a 6p to test my theory on, and hopefully I won't have to do it to mine. If you're tech savvy or know someone who is it might be worth a shot at saving your data. Or PM me and I'll give it a shot.
Click to expand...
Click to collapse
I appreciate the reply, I'll look into it for sure.
It'll be interesting to see what Google and Huawei say about this in the near future, now that this is becoming a more widespread issue. I went out and bought a G6 today, I'm a little afraid to spend money on the Pixel after reading about Google practically denying the problem exists with the 6p and their latest update. Time will tell, I suppose.
Just got mine back last week, same issue. Motherboard replaced under warranty. Phone was 11 months old hope new will last longer. No problems with the the being rooted
Mine just went to hell. I've seen a friends 6P go through bootloop, tried all sorts of stuff but couldn't help. He sent his in to Huawei and replaced.
I have been on 7.1.1 for a while, but all of a sudden just crapped out. 6 Days out of the Huawei extended warranty and they want $160 to swap.
Hesitant to drop $160, even $100 to replace and possibly face the same issue later on.
I turn it on once in a while and get teased by the damn phone...at one point it went all the way to the setup screen, then restarted.
Jessooca said:
Does anyone have any experience with Google or Huawei actually replacing/repairing their Nexus 6P (google store purchased) that is just a single month out of warranty? Google won't help despite the fact I am in a hurricane ravaged area of FL and the Hurricane hit here on the 11th, mine is out of warrant as of the 12th and I had no power for 9 days and up until the 13th my 6P never had an issue, now it's bootloop city and freezing constantly.
Click to expand...
Click to collapse
Not anymore. They've reviewed their policy on out of warranty devices and made a press release or statement that RMA's have been stopped for out of warranty devices. SOL. Hello new phone.
Jessooca said:
Does anyone have any experience with Google or Huawei actually replacing/repairing their Nexus 6P (google store purchased) that is just a single month out of warranty? Google won't help despite the fact I am in a hurricane ravaged area of FL and the Hurricane hit here on the 11th, mine is out of warrant as of the 12th and I had no power for 9 days and up until the 13th my 6P never had an issue, now it's bootloop city and freezing constantly.
Click to expand...
Click to collapse
I also have a 6p purchased through the Google store. I paid extra for Nexus protect. I was able to RMA my phone due to the battery issues of the 6p. Google was extremely easy to deal with and hooked me up with a new pixel XL.
If I were you I'd probably look 2nd generation of Pixels

Categories

Resources