Question Unable to install an external APK on Pixel 7 - Google Pixel 7

Got my Pixel 7 yesterday. So far it looks and feels great.
However I ran into the following problem: I'm not able to install an external APK on the phone (specifically InstaPro v 9.6, not sure if posting a link is against some policy or not, older versions of the app also fail to get installed). From built-in file explorer I'm getting `You can't install the app on your device.`, later I tried to install in with `SAI` app and got a bit more info: `INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113`. Installing the latest updates did not help. Just to clarify the installation of third party apps is allowed for the apps through which I tried the installation.
I'm able to install the same app on my Pixel 6 without any issues and it runs fine. Pixel 6 also runs Android 13 so I would expect
Googling the issue did not help much, most suggestions seem to have something to do with the way developers package or prepare the app.
Did anyone else run onto such issue and does anyone have any suggestions on how to get around it?

Ph0enix89 said:
Got my Pixel 7 yesterday. So far it looks and feels great.
However I ran into the following problem: I'm not able to install an external APK on the phone (specifically InstaPro v 9.6, not sure if posting a link is against some policy or not, older versions of the app also fail to get installed). From built-in file explorer I'm getting `You can't install the app on your device.`, later I tried to install in with `SAI` app and got a bit more info: `INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113`. Installing the latest updates did not help. Just to clarify the installation of third party apps is allowed for the apps through which I tried the installation.
I'm able to install the same app on my Pixel 6 without any issues and it runs fine. Pixel 6 also runs Android 13 so I would expect
Googling the issue did not help much, most suggestions seem to have something to do with the way developers package or prepare the app.
Did anyone else run onto such issue and does anyone have any suggestions on how to get around it?
Click to expand...
Click to collapse
Have you tried sideloading the app through adb?

Lughnasadh said:
Have you tried sideloading the app through adb?
Click to expand...
Click to collapse
No, I have not. Is it expected to produce different results? After seeing it work on Pixel 6 I started suspecting that there could be some OS changes that only got shipped with the new phone.

Ph0enix89 said:
No, I have not. Is it expected to produce different results? After seeing it work on Pixel 6 I started suspecting that there could be some OS changes that only got shipped with the new phone.
Click to expand...
Click to collapse
It might work. I'm guessing that since this phone shipped with A13, target SDKs for some apps may need to be updated.

Lughnasadh said:
It might work. I'm guessing that since this phone shipped with A13, target SDKs for some apps may need to be updated.
Click to expand...
Click to collapse
Sadly it produced the same results:
```
~> adb install /home/phoenix/Downloads/InstaPro\ ♚\ v9.60.apk 15:09:25
Performing Streamed Install
adb: failed to install /home/phoenix/Downloads/InstaPro ♚ v9.60.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
```

"no matching ABIS" means that the application you're trying to install is not compatible with the OS. I believe that you are trying to install a 32bit application on a 64bit-ONLY operating system.

96carboard said:
"no matching ABIS" means that the application you're trying to install is not compatible with the OS. I believe that you are trying to install a 32bit application on a 64bit-ONLY operating system.
Click to expand...
Click to collapse
How do I check if OS on Pixel 7 supports 32-bit apps?

Run "getprop ro.vendor.product.cpu.abilist" and with abilist32 and abilist64
This is what it shows on a P6P running graphene;
Code:
[ro.vendor.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist64]: [arm64-v8a]

Apparently, while Tensor G2 supports 32-bit ABIs, Google removed the previous ABIs in Android 13 for the Pixel 7 series. Apps affected will have to be compiled in 64-bit.

Just an interesting tidbit - Gooble was supposedly to stop allowing applications that did not support 64bit to publish on store:
Google Play will stop serving native apps without 64-bit CPU support in 2021
Starting on August 1st, 2021 Google Play will no longer serve native applications if they do not support the 64-bit CPU architecture.
www.xda-developers.com
EDIT: Actually, I think that meant that old applications would be delisted from store in 2021.
Apparently the 64bit requirement was made in 2019: https://developer.android.com/google/play/requirements/64-bit

96carboard said:
Run "getprop ro.vendor.product.cpu.abilist" and with abilist32 and abilist64
This is what it shows on a P6P running graphene;
Code:
[ro.vendor.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist64]: [arm64-v8a]
Click to expand...
Click to collapse
Indeed that's the output from Pixel 7:
> adb shell getprop ro.vendor.product.cpu.abilist
arm64-v8a
vs Pixel 6:
> adb shell getprop ro.vendor.product.cpu.abilist
arm64-v8a,armeabi-v7a,armeabi
I'll see if I manage to reach the developer and ask for an update. Thank you for helping me to get to the bottom of it.

Lughnasadh said:
Apparently, while Tensor G2 supports 32-bit ABIs, Google removed the previous ABIs in Android 13 for the Pixel 7 series. Apps affected will have to be compiled in 64-bit.
Click to expand...
Click to collapse
This appears to be confirmed.
https://twitter.com/i/web/status/1580580220913954817

@Lughnasadh ; the message directly before yours confirms it better.

96carboard said:
@Lughnasadh ; the message directly before yours confirms it better.
Click to expand...
Click to collapse
Didn't realize this was a contest to see which confirmation was better, but in the thread I linked was this:
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a]
[ro.product.cpu.abilist32]: []
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.vendor.product.cpu.abilist]: [arm64-v8a]
[ro.vendor.product.cpu.abilist32]: []
[ro.vendor.product.cpu.abilist64]: [arm64-v8a]
And besides, didn't even see the post you mentioned beforehand as I just got home and just replied to my own post. But thanks for letting me know of my inferior confirmation...

Lughnasadh said:
Didn't realize this was a contest to see which confirmation was better, but in the thread I linked was this:
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a]
[ro.product.cpu.abilist32]: []
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.vendor.product.cpu.abilist]: [arm64-v8a]
[ro.vendor.product.cpu.abilist32]: []
[ro.vendor.product.cpu.abilist64]: [arm64-v8a]
And besides, didn't even see the post you mentioned beforehand as I just got home and just replied to my own post. But thanks for letting me know of my inferior confirmation...
Click to expand...
Click to collapse
You linked to a restricted external site.

96carboard said:
You linked to a restricted external site.
Click to expand...
Click to collapse
What do you mean? I linked a tweet. Linking tweets are not against the rules. Just let it go man...

I'm on P7P and have same issues. I started a thread yesterday and it's pretty clear 32 bit support is off A13

Lughnasadh said:
This appears to be confirmed.
https://twitter.com/i/web/status/1580580220913954817
Click to expand...
Click to collapse
You are like the twitter king here! Thanks for those posts.

Lughnasadh said:
What do you mean? I linked a tweet. Linking tweets are not against the rules. Just let it go man...
Click to expand...
Click to collapse
Nobody wants to connect to some crap site like that.

96carboard said:
Nobody wants to connect to some crap site like that.
Click to expand...
Click to collapse
Literally nobody cares except you. Why do you always have to be so toxic?

Related

Screen casting, or the lack thereof

Why the filth-flarn-flarn-filth can't i cast the screen of my Android to my (stock) Chromecast yet, as announced?
I have a S4 (jflte), listed as supported. Running latest Omniron nightly (and up to date SuperSU, but that shouldn't matter), and i tried the following;
- update CC app to 1.7.4 from Android File Host
- update gapps to 20140708 and then to 20140716 in the hope Play Services would fix it
- reboot and factory reset chromecast until my fingers bled
- edited build.prop to appear as a hammerhead device, as advised by @murdoch1 in a different thread
- uninstalled CC app, rebooted
- re-installed Playstore version of CC app (also 1.7.4, now)
Please advise!
SCM020 said:
Why the filth-flarn-flarn-filth can't i cast the screen of my Android to my (stock) Chromecast yet, as announced?
I have a S4 (jflte), listed as supported. Running latest Omniron nightly (and up to date SuperSU, but that shouldn't matter), and i tried the following;
- update CC app to 1.7.4 from Android File Host
- update gapps to 20140708 and then to 20140716 in the hope Play Services would fix it
- reboot and factory reset chromecast until my fingers bled
- edited build.prop to appear as a hammerhead device, as advised by @murdoch1 in a different thread
- uninstalled CC app, rebooted
- re-installed Playstore version of CC app (also 1.7.4, now)
Please advise!
Click to expand...
Click to collapse
I don't know much about Omniron but all ROMs have things that have been removed/are missing, because the developer thought it makes the rom better/faster and they might have removed something with the functionality. Have you tried testing from a different rom? Maybe a TW ROM?
Znomon said:
I don't know much about Omniron but all ROMs have things that have been removed/are missing, because the developer thought it makes the rom better/faster and they might have removed something with the functionality. Have you tried testing from a different rom? Maybe a TW ROM?
Click to expand...
Click to collapse
That, i have not. didn't think that would be related, because the casting is initiated from the CC app and not from System>Display.
And i've been on Omni since the first official release for jflte.
Edit. I seriously had to look up what you ment by TW:silly:. If that what it takes i'll live without...
Most likely it's something to do with your phone's ROM. Like Miracast, Chromecast screen casting is dependent on both the device itself and the ROM, and it might depend on kernel/bootloader too. We don't know exactly what hardware/software components Google has leveraged to make this happen.
The only 100% guaranteed working configurations consist of:
Supported phone/tablet
Stock ROM on phone/tablet (root or not shouldn't matter)
Build 17xxx or newer on Chromecast (stock or rooted shouldn't matter as long as build is proper version)
Updated Google Play Services
Chromecast 1.7.4 app (not required in some cases)
SCM020 said:
Edit. I seriously had to look up what you ment by TW. If that what it takes i'll live without...
Click to expand...
Click to collapse
For the rest of the class, TW = TouchWiz = Samsung stock ROM (took me a while to figure that out too )
SCM020 said:
Why the filth-flarn-flarn-filth can't i cast the screen of my Android to my (stock) Chromecast yet, as announced?
I have a S4 (jflte), listed as supported. Running latest Omniron nightly (and up to date SuperSU, but that shouldn't matter), and i tried the following;
- update CC app to 1.7.4 from Android File Host
- update gapps to 20140708 and then to 20140716 in the hope Play Services would fix it
- reboot and factory reset chromecast until my fingers bled
- edited build.prop to appear as a hammerhead device, as advised by @murdoch1 in a different thread
- uninstalled CC app, rebooted
- re-installed Playstore version of CC app (also 1.7.4, now)
Please advise!
Click to expand...
Click to collapse
Try mirrorenabler http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
hwong96 said:
Try mirrorenabler http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Click to expand...
Click to collapse
That mysteriously fixed it somehow. Thank you!!
SCM020 said:
That, i have not. didn't think that would be related, because the casting is initiated from the CC app and not from System>Display.
And i've been on Omni since the first official release for jflte.
Edit. I seriously had to look up what you ment by TW:silly:. If that what it takes i'll live without...
Click to expand...
Click to collapse
bhiga said:
Most likely it's something to do with your phone's ROM. Like Miracast, Chromecast screen casting is dependent on both the device itself and the ROM, and it might depend on kernel/bootloader too. We don't know exactly what hardware/software components Google has leveraged to make this happen.
The only 100% guaranteed working configurations consist of:
Supported phone/tablet
Stock ROM on phone/tablet (root or not shouldn't matter)
Build 17xxx or newer on Chromecast (stock or rooted shouldn't matter as long as build is proper version)
Updated Google Play Services
Chromecast 1.7.4 app (not required in some cases)
For the rest of the class, TW = TouchWiz = Samsung stock ROM (took me a while to figure that out too )
Click to expand...
Click to collapse
I apologize to both of you, forgot I was in the Chromecast Thread and not a Samsung device thread, Touchwiz(TW) is thrown around and just expected to be understood over there. I forgot to change my lingo when I enter into the real world...
Znomon said:
I apologize to both of you, forgot I was in the Chromecast Thread and not a Samsung device thread, Touchwiz(TW) is thrown around and just expected to be understood over there. I forgot to change my lingo when I enter into the real world...
Click to expand...
Click to collapse
Haha no worries, my brain just kept going to Time Warner and thought "they're taking over cell phones now?? " It's all good.
Znomon said:
I apologize to both of you, forgot I was in the Chromecast Thread and not a Samsung device thread, Touchwiz(TW) is thrown around and just expected to be understood over there. I forgot to change my lingo when I enter into the real world...
Click to expand...
Click to collapse
It's just that's the last ROM I'd consider. Would have understood PA or AOKP in a heartbeat
SCM020 said:
It's just that's the last ROM I'd consider. Would have understood PA or AOKP in a heartbeat
Click to expand...
Click to collapse
It's not as absurd as you would think. I own a Galaxy note II, and I have to use custom versions of Touchwiz so that I can get the S-pen to work, and all other "Note specific" applications.

Google phone/dialer app for Moto G5+

Hi,
i am perfectly fine with stock ROM and only one thing i would like to have beside. And it is Google phone app with capability to do search nearby places right from the phone app and the capability to see who actually calling behind unknown number.
I see some apks on apkmirror, but latest nonnexus apk is from 2016. So i rather ask here first. Do you guys tried this app and can confirm it has all the features i would like to have? Is it possible to have this app on our phone?
Do you have link to app for our device?
Thank you
https://www.apkmirror.com/uploads/?q=google-phone
I pulled this from OpenGapps. Flash the following Google dialer framework in TWRP and install it from the playstore... All the features work for me.
atrac17 said:
I pulled this from OpenGapps. Flash the following Google dialer framework in TWRP and install it from the playstore... All the features work for me.
Click to expand...
Click to collapse
Tried this without success. Running lineageos 8.0.
edit2: actually it doesn't work. Givs me a device not supported error
HatchetJackk said:
Tried this without success. Running lineageos 8.0.
edit2: actually it doesn't work. Givs me a device not supported error
Click to expand...
Click to collapse
Possible operator error. Also, this isn't designed for Oreo to begin with.
atrac17 said:
Possible operator error. Also, this isn't designed for Oreo to begin with.
Click to expand...
Click to collapse
How is it possible user error if it wasn't designed for Oreo? you never mentioned what os it was meant for. In any case, it did not, in fact, work for Oreo. However I did successfully use it for 7. Thanks for your work.
HatchetJackk said:
How is it possible user error if it wasn't designed for Oreo? you never mentioned what os it was meant for. In any case, it did not, in fact, work for Oreo. However I did successfully use it for 7. Thanks for your work.
Click to expand...
Click to collapse
At first, I was saying it's an operator error because it does work. Of course it doesn't work for Oreo it clearly states the date when I pulled the framework in May. The OP was asking to use an updated dialer in stock. I provided him the framework with the ability to do so.... I wouldn't specify why because I was answering the OP.
atrac17 said:
At first, I was saying it's an operator error because it does work. Of course it doesn't work for Oreo it clearly states the date when I pulled the framework in May. The OP was asking to use an updated dialer in stock. I provided him the framework with the ability to do so.... I wouldn't specify why because I was answering the OP.
Click to expand...
Click to collapse
Understood. Hopefully you can understand my side, as well. Again, thanks for your work.
PumaPerez said:
Hi,
i am perfectly fine with stock ROM and only one thing i would like to have beside. And it is Google phone app with capability to do search nearby places right from the phone app and the capability to see who actually calling behind unknown number.
I see some apks on apkmirror, but latest nonnexus apk is from 2016. So i rather ask here first. Do you guys tried this app and can confirm it has all the features i would like to have? Is it possible to have this app on our phone?
Do you have link to app for our device?
Thank you
https://www.apkmirror.com/uploads/?q=google-phone
Click to expand...
Click to collapse
You can check my thread.. I've ported the google dialer to non rooted devices
https://forum.xda-developers.com/mo...-161735957-t3636608/post73025780#post73025780
abhishekiswithyou said:
You can check my thread.. I've ported the google dialer to non rooted devices
https://forum.xda-developers.com/mo...-161735957-t3636608/post73025780#post73025780
Click to expand...
Click to collapse
How do I use this app, if I've a rooted device, pls assist, thanks :good:
talk2indrajit said:
How do I use this app, if I've a rooted device, pls assist, thanks :good:
Click to expand...
Click to collapse
same procedure as non rooted devices, Install as normal apk
I can confirm that it works on Moto G5 Plus (Sanders), stock rom, rooted with Magisk. Installed the dialer framework from the post by @atrac17 above, then phone apk (v.11) from here. (Play Market installation was still showing as unavailable for my device.) Then all I needed to do was to change the default phone app to google phone rather than Moto. Thanks for your help, guys. Couldn't figure it out by myself.
So freaking annoying we have to do this!.. Why on earth do we need Moto's dialer?!

Question Restore from Google Backup

Apologies if this has been answered already - I've searched and not found an answer.
I've just received my China version; having installed Google Play, is there any way to force a restore of a Google backup of my previous phone - it would be so much easier if it could (re)install my apps and settings in one go. I can't seem to find a way to do it.
Thanks
Someone correct me if I am wrong, but I think restoring from Google backups is only possible during the initial configuration. And China ROM doesn't have Google Play 'out of the box', it needs to be installed by the user. So I'm afraid it's not possible. But again, I could be wrong.
I would recommend unlocking the bootloader and flashing either the Global ROM or Xiaomi.EU. Preferably Xiaomi.EU because Global ROM is significantly behind with updates.
I couldn't test it but if you have installed google playstore and the google app basic android should be available. Then you can "restart" the inital setup via adb command:
adb shell am start -n com.google.android.setupwizard/.SetupWizardActivity
That should run the google setupwizard. I can't try it as I have already .eu rom on my phone installed and there it is available from scratch.
RoughNeck1971 said:
I couldn't test it but if you have installed google playstore and the google app basic android should be available. Then you can "restart" the inital setup via adb command:
adb shell am start -n com.google.android.setupwizard/.SetupWizardActivity
That should run the google setupwizard. I can't try it as I have already .eu rom on my phone installed and there it is available from scratch.
Click to expand...
Click to collapse
Brilliant, thank you. I will try that this evening, after I've got through the debloating
apd said:
Brilliant, thank you. I will try that this evening, after I've got through the debloating
Click to expand...
Click to collapse
I keep fingers crossed. I hope it works out.
RoughNeck1971 said:
I keep fingers crossed. I hope it works out.
Click to expand...
Click to collapse
If it doesn't, I only need to last as long as installing another ROM, but of course have to wait a week for that to occur!
RoughNeck1971 said:
I keep fingers crossed. I hope it works out.
Click to expand...
Click to collapse
As it happens I just tried it and got an error message:
Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardActivity }
Error type 3
Error: Activity class {com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity} does not exist.
If that means anything to you and if there's an easy answer, I'd be grateful for the help. If not, don't worry
Ah - this is what I was afraid off. With installing google playstore the google setup is still missing. You could try the Android Setup Wizard from Google from APK mirror. This should install the missing files. But I really can't confirm that this will work. In worst case you need to do a factory reset. Or you just install the .eu rom and all problems gone .
Android Setup 230.346018473 (arm64-v8a) (Android 10+) APK Download by Google LLC - APKMirror
Android Setup 230.346018473 (arm64-v8a) (Android 10+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
RoughNeck1971 said:
Ah - this is what I was afraid off. With installing google playstore the google setup is still missing. You could try the Android Setup Wizard from Google from APK mirror. This should install the missing files. But I really can't confirm that this will work. In worst case you need to do a factory reset. Or you just install the .eu rom and all problems gone .
Android Setup 230.346018473 (arm64-v8a) (Android 10+) APK Download by Google LLC - APKMirror
Android Setup 230.346018473 (arm64-v8a) (Android 10+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Click to expand...
Click to collapse
That got a bit further - i got this output:
Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardActivity }
But then nothing else happened!
apd said:
That got a bit further - i got this output:
Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardActivity }
But then nothing else happened!
Click to expand...
Click to collapse
Damn. So it is missing something more. Then I'm out of options to be honest. Maybe someone else has an additional idea how to get around that. Or you really think about switiching to .eu rom. Sorry.
RoughNeck1971 said:
Damn. So it is missing something more. Then I'm out of options to be honest. Maybe someone else has an additional idea how to get around that. Or you really think about switiching to .eu rom. Sorry.
Click to expand...
Click to collapse
Thanks so much for your help - it was certainly worth a try! I'll wait for the bootloader to be unlocked
use Xiaomi's mi mover app on the play store and you install it on both the previous phone and the new one, it will move everything over for you. I have been using the built-in migration app for all my phones, and they work just as well as google backup
Princevelyn said:
use Xiaomi's mi mover app on the play store and you install it on both the previous phone and the new one, it will move everything over for you. I have been using the built-in migration app for all my phones, and they work just as well as google backup
Click to expand...
Click to collapse
Thanks very much - that is the solution. I had tried to use Mi Mover before using Google backup/restore but it kept failing.
The trick was – as you say – to install a fresh version from the Google play store and not to use the version which was already installed on the phone from the xiaomi App Store.
Once I did that, it worked a treat!!
i haven't had good luck with google restore....mobiletrans has been a godsend
speedstream said:
i haven't had good luck with google restore....mobiletrans has been a godsend
Click to expand...
Click to collapse
Thanks - I may try that next time, although it's quite pricey at $40 per year or a bit more for an outright purchase

Question new information regarding custom or globalrom?

I wanted to ask if there is any new information regarding a global rom or a custom rom? I would definitely be flashing it right away.
Best hope for that will be when the S version is released. According to available information it is virtually identical to the X, so the firmware might be transferable.
can't wait!
Hopefully.
I’m not sure how things will go. I would much prefer working with aosp to get a booting gsi rom personally
TBH I've got the X working so well now that I don't really see a huge need for a new ROM. If someone gets it working and shows a benefit then...
Yes, of course it works and doesn't cause any problems, but I would like only the voice assistants from Google
and android auto, all the rest is ok
Android auto is dead in the game bro'
Are there any new advances?
i suppose nothing, there is trouble with Vivo and unsecure Boootloader. Nobody seems interested by solid and friendly solution to unlock then after port a rom on this baby !
lesscro said:
i suppose nothing, there is trouble with Vivo and unsecure Boootloader. Nobody seems interested by solid and friendly solution to unlock then after port a rom on this baby !
Click to expand...
Click to collapse
that's a shame. I would really appreciate a custom rom or at least a European supported rom
A multilingual ROM (like Global) who can be really adapted to our market can be nice. Anyway X Fold S is just a small update and not a global phone market.
My magisk module for Android Auto and Google Assistant should work on vivo X Fold too.
[MIX Fold 2][MAGISK] Global ROM-ify module collection [Add translations, Google Assistant, Android Auto]
I decided to create a module sharing thread here. If Magisk is enabled, all modules will continue to work after the OTA update. (use "Install to Inactive Slot" method) If Magisk is disabled, the module also loses its effectiveness. Add official...
forum.xda-developers.com
AndroPlus said:
My magisk module for Android Auto and Google Assistant should work on vivo X Fold too.
[MIX Fold 2][MAGISK] Global ROM-ify module collection [Add translations, Google Assistant, Android Auto]
I decided to create a module sharing thread here. If Magisk is enabled, all modules will continue to work after the OTA update. (use "Install to Inactive Slot" method) If Magisk is disabled, the module also loses its effectiveness. Add official...
forum.xda-developers.com
Click to expand...
Click to collapse
I can confirm this works perfectly Google assistant works.
Haven't tried Android auto but I would be stunned if it didn't work
domineus said:
I can confirm this works perfectly Google assistant works.
Haven't tried Android auto but I would be stunned if it didn't work
Click to expand...
Click to collapse
You install Magisk ? With boot.img did you use ?
I install magisk and he ask me to choose an img...
I use magisk long time ago on custom rom, it was more easy...
I need to download official rom and extract boot.img ?
lesscro said:
You install Magisk ? With boot.img did you use ?
I install magisk and he ask me to choose an img...
I use magisk long time ago on custom rom, it was more easy...
I need to download official rom and extract boot.img ?
Click to expand...
Click to collapse
You can extract boot.img in two ways:
1. What you described
2. Use DSU Loader and pull the file out using the following commands in adb:
adb shell
su
dd if=/dev/block/by-name/boot of=/data/local/tmp/boot.img
chown shell.shell /data/local/tmp/boot.img
(After the end of adb shell)adb pull /data/local/tmp/boot.img
Click to expand...
Click to collapse
RR-99 said:
TBH I've got the X working so well now that I don't really see a huge need for a new ROM. If someone gets it working and shows a benefit then...
Click to expand...
Click to collapse
Can you share your experience with us as to what you did to get rid of Chinese and bloat sw?
domineus said:
You can extract boot.img in two ways:
1. What you described
2. Use DSU Loader and pull the file out using the following commands in adb:
Click to expand...
Click to collapse
Thx for your feedback.
Does this install will wipe all data ?
lesscro said:
Thx for your feedback.
Does this install will wipe all data ?
Click to expand...
Click to collapse
When I rooted it didn’t. When I BLU I think it did
kanf77 said:
Can you share your experience with us as to what you did to get rid of Chinese and bloat sw?
Click to expand...
Click to collapse
I haven't removed any Chinese bloatware, since I didn't find it was slowing down the phone or using too much memory. Quite happy to have it just sit there instead of risking removing too much.

Question APK Install Issue

When I am installing APKs from any file manager it's gives me an error App not installed as app isn't compatible with your phone but when I install same app from Google Playstore it get installed with out any issues.
Any idea why?
Screenshot attached.
ThnX
telepathy007 said:
When I am installing APKs from any file manager it's gives me an error App not installed as app isn't compatible with your phone but when I install same app from Google Playstore it get installed with out any issues.
Any idea why?
Screenshot attached.
ThnX
Click to expand...
Click to collapse
It's possible you downloaded the wrong version of the app. If you look at various apps on APKMirror, such as Google Photos, there are many different variants available. You want to use an arm64-v8a version, preferably "nodpi" as that should work with all devices.
telepathy007 said:
When I am installing APKs from any file manager it's gives me an error App not installed as app isn't compatible with your phone but when I install same app from Google Playstore it get installed with out any issues.
Any idea why?
Screenshot attached.
ThnX
Click to expand...
Click to collapse
For some reason Google made an absurd last minute decision to make 32bit arm apps incompatible with the Pixel 7 at the software level. There is a workaround which I can confirm does work, as I am using it, but to get it to work if you have already rooted your phone with magisk you will have to backup your data and then do a wipe of the device.
The workaround is at this thread
[Magisk] Magisk Zygote64_32: Enabling 32-bit Support For Apps
The 32-bit apps are back! https://streamable.com/hb1dqp Synopsis The Pixel 7 line is Google's first "64-bit only" phones, along with being the highest profile release of a 64-bit only device so far. The device uses the Tensor G2 (GS201), which is...
forum.xda-developers.com
t3chwizard said:
For some reason Google made an absurd last minute decision to make 32bit arm apps incompatible with the Pixel 7 at the software level. There is a workaround which I can confirm does work, as I am using it, but to get it to work if you have already rooted your phone with magisk you will have to backup your data and then do a wipe of the device.
The workaround is at this thread
[Magisk] Magisk Zygote64_32: Enabling 32-bit Support For Apps
The 32-bit apps are back! https://streamable.com/hb1dqp Synopsis The Pixel 7 line is Google's first "64-bit only" phones, along with being the highest profile release of a 64-bit only device so far. The device uses the Tensor G2 (GS201), which is...
forum.xda-developers.com
Click to expand...
Click to collapse
I am trying 64bit versions apk only but those are mod apks for games and I think modded apk Google might have banned installing on Pixel 7/7 Pro
telepathy007 said:
When I am installing APKs from any file manager it's gives me an error App not installed as app isn't compatible with your phone but when I install same app from Google Playstore it get installed with out any issues.
Click to expand...
Click to collapse
There's a new restriction with Android 13 for sideloaded apps not from Play Store, F-Droid and maybe other stores. I ran into it with an apk from Github. Your error doesn't relate but installing from a file manager is a symptom. In any case, if you think this restriction could be part of your problem search ACCESS_RESTRICTED_SETTINGS for a possible workaround.
@Nnik345 here you can find an answer and imo you should ask related questions better here instead of opening a new thread.

Categories

Resources