Partial wakelocks E6653 on Nougat 7.1.1 - General Questions and Answers

I've noticed that this particular thing was running at about 33% of the partial wakelocks the other day and I assume it was the culprit in running my battery down very fast. Like to know what it is - google isn't being too kind.
*job*/com.google.android.apps.nbu.files/.spamdetector.SpamService
Something to do with Gmail app perhaps ? Betterbattery stats was app I used to ascertain this.
What is this problem child and what can I do about it ?
Actually after a restart and 8 hours uptime it's showing 10% today so perhaps it's settling down ?
It has previously been rooted and has it's bootloader unlocked but it's back to 'standard' now - unrooted
I used a clean FTF and Flashtool (by Androxyde) to rewrite the system after I had previously rooted it and had Cyannogen on it. It doesn't need root to run better battery stats, as I installed it using some ADB commands which give it more permissions. Have also used some ADB commands, (re cmd appops set com.xxxx.xxx app RUN_IN_BACKGROUND ignore) to prevent some specific apps from running in background.
Am just not sure of how to deal with this particular item as I don't know what it is.

*job*/com.google.android.apps.nbu.files/.spamdetector.SpamService is service from this app i think store/apps/details?id=com.google.android.apps.nbu.files
Are you installed it? If so, try to uninstall it.

x-zin-x said:
*job*/com.google.android.apps.nbu.files/.spamdetector.SpamService is service from this app i think store/apps/details?id=com.google.android.apps.nbu.files
Are you installed it? If so, try to uninstall it.
Click to expand...
Click to collapse
It has been suggested to me by someone on a thread in a different forum that possibly this:
https://play.google.com/store/apps/details?id=com.google.android.apps.nbu.files&hl=en
is the cause - however they didn't detail why they thought that.................

drcspynz said:
It has been suggested to me by someone on a thread in a different forum that possibly this:
=com.google.android.apps.nbu.files&hl=en
is the cause - however they didn't detail why they thought that.................
Click to expand...
Click to collapse
Its just file explorer i think. You can get better app replacement for it.

x-zin-x said:
Its just file explorer i think. You can get better app replacement for it.
Click to expand...
Click to collapse
Yeah it does appear to be that particular app so I've deleted it. Was a beta version anyway. The Dev got feedback.

Related

Super SU Flashed without root on evo lte?

I've searched high and low but yet to find the correct answer. I also can't post in the development thread due to the 10 post limit. It is what it is.
The question that remains to be answered is it possible to have Super SU flashed but still not have full root access?
Back-story: I have an EVO 4g LTE that I rooted using regaw_leinad's one click RegawMOD EVO LTE Rooter. Worked like a charm. Due to unforseen circumstances I received a new EVO LTE and, like a dummy, applied the latest OTA. Well, the one click rooter did not work as planned. Got the phone unlocked and that was it. I still needed to flash Super SU, which I did. I thought all was well and good until I tried using build.prop and found out that I did not have root access, or at least couldn't use build.prop to edit. I tried another build.prop editor and it flat out told me I had no root access, yet Titanium Backup says I do.
Any suggestions?
Moved to General Q&A section.
Still no luck
Some one suggested reflashing Super SU. I did, but still have the same issue.
Have you tried just regular super user instead of super su. Idk exactly how the super user really works besides allowing apps root access. Maybe not all apps have a command to signal super su, but have it to signal super user since its kinda top seat between those two.
Just a thought to try. Its in play store
dumbest thing lately.....miui roms
Did you open the APK to see if binaries need to be updated?
lowandbehold said:
Did you open the APK to see if binaries need to be updated?
Click to expand...
Click to collapse
jaredw444 said:
Have you tried just regular super user instead of super su. Idk exactly how the super user really works besides allowing apps root access. Maybe not all apps have a command to signal super su, but have it to signal super user since its kinda top seat between those two.
Just a thought to try. Its in play store
dumbest thing lately.....miui roms
Click to expand...
Click to collapse
Would it be wise to install Super User with SuperSU already installed or do I need uninstall SuperSU first?
Haven't checked the APK.
It wouldn't hurt, but never messed with supersu so I don't know if it'd interfere
dumbest thing lately.....miui roms
jaredw444 said:
It wouldn't hurt, but never messed with supersu so I don't know if it'd interfere
dumbest thing lately.....miui roms
Click to expand...
Click to collapse
I'm at a loss. I installed Superuser and updated binaries yet still have the same result.
I get the following error running build.prop Editor...
"Error.java.io.FileNotFoundException:/mnt/sdcard/buildprop.tmp: open failed:ENOENT (No such file or directory)
Then I receive this error running BuildProp Editor (different program)...
"No root access is given! This Tool makes heavy use of it. You can't make changes, add propertys nor restore your build.prop file."
What file explorer are you using
Sent from my LG-VM670 using xda app-developers app
jaredw444 said:
What file explorer are you using
Sent from my LG-VM670 using xda app-developers app
Click to expand...
Click to collapse
File Expert v4.2.4 by Geek Wireless Technology and
Root Browser v1.4.0 by JRummy Apps
I'm wondering at this point if it would be possible to reset my phone to before the 1.22 update.
Download rootchecker from the market and run it to see what it says. It seems like you don't have full root.
lowandbehold said:
Download rootchecker from the market and run it to see what it says. It seems like you don't have full root.
Click to expand...
Click to collapse
We may be on to something here. Used rootchecker and another app to check access. Sure enough, I have complete root access...but...busybox is a different story. Downloading busybox as we speak and will post results afterwards. (May take awhile because the Sprint network at this location is SLOW).
truetexan71 said:
We may be on to something here. Used rootchecker and another app to check access. Sure enough, I have complete root access...but...busybox is a different story. Downloading busybox as we speak and will post results afterwards. (May take awhile because the Sprint network at this location is SLOW).
Click to expand...
Click to collapse
And we have liftoff...so to speak. Busybox was the culprit. I ASSUMED during the initail root process that busy box was intalled, it wasn't.
Thanks to everyone.
truetexan71 said:
And we have liftoff...so to speak. Busybox was the culprit. I ASSUMED during the initail root process that busy box was intalled, it wasn't.
Thanks to everyone.
Click to expand...
Click to collapse
Nice! Glad you got it figured out.

Shell Draining Battery

Any one seen this before? It's new to me. It also does not show up in gsam or bbs
jd1639 said:
Any one seen this before? It's new to me. It also does not show up in gsam or bbs
Click to expand...
Click to collapse
Flash SuperSU instead of SuperUser. It could be a fix. FAQ 4.
Already running super su.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Already running super su.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I never had this drain so I'm not sure it could help you but:
- try wakelock detector too enabling system services/app (advanced mode from the settings)
- remove apps newly installed and revoke root for some apps.
- rebooting doesn't change anything?
- did you or are you using adb shell at the moment?
Primokorn said:
I never had this drain so I'm not sure it could help you but:
- try wakelock detector too enabling system services/app (advanced mode from the settings)
- remove apps newly installed and revoke root for some apps.
- rebooting doesn't change anything?
- did you or are you using adb shell at the moment?
Click to expand...
Click to collapse
I just reached full charge and rebooted. I'll see if I get it again or it was just a fluke. I did use adb but not a shell and terminal emulator was not used or running
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I just reached full charge and rebooted. I'll see if I get it again or it was just a fluke. I did use adb but not a shell and terminal emulator was not used or running
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Are you running nightlies? If so using a previous version of /system/priv-app/Shell.apk might fix it.
Primokorn said:
Are you running nightlies? If so using a previous version of /system/priv-app/Shell.apk might fix it.
Click to expand...
Click to collapse
No it's all stock w/ xposed gb and app ops. Seems it was a fluke thing as it's gone away after a full charge and reboot
Sent from my Nexus 5 using XDA Free mobile app
seems like a stuck process, but it can very well be xposed. i know xposed is popular, but it does create a multitude of differing undocumented issues for many(while many have no issues or aren't aware of issues). so if it keeps happening, id try uninstalling xposed as a very first thing to try. i know that i personality help quite a few by suggesting uninstalling xposed.
A reboot would probably fix it next time you notice it.
Also try wiping cache and dalvik in recovery.

Bootloop on cm-13.0-20160115-NIGHTLY

I flashed supersu beta v2.52, what version should i flash?
You shouldn't flash it, cm has it already.
Areen said:
You shouldn't flash it, cm has it already.
Click to expand...
Click to collapse
For some apps (e.g. leandroid, wakelock detector) it's not enough. So which version is the proper one?
toster88 said:
For some apps (e.g. leandroid, wakelock detector) it's not enough. So which version is the proper one?
Click to expand...
Click to collapse
You probably have no idea how to properly set SU. It is already included in proper way and you should not flash any other version over it because it will cause bootloops.
Areen said:
You probably have no idea how to properly set SU. It is already included in proper way and you should not flash any other version over it because it will cause bootloops.
Click to expand...
Click to collapse
That's great, but maybe you could be a bit more helpful?
toster88 said:
That's great, but maybe you could be a bit more helpful?
Click to expand...
Click to collapse
What I meant is you should not flash anything because you already have included a great working SU into this rom. All you need to do is just set proper privileges in settings (Marshmallow thingy) and voila. If you can't do certain things or allow certain actions you have 99% chance that's sth with permissions in app or SU settings.
Areen said:
What I meant is you should not flash anything because you already have included a great working SU into this rom. All you need to do is just set proper privileges in settings (Marshmallow thingy) and voila. If you can't do certain things or allow certain actions you have 99% chance that's sth with permissions in app or SU settings.
Click to expand...
Click to collapse
I know that I've SU. What I'm saying is that with some apps it works just fine (adaway) and with others it doesn't (wakelock detector with since unplugged option enabled, leandroid doesn't work at all).
what can i do
i have flash super su 2.46 and know my moto g is on bootloop. I enter into fastboot mode, select recovery byt it doesnt works. What can i do?

How to remove Viper4android drivers

Hi all, I've had quite a few issues with Viper4android, including extreme battery drain (since installing my phone will drain from 80% to 0% overnight with no use), and inconsistent volume in various apps (Spotify only has about 60% volume output with random bursts to 100%).
How can I remove all of its components and revert back to stock? I'm guessing it's more involved than just reflashing the stock rom, perhaps I need radio files + others too
My phone is a Samsung s6 edge plus (SM-G928i).
Thank you all, and apologies if this is in the wrong place!
ReaperZ said:
Hi all, I've had quite a few issues with Viper4android, including extreme battery drain (since installing my phone will drain from 80% to 0% overnight with no use), and inconsistent volume in various apps (Spotify only has about 60% volume output with random bursts to 100%).
How can I remove all of its components and revert back to stock? I'm guessing it's more involved than just reflashing the stock rom, perhaps I need radio files + others too
My phone is a Samsung s6 edge plus (SM-G928i).
Thank you all, and apologies if this is in the wrong place!
Click to expand...
Click to collapse
Actually, its much easier than reflashing your ROM (though that would work fine too)
All you have to do is hit the menu button/3 dot icons>uninstall drivers>reboot. And you're done.
Freewander10 said:
Actually, its much easier than reflashing your ROM (though that would work fine too)
All you have to do is hit the menu button/3 dot icons>uninstall drivers>reboot. And you're done.
Click to expand...
Click to collapse
Thanks for the prompt reply! I'll give that a whirl
ReaperZ said:
Hi all, I've had quite a few issues with Viper4android, including extreme battery drain (since installing my phone will drain from 80% to 0% overnight with no use), and inconsistent volume in various apps (Spotify only has about 60% volume output with random bursts to 100%).
How can I remove all of its components and revert back to stock? I'm guessing it's more involved than just reflashing the stock rom, perhaps I need radio files + others too
My phone is a Samsung s6 edge plus (SM-G928i).
Thank you all, and apologies if this is in the wrong place!
Click to expand...
Click to collapse
This just removes the drivers, uninstalling the app after removing drivers and re-enabling your stock audio(if you had to remove/disable it), this should put you back to stock.
Freewander10 said:
Actually, its much easier than reflashing your ROM (though that would work fine too)
All you have to do is hit the menu button/3 dot icons>uninstall drivers>reboot. And you're done.
Click to expand...
Click to collapse
Sent from my SM-S903VL using Tapatalk
Droidriven said:
This just removes the drivers, uninstalling the app after removing drivers and re-enabling your stock audio(if you had to remove/disable it), this should put you back to stock.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Excuse my ignorance but could you tell me how to re-enable my stock audio? I get the feeling this was removed during the installation process
ReaperZ said:
Excuse my ignore but could you tell me how to re-enable my stock audio? I get the feeling this was removed during the installation process
Click to expand...
Click to collapse
By extracting a copy of the audioFX apk from your stock firmware
Or
By extracting it from a nandroid backup if you have one
Or
Find someone with your device and have them upload a copy of it.
Or
Find a copy with a Google search for:
"Audiofx.apk(or whatever the stock audio is called on your device) for (your model number and firmware version)
FYI, you would have had to manually remove or disable your stock audio yourself. It wouldn't have happened automatically, so if you yourself didn't remove/disable it then you probably don't have anything to worry about.
Sent from my SM-S903VL using Tapatalk
ReaperZ said:
Excuse my ignorance but could you tell me how to re-enable my stock audio? I get the feeling this was removed during the installation process
Click to expand...
Click to collapse
Did you flash V4A via recovery? Or did you install the app manually?
If you don't see the stock Equalizer in your app drawer then it was probably removed during installation of V4A (when done via recovery) but if it was installed manually then the equalizer app should still be installed/visible in your app drawer. All you have to do is open the app and toggle the on/off button.
If the app was removed though, you'll have to reflash your ROM to get it back.
NB 1. If stock EQ was already enabled, you might wanna disable it and give V4A another shot. As I've personally experienced issues with both of them enabled.
NB 2. Uninstalling the drivers practically kills the app. But you can go ahead and uninstall it as recommended by @Droidriven
Freewander10 said:
Did you flash V4A via recovery? Or did you install the app manually?
If you don't see the stock Equalizer in your app drawer then it was probably removed during installation of V4A (when done via recovery) but if it was installed manually then the equalizer app should still be installed/visible in your app drawer. All you have to do is open the app and toggle the on/off button.
If the app was removed though, you'll have to reflash your ROM to get it back.
NB 1. If stock EQ was already enabled, you might wanna disable it and give V4A another shot. As I've personally experienced issues with both of them enabled.
NB 2. Uninstalling the drivers practically kills the app. But you can go ahead and uninstall it as recommended by @Droidriven
Click to expand...
Click to collapse
I flashed a recovery file for it. So I might just take the easy route and reflash my rom I might give it another crack when I get my new phone in April / May!
Freewander10 said:
Did you flash V4A via recovery? Or did you install the app manually?
If you don't see the stock Equalizer in your app drawer then it was probably removed during installation of V4A (when done via recovery) but if it was installed manually then the equalizer app should still be installed/visible in your app drawer. All you have to do is open the app and toggle the on/off button.
If the app was removed though, you'll have to reflash your ROM to get it back.
NB 1. If stock EQ was already enabled, you might wanna disable it and give V4A another shot. As I've personally experienced issues with both of them enabled.
NB 2. Uninstalling the drivers practically kills the app. But you can go ahead and uninstall it as recommended by @Droidriven
Click to expand...
Click to collapse
Yep, my installations on all devices I've had have been via app which required me manually removing/disabling stock audio.
I've encountered installations on some devices that required using terminal emulator or adb shell to implement correctly, slightly tricky stuff that I don't remember the details for.
Sent from my SM-S903VL using Tapatalk
ReaperZ said:
I flashed a recovery file for it. So I might just take the easy route and reflash my rom I might give it another crack when I get my new phone in April / May!
Click to expand...
Click to collapse
I'm guessing your stock EQ was deleted then.
Just flash your ROM and you should be fine. Keep in mind though that any other additions/modifications you made to your system partition will be overwritten.
Uninstall Flashed App - Viper4Android
Hey folks,
I am new to xda and so this question might not be appropriate for this particular thread -- I don't know, I guess I'll take my chance. So, upon rooting my android device last week I went ahead and downloaded the Viper4Android audio enhancer as a zip, and installed it through the TWRP recovery terminal. This flashed the app on the phone drive. However, the Viper4Android driver is not installing properly and all my attempts to fix that are going in vain, thus I think the best solution is to uninstall the app and install a new package following a specific xda thread instructions to the letter. So my question is how do I uninstall a flashed app? I can't seem to find the app folder when the installation files are located. The app is present in my app menu. I am a root user and have directory apps like Root Explorer, Magisk Manager, BusyBox, RomToolbox etc. Btw, I've read most of this thread, and it mainly discusses the removal of the drivers. (Which I presume never installed in my phone anyways, as Viper4Android never worked -- hence why I am looking to uninstall the whole thing, and try anew). I have a Moto g5 plus.
How should I proceed? What's the best tool to uninstall a flashed Viper4Android App?
Any help would be much appreciated!
Thanks,
Sjbay93 said:
Hey folks,
I am new to xda and so this question might not be appropriate for this particular thread -- I don't know, I guess I'll take my chance. So, upon rooting my android device last week I went ahead and downloaded the Viper4Android audio enhancer as a zip, and installed it through the TWRP recovery terminal. This flashed the app on the phone drive. However, the Viper4Android driver is not installing properly and all my attempts to fix that are going in vain, thus I think the best solution is to uninstall the app and install a new package following a specific xda thread instructions to the letter. So my question is how do I uninstall a flashed app? I can't seem to find the app folder when the installation files are located. The app is present in my app menu. I am a root user and have directory apps like Root Explorer, Magisk Manager, BusyBox, RomToolbox etc. Btw, I've read most of this thread, and it mainly discusses the removal of the drivers. (Which I presume never installed in my phone anyways, as Viper4Android never worked -- hence why I am looking to uninstall the whole thing, and try anew). I have a Moto g5 plus.
How should I proceed? What's the best tool to uninstall a flashed Viper4Android App?
Any help would be much appreciated!
Thanks,
Click to expand...
Click to collapse
Did you solve it ?coz i have the same issue
I found a fix for a flashed Viper4Android
Just run the same package you used to install the V4A and it will remove it
Pretty simple.
hit the thanks button if I helped
MAST1999 said:
Just run the same package you used to install the V4A and it will remove it
Pretty simple.
hit the thanks button if I helped
Click to expand...
Click to collapse
Hi, this is my first xda post so there is no thanks button yet . But I'll go on ahead and say "Thank You". You solved my problem so easily.
Help!!!
Liens Sparks said:
Hi, this is my first xda post so there is no thanks button yet . But I'll go on ahead and say "Thank You". You solved my problem so easily.
Click to expand...
Click to collapse
Hello please what package did you install to remove the flashed viper android

Nope.

Nope.
^Preemptively answering all PMs.
This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol ?
Thanks for this. Can you tell me if the transcripts for screened calls are available with this?
mikkis2k said:
This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol
Click to expand...
Click to collapse
What are you asking for?
lollyjay said:
Thanks for this. Can you tell me if the transcripts for screened calls are available with this?
Click to expand...
Click to collapse
I'm not sure if call screen saves the transcript, but I've interacted with live transcriptions with multiple responses. You can see my screenshots in the other call screen thread.
TotallyAnxious said:
What are you asking for?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?
mikkis2k said:
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?
Click to expand...
Click to collapse
No idea. I'll maybe look into it. But it's not something that immediately hits me as "hey I can do that". I'm incredibly lazy and stoned a lot (stage 3 colon cancer survivor). So keep that in mind lol
Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Click to expand...
Click to collapse
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215
TotallyAnxious said:
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215
Click to expand...
Click to collapse
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Click to expand...
Click to collapse
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.
TotallyAnxious said:
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.
Click to expand...
Click to collapse
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Click to expand...
Click to collapse
You should follow the instructions. If it says install Google phone, you should do that. If it's already installed that means you should uninstall to install. And it's just a handful of shell script commands. It is NOT the issue.
I'm not trying to be difficult. But you've twice not followed the instructions. If you don't follow them. It won't work.
The instructions were set up specifically for this. The non-boot that is caused by Google phone being installed as a system app prior to being a user app. I have no idea why in hell that would cause a non-boot. But it does. As I said I am very lazy. I did everything I could to make this a one and done module. So I wouldn't have to provide much support.
Kirisakira companion is listed as feature but I actually rewrote it and that will probably be put into the original mod from freak07. It's just to emphasize not needing to install both.
I think it's ridiculous it requires instructions but it's the only consistent way I've found to get all the listed features working. Please please please ? ?? read them carefully and follow them. Meaning the below paragraph is the ridiculous part btw.
It makes no sense Google phone causes a non-boot when installed as system app first. Even in a module by itself. It causes that.
I spent a week figuring out the easiest way to do this. And I got it down to under 10 steps. Please follow them.
I even spent time leanring how the unity module template works ecause the companion module is unity. And I'm really lazy.
Simplified instructions
How to install (Magisk Manager or TWRP):
0. Uninstall Kirisakura kernel companion and Google Phone, if both/either are installed. Reboot if you uninstalled.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk inside the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
If you don't follow the instructions, you'll probably end up in a non-boot/bootloop.
@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Sent from my JiaYu S3 using XDA Labs
lollyjay said:
@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Click to expand...
Click to collapse
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.
TotallyAnxious said:
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.
Click to expand...
Click to collapse
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Sent from my JiaYu S3 using XDA Labs
lollyjay said:
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Click to expand...
Click to collapse
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works? Until it's posted here, people can click the link to see it.
https://forum.xda-developers.com/on...-nolimits-7-0-speed-ram-t3933927/post80645203
TotallyAnxious said:
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works?
Click to expand...
Click to collapse
Sure, np
Sent from my JiaYu S3 using XDA Labs
Hi, Ive just followed the instructions and got this working.. but i previously had the google phone installed as system app so went to my uninstaller and uninstalled 3 things, phone, phone .com and android.phone i think it was and now i have no mobile data.
Any idea what i install again to get this back? Thanks!

Categories

Resources