Related
A malware in form of many apps have been identified lurking in android market. A patch is available for existing users and ROM cooks. More details here
http://forum.xda-developers.com/showthread.php?t=977154
Sent from my LG-P500 using XDA App
but if the exploit is based on rageagainstthecage method why it works on android 2.2.1 or 2.2.2?
I'm not sure. I've read around other forums and some have tried and gotten success with RATC using their PC. I'm not sure if 2.2.1 and 2.2.2 only breaks S1C and Z4
I'll rather be safe than sorry
If the exploit roots the phone and does bad stuff, what if the phone has already been rooted? Will superuser still prompt us that the specific program is trying to gain root access? I'll try installing a "bad app" that was listed on the thread link you gave xD
that was good... if you can find affected apps... it was completely removed from the market the 2nd day of its release.
i sure do want to try this too... just to test the waters
i guess a complete flash will kill the malware on the other hand *lol*
i thought 2.2.2 was created just to implement this patch?
well thats what wikipedia told me
*******MAY 2016 UPDATE
Android Pay is working on the PureNexus May 2016 layers build
To attain this, delete the following files
com.google.android.camera2.xml
Located in system/etc/permissions
And
com.google.android.camera2.jar
Located in system/framework
*******BEGIN PRELIMINARY NOTES*******
-->To go from system root to systemless root,
please use the SuperSU Uninstaller zip linked below and not the unroot feature built into the SuperSU app
-->To fully unroot if on systemless root or system root, use the unroot feature in the apk
*******END PRELIMINARY NOTES*******
If, like me, you've become increasingly desirous of having Android Pay functioning on your rooted device, yet preserving that which you love about your custom setup (see thread title), this thread attempts to provide the resources you need to attain your objective.
For me, I believe that the tipping point came as a matter of principle...I wanted a feature from which I'll likely derive zero utility.
Let me be clear: I see no use whatsoever for Android Pay, and yet, like most Americans, I absolutely must have it.
I found myself returning to the same excuse, "I have a debit card, why do I even want this goofy feature?" That's a good question, but the answer is equally obvious...because it exists.
And I'd see yet another user getting the bloody thing to work on a rooted, custom rom. I hope you can see the urgency.
Just like the one ring to rule them all, the lure of Android Pay is really due to its power that it holds over us...
We Wants It...Stupid HOBBITSES
Many users have grown weary of wading through...
-->Disparate posts within rom threads
-->Dedicated threads for various elements of in the title of this thread, now scattered across xda like the diaspora of a lost tribe (how many Viper4android threads are there?)
-->Posts cross-linked within other threads for a given feature
My reticence would again solidify every time I read another post or series of posts about the precise means a given user went about obtaining Android Pay, and the commensurate loss of a different feature...or, no mention of a feature about which I cared.
So this thread is an attempt to redress these issues; specifically, after reading this, you should be able to have...
1.1-1.5. Systemless Root - If Using System Root
1.6. Updating Systemless Root Versions
2. Properly Themed Apps
2a. Hard-coded themed apps
2b. Theme Ready Google Apps
3. Layers
4. Viper4android that does not break your AUX jack or Chromecast
5. Busybox
6. Android Pay
1. Systemless Root
Whether you are running stock, or one of the few AOSP roms claiming to have Android Pay functioning on your device, this is your first step
If you are running a rooted rom, installing a pre-rooted rom, or want to flash a rom that is pre-rooted, to attain Systemless Root, you'll need the following resources...
1.1. The Latest Systemless SuperSU Zip (scroll to the bottom
http://forum.xda-developers.com/showpost.php?p=64161125
1.2. System Root Removal Tool /unSU
http://forum.xda-developers.com/showpost.php?p=63615067
1.3. Busybox for All Devices (scroll down to the section labeled "Busybox Installer")
http://forum.xda-developers.com/showthread.php?t=2239421
1.4. These Two Terminal Commands (have them in a notepad file, on your computer, or just, literally written down on a piece of paper)
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
1.5. To Install Systemless Root
1.5.1. Boot into Recovery
1.5.2. Install Pre-Rooted Rom + Gapps if Needed
1.5.3. Flash unSU Zip
1.5.4. Go to TWRP Main Menu, Go to Advanced, Terminal Command, type each command exactly as above, one at a time), hitting return in between each line
***you'll only do this once if you plan on staying on systemless root
1.5.5. Flash Systemless Root Zip
1.5.6. Flash Busybox Zip
1.5.7. Flash Custom Kernel if Desired
1.5.8. Fix Folder Permissions
-->Boot your device
-->Using Root Explorer or similar app, navigate to the folder labeled "su," as below...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-->Then hard press on the folder labeled "bin" and select the pop-up option for permissions, so below...
-->Set permissions to 0751, or deselect the check boxes as below...
1.5.8. Keep Reading, or...
Boot to System if This Is All You Want
1.6. Updating Systemless Root Versions
If you're already running Systemless Root and wish to upgrade to the latest version, follow these steps...
1.6.1. Flash latest version of SuperSU
1.6.2. Flash custom kernel if desired
***Note that if you omit the second step above, and wish to stay on a stock, no force encryption kernel (like one that ships with PureNexus), there is no need to reflash the kernel that came pre-installed with your rom. Just flash the latest version of Systemless Root.
2. Viper4android
2.1. Grab a Zip from the Viper4android Atmos Thread Here (some recommend the Viper4android Atmos Sony Beats Edition...so why the heck not?)...
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
2.2. Flash in Recovery
3. Properly Themed Apps
If one wants properly themed apps, and since the Gapps packages that allow working Android Pay are minimal, one must add them
3.1. Hard Coded Themed Apps
Using the Team BlackOut Updater (linked below), download those you want and flash in recovery...make sure to grant the app write permissions to your internal SD storage
http://bit.ly/1OcThZg
3.1.1. Download the Gapps that you want, flash in recovery
3.2. Theme Ready Google Apps
Go to this thread, download what you want...
http://forum.xda-developers.com/android/apps-games/apps-themeable-hangouts-layers-cmte-t3113192
3.2.1. Flash is recovery
3.3. All At Once in TWRP, in Sequence
You can and should flash all of these one after the other in TWRP...here are a few reasons why...
3.3.1. If you're using Gmail, and the minimal Gapps doesn't include it, you'll now have it waiting for you upon boot
3.3.2. If you've got a ton of downloaded music from Google Music, it'll still be there waiting for you if you flash Google Music during install (ie, you'll not have to download all of your music again)
3.3.3. Do you really want to set up hangouts, Google Plus (I turn off notifications and sync for this app...why do that every bloody time...), etc?
3.5. Layers
3.5.1. Install the latest version of the layers manager, and install whatever layers your want
3.6. Busybox That Works
You've already done that
3.7. Android Pay
3.7.1. Download from the Play Store, Add Cards
3.7.2. Note that not all cards will work...it's not the fault of the tools you've been given on this site...it's symptomatic of the reality that none of your cards is issued by participating Android Pay partners
4. Test Android Pay
4.1. You can download SafetyNet Helper Sample from the Play Store...
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
The app is temperamental, and can throw up a false negative...but you will get a positive result most all of the time
4.2. Buy a dang soda, pack of gum at CVS, some cheap gift from Walgreens...I don't care from where...to see if it works (it should)
5. Odds & Ends
A few items of note...
5.1. All of your previously apps granted root permission will need so again
5.2. Stay on top of themed apps...layers can never properly theme certain apps if there's a stock version in the data partition of your device.
5.3. Thank all of the devs whose tools are linked in this thread, donate to them, and be sure to buy anything that they may have for sale...they are the best in class.
5.4. Many things may or definitely will break Android Pay, even if you've set it up properly, including Xposed, theme engine, some DPI changing apps, etc. Just be mindful that this could change if you install other items.
6. Credits
@nathanchance, for being such a good dude
@inffy, for being helpful at all times, while maintaining near pitch-perfect, subtle venom
@osm0sis, for just everything he has provided
@BeansTown106, for building his rom, and not just stumbling but actually figuring out what prevented Android Pay from working on his rom
@daveyannihilation, for being such a great guy, themer, forum moderator, and finest pineapple lover I've ever encountered
@Woody, for having done the heavy lifting on most all of this prior to me
Chainfire
Viewers like you that contribute to Public Television...thanks for your support
Good luck!
Solid work! Gonna add it to my signature and I will add it to my posts as soon as I can.
Great post, and thanks for the mention!
Venom indeed flings in my veins
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Subiegsr said:
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Click to expand...
Click to collapse
I am using the all-in-one package by @guitardedhero
Please link to my thread, not my zip. Thanks.
osm0sis said:
Please link to my thread, not my zip. Thanks.
Click to expand...
Click to collapse
Yes sir...taken care of it.
My apologies.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Me from another thread said:
As an aside, I have an almost completely stripped down /system partition as far as gapps go and have even substituted several TBO ThemeReady versions, as well as Clear YouTube. So if I were to put a wager on what trips the Pay failure [I am speaking in systemless root terms], I would lay bets on system/bin, /system/xbin, busybox configurations and changes to some shadow policy that no one has figured out. Because simply adding or removing apks from /system (not including any signature checked apks such as a modified GMusic or Chrome) and utilizing the /su folder correctly doesn't trip the Pay verification, at least not for me.
Click to expand...
Click to collapse
Thanks
Bookmarked in my tips folder.
I'm sure I'll refer to it many times.
viper4android link is down
Sent from my Nexus 6P using Tapatalk
Most excellent! U Rock on XDA!!
galaxys said:
Most excellent! U Rock on XDA!!
Click to expand...
Click to collapse
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Woody said:
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Click to expand...
Click to collapse
This is true...LOL! I'll continue to scout the teams!
galaxys said:
This is true...LOL! I'll continue to scout the teams!
Click to expand...
Click to collapse
Sometimes looking at the forums via browser really has its advantages.
I'm so glad I looked at this exchange...I'm quite thankful for those cheerleaders...they really want me to have my device exactly as I like it.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Woody said:
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Click to expand...
Click to collapse
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
micmars said:
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The links in the OP all work for me...
http://forum.xda-developers.com/showthread.php?t=2952137
ViPER|Audio || ViPER|Atmos 4.1 * SQ Driver * Audiophile Profile * Beats * Huawei *
They are direct downloads at the bottom of the OP...
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
Click to expand...
Click to collapse
Excellent...I'll add this to the OP, along with the one provided by Woody.
Do you mind telling me...
1. The rom you're running
2. The kernel you're on
3. If you're SELinux is set to permissive or enforcing
Many thanks.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
THIS IS NOT MY WORK.
The original developers can be found HERE. All credits to them.
I wanted to share this sound mod with you with a minor adjustment. The only adjustment I have made to the zip file is to modify which packages that should be installed. This can be altered to your own needs, but I wanted to share one that works with AOSP on Nougat. This should work on Oreo as well, both 32 and 64-bit.
What is included in this repacked version:
Magnum Opus Core module
Magisk Module
ViPER4Arise™ 2.3.4.0 module
Dolby Digital Plus™ module
Sony™ Xperia XZ Music Suite module
AOSP MusicFX module
Please give a thumbs up in the original thread if you find it useful.
For further adjustments or questions see the original thread.
Download HERE
Installation instructions:
Download
Install - You will encounter "Error 1" and the installation stops. This is to create the required files for the next step.
Install again.
Done!
Wait, what exactly is the point of this zip file you've created? There's just a tiny modification you've done, which you haven't clearly explained.
You basically just reposted another thread without any proper meaning or modification. Please stop spamming the forums. Everyone knows how to download ARISE, and there's no need for a new thread about it.
thes3usa said:
Wait, what exactly is the point of this zip file you've created? There's just a tiny modification you've done, which you haven't clearly explained.
You basically just reposted another thread without any proper meaning or modification. Please stop spamming the forums. Everyone knows how to download ARISE, and there's no need for a new thread about it.
Click to expand...
Click to collapse
Sorry I didn't know this mod existed until yesterday so I thought it was worth sharing with an even easier way of installing, so more people could enjoy this amazing mod. But that is not the case then this can be removed.
Google Dialer v37 & Contacts v3.7.7 on Stock ROMs (any ROM really) August 1st, 2019
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
Link to the thread in V20's apps section HERE
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
as always, my latest updates and newest files can be found in this shared Google Drive folder
This link has been changed, the correct one is above. I had (wanted) to move this project to a separate dedicated account that was not so personal. Reshare the folder to yourself using Google Drive and/or update your bookmark.
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-(arm64)-33.0.247985459-publicbeta-3998624.apk
Contacts-com.google.android.contacts-3.5.51.247103087-2209215.apk
OLD Changelog:
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
- updated all the framework files to match the ones in the latest release from opengapps
- removed LGInCallUI app as it is not completely necessary in this particular project
arm64 zips
Phone-com.google.android.dialer-37.0.260231449-publicbeta-4339080.apk
Contacts-com.google.android.contacts-3.7.7.260733580-2243311.apk
April 25th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785841.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209036.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785840.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209035.apk
All files can be found and downloaded from my shared Google folder (above) or attached to this post (below).
March 27th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta-3785464.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
February 22nd, 2019
- updated both apps to latest version of each as supplied by Google. App versions are below...
arm64 zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570857.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570850.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
questions or comments? leave a reply here and I will see it. I don't visit here often but I should get back to you either immediately or within 2-3 weeks.
~syndre
- I don't think it's necessary, but by request (and to avoid confusion) I have made a Android 9.0+ PIE compatible flashable zip to install just the dialer's framework.
January 22nd, 2019
- Updated apks to latest versions from Google
Phone-com.google.android.dialer-28.0.229824408-publicbeta-3464836.apk
Contacts-com.google.android.contacts-3.3.3.226019458-2171201.apk
-I uninstalled any updates to the phone and contacts app I had installed, and flashed the non-magisk version on to my V30+, both apps are working fine.
-I copied those files into the magisk template I've been using and zipped that to create a magisk installable version. I have not tested this one but I assume it will work for those who use it.
- expect arm versions within the next week.
downloads are attached below, to this post.
December 20th, 2018
I am still not sure why it was happening, but the Phone app started randomly force closing on me a few days ago. I do a lot of playing around with mods and stuff so it could just be me. I have updated and tested both of the zips being released today, and the app is working again for me. I use a stock Oreo LG ROM. Everyone who hasn't had this issue or if you're on another device or on AOSP, ignore this paragraph. Theres a few files different in here from the previous version, so please flash this update so I know we're all on the same page. ty
- Updated dialer to latest apk from Google: v27.0.225573798-publicbeta-3347328.apk
- Updated/changed a couple framework related files to get the app to stop force closing on my device.
- arm (32) versions made and posted, too. Make sure you use the correct zip for your device!
New files can be found attached onto this post below and/or in the drive folder linked to above.
November 26th, 2018
updated phone to today's release from google
These are a little different from the previous (Nov 26) version, if you experience any issues at all please let me know!
attached below, and also available HERE
November 26th, 2018
updated arm64 apk's
arm update soon
flashable zips are attached below
November 15th, 2018
seems like they always put one out after I post... v26 is supposed to officially have dark mode in the dialer app (now both phone and contacts).
attached below
November 13th, 2018
my last post in this thread
Updated APK's to versions:
Phone-com.google.android.dialer-25.0.220310144-3118535.apk
Contacts-com.google.android.contacts-3.2.4.220343473-2161331.apk
both regular and magisk flashable zips are attached to this OP.
You can also find everything related to this project here in this shared drive folder.
New Favorites Section and Dark Mode on display in this Screenshot Album...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above is still not Google official, but easy to manipulate. See thread started by @JonnyTrulove HERE!
October 27th, 2018
Updated arm64 APKs to Google's newest version of each, both released today:
Phone-com.google.android.dialer-25.0.218361296-3118167.apk
Contacts-com.google.android.contacts-3.1.6.218196352-2149637.apk
I'll upload zips with version 25 for arm devices soon. I'm literally on my phone, typing this from a pitch dark cabin in the woods in the Midwest U.S. with someone sleeping a foot away from me.
Download arm64 zip to flash directly to system, also attached below OP
Download arm64 zip packaged as a magisk module, instead, also attached below OP
LINK CHANGED/UPDATED
Link to my NEW shared drive folder.
October 8th, 2018
arm64 versions with new contacts v3.1.3 update
arm64 version with new contacts v3.1.3 update -Magisk Module
I built these and edited this top post totally on mobile, I hope it works..
I'll fix[/IMG] the rest later
it has just come to my attention that some people (on other devices) are having problems because I never switched over to the 2018 dialer framework in these zips. Both versions have always been there, I just had it named in such a way that the 7.0 version wax being used.
I have changed it over to the newer Oreo 8.0 framework, and will use that from today onwards.
Any issues because of this on LG phones? Please leave a response about it.
download 8.0 framework below, or here
October 3rd, 2018
Updated all apk's involved, and put together an arm version so I could use it on my older arm devices.
arm64 version for V30 and newer phones, magisk'd
arm64 version that writes directly to /system partition
arm version for your older phones , magisk'd
arm version that writes directly to /system partition
I have also attached the same 4 zips to this top post. They must have raised the file size limit recently or something ¯\_(ツ)_/¯
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
unattached file DL count -
arm64:3640 | arm64-magisk: 1332 | arm:398 | arm-magisk: 436
syndre said:
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Link to the thread in V20's apps section HERE
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
Thanks
Click to expand...
Click to collapse
You don't need to move contacts to the system. Just the phone app.
TotallyAnxious said:
You don't need to move contacts to the system. Just the phone app.
Click to expand...
Click to collapse
Ok, and?
I like it in /system, where it won't get accidentally removed.
I assume since you took the time to comment that you think its better installed as a user app for some reason.. I'm curious now, what is/are those reasons?
Putting apps like that on the system partition makes no difference in functionality, and saves space it would otherwise be taking up on /data...
Your stock contacts app comes out of the box on /system, most if not all gapps packages put contacts onto /system.
There are many, many apps that will work on either system or installed as a user app.
I put it there because I like it there. phone and contacts in my installer come together as one package. There's no reason to not keep it simple and put both apps in the same destination.
Thanks for commenting, I guess... but I don't know why you are telling me something I'm well aware of.
Once you have the framework and permission files on the system partition for the phone app, you can sideload that APK too onto /data, if that's what you prefer.
I don't plan on changing anything, and look forward to later in the day when I'll hopefully forget about being confused about why you needed to mention this, especially with zero context.
Sent from my LGE V30+ using XDA Labs
I used this on my phone - I previously had Contacts from the Play Store and a modified copy of Phone from Martin.077 (I was using version 20). Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me with a retail US998+ on Verizon, and this is mostly stock firmware. I say mostly stock because I have the Verizon modem flashed - signal strength at my home doesn't seem as good with the V30 as it was with my Droid Turbo, so I've been experimenting.
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
tagor said:
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
Click to expand...
Click to collapse
Installing any of my zips from this thread will not do anything to your stock dialer app (as far as I know).
You will have to go into the phone settings and switch which one you want set as the default.
To use stuff in the google one, you must set google phone as default.
If you ever need to update your PRL or anything like that, you will have to switch it back to the LG contacts app, or else the dialer "secret codes" wont do anything.
I should have mentioned that in the OP..
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
hitokage004 said:
Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me
Click to expand...
Click to collapse
Replying to myself to indicate this apparently isn't correct (based on info from another thread). I didn't know when people referred to visual voicemail, they were referring to the text transcription stuff. I have a Google voice number that isn't really used, but I've seen the transcriptions on the website from people who misdialed and left a message - I wasn't particularly impressed and had to listen anyway.
It was mentioned that there is configuration files that will make it work though, so what I said is partly correct - as the voicemail tab shows in the Google dialer when using this version. The modified version I used before didn't have that tab.
EDIT - See below.
ChazzMatt said:
Visual Voicemail is not transcription. Visual Voicemail is merely a list of voice messages so you can pick and choose the order you wish to listen or even delete without listening. It MAY also include voicemail-to-text transcription, but that is not the purpose of the visual voicemail definition. Early visual voicemail applications (from when the name came) did not have voicemail-to-text transcription and was called that because you could SEE the list of messages on a video interface.
https://www.lifewire.com/what-is-visual-voicemail-3426762
https://en.wikipedia.org/wiki/Visual_voicemail
__________
If they were referring only to voicemail-to-text transcription, they are wrong. That can be INCLUDED in a "Visual Voicemail" service, but is not what visual voicemail means.
Google Voice does have "visual voicemail" (list of messages on the website) as well as having voicemail-to-text transcription (website, text, and email). Both my wife and I have Google Voice numbers and I appreciate both the text and email transcriptions I receive.
Click to expand...
Click to collapse
:good:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
saxena1 said:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
Click to expand...
Click to collapse
thats fine just please don't forget to mention where you got it from
syndre said:
thats fine just please don't forget to mention where you got it from
Click to expand...
Click to collapse
Already mentioned you name
please update your post regularly ?
saxena1 said:
Already mentioned you name
please update your post regularly
Click to expand...
Click to collapse
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
syndre said:
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
Click to expand...
Click to collapse
How do I get VM to show up in the Google dialer?
I have my stock T-Mobile VM app installed.
Sent from my LG-H932 using XDA Labs
Contacts installed fine, but not the dialer. I get "App not installed". Anyone know how to fix this?
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
nobdow said:
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
Click to expand...
Click to collapse
This doesnt need root or TWRP. Just download and run the apk.
You don't need root? I've got no where to put the zips (but I don't have root)
The APK for contacts installs but phone does not install on my v30 h933 - the package installer sometimes doesn't even give an error and other times it just says "not installed".
I can't get the apk to install either.
Sent from my LG-H931 using Tapatalk
Yeah, can't get it to stick on a stock 932.
You can use this without root, but the bootloader must be unlocked and TWRP installed. Unlocking the bootloader and installing TWRP doesn't require you to install a root app like Magisk.
For those who want to use the Google Dialer (aka Phone) without unlocking the bootloader - I used Martin.077's patched copy previously. With that version though, you'll have to wait for them to update it - it can't use the updates from Google in the Play Store. Google Contacts will install and update from the Google Play Store without any modifications.
EDIT: It's too annoying to maintain and edit 6 separate threads. The installer works across all devices, so please visit this post for the latest version: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks!
NOTE: Download link in the OP will install mod for the current patch level down to January 2021. It will detect your current patch level and install the correct file. For earlier system builds from 2020 and prior, please use the official discontinued module on the Magisk Manager repo. I did not clone the entire Active Edge Mod repository; my unofficial repository only hosts January 2021 and later builds.
Changes:
I know, I know... I said I was done with releasing my Unofficial Active Edge Mod installer, yet here's another month's update. I might keep doing it for those that update immediately and want it a bit sooner, so long as it's fortunate enough to happen on a day when I'm able to do it relatively quickly. Since I'm building these anyway and sending them over to the dev, for now, to upload to the official Magisk repo, for now I don't mind also updating it here a bit sooner. Anyway, more on this below and some of the headache involved moving forward...
04-05-2021: Soooo... the script I wrote to churn these out as quickly as possible as Google releases the updates, relied on system image dumps on GitRip... unfortunately the domain was seized by the FBI (lol) and so it looks like the old dumper is no longer updating his Android dumps repo on GitRip. Fortunately, mikalovtch pointed me over to a new source that hosts such system dumps, and I was able to get these done relatively quickly afterwards. OP is updated with the 04-05-2021 installer now!
03-02-2021: Meant to post an update a week or two ago. Noticed the magisk module on the official Magisk repo now says [RE-CONTINUED], so there really isn't much need for me to continue updating this anymore! As a final gift, I ran my batch builder script and built the modded apk's for all variants for the 2021-03-05 patch level, and download link for the module installer is in the OP.
02-02-2021: February 2021 mod is now uploaded. Updated installer is in the link in the OP.
02-01-2021: Modified and uploaded modded SystemUIGoogle.apk files for 3 / 3 XL / 3a / 3a XL to GitHub repository. Updated Magisk installer slightly to accommodate this, and removed a few unnecessary lines. Won't make any difference if you already installed the first release.
i5lee8bit said:
ONLY WORKS FOR PIXEL 4 XL "CORAL" AND PIXEL 4 "FLAME"!!!!
(WON'T EVEN INSTALL ON OTHER DEVICES, SO DON'T BOTHER)
tl;DR - A continuation of the "[Discontinued]Active Edge Mod for Pixel devices" Magisk module on the Magisk Module Repository, discontinued and last released for 2020-12-05 patch level. This is simply the same exact mod applied to the 2021-01-05 patch level. PLEASE DO NOT BOTHER THE ORIGINAL DEV FOR ANY SUPPORT - THIS IS AN UNOFFICIAL MOD.
Click to expand...
Click to collapse
awesome work mate, love this mod. i saw ur post on pixel 4xl forum first and downloaded and flashed that. everything seems 2b working fine! but then i noticed this thread posted seperately on our phone's forum. is there any difference between them?? just wanna make sure that i flashed the rite file. thx again for all mate
vdevl said:
awesome work mate, love this mod. i saw ur post on pixel 4xl forum first and downloaded and flashed that. everything seems 2b working fine! but then i noticed this thread posted seperately on our phone's forum. is there any difference between them?? just wanna make sure that i flashed the rite file. thx again for all mate
Click to expand...
Click to collapse
Yep, you flashed the right file. Both posts link to the same zip file. The module installer, like the original module, gathers your device information and then downloads the correct file for your device and installs it. Even has an MD5 hash checksum check to make sure it's all good before installing. It was actually a really fun little project to work on, and interesting to see how Jan designed it to be semi-automated, with several fail-safe checks. For example, there's a post fs data script to also disable the module automatically if the user upgrades the system patch level and hasn't yet upgraded the module, likely to ensure the systemuigoogle mod isn't incompatible with the new update and potentially cause issues. Really well designed by the original dev!
How do I actually map it? I have installed on my pixel 4xl but it only opens an unusable google assistant UI.