Hello All,
Just got my Incredible Rooted after some initial troubles. I removed CityID, Footprints, and Peep during the adb shell.
Now my GPS is constantly on when the phone is on. The Icon is always there in the notification bar.
Anybody have any idea why this is? or how to stop it? Its killin my battery. THANKS!
Got it!
Beautiful Widgets was causing the GPS usage. Went away the second I uninstalled it. I am reinstalling now and I doubt it will come back.
Sorry for wasting a thread. Hope this helps any other users.
Mine was doing that too. I dropped the Beautiful Live Wallpaper I was using and rebooted the phone, then the GPS stopped coming on and it seems to be fine now. I still have Beautiful Widgets installed, and never uninstalled it either.
mine seems to stay on. no widgets or anything.
hadisious said:
Hello All,
Just got my Incredible Rooted after some initial troubles. I removed CityID, Footprints, and Peep during the adb shell.
Now my GPS is constantly on when the phone is on. The Icon is always there in the notification bar.
Anybody have any idea why this is? or how to stop it? Its killin my battery. THANKS!
Click to expand...
Click to collapse
Tell me if you still have the Google navigation icon.
I don't know if this would work, since I still have not rooted myself (just got back from LA and am setting up a proper dev environment for some real programming first... hopefully =p). But there are several widgets (one in sense, one in base Android I believe) that allow you to switch GPS/wifi/3G data/etc with a click of a button. The android-base widget is called "Power Control" and the HTC buttons can be selected by going to Widgets => Settings, then dragging and dropping which ones you want to use.
I hope the solution can be this easy (although it seems to rarely be, heh).
Did Amazon push out an update to settings? I had a notification today that I've never seen before, it was the settings icon and said something about an update available, I just dismissed it because I didn't want to update, but now some settings selections are not available. I can't turn on or off hotspot or configure it, data usage is now blank, among others.
I don't think it's something I did, because I haven't messed with anything in a few weeks. I'm rooted, with a few apps frozen, Google apps installed, xposed, etc. Thought I had this thing about perfect and now this. Anyone else see this?
Correction, this seems to happen when the battery starts getting low, some settings menus don't work.
Hi All
First time really contributing to this but I feel like some super-duper hacker (not that I know anything!). I'm smart and can play around with things. I actually trained as a lawyer, went into recruitment but am now considering moving into computing! This is fun and you can be involved in projects. However my eye has developed a nasty twitch... Recruitment is dead now anyway. (Any tips on how I can begin getting into programming/app development/ XDA work etc whatever it is would be appreciated, (I literally have no idea where to go but I'd like to!)).
Anyway, back on topic:-
So...I've been up for the past 24 hours with a new laptop and at first rescuing my Samsung Galaxy S6 which got caught in a bootloop with no recovery, (had to hard reset, lost all data), upgraded Android to Nougat. It all started when I went to do a recovery boot to get Magisk to work but it all went haywire. :crying:
Happy to give you a system specs - models - builds etc, if there's a good way of doing that let me know and I'll post so you techies can take a look and see what might be the reasons behind the issues. I'm running a 'bug report' through Developer Options at the moment and can post this if useful? I have a Bug Report that I've generated if this is useful to anyone in getting to the bottom of these issues, let me know and I can send...
Ok, so with no further waffling, the issues I've seen so far in the short time I've had this lineage-14.1-20170307-UNOFFICIAL-Nexus7420-zerofltexx-2 (this is the Zip file that I found for the Samsung Galaxy S6 which I understand is only developmental at the moment, it doesn't have its own one yet?)... (in descending order of importance):-
1. Fastcharging - this is very important to me. This seems to have stopped working. How can we get this back? Potentially a dealbreaker with the ROM if this can't be sorted quickly.
2. EE I should be receiving 4G++ super duper speeds on EE. This is really impressive and is very important again. However, since flashing the ROM etc, it's only connecting to T-Mobile (a connected network to EE but doesn't benefit from their 4G++ network, EE bought T-Mobile in the UK ages ago). I've contacted EE about this as I thought it may just be a settings issue. They sent me settings though it's still not working. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
3. Whatsapp VoiceNotes - I use WhatsApp voicenotes all the time; it's a crucial part of my day. Since upgrading there are two issues I can see with this:- a) there is an interference noise that ruins the clarity of each recording sent, it's there the whole time; and b) the recording itself sounds like it's slowed down and doesn't sound normal or right. At the moment this is unusabule and it's massively important, I'd imagine to most people too. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
4. Magisk - The reason for embarking on the entire debacle of the past 24 hours has been to be able to hide my root. That's why I wanted Magisk in the first place so I could use the apps like banking apps and SnapChat and Virgin TV that in draconian fashion refuse to let one use them when it sees it's a rooted device. Magisk to the rescue (in theory). So when I load up Magisk Manager now under SafetyNet Check Success, the basicIntegrity option is sometimes fine though now it's showing 'X'; and 'ctsProfile:false' is permanently showing. I've hidden Google Play Services and Google Play as I read this can cause issues. It does show #superuser in the dropdown and I'm not sure if this is a legacy from SuperSu I had before (don't think so as I did a complete reboot) or if this is part of the app?
5. Torch - torch option on settings panel doesn't seem to yield any torchlight at all. I wonder if other apps work or if there's anything the techies can do here?
Thanks so much for reading and I look forward to helping or assisting in solving in whatever way I can.
bestfootie said:
Hi All
1. Fastcharging - this is very important to me. This seems to have stopped working. How can we get this back? Potentially a dealbreaker with the ROM if this can't be sorted quickly.
2. EE I should be receiving 4G++ super duper speeds on EE. This is really impressive and is very important again. However, since flashing the ROM etc, it's only connecting to T-Mobile (a connected network to EE but doesn't benefit from their 4G++ network, EE bought T-Mobile in the UK ages ago). I've contacted EE about this as I thought it may just be a settings issue. They sent me settings though it's still not working. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
3. Whatsapp VoiceNotes - I use WhatsApp voicenotes all the time; it's a crucial part of my day. Since upgrading there are two issues I can see with this:- a) there is an interference noise that ruins the clarity of each recording sent, it's there the whole time; and b) the recording itself sounds like it's slowed down and doesn't sound normal or right. At the moment this is unusabule and it's massively important, I'd imagine to most people too. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
4. Magisk - The reason for embarking on the entire debacle of the past 24 hours has been to be able to hide my root. That's why I wanted Magisk in the first place so I could use the apps like banking apps and SnapChat and Virgin TV that in draconian fashion refuse to let one use them when it sees it's a rooted device. Magisk to the rescue (in theory). So when I load up Magisk Manager now under SafetyNet Check Success, the basicIntegrity option is sometimes fine though now it's showing 'X'; and 'ctsProfile:false' is permanently showing. I've hidden Google Play Services and Google Play as I read this can cause issues. It does show #superuser in the dropdown and I'm not sure if this is a legacy from SuperSu I had before (don't think so as I did a complete reboot) or if this is part of the app?
5. Torch - torch option on settings panel doesn't seem to yield any torchlight at all. I wonder if other apps work or if there's anything the techies can do here?
Thanks so much for reading and I look forward to helping or assisting in solving in whatever way I can.
Click to expand...
Click to collapse
So in addition to these I've also discovered a further three issues:-
6. WhatsApp camera not working - you can take a photo within WhatsApp but it doesn't progress to the launch screen to the next screen to send the photo. Strangely, video clips do seem to work...
7. Bluetooth headset doesn't seem to be working anymore
8. Sky Sports App once you get past permissions and everything to watch the show it freezes on the loading step. I imagine this is something to do with the modified ROM/Kernel?
bestfootie said:
So in addition to these I've also discovered a further three issues:-
6. WhatsApp camera not working - you can take a photo within WhatsApp but it doesn't progress to the launch screen to the next screen to send the photo. Strangely, video clips do seem to work...
7. Bluetooth headset doesn't seem to be working anymore
8. Sky Sports App once you get past permissions and everything to watch the show it freezes on the loading step. I imagine this is something to do with the modified ROM/Kernel?
Click to expand...
Click to collapse
9. I'll also add in here that call volume and volume in general seem really low.
As a result of these nine bugs I'm going to have to revert back to an older version, quite possibly Stock Android, unfortunately... :crying:
Anyone having issues with their P2XL/Android Pie and location related things?
Examples...
My smart lock (August) no longer auto unlocks when I get home.
My Nest thermostat no longer knows I'm home (and adjusts temp) until I walk in front of it.
My Phillips Hue lights no longer auto turn on when I get home after dark.
Etc etc.
Started around the time Pie was released, but I don't think at EXACTLY the same time (shortly after, I think). My wife has a P1XL and Pie and has the same issues.
I initially chalked it up to needing a fresh install, but I finally got around to doing that with no improvement.
Confirmed all of the location/scanning stuff in Settings is enabled. GPS itself works fine (e.g. no issues with Google Maps).
In fact, if I open the August app, it knows where I am... The change in location simply didn't trigger the unlock process.
I'm guessing either a Pie bug, or these apps needing further updates... But not seeing much in the way of other people's reports has me uncertain.
All related issues (August, Nest, Hue) started at the same time as each other and the same time on both phones (mine and my wife's).
I've tried toggling things on and off, re-installing things without letting Google restore data, minimal installations to ensure it wasn't some sort of app conflict.
At this point, I can't think of anything else to try. Obviously I can reach out to Google... Just not super optimistic about it accomplishing anything.
If anyone can confirm from their end or has any troubleshooting ideas, I appreciate the share in advance.
Thanks.
Edit: Oh, I also turned off battery optimization for those apps and eventually Adaptive Battery was turned off in general.
I've been having an issue with my Z2 Force that I've never had with any of my other phones. For some reason, it acts like I'm hitting the home button, even when I'm not touching it. I could be using a web browser, the XBox app, or any other app and it will go back to whatever launcher I have set as default. It doesn't close the app, it just minimizes it. I've tried disabling the home button for navigating & use the touch buttons instead, and when that didn't work I tried doing a factory reset. Well, it's still doing it, and I'm to the point where I'm very tempted to try to use one of the rooting methods I was able to find online, one of which does mention the specific model of my Verizon variant (XT1789-01). I can live without root if needed, but this 'phantom home button pressing' thing is driving me nuts. Any help is appreciated, and thanks.
I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.
Eco0901 said:
I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.
Click to expand...
Click to collapse
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.
will4958 said:
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.
Click to expand...
Click to collapse
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):
Eco0901 said:
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):
Click to expand...
Click to collapse
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.
Maybe a downgrade to 8.0 will make it, this bug is so annoying
Eco0901 said:
Maybe a downgrade to 8.0 will make it, this bug is so annoying
Click to expand...
Click to collapse
It's possible that might work, but either way I still need to be able to root the thing and find a ROM made for the Verizon model. My phone has only been doing this for a couple weeks or so, but before that it would actually fully close certain apps (gsam Battery Monitor, RadioU, Taskbar, and some others). However, I more than less fixed that by setting the timers for those apps to 23 hrs.
How did you set the timers? That fixed the problem of minimizing the apps?
Eco0901 said:
How did you set the timers? That fixed the problem of minimizing the apps?
Click to expand...
Click to collapse
The reason why I tried setting timers on certain apps was because they were being killed automatically, this was before the 'phantom' home button thing. The following steps may/may not resolve your current issue, but you can try them if you'd like:
1. Go to Settings
2. Apps & notifications
3. Screen time
4. At the bottom, you'll see a few apps listed, and a an option to show all of your apps. Select 'Show all apps', then the app you want to set the timer for.
5. Next to each app you'll see a little hour glass. If it's empty, then there is currently not timer set. If you'd like to set a timer, tap the hour glass, then set your desired time.
Again, I did all this well before my phone started acting like I was hitting the home button in an effort to get it to stop closing my favorite apps. For the most part, it worked, but the automatic closing thing only started after the upgrade to Android 9. I did find a site where I could download a previous stock ROM, but without root it may/will re-update again. There's an app that let's you prevent updates, but the phone has to be rooted in order for the app to work. I can't really remember the name app right now, but I used to use it on my Note 4. I think there was also a way to do it through the command line in Windows (might've worked in Linux, too), or it might've been a combination of an app and the command line.
In any case, the root method I thought I'd found wasn't really all that instructive, and I need to make sure I can actually fully unlock the boot loader before attempting root. If I can't unlock it, then whatever root method I try won't stick. The auto home button thing, at least on my phone, seems to be random, though. Sometimes it'll be fairly soon after opening an app, other times the app will stay open for a good while before going back to the home screen.
Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.
Eco0901 said:
Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.
Click to expand...
Click to collapse
It may not immediately update the OS after a downgrade, but you would get a notice there's an update available, even on a rooted phone. Since root only removes the barriers that're usually there to keep the less knowledgeable from hurting their phones, you'd still get any update notices a non-rooted phone would usually get. There is an app called NoBloat Free, and with it there are two files you'd be able to block that'd keep your phone from updating when you don't want it to. I'm not sure if the app is still in the Play Store or not, but I did use it on my Note 4, and it worked pretty well.
On a side note, I've had Opera open on my phone for a while now, and so far it hasn't gone back to the home screen yet. As for the phone itself, Moto phones are pretty good phones, my Z2 Force is my fourth phone from Moto (the other three being the RAZOR smartphone, Bionic, and the original RAZOR, which I sometimes miss). For all we know, our issue could be caused by a software glitch, hence my desire to root and test a different ROM.
Do you know how to downgrade to 8.0? I'll try it, it's a good phone and I didn't pay so much por this, that's why I'm not that angry. I won't root the phone since the games I play would kick me from the game. So just for make me sure I understand, do you reestablished the phone with a computer or from the same phone?
will4958 said:
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.
Click to expand...
Click to collapse
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body
Eco0901 said:
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body
Click to expand...
Click to collapse
I think I may have finally given my phone the smack in the pants it needed to start behaving itself again. I followed the link you provided, and one of the comments suggested installing any updates for a couple Verizon apps and disabling them. Not sure if this would work on a non-Verizon phone or not, but I've had the XBox app open on my phone for over 20 minutes now, and so far it hasn't minimized yet. To be accurate, I even closed & reopened the app. The apps mentioned were Verizon App Manager & My Verizon Services. I was able to disable the first app, but not the second, and rebooted my phone after doing so.
If your phone isn't from Verizon, there may be a similar pair of apps you could try disabling, though I'd probably look it up first to be on the safe side.
Update: It's been almost two hours now and the app still hasn't closed. Now, to get the screen protector residue off my phone.