I figured out how to reliably/permanently enable the "Flip to Shhh" feature from the Pixel 3, it works fine on my Pixel 2 XL and I made a Magisk module out of it.
Credits also go to https://www.xda-developers.com/digital-wellbeing-flip-to-silence-google-pixel-2 for pointing out the feature is located in Digital Wellbeing.
Note: after installing this module, you need to go to Settings -> Apps and *uninstall* updates to Digital Wellbeing. That's needed because the app in /data/app overrides the one in /system that the module replaces.
View attachment shhh.zip
Thanks man, that is what i was searching for good job
Phoenix Wright said:
I figured out how to reliably/permanently enable the "Flip to Shhh" feature from the Pixel 3, it works fine on my Pixel 2 XL and I made a Magisk module out of it.
Credits also go to https://www.xda-developers.com/digital-wellbeing-flip-to-silence-google-pixel-2 for pointing out the feature is located in Digital Wellbeing.
Note: after installing this module, you need to go to Settings -> Apps and *uninstall* updates to Digital Wellbeing. That's needed because the app in /data/app overrides the one in /system that the module replaces.
Click to expand...
Click to collapse
Works perfectly. Thanks
So if I understand this correctly, we shouldn't update the app through the play store after installing the module?
AcidNoteZ said:
So if I understand this correctly, we shouldn't update the app through the play store after installing the module?
Click to expand...
Click to collapse
That's correct, I'll try to keep the modded app updated anyway.
AcidNoteZ said:
So if I understand this correctly, we shouldn't update the app through the play store after installing the module?
Click to expand...
Click to collapse
That's correct, I'll try to keep the modded app updated anyway
Hey,
I think this module doesn't work on Android Q. Can you update the same.
Thanks, I love you for this!
edit: Actually, didn't notice this is for Pixel 2 XL, I have the regular Pixel 2. When installing the module and uninstalling updates from Digital Wellbeing the app just disappears on me when I reboot.
edit 2: Appears the modded APK doesn't install on the regular Pixel 2. If you could be so kind to port this over to the Pixel 2 that would be awsome!
Easy solution https://forum.xda-developers.com/pixel-2-xl/themes/root-enable-call-screening-pixel-t3861350/page38
Look at Post #378 and follow the rest of the Thread for a easy install...
Miustone said:
Easy solution https://forum.xda-developers.com/pixel-2-xl/themes/root-enable-call-screening-pixel-t3861350/page38
Look at Post #378 and follow the rest of the Thread for a easy install...
Click to expand...
Click to collapse
This unfortunately caused my phone to boot loop.
Hadookie said:
This unfortunately caused my phone to boot loop.
Click to expand...
Click to collapse
Same here with the latest Pix3lfy Module. 2.9.1 was working fine... Don't have a Backup anymore
My Module enables the Flip function anyways...
Hadookie said:
Thanks, I love you for this!
edit: Actually, didn't notice this is for Pixel 2 XL, I have the regular Pixel 2. When installing the module and uninstalling updates from Digital Wellbeing the app just disappears on me when I reboot.
edit 2: Appears the modded APK doesn't install on the regular Pixel 2. If you could be so kind to port this over to the Pixel 2 that would be awsome!
Click to expand...
Click to collapse
That's really interesting, could you get digital wellbeing from the play store and post the latest apk here? I assume digital wellbeing isn't the same for all devices, as weird as that is...
(You're using Pie, right? I'd be surprised if this worked on Q)
Miustone said:
Same here with the latest Pix3lfy Module. 2.9.1 was working fine... Don't have a Backup anymore
My Module enables the Flip function anyways...
Click to expand...
Click to collapse
According to the devs on github Pix3lify doesn't actually enable it, it only enables the menu (by manually enabling the activity). The feature doesn't actually work if you try it. Sadly patching the apk or changing your device to the Pixel 3 in build.prop is necessary (the latter causes issues with the camera though, so I'd not advise to do it).
Phoenix Wright said:
According to the devs on github Pix3lify doesn't actually enable it, it only enables the menu (by manually enabling the activity). The feature doesn't actually work if you try it. Sadly patching the apk or changing your device to the Pixel 3 in build.prop is necessary (the latter causes issues with the camera though, so I'd not advise to do it).
Click to expand...
Click to collapse
I'm using it now and since almost 4 Weeks without Problems... Even Call Screening worked. Only Bug is the Portrait Mode in the Camera since WE don't have a Dual Camera on the Front (Compared the Media Profiles). Call Screening isn't included in my Patch since it really needs a Tricky way to enable it. Pix3lfy is focused on that and i don't want to Copy them...
Miustone said:
I'm using it now and since almost 4 Weeks without Problems... Even Call Screening worked. Only Bug is the Portrait Mode in the Camera since WE don't have a Dual Camera on the Front (Compared the Media Profiles). Call Screening isn't included in my Patch since it really needs a Tricky way to enable it. Pix3lfy is focused on that and i don't want to Copy them...
Click to expand...
Click to collapse
They change the build.prop to the Pixel 3 then I guess. This module avoids having to spoof the Pixel 3 and getting the issue you described, but it replaces the apk
Phoenix Wright said:
That's really interesting, could you get digital wellbeing from the play store and post the latest apk here? I assume digital wellbeing isn't the same for all devices, as weird as that is...
(You're using Pie, right? I'd be surprised if this worked on Q)
Click to expand...
Click to collapse
https://drive.google.com/file/d/1JFRzBO0CI-ty9zAlt3U1Ly9EtezKOS7L/view?usp=drivesdk
Yes, I'm on Pie. Thanks for looking into this.
Hadookie said:
https://drive.google.com/file/d/1JFRzBO0CI-ty9zAlt3U1Ly9EtezKOS7L/view?usp=drivesdk
Yes, I'm on Pie. Thanks for looking into this.
Click to expand...
Click to collapse
Hmm, it's indeed the same apk, are you using stock? Can you see if (without the module enabled) you see a /system/priv-app/WellbeingPrebuilt/WellbeingPrebuilt.apk?
Assuming those are both true, this might be an occurrence of this Magisk module corruption bug in case you aren't on 18.2 Canary: https://forum.xda-developers.com/ap...systemless-t3432382/post79077130#post79077130 (which would end up truncating the Wellbeing apk, making it invalid).
(To be sure, uninstall the module, update to 18.2 Canary, and reinstall it).
If this doesn't work, I can only think that for whatever reason your phone is verifying signatures of apks in the /system partition. This shouldn't happen and several other modules like YT Vanced exploit this (and I tested this mod to work without signature check patches), but in case the above fails, this module patches out signature checks:
https://cdn.discordapp.com/attachments/504024533125300224/538394292121763860/signaturepatches.zip (note: the module has to be uninstalled before any Android update and reinstalled after the update).
Phoenix Wright said:
Hmm, it's indeed the same apk, are you using stock? Can you see if (without the module enabled) you see a /system/priv-app/WellbeingPrebuilt/WellbeingPrebuilt.apk?
Assuming those are both true, this might be an occurrence of this Magisk module corruption bug in case you aren't on 18.2 Canary: https://forum.xda-developers.com/ap...systemless-t3432382/post79077130#post79077130 (which would end up truncating the Wellbeing apk, making it invalid).
(To be sure, uninstall the module, update to 18.2 Canary, and reinstall it).
If this doesn't work, I can only think that for whatever reason your phone is verifying signatures of apks in the /system partition. This shouldn't happen and several other modules like YT Vanced exploit this (and I tested this mod to work without signature check patches), but in case the above fails, this module patches out signature checks:
https://cdn.discordapp.com/attachments/504024533125300224/538394292121763860/signaturepatches.zip (note: the module has to be uninstalled before any Android update and reinstalled after the update).
Click to expand...
Click to collapse
Yes I'm on stock with a custom kernel. I'll try these instructions out in a sec.
Hadookie said:
Yes I'm on stock with a custom kernel. I'll try these instructions out in a sec.
Click to expand...
Click to collapse
Let me know when you do
Phoenix Wright said:
Let me know when you do
Click to expand...
Click to collapse
So I got your module to work on my Pixel 2. Seems like there was either a bug with Magisk + user error involved in me not getting it to work.
Hmm, it's indeed the same apk, are you using stock? Can you see if (without the module enabled) you see a /system/priv-app/WellbeingPrebuilt/WellbeingPrebuilt.apk?
Click to expand...
Click to collapse
I was able to find the directory you mentioned. Even when removing the module, installing canary, and rebooting I still couldn't get your module to work. After upgrading to canary and rebooting what appeared to be Wellbeing dependencies started to crash on start up. Very annoying. I also couldn't open Wellbeing as it seemed to have been corrupted. What I did to get your module to work was uninstalling Digital Wellbeing + manually deleting the /system/priv-app/WellbeingPrebuilt directory, rebooting, and then installing your module in Magisk Canary and then rebooting. Now I have flip to shhh on my Pixel 2.
What I do find weird is that the Play Store hasn't given me the option to update Wellbeing but that's OK with me. Only thing I need it for is flip to shhh.
Related
Hello all, I'm on D855,and after few attempts I managed to get Xposed working. I had issues with SDK 21 thing.
Now its working but can't se 'table thing' on there. It just says 'version 74 is active' with no possibility to press Install/Update. There is screen shot. Is this behavior normal for xposed, or I did something wrong?
Thanks.
Sorry, posted it here instead of general. And now don't know how to delete it...
Sorry.
-
mrpi64 said:
if you installed the xposed installer apk, then that's one step done. but, unless you haven't flashed the xposed SDK zip yet, you'll need to do that - it's the (or at least probably the easiest) way to install xposed. flash it with a custom recovery or whatever else you have, and after a reboot you should see that it tells you the SDK is installed, and from there you can browse and pick modules from the repo.
I'm not sure if that answers your question (was in a bit of a hurry so skimmed read it incorrectly so no, it doesn't answer the question ), but in general (at least for me), those buttons are blanked out, and I do everything by flashing.
Click to expand...
Click to collapse
Thanks.
Xosed works. Mods are working, I just needed to know is the installation ok, cause, it wouldn't be the first time for something working, but making phone slower due to bad installation.
Sent from my LG-D855 using Tapatalk
-
mrpi64 said:
the buttons on mine are the same as on yours - disabled. everything seems to be normal though, and I don't see anything going wrong, so I would *assume* it's fine.
---------- Post added at 09:47 AM ---------- Previous post was at 09:35 AM ----------
just to confirm, here's a screenshot of my device. maybe it's the device itself or something's been configured so that the xposed installer cannot modify the SDK installation. but, like I said, it's normal for me and even if it wasn't the most normal thing you can always perform the operations through recovery anyway
Click to expand...
Click to collapse
Thanks.
Than it's all good.
Now, can anyone tell me mod to disable nav bar on g3. I did that with gravity on Nexus, and can't find option on xposed. I can, but it remove them permanently.thanks
Live long and prosper.
-
mrpi64 said:
there is a G3 tweakbox here, not sure if it's what you're looking for but I hope this helps
Click to expand...
Click to collapse
Tweakbox doesn't seems to have that option. It have remove nav bar, and it disable bar permanently. Unless I'm missing something.
Live long and prosper.
-
mrpi64 said:
are you looking to temporarily or permanently remove it?
Click to expand...
Click to collapse
Well I would like something like extended display (it's called like that in CM I think) or PIE from Paranoid android.
So to have them, but hidden.
Stock option doesn't work as it keeps them on launcher and keyboard.
Live long and prosper.
-
mrpi64 said:
there are a few xposed modules (I think, at least one) which give you Pie/expanded desktop - would a module like GravityBox work?
Click to expand...
Click to collapse
Of course, but can't find mod like that for G3...
Live long and prosper.
-
mrpi64 said:
have you tried GravityBox? and I'm guessing you're running an AOSP stock ROM?
Click to expand...
Click to collapse
As I understand GravityBox is for Nexus. I'm on Cloudy for G3,and that is stock based custom rom.
Live long and prosper.
-
Hey guys, thought id create a thread for people to discuss any issues of tips for android pay UK as it was released on 18/05/2016.
I've managed to get it working - Rooted with latest chroma & systemless root!
Tested in a shop - works perfectly!
Method if ROOTED
1. Make sure you are on latest systemless root beta.
2. Uninstall any ad blocking software (adaway edits system)
3. Enter the following permission changes in ADB or using a root explorer.
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
4. Restart phone
5. You should now be able to add a card and then try it out in a shop. If not, try a clean install of your ROM and systemless root.
OPTIONAL - if you use adaway, there is a systemless version you can use so that it doesn't modify the system! Flash the "Systemless Hosts file" Zip in the link below PRIOR to adaway installation!
http://forum.xda-developers.com/showthread.php?t=2190753
Enjoy! =]
hltbest said:
Hey guys, thought id create a thread for people to discuss any issues of tips for android pay UK as it was released on 18/05/2016.
I've managed to get it working - Rooted with latest chroma & systemless root!
Tested in a shop - works perfectly!
Click to expand...
Click to collapse
May i Ask how?
I can second that - works like a charm!
I have Pure Nexus ROM installed.
Can download the app but get the message "Google is unable to verify that your device or the software running on it is Android compatible" when I try and add a card.
Android n v3 rooted and working good I think it's setup but not tested lol
Stretlow said:
May i Ask how?
Click to expand...
Click to collapse
Ive added the method to the 1st post so people can see how to do it!
Let me know if it works!
I flashed the latest N Dev preview then activated Pay but had a "can't verify your version of android" error message. Turns out I had changed the DPI on the last dev preview and after setting it to default Pay started working (at least I could now add a card). I'll test it actually works at a terminal today. Systemless root, adaway etc. As a matter of interest, I left a review on the Playstore (before changing the DPI) and Google answered within minutes asking me if I was rooted and/or on the preview. They also informed me they're actively working on allowing Pay to work on rooted devices.
*Edit* Yep, successful payment made today.
Nexus 6P
I'm on stock rooted systemless and latest AdAway installed no problem with Android pay.
Sent from my Nexus 6P using Tapatalk
AlmightyAl said:
I have Pure Nexus ROM installed.
Can download the app but get the message "Google is unable to verify that your device or the software running on it is Android compatible" when I try and add a card.
Click to expand...
Click to collapse
I suggest you wipe /system and install Pure Nexus again; this time don't use the newest provided GApps for that Rom, use the 2-3-16 GApps, or you can try Open GApps. Now flash the UnSu Update file, or whatever it's called to unroot Pure Nexus (Pure Nexus has /system root by default and will never work with Android Pay). After you've done that you can root with systemless root and AP should work. Check with the SafetyNet app from the Play Store to make sure it passes all the checks.
bouchigo said:
I suggest you wipe /system and install Pure Nexus again; this time don't use the newest provides GApps for that Rom, use the 2-3-16 GApps, or you can try Open GApps. Now flash the UnSu Update file, or whatever it's called to unroot Pure Nexus (Pure Nexus has /system root by default and will never work with Android Pay). After you've done that you can root with systemless root and AP should work. Check with the SafetyNet app from the Play Store to make sure it passes all the checks.
Click to expand...
Click to collapse
Yes. I did this and it works (not tried posting yet though!).
I wiped, reflashed, used April's gapps, followed all the other steps and hey presto! Thanks
Installed it the other day and used it for the first time today; feels pretty magical!
I'm not able to add any more cards at this point though even though my bank supports Android Pay. I keep getting a super vague and unhelpful "Request Failed" error message. My bank tells me it's Google's fault, and Google seems to be clueless about it. Anyone have any more information on this error?
AlmightyAl said:
Yes. I did this and it works (not tried posting yet though!).
I wiped, reflashed, used April's gapps, followed all the other steps and hey presto! Thanks
Click to expand...
Click to collapse
Works perfectly. Paid for my Friday night beers. Woohoo!
Where can I find systemless root for Preview 3 ?
Android Pay has been pretty ropey in my experience, been very slow to make payment, can take a good 4-5secs to get locked-on when it works, which it doesn't always. For the last couple of days I've only used it on the Underground when I know both entry and exit wouldn't be busy, basically not at rush hour.
I've tried all different approaches... top of phone, middle and bottom. Nothing seems to improve the speed of payment. Any tips on how I could improve performance?
Ta.
jodvova said:
Where can I find systemless root for Preview 3 ?
Click to expand...
Click to collapse
Your need modified boot then twrp and then flash SuperSU 2.72 or above
Just used android pay for the first time in Aldi. Worked very well, was really impressed!! Currently running the android N preview 3.
Sent from my Nexus 6P using XDA-Developers mobile app
highburybloke said:
Android Pay has been pretty ropey in my experience, been very slow to make payment, can take a good 4-5secs to get locked-on when it works, which it doesn't always. For the last couple of days I've only used it on the Underground when I know both entry and exit wouldn't be busy, basically not at rush hour.
I've tried all different approaches... top of phone, middle and bottom. Nothing seems to improve the speed of payment. Any tips on how I could improve performance?
Ta.
Click to expand...
Click to collapse
The NFC chip on the 6P is inside the glass visor. Make sure you touch any payment platform with that.
By the way, if the SafetyNet app says it passed the checks, can I use Android Pay without problem? I'm rooted with systemless root and have Adaway without any zips. However, in the Adaway settings I use the data/data/hosts target. Safety Net passes. I don't have a card that can be used with Android Pay right now, but it should be coming next week.
Sent from my Nexus 6P using Tapatalk
sherlock5545 said:
The NFC chip on the 6P is inside the glass visor. Make sure you touch any payment platform with that.
By the way, if the SafetyNet app says it passed the checks, can I use Android Pay without problem? I'm rooted with systemless root and have Adaway without any zips. However, in the Adaway settings I use the data/data/hosts target. Safety Net passes. I don't have a card that can be used with Android Pay right now, but it should be coming next week.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just an FYI
There is a zip you can flash prior to installing Adaway that makes AP and Adaway play nice together
https://www.androidfilehost.com/?fid=24438995911977059
From the OP in the Adaway thread
Yesterday I tried n preview 3 for the first time and I must say that I'm impressed. Installed android pay with no problems at all. The only thing that seems a little annoying is that I was endeavouring to make twrp work, which I couldn't, and when it hung and I had to reinstall n3, I found I was required to phone the bank again to reactivate the card.
jodvova said:
Where can I find systemless root for Preview 3 ?
Click to expand...
Click to collapse
Just look for SuperSU 2.74 beta. That's working fine for me!
sherlock5545 said:
The NFC chip on the 6P is inside the glass visor. Make sure you touch any payment platform with that.
By the way, if the SafetyNet app says it passed the checks, can I use Android Pay without problem? I'm rooted with systemless root and have Adaway without any zips. However, in the Adaway settings I use the data/data/hosts target. Safety Net passes. I don't have a card that can be used with Android Pay right now, but it should be coming next week.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I used Android Pay yesterday, systemless rooted and Adaway installed v3.1.1(56)
A few days ago, there was an update from zhuhang for the already released Viper4Android 2.5.0.5. It addresses the issues that a lot of people are having with getting V4A working under Nougat. I tested it with my ROM, and the driver installed without error. So then I decided to make a flashable zip that would preinstall the driver and save you a few minutes plus a reboot. Other than possibly needing to grant Storage permissions in Settings, this is a quick flash and go.
The zip that should work on any LG-based ROM, and possibly on AOSP-based as well. Just download, flash in TWRP, and reboot. You may need to grant Storage permissions in Settings.
XDA Thread:
https://forum.xda-developers.com/showthread.php?t=2191223
V4A Blog Site:
http://vipersaudio.com/blog/?page_id=31
I [obviously] didn't create V4A, but if you include my zip in your ROM, please give a mention and link back to this thread.
First
Thanks for this.. I'm sure many will get use out of it..!
Not sure if I did something wrong or not - but I can't get it to work.
I'm on DevDigital's ls997 ver 6.5 magisk phh.
Flashed in twrp. Granted root permision.
go to SuperSU / un-check Mount_name spaces separately / under the settings. turn on adb debugging.
Inscribed via LG v20 (iOS 11.1.0 Aplha)
midmadn said:
Not sure if I did something wrong or not - but I can't get it to work.
I'm on DevDigital's ls997 ver 6.5 magisk phh.
Flashed in twrp. Granted root permision.
Click to expand...
Click to collapse
You shouldn't have been promoted to grant root access. V4A only needs root to install the driver, which is preinstalled.
If you're being prompted to install a driver, the ROM likely uses a different conf file to control audio.
Sent from my iPhone 7 Plus using Tapatalk
He built and ported to magisk recently. Has a module you need to install then install Swansong
I haven't played with it yet. I like the new app but dont see a diffence in drivers from 2.5.0.4 to 2.5.0.5
Magisk has a compatible module in his downloads via the app that works with my rom (2.5.0.4)
I install that via magisk manager then i pulled the latest viper4arise.apk and installed instead of the older ui viperfx apk that is linked on the downloads page inside magisk manager.
Driver installs correctly for many others as well. You may need to dirtyflash my rom and start over. Magisk manager also received a update yesterday via playstore. The process on phh or magisksu as its now called is different now as its "systemless" vs modifying the actual system files.
If you dont want to go 5through the hassel of above. Just go to developer settings inside of the viper apps settings and turn off selinux and recheck driver status. Im 99% sure it works this way but ive said it before, i wont push the rom this route as i dont perfer it to be off by defualt.
Hope this helps
Got it all worked out thanks to the rom creator above. Team DevDigitel.
Thank You
Thank you for your work on this flashable zip it's much appreciated, I just have a couple of questions though for anyone who might know..
I'm still running the original stock rom (rooted with TWRP) on my LG V20 and a while back I followed the directions from another thread to install V4A, and I was able to get it to work (even through bluetooth) but it's kind of wonky and just hit or miss so I'd really like to try this one out instead.
I'm assuming I should uninstall the version of V4A I have right now but is there anything else that I need to do (besides a nand backup) before flashing this one? Also one of the steps to install the V4A I have right now was deleting a system file (I'll have to go look to be sure but I believe it was something like mixer_paths.xml), so I just thought I'd check to see if that will somehow effect this version or if I possibly need to put the original file back where it was before flashing this one?
I apologize if these are stupid questions but I just thought play it safe and check first before giving this a shot, because even though the version I have is kind of wonky it still works through bluetooth which from what I've read is something that a lot of people haven't been able to get working, and since I use it so much I'm just afraid to even risk losing it. Anyway I'll definitely create a backup before doing anything but any help or suggestions would be appreciated. Thanks!
Sent from a ridiculously modified ColecoVision
jeep447 said:
Thank you for your work on this flashable zip it's much appreciated, I just have a couple of questions though for anyone who might know..
I'm still running the original stock rom (rooted with TWRP) on my LG V20 and a while back I followed the directions from another thread to install V4A, and I was able to get it to work (even through bluetooth) but it's kind of wonky and just hit or miss so I'd really like to try this one out instead.
I'm assuming I should uninstall the version of V4A I have right now but is there anything else that I need to do (besides a nand backup) before flashing this one? Also one of the steps to install the V4A I have right now was deleting a system file (I'll have to go look to be sure but I believe it was something like mixer_paths.xml), so I just thought I'd check to see if that will somehow effect this version or if I possibly need to put the original file back where it was before flashing this one?
I apologize if these are stupid questions but I just thought play it safe and check first before giving this a shot, because even though the version I have is kind of wonky it still works through bluetooth which from what I've read is something that a lot of people haven't been able to get working, and since I use it so much I'm just afraid to even risk losing it. Anyway I'll definitely create a backup before doing anything but any help or suggestions would be appreciated. Thanks!
Sent from a ridiculously modified ColecoVision
Click to expand...
Click to collapse
You don't need to delete any files for this zip. You're supposed to delete /system/etc/audioeffects.conf, but I've done that with the script.
As I use this more, Bluetooth still occasionally doesn't process after pausing for an extended period, like getting out of the car for more than 5 minutes, but all you need to do for it to kick back on is exit V4A from the menu, then open it up again. It'll immediately start processing again.
If you have an unmodified system backup to restore, that will help ensure it works OK, but it may not be needed.
Sent from my iPhone 7 Plus using Tapatalk
NotATreoFan said:
You don't need to delete any files for this zip. You're supposed to delete /system/etc/audioeffects.conf, but I've done that with the script.
As I use this more, Bluetooth still occasionally doesn't process after pausing for an extended period, like getting out of the car for more than 5 minutes, but all you need to do for it to kick back on is exit V4A from the menu, then open it up again. It'll immediately start processing again.
If you have an unmodified system backup to restore, that will help ensure it works OK, but it may not be needed.
Sent from my iPhone 7 Plus using Tapatalk
Click to expand...
Click to collapse
Thank you for the quick response and for the info and I have no clue why I had mixer_paths on the brain but yeah audioeffects.conf is the file I had to delete while installing the version I have, and as far as what you said about the bluetooth acting up it sounds pretty similar to the wonkyness that I was describing with the version I currently have.
One weird thing that I've noticed with mine (and I don't have the slightest idea how or why it's doing it) is when I'm listening to music through my bluetooth headset, none of the settings under the "Bluetooth" section in V4A have any effect on the sound whatsoever.. but what's weird is that all of the settings under the "Headphones" section do (so it's basically like the section names were swapped somehow)?!
I know for sure that I don't have anything plugged into the jack and the headset I'm using is definitely bluetooth (because it's pretty easy to tell lol), so I have no clue why the settings under headphones would work just fine while the ones under bluetooth don't do it anything at all?
Anyway thank you again for the info I'll give it a shot as soon as I have time and let ya know how it went, and unfortunately the only thing I didn't backup was my unmodified system (it didn't even cross my mind until after I was done rooting) but hopefully it'll still be ok. Thanks again!
Sent from a ridiculously modified ColecoVision
jeep447 said:
Thank you for the quick response and for the info and I have no clue why I had mixer_paths on the brain but yeah audioeffects.conf is the file I had to delete while installing the version I have, and as far as what you said about the bluetooth acting up it sounds pretty similar to the wonkyness that I was describing with the version I currently have.
One weird thing that I've noticed with mine (and I don't have the slightest idea how or why it's doing it) is when I'm listening to music through my bluetooth headset, none of the settings under the "Bluetooth" section in V4A have any effect on the sound whatsoever.. but what's weird is that all of the settings under the "Headphones" section do (so it's basically like the section names were swapped somehow)?!
I know for sure that I don't have anything plugged into the jack and the headset I'm using is definitely bluetooth (because it's pretty easy to tell lol), so I have no clue why the settings under headphones would work just fine while the ones under bluetooth don't do it anything at all?
Anyway thank you again for the info I'll give it a shot as soon as I have time and let ya know how it went, and unfortunately the only thing I didn't backup was my unmodified system (it didn't even cross my mind until after I was done rooting) but hopefully it'll still be ok. Thanks again!
Sent from a ridiculously modified ColecoVision
Click to expand...
Click to collapse
You can definitely control BT devices from the BT tab on this one. And I've found with more testing that before I get in my car, switch to V4A and exit it, then open it again as soon as Play Music connects. Works every time.
I would just like to say thank you!!
I installed this .zip on my T-mo variant over the previous V4A install via dirty flash. It resolved my Bluetooth processing issues on the stock V20 ROM. I've been working on this the past few days. VERY happy it now works in my car like my last phone did!
Now, once I get the nerve to flash over the new modem and bootloader via TWRP to get up to 20j, I'm highly inclined to check out the new ROM by NATF.
Cheers!
joesee said:
I would just like to say thank you!!
I installed this .zip on my T-mo variant over the previous V4A install via dirty flash. It resolved my Bluetooth processing issues on the stock V20 ROM. I've been working on this the past few days. VERY happy it now works in my car like my last phone did!
Now, once I get the nerve to flash over the new modem and bootloader via TWRP to get up to 20j, I'm highly inclined to check out the new ROM by NATF.
Cheers!
Click to expand...
Click to collapse
Thank you.
The new modem and other firmware is not a strict requirement for ROMs built on 10j. You just need to make sure TWRP is on the latest release.
NotATreoFan said:
A few days ago, there was an update from zhuhang for the already released Viper4Android 2.5.0.5. It addresses the issues that a lot of people are having with getting V4A working under Nougat. I tested it with my ROM, and the driver installed without error. So then I decided to make a flashable zip that would preinstall the driver and save you a few minutes plus a reboot. Other than possibly needing to grant Storage permissions in Settings, this is a quick flash and go.
The zip that should work on any LG-based ROM, and possibly on AOSP-based as well. Just download, flash in TWRP, and reboot. You may need to grant Storage permissions in Settings.
XDA Thread:
https://forum.xda-developers.com/showthread.php?t=2191223
V4A Blog Site:
http://vipersaudio.com/blog/?page_id=31
I [obviously] didn't create V4A, but if you include my zip in your ROM, please give a mention and link back to this thread.
Click to expand...
Click to collapse
Out of desperation I tried this on my nexus 6 running 7.1.2, works perfect so far, appreciate you work on this.
Sent from my Nexus 6 using Tapatalk
9wire said:
Out of desperation I tried this on my nexus 6 running 7.1.2, works perfect so far, appreciate you work on this.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Excellent! I'm glad it works for you. The changes made should work on multiple devices, I just couldn't test it myself.
Can we flash this if we have dolby? Or should I uninstall dolby 1st?
Still_living714 said:
Can we flash this if we have dolby? Or should I uninstall dolby 1st?
Click to expand...
Click to collapse
They can co-exist.
Sent from my iPhone 7 Plus using Tapatalk
Thanks!
Just wanted to say thanks for this. It worked great right from the get go. If anybody is wondering its running on JDCTeam AOSP 7.1.2 on a beat up old S4.
NotATreoFan said:
A few days ago, there was an update from zhuhang for the already released Viper4Android 2.5.0.5. It addresses the issues that a lot of people are having with getting V4A working under Nougat. I tested it with my ROM, and the driver installed without error. So then I decided to make a flashable zip that would preinstall the driver and save you a few minutes plus a reboot. Other than possibly needing to grant Storage permissions in Settings, this is a quick flash and go.
The zip that should work on any LG-based ROM, and possibly on AOSP-based as well. Just download, flash in TWRP, and reboot. You may need to grant Storage permissions in Settings.
XDA Thread:
https://forum.xda-developers.com/showthread.php?t=2191223
V4A Blog Site:
http://vipersaudio.com/blog/?page_id=31
I [obviously] didn't create V4A, but if you include my zip in your ROM, please give a mention and link back to this thread.
Click to expand...
Click to collapse
always a true hero. hope all is well with you and yours.
Works perfect on Desolation Rom . Just flash and reboot and approve with SuperSU and Awesomeness !
Sent from my LG-LS997 using XDA-Developers Legacy app
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question.
Instead this thread is intended to share experiences as I spend quit some days to become my phone as free from Google.
I did this on a Galaxy A3 (2017) with LOS.
First of course is not to install Gapps. We can replace many of its functionality. First of all we need a store to download apps. I highly recommend FDroid as a first choise. You can download the app at their website.
With this you get a variety of apps for almost all, but not all problems. Nevertheless I recommend to take your time and check what is offered there, even if you used other apps before.
If you don't find an equivalent, you might want access the google playstore. In FDroid there are two apps available for this purpose. With both you can anonymously access all (not payed) apps on Playstore. You can of course login with your google accound, but ... ok, that's not so anonymous anymore
What else do we miss without Gapps. There is a way of receiving push notifications, that is often handled via GCM (google cloud messanging).
First of all we need to enable spoofing. This was quite a challange, as usual tools (tingle, ...) work with non-odexed ROMS, while that for A3 is an odexed ROM.
Finally I found a zip here, that works for me:
https://forum.xda-developers.com/showpost.php?p=77456471&postcount=3775
Download that zip, goto TWRP.
Before installing it you have to do two steps.
Mount /system
Create a link (with advanced/terminal): ln -s /system/vendor /vendor
Otherwise install of this zip will fails. Be patient, it takes around 5..10min to pass.
Now we can work with microG, that will replace some google-APIs.
Add the repo "microg.org/fdroid/repo"
Then install micoG core, fakestore and proxy.
To get unifiedNLP running (this is for location services) the microG core must be a system app.
So do a reboot in the TWRP. Mount system first.
Than copy with integrated filemanager the folder com.google.android.gms-xxxx
from /data/app/
to
/system/priv-app
and reboot.
You will find in your app-overview the microG app - please open and let selftest run.
Enable permissions there and also disable battery optimisation
unifiedNlp should be registered. Next is to enable them.
Download from FDroid these two apps:
Local GSM Location (with this you can download a database of cell towers and their location, giving you a chance to get a rough estaimatin where you are, without waste of energy for GPS)
and
NominatimNlpBackend (to get your position as street/city/country instead of coordinates).
Very important:
Apps that require this gapps need to be installed after microG. Otherwise they will not work properly.
I guess that are usually apps that needs location.
Feedback for microG installation
I´ve tested your microG installation these days. Worked like a charm ! Thanks for your post.
The Nanodroid patcher referred in your link was gone, so i used http://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-18.1.20180909.zip.
I had the same problems with Yalp downloads you´ve described earlier, after reboot it worked.
GCM works, but just not with Threema ;-( But it´s a known problem.
Getting NLP to work was a little bit of hassle, but I found many articles about it. Was not sure which of the backends to use, there are many.
What is interesting - I didn´t use encryption and patched the ashyx_no_encryption patch right after flashing LOS and I didn´t use SU or Magisk right now. Result: absolutely no boot loops and no reboot after power off !
From which stock variant you came ?
@cyberbix:
The patcher for spoofing was quite beta at that time. Did you have to do any preparations to let it run? I remember in TWRP I had to mount /system and create that /vendor-link. Is it still required? I reported my issued there but I am not sure he cooked it with these patches finally.
The Yalp issue is completely independent on microG. It seems that there is a bug in the Downloader of LOS15.1. There are others suffered from this issue, not just the A320FL. The workaround to use internal download works.
Can you give more details about the NLP-hassle? That might help others to not go that painful way. Imho all is fine if you copy (or move) the folder I described above and reboot.
About the backends ... I think there is no alternative for Nominatim, which works only online. For the cell bases location I prefer a offline solution, I found that "Local GSM Location". The microG-Packages usually contain the mozilla-online backend.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I had latest Oreo 8.0 installed before. But I am not sure whether or not I updated the bootloader too with Odin.
@starbright_
Did you have to do any preparations to let it run?
Yes. I did exactly the same as you did in TWRP.
Can you give more details about the NLP-hassle?
I wasn´t sure if its needed at all and even if microG went green, the backends seemed not wo work at all.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I did it in the same way as you. Flashed the patcher, installed the rest from FDroid. That´s it.
Moreover: i didn´t install Magisk or any other root and I didn´t use Xposed. I used the push notification tester to test GCM. Everything was fine.
I can check if installing an su package or Magisk will lead into the same problems.
Installed Magisk on top of your microG setup. Everything works, see McFys thread. I guess you just didn´t read what TB tells about SU.
starbright_ said:
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question..
Click to expand...
Click to collapse
My experience below:
-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green
-yalp works fine, i like it, but in the end i had to use my goggole account instread of the experimental 'internal account' and this because of gmaps
-gmaps works fine BUT it doesn't find the current gps position unless i restart it (long press on back arrow). This is odd because other map-apps (openstreet, tomtom..) work! Also, when i need to use the google account to save some locations or simply the offline maps, it does work only for the first time, later it doesn't recognize my (already set) googke account
-i don't know if it's related to microg but camera doesnt find the gps, while opencamera yes, fotej camera neither
-again, i don't know if it's related to microg but each time i add the google account i loose my contact list
-apps that need to talk with playstore doesn't work at all, I wanted to use Europe3D by geoflier and it didn't load properly until i installed also the playstore
- the same for those apps that need to purchase some addons
-BUT worst, above all (crying) is that the speechTotext is not wotking and it's a feature I really miss!
I don't know if a proper patched rom would work better, I always hope that mcFy finds some time to release the rom already patched.
Anyhow next days I will try to reinstall the stock rom to see if these behavioours happen also there.
I did another installation again. More details next.
But finally I gave up. I couldn't solve two issues
- neither telegram nor whatsapp works after a few minutes (doesn't wake up at incoming calls)
- heavy instabilities with LOS15.1/Magisk/Xposed/microG
I didn't find which component is responsible for that, but I remember that I didn't always get SU with Magisk. After a reboot it works again.
Even such components as DuckDuckbrowser crashed.
I couldn't recover my apps backup by TB from my previous S5mini on A3 with TB and Magisk (Parser error).
I need a rest from all this stuff.
starbright_ said:
I
I need a rest from all this stuff.
Click to expand...
Click to collapse
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
pink0 said:
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
Click to expand...
Click to collapse
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means this.
I installed localGSMbackend which created an offline database with celltowers. This works fine in energy saving mode I get a rough position without any waste of energy or privacy (as offline).
Altogether I did at least 20 complete wipes and started from scratch.
At the first I started early with root (either Magisk or LOS-addsu).
Than there are two options to get a spoofed ROM.
Either via Xposed/Fakestore module or via nanodroid patcher.
Both works in general.
Than installed microG (different ways - manually, nanodroid, unofficial installer, that are the 3 options I know).
But it always become instable. Apps don't get root anymore or does FC ....
So I did it another way around.
I first installed all required via FDroid (without any root, Xposed ...). That seems to me rather stable. The good thing: this are around 80% or apps I need. Than I did a backup, so that I don't have to starts from scratch, which is painful as hell with around 40 .. 60 apps.
My last attempt was after that install Magisk, Xposed, Fakestore. Spoofingchecker was red, but a microG gets green.
I installed it with nanodroid (created first with setup wizard a file, so that only microG and mapsapiv1) gets installed.
This was first time my apps work fine with maps. Other attempts to manually install the maps framework/lib wasn't succesful (why ever).
Problems started when installing TB. First it doesn't get root permission. After a restart it works, but I get parsing errors. If I understand FAQ this is due to different busyboxes ?!? Ok, the backups I created at another device with LOS14.1 and addsu.
But this was not the only issue. Browser crashed and I never get neither Telegram nor Whatsapp to get wake up after a few minutes of deep sleep (they arn't get registered at microG too, so this might be another issue).
@pink0:
Did I understand it right, you use GMaps?
@cyberbix:
My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Does your system keeps stable after all?
To be honest, that Magisk and Xposed seems to add to much intrusive stuff that might fail altogether. But even with the manual way it wasn't perfect. Maybe after a rest and with the next version from McFy I try this again. Good luck I didn't sell my old S5min til now.
starbright_ said:
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means
@pink0:
Did I understand it right, you use GMaps?.
Click to expand...
Click to collapse
it's here i writed down because my personal memory buffer, at my age, is really small
yes gmaps is working quite good except the behavour I wrote, but enabling developer options I can easily kill the program to get the new/current position (also I noriced tgat because of this gps problem ir cannot calculate any route while navigating)
I also dislike the idea of using xposed bexause I never needed it but now it's different
about telegram/whatsup i'm not using such softwae so I can't say what's wrong
starbright_ said:
...My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Click to expand...
Click to collapse
I do not use WhatsApp, I use Threema and Threema has known problems with microG GCM.
starbright_ said:
Does your system keeps stable after all?
Click to expand...
Click to collapse
Yes, but I didn´t flash Xposed, just Magisk.
Ok.That spoofing can happen via Xposed Module or nanodroid patcher. For non-odexed ROMs are more options (tingle,...) but not for ours.
So after all I am now happy with my current installation:
- install TWRP via ODIN
- Wipe in TWRP (system, data, cache, dalvik)
- install Lineage via TWRP
- boot into system
- install FDroid
install and setup most of needed apps - there is a good selection of apps in FDroid now
- Create Backup (via TWRP)
- Install Magisk (viaTWRP) and Magisk Manager in LOS
- Setup adaware and afwall (both from FDroid as they need root)
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
- install Yalp from FDroid and via Yalp the missing apps that are not available via FDroid.
I found that Telegram (and Whatsapp not 100% sure yet) push-notification work. I disabled battery optimization for both.
starbright_ said:
So after all I am now happy with my current installation:
[...snip..]
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
Click to expand...
Click to collapse
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
pink0 said:
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
Click to expand...
Click to collapse
I am not sure, but the LOS15.1 for A3 2017 (by @McFy from 08/21) ROM is in a state you need the patcher. Other methods (as tingle - what I used before with other mobiles) don't work.
Not sure what is odexed and deodexed. The only other method works for spoofing is Xposed framework. There is a module that fakes this. But until now I did't see a need for Xposed and I don't want to increase complexity. (From that point of view I rather should go for addsu instead of Magisk)
I did first a Magisk installation, as root is more important and you have later the chance to chose between microG and Gapps. (Did it step by step with backups not to start again from scratch).
But I didn't use Magisk for installation, but TWRP. How does it works? I am a Magisk newbee.
An update of LOS15 requires to redo it. I also updated microG in this sequence. Just as a short summery:
- boot into TWRP
- wipes system/cache/dalvik
- installed new LOS
- installed Magisk
- reboot into system (just for curiosity, probably not required) and back to TWRP
- let run uninstaller of microG (I used the zips from here: https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- install (run) the patcher (be patients, that takes long time, maybe 15min)
- install (run) setup wizard (selected only few things, as maps-api, can remember exactly)
- install the real package (install what has been selected in setup).
check this out https://hackernoon.com/e-first-beta-soon-to-be-released-82d7ec950dd
basically, this is a LOS-based rom including microG, aiming at avoiding google applications/usage.
or https://download.lineage.microg.org/a5y17lte/
Nominatim backend
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
cyberbix said:
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
Click to expand...
Click to collapse
My selfcheck gives just 2 unchecked points:
Playstore signature (I installed Fakestore+Yalp and Fdroid)
Radiocell based location (altough Nominatem is setup).
"Playstore signature" I could manage after apply permission spoofing to Fake Store (system app).
But, I don't get any app registered, although I have enabled Google registration and GCM.
I even deinstalled ebay and installed it again - no effect. ?!? What can I do?
I remember @cyberbix mentioned the Push notification tester:
It fails for me with step1 - "No register" ?!? How can that be? What did I miss.
[/COLOR]
starbright_ said:
?!? How can that be? What did I miss.
Click to expand...
Click to collapse
Did you do the device check-in ?
See https://f-droid.org/en/packages/com.thermatk.android.xf.fakegapps/
What is push notifcation exactly claiming ? Unable to register or missing Play services ?
Is there anything I can do about this?
Did you try this:
https://forum.xda-developers.com/apps/magisk/fix-magisk-manager-20-3-ctsprofile-t4080921
- Before starting the steps, uninstall all Magisk modules and reboot.
- If your device is not listed in the Props Config, you can try Google Pixel 2 or 3 and Android 10.
- Don't forget to hide Magisk in the Options and Google Play Services, Google Play Store, Google Pay and all banking/game apps in the Magisk Hide menu.
- You should know that all Samsung services (Pay, Pass, Secure Folder, etc.) related to KNOX will never work after rooting (= KNOX tripped)...
LeGi0NeeR said:
Did you try this:
https://forum.xda-developers.com/apps/magisk/fix-magisk-manager-20-3-ctsprofile-t4080921
- Before starting the steps, uninstall all Magisk modules and reboot.
- If your device is not listed in the Props Config, you can try Google Pixel 2 or 3 and Android 10.
- Don't forget to hide Magisk in the Options and Google Play Services, Google Play Store, Google Pay and all banking/game apps in the Magisk Hide menu.
- You should know that all Samsung services (Pay, Pass, Secure Folder, etc.) related to KNOX will never work after rooting (= KNOX tripped)...
Click to expand...
Click to collapse
@jhill110 sorry for necroposting this, but does it work out for you?
Arobase40 said:
SafetyNet fix !
Quicker and easier SafetyNet fix :
Erase the cache from Magisk and flash one of these two fixes :
I used the first one and it works so I didn't test the second...
At least Secure Folder is working fine. Knox deployment is behaving weirdly as it is asking a two pass authentication and it is asking a numerical code when I receive an alphanumerical code... ^^
I don't use Samsung Pay (should at least work with Android Pay but I didn't test it) and I don't use Samsung Pass either but I don't think there should be a real problem as it was asking me to set it up but I removed totally from the system...
Click to expand...
Click to collapse
actually for me safety net fix only works for android 11 version rom of this device, and even then secure folder doesnt work correctly (for me?), it doesnt save the password, and keep poping up asking to set a password whenever I tried to enter it. The device itself become unstable and keep hot rebooting after every unlock, eventually get thermal throttled for no reason. Though the safety net solution I used was this one: kdrag0n/safetynet-fix , and prob not the one you listed actually its the same developer, though his repository does not contain a v2 release. I still gona try it though
edit: working now, not hot rebooting (yet), but secure folder still doesnt save password, thus cant still be used yet
Arobase40 said:
So make sure you pass the SafetyNet test in Magisk. When done and passed, uninstall completely and properly Secure folder from your settings, and reboot.
Click to expand...
Click to collapse
the safetynet fix worked on my device when the rom is still on android 10. That is to say, it passed the safetynet test. It was extremely unstable though, hot rebooting after every unlock (unlock, black screen samsung, then back to lock screen) I couldn't get into magisk and disable it, had to delete it through twrp. It was until android 11 that I tried it again. not extremely unstable, just "useable unstable". That was the release file on kdrag0n's repository. Your uploaded v2 file works amazingly. Thanks for sharing:>
Arobase40 said:
I wonder why you mention Android 10 when we're with Android 11 for a long time now...
So is your issue totally fixed with no instability at all anymore and is Secure Folder working also ?
Click to expand...
Click to collapse
I just want to share my experience about the same device with (prob) the same safety net fix that works on yours, but not my device.
yes, with your safety net fix my tab runs absolutely stable, and I've just tried uninstall secure folder and reinstall it again. Its working perfectly now