Develop Bugs

Help with Gallery 3D

I recently tried out CM 7.1 and to my surprise the "Gallery 3D by Rayman50" force installed itself after i launched the market, now i cant remove it anymore. I went back to my previous rom (2.3.4 stock tmobile rooted) I did a fresh install ,wiped all system data, cache,etc... and as soon as i sign into market on the stock 2.3.4 rooted rom, the app is back on and installed. I even disabled auto synch and auto back up to prevent the install but it hasn't helped. I had the stock 2.3.4 rooted rom before and didnt have the issue, it started all after installing CM 7.1 a few days ago. Anyone else having this problem?
thanks

Not per se, but I'd guess that this is somehow connected to backing up your settings to your google account. So it's probably still set for automatic download (had this with different apps before).
I'd just let all apps install automatically via the android market and then uninstall it with titanium backup. When your device next syncs with your google account, it should remove the 3d gallery so this won't happen again. (You'd obviously have to activate auto-backup again for this to work)

greed2 said:
on JB CyanogenMod 10 gallery dont see photos
Click to expand...
Click to collapse
The OP said nothing about jellybean, and from your other posts seems you're post-padding.

version of gapps with least crashing in cm11 safestrap?

Don't remember for sure which version I flashed, but it was one of the accepted ones. I think probably one of the middle options. Anyhow, whenever the network changes, or at least when wifi connects, it gives two messages that google play services has stopped. Every time.
So I want a version that does not crash. Ever. If possible.
Thanks in advance.

open gapps stock 4.4 hasn't crashed for me yet.

(Guide) To Install Google Floating Dialler on Mi A1 without root or MOD

Hi Mi A1 Device Holders,
I was curious of Google Floating Dialler on my device running Android O. So tried a modded APK from one of the threads. However I couldn't install the mod on to my device when it was in Beta stage. After several attempts.
Now Google have released a new version v17 in which the floating bubble dialer is enabled by default. You may refer to the below link.
https://www.xda-developers.com/enable-google-dialer-floating-bubble-2/.
So I wanted to try it again and went to Playstore and it doesn't allow me to download. Tried downloading and installing from Apkmirror. However I couldn't install it.
But I managed to install it with a small tweak.
Here is the Guide:
1. Hold the Phone app Icon and Click App Info
2. Scroll down to Option Phone App. If it is showing YES, you will not be able to install the new app. So you need to change it NO.
Note: You will not be able to do it without another Dialler app installed on your phone. For this, I installed TrueCaller App and then changed it. You may try with other dialer apps.
3. Install the latest app downloaded from ApkMirror or the one attached below.
4. Again, hold the Phone app Icon and Click App Info and shift the Phone App from True Caller(in my case) to Phone app.
5. You are done.
Enjoy :good:
Hit a thanks if you like it
P.S:
I was using v16 which got automatically updated from Playstore from the previous version. On top of that I installed the V17. My device is not rooted and using stock os...and I find absolutely no issues or lag or whatsoever

well in my case i just installed it and it worked voilaa.... Thanks for link

Thanks for the APK. I was able to install but now I can't search for contacts using T9 dialer. I now need to manually tap the search bar on the top and type in the letters.
Even manually searching is really slow and delayed.
Any fix for this?

Edit: The problem goes away if I roll back to the default Phone app, but comes back once I reinstall the above Apk.
What's going on here?

Leong428 said:
Edit: The problem goes away if I roll back to the default Phone app, but comes back once I reinstall the above Apk.
What's going on here?
Click to expand...
Click to collapse
It's working fine with me.. I find no such issues. You may try clearing the cache/data of the app. See if it helps.

kamireddybhargav said:
It's working fine with me.. I find no such issues. You may try clearing the cache/data of the app. See if it helps.
Click to expand...
Click to collapse
I tried that but it didn't help. Any other ideas?

I figured out the issue! For some reason Google Phone v17 did not work well with Contacts v2.4.
T9 dialling was very slow to search the contacts (10-15 seconds).
I tried everything from reviewing permissions, clearing cache, removing accounts etc. But nothing worked.
Finally I decided to manually check apkmirror and update the Contacts app to v2.5 and presto! Reduced lag when using T9 dialling!!
There is still an ever so slight lag compared to when I roll back to the v13 Google Phone, but it's much more usable now. Hope this helps!

Leong428 said:
I figured out the issue! For some reason Google Phone v17 did not work well with Contacts v2.4.
T9 dialling was very slow to search the contacts (10-15 seconds).
I tried everything from reviewing permissions, clearing cache, removing accounts etc. But nothing worked.
Finally I decided to manually check apkmirror and update the Contacts app to v2.5 and presto! Reduced lag when using T9 dialling!!
There is still an ever so slight lag compared to when I roll back to the v13 Google Phone, but it's much more usable now. Hope this helps!
Click to expand...
Click to collapse
i tried this on my redmi note 4, but when i make a call, history is not logged in new phone app, only in the old one. any suggestions? i hate these gapps [emoji14]
Sent from my Redmi Note 4 using Tapatalk

Have you tried setting the new phone app as the default and disabled the old one?

I was using v16 on January stable build and all was fine then i downloaded apk of v17 from apk mirror and it was also working fine aftert that i changed my rom to new February beta and now after installing v17 when i open phone app a popup appears everytime with a message that this app is not compatible and calls may not work correctly. Even though app was working fine but that popup was irritating me so i modded my phones build prop to pixel xl 2 and now Phone app is compatible with my Mi A1 and i can see it in play store aswell ??????

I was using v16 which got automatically updated from Playstore from the previous version. On top of that I installed the V17 and I find absolutely no issues or lag without build prop changes. Moreover, my device is not rooted for your info...

Android Auto Broken for me since Oreo! Problem persists across OOS and Custom Roms!

I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,

Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!

Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.

Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.

captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?

Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.

UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.

Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.

Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.

That was the one thing that consistently worked for me. Which rom are you on?

PlayStore is unable to Update Chrome after MiUi12 updated in my Redmi note 8 pro.

Hello I'm umesh soni, from India
As i mentioned, my playstore is unable to update Chrome browser and its Plug-in (or whatever you call it) WebView, since I updated my phone to latest Android version 10.
I tried to clear Data and force stop, play Store, re-start my phone, clear cache... Every possible thing....
Also I tried to uninstall the chrome, but since chrome is my pre-installed primary browser so I cannot completely uninstall it, so when i tapped Uninstall button, basically it just uninstall the update and back to older version...
Even After doing this, the update button stays unresponsive, i tried to update via opening playstore.com from browser, and tried to update Chrome, and it also not worked.
So finally after everything i decided to download Apk file from other sources, (Apkmirror.com)
But this is not the solution..
Please tell me why only chrome & WebView is not updating, and rest of the app are working completely fine, and update when ever i want.
Please help me...
Thank you.

Kingofumesh17 said:
Hello I'm umesh soni, from India
As i mentioned, my playstore is unable to update Chrome browser and its Plug-in (or whatever you call it) WebView, since I updated my phone to latest Android version 10.
I tried to clear Data and force stop, play Store, re-start my phone, clear cache... Every possible thing....
Also I tried to uninstall the chrome, but since chrome is my pre-installed primary browser so I cannot completely uninstall it, so when i tapped Uninstall button, basically it just uninstall the update and back to older version...
Even After doing this, the update button stays unresponsive, i tried to update via opening playstore.com from browser, and tried to update Chrome, and it also not worked.
So finally after everything i decided to download Apk file from other sources, (Apkmirror.com)
But this is not the solution..
Please tell me why only chrome & WebView is not updating, and rest of the app are working completely fine, and update when ever i want.
Please help me...
Thank you.
Click to expand...
Click to collapse
Hi,
I have a Xiaomi Poco F3 and a Redmi Note 8 pro that are facing the same issue, I have investigated a bit more by doing an adb logcat on only the Poco F3, and I have found that the following error gets triggered when I try to update Chrome.
Code:
4-10 00:34:14.008 17140 17170 E Finsky : [993] tvh.apply(44): IQ::GROUP_INSTALL: Error validating group. Rejecting requests: [com.google.android.trichromelibrary, com.android.chrome]
04-10 00:34:14.008 17140 17170 E Finsky : com.google.android.finsky.installqueue.impl.preprocessor.GroupInstallValidator$InvalidGroupException: GROUP_INSTALL: Group com.google.android.trichromelibrary and com.google.android.trichromelibrary have overlapping module [com.google.android.trichromelibrary, com.android.chrome]
long backtrace from java
TLDR: Cannot install chrome update because group trichromelibrary and trichromelibrary are in conflict.
Yeah makes senses since this library exists already...thus it conflicts with itself.
I don't know why this check is only made under MIUI 12, and not LOS (Lineage OS roms for instance) because I could update chrome on LOS with no issue like this, this doesn't look like a Google Play Store issue but more a MIUI 12 issue.