Related
Hey all,
Yes, first post, and yes, I did search for a solution to my problem, but didn't see this one, and didn't like those.
Was having trouble with Google Wallet on CM 10.1. I went to stock (from backup) and pulled that build.prop file for comparison to the CM 10.1 build.prop. There were some discrepancies and I changed the values to what is below.
Code:
ro.product.brand=htc
ro.product.name=m7wls
ro.product.device=m7wls
ro.product.name=HTCONE
Removed this line as well.
Code:
ro.product.locale.region=US
Saved, then rebooted the phone. Installed Google Wallet. Ran it. Everything worked as expected (says "Unsupported Device" at the top, but I assume its due to being rooted).
I searched for this solution but could not find it. If I posted out of error, please forgive me, I usually only lurk on here.
Veranor said:
Hey all,
Yes, first post, and yes, I did search for a solution to my problem, but didn't see this one, and didn't like those.
Was having trouble with Google Wallet on CM 10.1. I went to stock (from backup) and pulled that build.prop file for comparison to the CM 10.1 build.prop. There were some discrepancies and I changed the values to what is below.
Code:
ro.product.brand=htc
ro.product.name=m7wls
ro.product.device=m7wls
ro.product.name=HTCONE
Removed this line as well.
Code:
ro.product.locale.region=US
Saved, then rebooted the phone. Installed Google Wallet. Ran it. Everything worked as expected (says "Unsupported Device" at the top, but I assume its due to being rooted).
I searched for this solution but could not find it. If I posted out of error, please forgive me, I usually only lurk on here.
Click to expand...
Click to collapse
I can confirm that this line alone works:
Code:
ro.product.device=m7wls
I myself recieve the error "Not Supported"
No dice on this end either.
For the record, is the Wallet you are using from the Play Store or is it some third party cracked one?
rougegoat said:
No dice on this end either.
For the record, is the Wallet you are using from the Play Store or is it some third party cracked one?
Click to expand...
Click to collapse
I'm fairly certain mine is from the Play store. I'm not 100% on that though.
rougegoat said:
No dice on this end either.
For the record, is the Wallet you are using from the Play Store or is it some third party cracked one?
Click to expand...
Click to collapse
Wallet from the play store. I went through this twice, then updated to the latest nightly and saw that it broke, so I force closed it, deleted cache, updated build.prop, rebooted, and i was able to initialize wallet again just fine.
Veranor said:
Wallet from the play store. I went through this twice, then updated to the latest nightly and saw that it broke, so I force closed it, deleted cache, updated build.prop, rebooted, and i was able to initialize wallet again just fine.
Click to expand...
Click to collapse
Followed to a T on the most recent nightly, still no dice.
rougegoat said:
Followed to a T on the most recent nightly, still no dice.
Click to expand...
Click to collapse
That's bizarre. I can even go back to the build.prop, change the settings back, reboot, and my wallet breaks. I'll double-check the settings to make sure there wasn't something I missed here.
If you want to kill the unsupported app banner, use MoDaCo Toolkit. I didn't see this issue at all though, so something seems up. You could try the aforementioned toolkit to download an installer and see if that works either.
I've redone this process, only doing one item at a time. Wallet functions when you change the following value.
I tested this by wiping and flushing cache thru recovery, then installing latest nightly.
After that finished, I installed Wallet, verified that it did not work.
Opened build.prop and changed the following property. Force closed Wallet, flushed data. Rebooted.
ro.product.model
from "One" to "HTCONE"
Opened Wallet - completed setup.
The m7spr is supposed to be m7wls though - not sure why I added those, thought maybe they were linked.
This works. Just got some mc Donald's.
Sent from my HTCONE using Tapatalk 4 Beta
As of the nightly today, this no longer works. :-/ Worked yesterday though.
Veranor said:
I've redone this process, only doing one item at a time. Wallet functions when you change the following value.
I tested this by wiping and flushing cache thru recovery, then installing latest nightly.
After that finished, I installed Wallet, verified that it did not work.
Opened build.prop and changed the following property. Force closed Wallet, flushed data. Rebooted.
ro.product.model
from "One" to "HTCONE"
Opened Wallet - completed setup.
The m7spr is supposed to be m7wls though - not sure why I added those, thought maybe they were linked.
Click to expand...
Click to collapse
Here is what I did:
Update to newest nightly
Use recovery to clear cache, dalvik cache, reboot
Confirm Wallet does not work
Force closed Wallet, cleared its cache, data
Edit build prop from "ro.product.model=One" to "ro.product.model=HTCONE"
clear cache, dalvik cache, reboot
Confirm that Wallet still does not work
If you flash another nightly you have to do the build prop edit AGAIN....OK. The flash overwrites it.
Sent from my One using Tapatalk 4 Beta
david279 said:
If you flash another nightly you have to do the build prop edit AGAIN....OK. The flash overwrites it.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Assuming you are talking to me, I am quite well aware. Back to Xposed I go I guess.
david279 said:
If you flash another nightly you have to do the build prop edit AGAIN....OK. The flash overwrites it.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
True, but if all that it takes to fix it is one line change in the build.prop, that can be reported to the CM guys and fixed in future builds.
Tell @kushdeck
Sent from my One using Tapatalk 4 Beta
david279 said:
Tell @kushdeck
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Brought it up in the CM10.1 thread already. It probably isn't being taken too seriously though since it apparently does not work every time or for every device.
Go on IRC beware though it's a hard place.
Sent from my One using Tapatalk 4 Beta
david279 said:
Go on IRC beware though it's a hard place.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm not one to report a fix there that I have confirmed does not work all the time. Feel free to report it yourself.
Hi guys. I'm going to apologize in advance that I am a noob when it comes to hacking and rooting. I've successfully gained root access to my Verizon LG G2 using my computer. I used originally used an app called G2 Tweaksbox that allows you to change a lot of things about the phone. But then I wanted to try the famous CM 11. I did the tutorial on youtube, but I didn't install the GAPPS zip. Then I rebooted my phone and now it became stuck on the LG startup screen but looping over and over again. I've tried to hard reset it but it won't work. Is there any possible way to fix this, because I used another family members upgrade to get this phone after I broke my last one? Please don't judge but please help me if you can.:crying::crying::crying:
DevStep said:
Hi guys. I'm going to apologize in advance that I am a noob when it comes to hacking and rooting. I've successfully gained root access to my Verizon LG G2 using my computer. I used originally used an app called G2 Tweaksbox that allows you to change a lot of things about the phone. But then I wanted to try the famous CM 11. I did the tutorial on youtube, but I didn't install the GAPPS zip. Then I rebooted my phone and now it became stuck on the LG startup screen but looping over and over again. I've tried to hard reset it but it won't work. Is there any possible way to fix this, because I used another family members upgrade to get this phone after I broke my last one? Please don't judge but please help me if you can.:crying::crying::crying:
Click to expand...
Click to collapse
Which cm did you try? The official or JackpotCalvin's?
Sent from my VS980 4G using XDA Premium 4 mobile app
njstein said:
Which cm did you try? The official or JackpotCalvin's?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the official nightly version. Thanks for the quick reply.
DevStep said:
I tried the official nightly version. Thanks for the quick reply.
Click to expand...
Click to collapse
If you did a nano backup then restore that if not you are going to have to do the revert back to stock. But for your information for later on. If you install xposed with any modules. Make sure to properly Uninstall all them before you change roms or make any changes
One last thing the official cm rom is no longer supported. No one to work on the g2 anymore
simple_fear85 said:
If you did a nano backup then restore that if not you are going to have to do the revert back to stock. But for your information for later on. If you install xposed with any modules. Make sure to properly Uninstall all them before you change roms or make any changes
One last thing the official cm rom is no longer supported. No one to work on the g2 anymore
Click to expand...
Click to collapse
Why would you need to uninstall Xposed modules? Everything gets wiped anyway.
mjones73 said:
Why would you need to uninstall Xposed modules? Everything gets wiped anyway.
Click to expand...
Click to collapse
I had issues with my phone messing up if I kept xposed with modules installed still when I did clear all and installed a rom. Not sure why but I Uninstall now and no issues anymore. I actually lost knock on once leaving xposed installed. I confirmed it with going back to my nano Uninstalling xposed and knock on worked fine
simple_fear85 said:
I had issues with my phone messing up if I kept xposed with modules installed still when I did clear all and installed a rom. Not sure why but I Uninstall now and no issues anymore. I actually lost knock on once leaving xposed installed. I confirmed it with going back to my nano Uninstalling xposed and knock on worked fine
Click to expand...
Click to collapse
That's an odd one since Xposed runs in /system. Were you wiping /system and /data without restoring anything on a clean install?
mjones73 said:
That's an odd one since Xposed runs in /system. Were you wiping /system and /data without restoring anything on a clean install?
Click to expand...
Click to collapse
I did a full wipe with Clean install
simple_fear85 said:
If you did a nano backup then restore that if not you are going to have to do the revert back to stock. But for your information for later on. If you install xposed with any modules. Make sure to properly Uninstall all them before you change roms or make any changes
One last thing the official cm rom is no longer supported. No one to work on the g2 anymore
Click to expand...
Click to collapse
Yeah I downloaded xposed and I got the latest module for support. I had no idea that you needed to delete them after you wanted to download a new ROM. Okay so do I fix this? My phone is stuck looping on the LG bootup message and the only way I can stop it is by hard reseting it and that just turns it off. How do I access it on my computer and reflash the stock? Please help.
DevStep said:
Yeah I downloaded xposed and I got the latest module for support. I had no idea that you needed to delete them after you wanted to download a new ROM. Okay so do I fix this? My phone is stuck looping on the LG bootup message and the only way I can stop it is by hard reseting it and that just turns it off. How do I access it on my computer and reflash the stock? Please help.
Click to expand...
Click to collapse
Follow the stock restore guide in the general section.
DevStep said:
Yeah I downloaded xposed and I got the latest module for support. I had no idea that you needed to delete them after you wanted to download a new ROM. Okay so do I fix this? My phone is stuck looping on the LG bootup message and the only way I can stop it is by hard reseting it and that just turns it off. How do I access it on my computer and reflash the stock? Please help.
Click to expand...
Click to collapse
Once your phone is off, hold up and plug it in to your computer. This should put you in download mode. Hopefully you have all the drivers installed...
Sent from my VS980 4G using XDA Premium 4 mobile app
Hi,
I seem to have managed to bootloop my Nexus 5. Yesterday I updated my Nexus to Android Lollipop (through the system update), I rooted it with CF-Root. All working well after.
However, I noticed that xposed was not activated. So I pressed on uninstall with the intention to install again. As soon as it rebooted, the device got a bootloop.
What should I do?
I tried the xposed-disabler fix but to no avail.
Thanks,
Immortali
Flash stock firmware again. I'm sure stock images are available in the N5 section.
Also, Xposed is not compatible with Lollipop so don't try to install it again unless you want to recover from another bootloop.
Sent from my C6603
Dies that mean that I will lose all data and need to reinstall all apps again?
immortali said:
Dies that mean that I will lose all data and need to reinstall all apps again?
Click to expand...
Click to collapse
I don't have an N5, but you should be able to just flash /system leaving your data intact.
If you ask in the N5 section I'm sure someone there will help you.
Sent from my C6603
You can save your data!
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
OmerElbaz said:
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
Click to expand...
Click to collapse
I'll try that
I did something else:
I did a Nandroid backup, Flash Stocked and then restored the data part only. It is still in the bootloop, therefore I am presuming that the data is actually corrupted.
Can I edit a nandroid backup that is saved on my pc and remove xposed from it?
I think teh lesson here is when moving from one version of Android to another you should do a clean install, either that or just dirty flash over the after a system wipe. Either way I struggle to see how this is an Xposed issue..
OmerElbaz said:
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
Click to expand...
Click to collapse
Please note that even without the -w flag, if it flashes over userdata.img then that's a wipe.
cmstlist said:
Please note that even without the -w flag, if it flashes over userdata.img then that's a wipe.
Click to expand...
Click to collapse
I didn't knew that actually, what exactly does it wipes?
And still it's pretty much the best you can do... I think
Argh, did exactly the same with the same result. So it's an XPosed issue.
Installed Lollipop OTA on my Nexus 7 WiFi 2013 with XPosed installed. Everything fine and running for a few days.
A few hours ago I decided to remove the XPosed framework from inside the XPosed installer and rebooted -> bootloop.
Strange that this happens after removing XPosed.
OmerElbaz said:
I didn't knew that actually, what exactly does it wipes?
And still it's pretty much the best you can do... I think
Click to expand...
Click to collapse
Userdata.img covers the entire data partition including internal SD, installed apps and app data. Flashing Userdata.img is equivalent to a full data and storage wipe.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:11 AM ---------- Previous post was at 08:07 AM ----------
Inferi0r said:
Argh, did exactly the same with the same result. So it's an XPosed issue.
Installed Lollipop OTA on my Nexus 7 WiFi 2013 with XPosed installed. Everything fine and running for a few days.
A few hours ago I decided to remove the XPosed framework from inside the XPosed installer and rebooted -> bootloop.
Strange that this happens after removing XPosed.
Click to expand...
Click to collapse
All the modifications that Xposed originally made to your system were reverted by the OTA. I'm sure what happened was the Xposed installer held onto backups of the system files it had modified. When you "uninstalled" Xposed it replaced some proper Lollipop system files with backups that came from KitKat. No wonder it bootlooped.
Since it corrupted system files, what you really need to do is reflash the system.img of Lollipop in fastboot. Then it should boot fine without data loss. Then reroot if you want to.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
Userdata.img covers the entire data partition including internal SD, installed apps and app data. Flashing Userdata.img is equivalent to a full data and storage wipe.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:11 AM ---------- Previous post was at 08:07 AM ----------
All the modifications that Xposed originally made to your system were reverted by the OTA. I'm sure what happened was the Xposed installer held onto backups of the system files it had modified. When you "uninstalled" Xposed it replaced some proper Lollipop system files with backups that came from KitKat. No wonder it bootlooped.
Since it corrupted system files, what you really need to do is reflash the system.img of Lollipop in fastboot. Then it should boot fine without data loss. Then reroot if you want to.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Are you sure about the wipe?
Cuz I think I already used this method once "without wiping" (For sure used it WITH wiping b4 but I'm not sure I also used without..) and if I really used it this way then I'm pretty sure it didn't wiped any of my data (I may be wrong, though, let me know if it's 100% wipes).
Thanks for all the suggestions, I managed to reboot my Nexus 7 without any loss of userdata.
With help of the Nexus Root Toolkit v1.9.8 I flashed the system.img from the razor-lrx21p-factory-ba55c6ab.zip onto my device in bootloader mode. Within 3 minutes I was up and running again.
That's all it takes to fix the bootloop.
Ok, but the question is "What to do to uninstall Xposed after Lollipop Update ?"
db77 said:
Ok, but the question is "What to do to uninstall Xposed after Lollipop Update ?"
Click to expand...
Click to collapse
You don't do anything. If the update succeeded and your device boots successfully, then the update already removed Xposed.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
You don't do anything. If the update succeeded and your device boots successfully, then the update already removed Xposed.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Some people who try to uninstal Xposed, have bootloop.
I haven't uninstall Xposed and I wait for an update for Lollipop... because my Nexus 5 works fine without uninstall Xposed. But it don't work...
db77 said:
Some people who try to uninstal Xposed, have bootloop.
I haven't uninstall Xposed and I wait for an update for Lollipop... because my Nexus 5 works fine without uninstall Xposed. But it don't work...
Click to expand...
Click to collapse
What doesn't work? The OTA? Lollipop? Xposed?
If you did the OTA and the OS works, then just remove the Xposed Installer app and your Xposed modules. Xposed itself is no longer installed so don't take any further steps.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
What doesn't work? The OTA? Lollipop? Xposed?
If you did the OTA and the OS works, then just remove the Xposed Installer app and your Xposed modules. Xposed itself is no longer installed so don't take any further steps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Xposed don't work under Lollipop.
On my Nexus 5, Xposed is always present but don't work, because ART et not Dalvik.
It has not been uninstalled...
db77 said:
Xposed don't work under Lollipop.
On my Nexus 5, Xposed is always present but don't work, because ART et not Dalvik.
It has not been uninstalled...
Click to expand...
Click to collapse
What makes you say Xposed is still there? The files that were patched when you installed Xposed under KitKat have been replaced by the Lollipop upgrade. Hence it's gone.
http://d-h.st/tTn
Flash after the ROM giving you the error.
I'm assuming it only happens to Sprint users, so it also includes the fixed Sprint APN.
Enjoy.
Works great. Thanks.
I don't think a carrier would have anything to do with it at all since this is the Nexus 5, and carriers have absolutely nothing to do with any aspect of the device, both software and hardware.
It does have a lot to do with it actually.
Great fix, seriously a life saver I've been pulling my hair out trying to figure it out. The closest I got was to just delete the apk from the rom if possible before flash.
Thanks so much
Going to try this tonight. Been pulling out my hair trying to figure this out with some roms
Well, whatever it does it worked. I flashed this after installing the AICP 5.0 nightlies that were giving me update device crashes. They no longer occur... thanks
@Lethargy you make me lol in every thread, brighten my days. Hats off to you ??
At least for me, while this zip does make the error message go away, it's not actually installing a working replacement. If you use a file manager and go to /system/app/OmaDmClient and try to install the apk within, you will get the standard install confirmation, not the one for updating existing software (which it should do if the app was already correctly working). So while this is technically a "fix", it's the same as just deleting the buggy apk.
Sent from my Nexus 5 using XDA Free mobile app
bray424 said:
At least for me, while this zip does make the error message go away, it's not actually installing a working replacement. If you use a file manager and go to /system/app/OmaDmClient and try to install the apk within, you will get the standard install confirmation, not the one for updating existing software (which it should do if the app was already correctly working). So while this is technically a "fix", it's the same as just deleting the buggy apk.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thinking I skipped setting perms in a rush. Either way, it shouldn't be needed for too long. I flashed to 5.0.1 without needing anything besides the fixed APN. I do see an issue with prl/profile update however.
killersloth said:
Thinking I skipped setting perms in a rush. Either way, it shouldn't be needed for too long. I flashed to 5.0.1 without needing anything besides the fixed APN. I do see an issue with prl/profile update however.
Click to expand...
Click to collapse
You a sprint user by chance?
crazyeats said:
You a sprint user by chance?
Click to expand...
Click to collapse
Yep
really need this file, can anyone please upload valid zip at legit host.
update: got it, not sure whether dev-host was backup or using different pc did the trick!
I'm having this same problem on my L720...
I assume this file wont work...
Is there a way to fix on my CM12 install without reflashing?
gbean009 said:
I'm having this same problem on my L720...
I assume this file wont work...
Is there a way to fix on my CM12 install without reflashing?
Click to expand...
Click to collapse
It should work, all it does is replace an apk and insert apns to /etc
Tried on my LG G2 LS980 with FreedomPop, but it didn't fix the Update Device error. Any clue for the failure?
This "fix" is crap. Don't flash random stuff to your device. No documentation? No source for the included APK?
Here is what I did to get the latest Google dialer to run on my Stock Nougat ROM.
Install the dialer framework via TWRP (attached)
Freeze the stock phone app
Install the Google phone app (attached), make it the default and give it permissions
Reboot
I am now using the latest Google Dialer.
Proximity search and Spam detection work too.
swieder711 said:
Here is what I did to get the latest Google dialer to run on my Stock Nougat ROM.
Install the dialer framework via TWRP (attached)
Freeze the stock phone app
Install the Google phone app (attached), make it the default and give it permissions
Reboot
I am now using the latest Google Dialer.
Proximity search and Spam detection work too.
Click to expand...
Click to collapse
I can confirm this works on Stock Magisk rooted Nougat 7.0
EDIT/UPDATE 11/09 - Cannot hang up phone. Went back to stock app.
Stock 7.0, no root, booted twrp, flashed, ..... Everything okay.
Thanks. All you need is the framework. Then download dialer. This was easier than using GAPPS.
schneid said:
I can confirm this works on Stock Magisk rooted Nougat 7.0
EDIT/UPDATE 11/09 - Cannot hang up phone. Went back to stock app.
Click to expand...
Click to collapse
Did you select the new phone app as the default?
Sent from my Nexus 7 using Tapatalk
swieder711 said:
Did you select the new phone app as the default?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I "froze" the original in TiBackup. Not enough?
schneid said:
I "froze" the original in TiBackup. Not enough?
Click to expand...
Click to collapse
Not enough. You need to select the new phone app as the default. Manage Apps / select gear / default
Sent from my XT1575 using Tapatalk
Not that this makes any sense, but I installed this and immediately lost LTE service in a place where I always have LTE service. Is there a way to uninstall the framework to see if it caused the issue?
NEVER MIND. Seems to have just been a glitch.
Which Phone Properties should be Frozen, I have 3 in Titanium Backup, the Phone Check is an app I use to check for Signal Strength.
CLETjB said:
Which Phone Properties should be Frozen, I have 3 in Titanium Backup, the Phone Check is an app I use to check for Signal Strength.
Click to expand...
Click to collapse
The one that says PHONE 3.00
CLETjB said:
Which Phone Properties should be Frozen, I have 3 in Titanium Backup, the Phone Check is an app I use to check for Signal Strength.
Click to expand...
Click to collapse
According to TiBu, I am currently running "Phone 14.0.176716531" which I think it the latest update from Google. The update came out this week. Any other Phone apps should be frozen.
PS: Don't forget to select the new Phone app as the default. Its under the "gear icon" in Manage Apps.
In Titanium Backup, could the new Phone be converted to System App?
I still haven't got the G Phone to display right but have manged to turn on WiFi Calling in the Moto Phone. Will the G Phone support WiFi Calling? WiFi Calling is pretty slick. Reception sucked in my house but with WiFi Calling i feel like I am using an AT&T landline from years ago. As they said, "you can hear a pin drop".
I turned on WiFi caller using Magisk VoEnabler.
This works for me, and play store did update to v14, but now I can't update to v15 due to a 505 error. I tired downloading the apk from apkmirror but get a conflicting name error, even when I uninstall the original app. Any ideas on how to update?
slicetwo said:
This works for me, and play store did update to v14, but now I can't update to v15 due to a 505 error. I tired downloading the apk from apkmirror but get a conflicting name error, even when I uninstall the original app. Any ideas on how to update?
Click to expand...
Click to collapse
I am on v14 and see a failed update to v15. I wonder if there is a new framework file. Let me look around.
swieder711 said:
I am on v14 and see a failed update to v15. I wonder if there is a new framework file. Let me look around.
Click to expand...
Click to collapse
Awesome. Thanks!
I copied the V15 Dialer.apk (was renamed) to the folder /system/priv-app/dialer. I made the permissions -rw-r-r-. After a reboot I am now running the latest Google Dialer.
Prior to installing the apk, I ran a Zip file created by xabat, https://drive.google.com/file/d/1dnZgFzKxYt9j8_uDwp5_36irMDsvN0q7/view?usp=drivesdk but I dont think that helped since I was still running the V14 Dialer afterwards.
Video icon is greyed-out and not seeing a setting for Assisted Dialing. Looks like v14, but its definitely v15.
swieder711 said:
I copied the V15 Dialer.apk (was renamed) to the folder /system/priv-app/dialer. I made the permissions -rw-r-r-. After a reboot I am now running the latest Google Dialer.
Prior to installing the apk, I ran a Zip file created by xabat, https://drive.google.com/file/d/1dnZgFzKxYt9j8_uDwp5_36irMDsvN0q7/view?usp=drivesdk but I dont think that helped since I was still running the V14 Dialer afterwards.
Video icon is greyed-out and not seeing a setting for Assisted Dialing. Looks like v14, but its definitely v15.
Click to expand...
Click to collapse
So should I get the apk from apkmirror? I'm a bit confused.
Yes.
I'll post the apk when I am back on my PC.
swieder711 said:
Yes.
I'll post the apk when I am back on my PC.
Click to expand...
Click to collapse
Kick ass. Does it replace the stock dialer apk that's in that folder? Should I remove the v14 app via tibu?