Related
So has anyone noticed that the Google Camera app is no longer visible in the play store? It may just be in the USA where I am, but the only way I can find the Google Camera app, is when I'm behind a VPN for another country. Anyone else notice this or know why?
I read something about this the other day. It has disappeared from the Play Store, it's not just in the US. You can still find it on APKMirror.
https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera&hl=en
The direct link still works, but unless you own a Nexus 5, 6, 9, 5X or 6P, you will not be able to install it as Google has restricted the app to those devices. Further, you can not search for the app on the PC or the Play Store, which I believe means the link's only purpose is to allow for updating the app for the Nexus line. It's still possible to download it from APK Mirror, but for devices other than the five mentioned, it probably will report an older version, if it installs at all.
The real question is, what is Google planning here? We just don't know.
Strephon Alkhalikoi said:
https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera&hl=en
The direct link still works, but unless you own a Nexus 5, 6, 9, 5X or 6P, you will not be able to install it as Google has restricted the app to those devices. Further, you can not search for the app on the PC or the Play Store, which I believe means the link's only purpose is to allow for updating the app for the Nexus line. It's still possible to download it from APK Mirror, but for devices other than the five mentioned, it probably will report an older version, if it installs at all.
The real question is, what is Google planning here? We just don't know.
Click to expand...
Click to collapse
No idea! What's weird is that I saw people on Reddit saying they were from Canada and they were able to search the app in the playstore, and after using a VPN and spoofing my location, I was able to search it in chrome as well! I'm not sure what they're doing, but it's really strange!
could be a problem of playstore.. this has existed for the past few weeks now.. but searching for the app on google still routes you to the playstore.. wonder why app cant be visible on the playstore itself
There is one other app they have with this behavior: Google Play Services. You can search for com.android.google.gms in the Play Store on both PC and device. However it won't show up, and you have to use a direct link to see it. Unlike Google Camera however, Play Services is for every phone.
Hopefully it's a mistake on Google's part and it will be fixed soon.
For what it's worth, today on nexus 6 with pico open gapps, and AICP 13 (8.0 Oreo), the above link gave "not available in your country" (USA) in browser, but copying the link in the browser had an option/link to play store, which did work, and after install Gcamera works! I was missing photosphere, so thanks!
Hello,
I installed Android Things IoT for Raspberry Pi 3 from:
developer.android.com/things/hardware/raspberrypi.html
This is an amazing system that I can add many app to, and I can use GPIO too, for starters, you need to use the adb tool, but I've installed a launcher (link below) and now I can see all the screens as a Device Android normal.
w w w .apkmirror.com/apk/teslacoil-software/nova-launcher/nova-launcher-5-0-3-release/nova-launcher-5-0-3-android-apk-download/
But the Google Play Store that I installed does not work, I believe some app is missing and this is bad for me, I am not able to know which app I have to install.
You can help?
Would it be possible to make an image with the application needed to run the Play Store?
Thank you!
rtek1000 said:
Hello,
I installed Android Things IoT for Raspberry Pi 3 from:
developer.android.com/things/hardware/raspberrypi.html
This is an amazing system that I can add many app to, and I can use GPIO too, for starters, you need to use the adb tool, but I've installed a launcher (link below) and now I can see all the screens as a Device Android normal.
w w w .apkmirror.com/apk/teslacoil-software/nova-launcher/nova-launcher-5-0-3-release/nova-launcher-5-0-3-android-apk-download/
But the Google Play Store that I installed does not work, I believe some app is missing and this is bad for me, I am not able to know which app I have to install.
You can help?
Would it be possible to make an image with the application needed to run the Play Store?
Thank you!
Click to expand...
Click to collapse
I haven't done this yet, but I'm curious if it's like adding Google to fire tablets:
Google Account Manager
http://www.apkmirror.com/apk/google-...count-manager/*
Google Services Framework
http://www.apkmirror.com/apk/google-...ces-framework/
Google Play Services
http://www.apkmirror.com/apk/google-...play-services/
Google Play Store
http://www.apkmirror.com/apk/google-...le-play-store/
Just thinking out loud. Someone more knowledgeable should chime in.
Sent from my Nexus 5X using Tapatalk
I don't have the link, but I recall comming across something where they used GAPPS pico to install the Playstore.
https://github.com/opengapps/opengapps/wiki/Pico-Package
As far as I can tell, this should install the PlayStore, but I think you need to use the GAPPS install script to copy the apps onto the SD card, then put it back in the RP I
BTW. I installed the Android Things RPI image a few days ago, but as you noted, it doesnt have a launcher, so its not possible to do anything, apart from display the popup about the hardware details
---------- Post added at 08:58 AM ---------- Previous post was at 08:39 AM ----------
BTW.
I tried installing the Nova package, and can now see the settings app.
I tried enabling the developer options but when I try to go into them, the settings app keeps crashing.
I presume this is not something that Google envisioned people doing with this build of android
Edit 2.
The display is very slow. I presume this is because the GPU is not being used.
Unless there was eventually a build of Android Things for RPI that used the GPU, its not going to be a particularly usable system in conventional terms.
Edit 3.
You may like to try http://konstakang.com/devices/rpi3/ instead
trouble loading LineageOS 14.1 for starters lol
hello im new on here and have been using my raspberry pi 3 for mostly a retropie img .......using a class 10 Samsung 128gb for that and didn't want to format to try to see how the android works out...the card I loaded the LineageOS img may not be such dependable 64 gb card.... so did the normal format and win32 write .......the screen loads to the blue line with the circle going by but does not get passed that ...wish ive gotten farther but could this mean the card is not good enough?? or does it sound like another issue?? hope this the place to ask as im new here ....thanx
I upgraded from O to P, then rolled back to O after a few days of trying out P (have my own reasons, one of which is that of Magisk and the number of issues that I and others experienced/are experiencing on P).
Before the upgrade, I received a Play Store update for the Nokia Camera that was at v90.9.xx at the time. It was working well with O despite issues here and there. Then I made the jump to P, which came with the v91.9.xx Nokia Camera.
Now that I rolled back to O with Sept 2018 patch level, I was surprised to find out that the Nokia Camera from the Play Store disappeared. I could no longer update the app that came with a v8.xxx. It is now marked as incompatible with my device. As a workaround, I sideloaded the latest v91.9.1130.40 available apk from apkmirror. It installed and ran normally but then would immediately FC after a few minutes. No amount of clearing appdata/cache would make it run on O without FCing. So I settled with the last version that ran without issues, v90.9.1125.10.
My question is, would anyone have any idea if HMD is removing support on O for future versions of the Nokia Camera starting with v91.xx?
In the app description it still says there for requirements a Nokia smartphone running at least Android O 8.0 and the apk, even though its target SDK is api28 (Pie), its minimum SDK is api26 (Oreo).
EDIT: Even though I'm using a gcam port for my shots, I would still like to have an updated stock cam on Oreo for its other features like bothies, PRO mode, and 16MP selfies ?. I plan on staying a little while longer on O. ?
I have updated to Pie among other reasons, for new camera software since I get use to on Nokia 6.1
miljenko said:
I have updated to Pie among other reasons, for new camera software since I get use to on Nokia 6.1
Click to expand...
Click to collapse
That's a valid point, but not quite helpful in my inquiry. The Nokia Camera SHOULD be made available to at least Oreo and later. There hasn't been a complete rollout of Pie in Nokia's entire device lineup, but the Play Stores marks the current version v91.9.1133.80 incompatible with Oreo, locking out devices that still have no Pie update available and denying updates and bug fixes to the stock camera.
braveheartleo said:
That's a valid point, but not quite helpful in my inquiry. The Nokia Camera SHOULD be made available to at least Oreo and later. There hasn't been a complete rollout of Pie in Nokia's entire device lineup, but the Play Stores marks the current version v91.9.1133.80 incompatible with Oreo, locking out devices that still have no Pie update available and denying updates and bug fixes to the stock camera.
Click to expand...
Click to collapse
But it is available on Play store for Nokia 6.1 2108 running Oreo.
braveheartleo said:
I upgraded from O to P, then rolled back to O after a few days of trying out P (have my own reasons, one of which is that of Magisk and the number of issues that I and others experienced/are experiencing on P).
Before the upgrade, I received a Play Store update for the Nokia Camera that was at v90.9.xx at the time. It was working well with O despite issues here and there. Then I made the jump to P, which came with the v91.9.xx Nokia Camera.
Now that I rolled back to O with Sept 2018 patch level, I was surprised to find out that the Nokia Camera from the Play Store disappeared. I could no longer update the app that came with a v8.xxx. It is now marked as incompatible with my device. As a workaround, I sideloaded the latest v91.9.1130.40 available apk from apkmirror. It installed and ran normally but then would immediately FC after a few minutes. No amount of clearing appdata/cache would make it run on O without FCing. So I settled with the last version that ran without issues, v90.9.1125.10.
My question is, would anyone have any idea if HMD is removing support on O for future versions of the Nokia Camera starting with v91.xx?
In the app description it still says there for requirements a Nokia smartphone running at least Android O 8.0 and the apk, even though its target SDK is api28 (Pie), its minimum SDK is api26 (Oreo).
EDIT: Even though I'm using a gcam port for my shots, I would still like to have an updated stock cam on Oreo for its other features like bothies, PRO mode, and 16MP selfies . I plan on staying a little while longer on O.
Click to expand...
Click to collapse
I am in the same shoes like you. I also want to stay on Oreo for some more time until they fix graphic glitches and some small bugs on Pie.
Last time I rolled back from Pie beta to Oreo, Nokia camera was also not showing on the Play store, and after a week or so, the update came...
We shall see about this time.
Btw. camera version you marked as one to be working, is also crashing for me, especially when I try to use the silly faces and masks from the top shortcuts...
miljenko said:
But it is available on Play store for Nokia 6.1 2108 running Oreo.
Click to expand...
Click to collapse
I'm surprised that it appears on a Nokia 6.1 2018 running Oreo. Does the v91.9.1133.80 work flawlessly with it without crashing? Are the AR stickers working as well? (Though I have my doubts about that, I don't know if AR is supported in that device, lemme know ?)
pujolsk said:
I am in the same shoes like you. I also want to stay on Oreo for some more time until they fix graphic glitches and some small bugs on Pie.
Last time I rolled back from Pie beta to Oreo, Nokia camera was also not showing on the Play store, and after a week or so, the update came...
We shall see about this time.
Btw. camera version you marked as one to be working, is also crashing for me, especially when I try to use the silly faces and masks from the top shortcuts...
Click to expand...
Click to collapse
Hey thanks for dropping by. Regarding that crash with stickers on v90.9.1125.40 yes I experienced that as well and wrote it off as a bug ?, needing a fix. But that's not possible atm because Nokia Camera in the play store on on this phone is marked incompatible, at least on Oreo.
I too am thinking the same way as you, when issues with Pie iron out. The UI glitches I find inconvenient and distracts from the experience. More than that, Magisk is incompatible with Pie on this device, causing certain system functions to go missing, further making the experience unbearable ?. But I do like the improvements Pie brings to the table.
braveheartleo said:
I'm surprised that it appears on a Nokia 6.1 2018 running Oreo. Does the v91.9.1133.80 work flawlessly with it without crashing? Are the AR stickers working as well? (Though I have my doubts about that, I don't know if AR is supported in that device, lemme know ?)
Click to expand...
Click to collapse
Everything works normally, no glitches.
miljenko said:
Everything works normally, no glitches.
Click to expand...
Click to collapse
Thanks for the sitrep on that end. But here it's a different story. ?
Hmm this is weird. I never had the application available on the store for my Nokia 7 plus (O and P)
@braveheartleo : I have the same issue. TA-1046 September patch 8.1.0. The update was showing 1-2 weeks back. I had updated earlier (successfully) but downgraded because of the missing HDR option (autoHDR was not working effectively for me). So I disabled and re-enabled it, going back to factory version. The update was visible but for the last couple of weeks it's not appearing in play store at all.
I had tried to re-update a while back, but it would always get stuck after downloading about 84mb, exactly after downloading the app itself and before downloading "extra data" part that goes upto 150mb. I think its an obb file.
So a couple of days back I found an obb file, around 150mb inside Internal Storage/Android/obb/com.hmdglobal.camera2/.
I wasn't able to delete it, so I forcefully removed it root and went to retry the app update where I found it had disappeared. I obtained the play store url in google, opened it as a webpage, clicked the button to "show in play store".
The app appeared but showed as being incompatible with this device.
I have tried to sideload it (a while back when I could't update), it installs fine but FCs at certain modes (unfortunately I don't remember correctly). Seems I have to use factory one for now.
Gravemind2015 said:
@braveheartleo : I have the same issue. TA-1046 September patch 8.1.0. The update was showing 1-2 weeks back. I had updated earlier (successfully) but downgraded because of the missing HDR option (autoHDR was not working effectively for me). So I disabled and re-enabled it, going back to factory version. The update was visible but for the last couple of weeks it's not appearing in play store at all.
I had tried to re-update a while back, but it would always get stuck after downloading about 84mb, exactly after downloading the app itself and before downloading "extra data" part that goes upto 150mb. I think its an obb file.
So a couple of days back I found an obb file, around 150mb inside Internal Storage/Android/obb/com.hmdglobal.camera2/.
I wasn't able to delete it, so I forcefully removed it root and went to retry the app update where I found it had disappeared. I obtained the play store url in google, opened it as a webpage, clicked the button to "show in play store".
The app appeared but showed as being incompatible with this device.
I have tried to sideload it (a while back when I could't update), it installs fine but FCs at certain modes (unfortunately I don't remember correctly). Seems I have to use factory one for now.
Click to expand...
Click to collapse
Thanks for chiming in. ?
We have the same experience regarding the stock cam. Although I haven't been using stock for taking photos, I too noticed the FCs you have seen. Regarding manual HDR toggle missing from v90.x onwards, I found an earlier version on apkmirror that has HDR toggle in the UI, v85.9.1124.31. Perhaps you can try that out as a stop-gap to the issues we are getting starting with v90.x
One other here commented that the latest Play Store version is compatible with Nokia 6.1 on Oreo, but I wonder how compatible it is in practical terms (no FCs, etc.).
braveheartleo said:
Thanks for chiming in. [emoji16]
We have the same experience regarding the stock cam. Although I haven't been using stock for taking photos, I too noticed the FCs you have seen. Regarding manual HDR toggle missing from v90.x onwards, I found an earlier version on apkmirror that has HDR toggle in the UI, v85.9.1124.31. Perhaps you can try that out as a stop-gap to the issues we are getting starting with v90.x
One other here commented that the latest Play Store version is compatible with Nokia 6.1 on Oreo, but I wonder how compatible it is in practical terms (no FCs, etc.).
Click to expand...
Click to collapse
Apparantly a new camera version has been uploaded to Google play (here) with some new features. Unfortunately, it's still showing as incompatible. Not just for us, but folks on Nokia 8 and Nokia 6.1 also confirmed the same in a telegram group.
HMD is truly going bananas and nuts.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
HMD is truly going bananas and nuts.
Click to expand...
Click to collapse
"going"??????? :laugh:
Gravemind2015 said:
Apparantly a new camera version has been uploaded to Google play (here) with some new features. Unfortunately, it's still showing as incompatible. Not just for us, but folks on Nokia 8 and Nokia 6.1 also confirmed the same in a telegram group.
HMD is truly going bananas and nuts.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Speaking of, have you noticed how the Nokia Mobile Support app quickly jumped from one version to another (it's now at 2.0.9 as of this writing, starting from 2.0.3)? Sure, quick fix releases are commendable, but then you start to wonder how QC for software development is on their end.
divvykev said:
"going"??????? :laugh:
Click to expand...
Click to collapse
At this point, it should be safe to say that they've "gone" now :laugh:, with all the bugs people are experiencing on Pie (3.22C), their unstoppable streak on releasing new phones (and now the change to confusing global naming scheme as well), and missed targets on timely releases of monthly updates, resulting in a release that is rushed (and buggy compared to the betas). :laugh:
braveheartleo said:
Speaking of, have you noticed how the Nokia Mobile Support app quickly jumped from one version to another (it's now at 2.0.9 as of this writing, starting from 2.0.3)? Sure, quick fix releases are commendable, but then you start to wonder how QC for software development is on their end.
At this point, it should be safe to say that they've "gone" now :laugh:, with all the bugs people are experiencing on Pie (3.22C), their unstoppable streak on releasing new phones (and now the change to confusing global naming scheme as well), and missed targets on timely releases of monthly updates, resulting in a release that is rushed (and buggy compared to the betas). :laugh:
Click to expand...
Click to collapse
Yeah exactly.
Gravemind2015 said:
Yeah exactly.
Click to expand...
Click to collapse
Love it when they do that.
got the same incompatible thing on the play store with 2 nokia 7 plus... but its installed. lol
Some problem with novatek-07 displays , what happens with nokia hmd ??
Really they have to repair all novatek displays ? Cant fix it wiyh software ?
This forum is meant for people who are getting locked out of their accounts due to "3rd Party Plugins or Applications"
We need to stop this from happening so share your experiences and thoughts on the matter.
I have 2 devices: a Nexus 6P running Pie (Pixel Experience) and a Pixel 3XL on the stock Pie rom. Both are rooted with Magisk Canary builds and both have Magisk Hide turned on. Snapchat never detects root on the Nexus but ALWAYS detects it on the Pixel. I've even repackaged Magisk on the Pixel but that doesn't help. I've read that it's easier for apps to detect root on A/B partition devices so maybe the newer, updated Snapchat apps have code to detect it. When I have time, I'll try an old version and see if it works...
Note that I don't believe Snapchat bans just by detecting root. It is detecting certain apps that are somehow triggering it. If you check the list of apps that you have given permission for superuser, it would be one of those. The app that I had that was triggering Snapchat was an app named app ops. I had downloaded it and just giving it permissions alone was getting me banned on Snapchat. I think this problem only affects users running Oreo or higher for whatever reason. I myself had an old phone running marshmallow with app ops and never experienced a ban. I don't think that any of the people reporting the problem had anything lower than Oreo. If you have somehow discovered the app causing your problems, uninstalling it may not fix your problem. I had to wipe my phone in order to fix it because I was still receiving bans despite uninstalling the app that was causing my problems
I've never installed app ops so that's not my problem.
As for A/B partitioning, I'm on a Samsung galaxy Note 8 and it didn't come out with this on my device so yeh ?
The main thing I found out that I had to do, was repackage the manager and I haven't been banned for the last 4 days
I am on the S8 plus and was locked out for 12 hours before. Snapchat continued to lock me out even when I fully uninstalled magisk. I decided to clean install a different Rom which seemed to do the trick. A month later I decided to go back to my original Rom and guess what? Can't even login coz of some mod I think.
So I would say it depends on what mods you have installed yourself or packaged with the custom ROM.
Snapchat ban
I have same problem. Yesterday they gave me ban but i was unbanned with their site. But today they give me one more ban but now is for 24h ... anyone know how to fix snap or maybe hide root? S7 9.0 blackdiamond v3
Downloaded an early January 2019 version of Snapchat and signed up for a new account on my Pixel 3XL. All was good at first then I closed the app. When I tried to sign back in, I got the "problem connecting to server" error which requires an update to the most current version. I updated and after just a few hours, I got the "12 hour account locked" message for "3rd party apps". I've had Magisk Manager repackaged but that obviously didn't help. BTW, I have not repackaged Magisk on my Nexus 6P and it's still works. I found a comment by a user of the Bitmoji app (which I use on my Pixel but not my Nexus) that reported his Snapchat was locked by this app so I uninstalled it. We'll see how it goes when my 12 hour ban is up...
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
newkydawg said:
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
Click to expand...
Click to collapse
What apps have you given superuser? The app causing you problems is likely in that list
I had this happen before to me, i uninstalled edXposed and i was able to use snapchat even while on a 24 hour ban
iMystic said:
What apps have you given superuser? The app causing you problems is likely in that list
Click to expand...
Click to collapse
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
newkydawg said:
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
Click to expand...
Click to collapse
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
iMystic said:
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
Click to expand...
Click to collapse
Both my Pixel 3XL and Nexus 6P are running Android 9 rooted with Magisk Canary (19005). Both have the same apps with superuser rights. All this to say that Snapchat was working fine on both for months and for about the last 6 weeks, my Pixel 3 XL's account gets locked and my Nexus 6P does not.
Thanks for trying to help and glad you figured your problem out.
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
There are all the reasons why i purely stopping to use Snapchat, and also due to the fact that the application is so badly optimized for Android (even since the complete redesign of the application), in the end considering my use so irregular, I just uninstalled it, so no problem.
The time of Snapprefs and Snaptools was fun and funny, and especially less vicious as a concept than the basic one.
The good old days, but all good things must come to an end.
Rom said:
snip
Click to expand...
Click to collapse
It's what happens when a company becomes complacent and puts more effort into blocking modifications instead improving their terrible app.
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
I have got a problem, I have a Nokia 7 Plus, stock fw no changes at all!
And I keep getting banned... Support is a joke, I just get automatic replies...
The only reason i may have for getting bans is if snap scans the sd card, where I have magisk and roms files from other devices...
Any tips ???
newkydawg said:
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
Click to expand...
Click to collapse
I tried to follow the instructions but snapchat keeps saying there was a connection problem with the server.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
Does this mean that I can't use energized adblock magisk module? Do I have to use only the Snapchat adblock magisk module that you linked for any kind of adblocking on the device.
Thanks!
So I just upgraded my Nexus 6 from stock 7.1.1 to LineageOS 15.1 (Android 8.1). The installation went very smoothly and the phone feels like new. I spent hours getting the apps set up and I started to notice that some of the apps didn't get reinstalled automatically. Then I realized that Netflix never got reinstalled... no worry, I'll just go install it. Couldn't find it in the play store, then I found this url: https://help.netflix.com/en/node/12983 which first has you check the play store for certification. Mine says "Device is not certified". Is this expected? I must be missing a host of various apps from the play store because of this. I googled a bit and searched the Nexus 6 forums here for certification and certified but couldn't find anything useful for Nexus 6 phones that end up with this message.
The netflix help page instructs you to manually install the app at the end. I tried doing that and when I launch it, it reports "This device is not supported by the app" and closes. So I guess I'm SOL? The weird thing is my wife's phone is a Samsung S5 and it's been running LOS for a long time, 15.1 up until about a month ago then upgraded to 16. I've been running netflix on it from the play store forever. I've used netflix on my Nexus with 7.1.1 before I wiped it. How do I get it working again? I'm wondering if I go to LOS 16 which I guess I *could* try...
Any suggestions?? Can I spoof the play store so it works somehow?
I've done some more googling and I found these pages:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
I put my GSF Device-ID into this page: https://www.google.com/android/uncertified/ and I'm still unable to find netflix in the play store. Am I screwed?
Is everyone who uses Lineage OS on their Nexus 6 unable to use Netflix and other certified-only apps?
spikeygg said:
I've done some more googling and I found these pages:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
I put my GSF Device-ID into this page: https://www.google.com/android/uncertified/ and I'm still unable to find netflix in the play store. Am I screwed?
Is everyone who uses Lineage OS on their Nexus 6 unable to use Netflix and other certified-only apps?
Click to expand...
Click to collapse
From my experience, initially the playstore wont let you install netflix after a fresh install but it has happened numerous times where I go back into the playstore later or after clearing playstore data that it becomes available. I have never used lineage though on our phones. Both our phones are running CrDroid Pie Unofficial and Netflix works fine but after the initial clean flash its not downloadable immediately from the Playstore but does become available either after some reboots and/or wiping playstore data.
I got it worked out. I needed Magisk. Very nice solution to this issue.
spikeygg said:
I got it worked out. I needed Magisk. Very nice solution to this issue.
Click to expand...
Click to collapse
hey can you please share the solution I'm also facing same problem after updating my firmware on oppo a15s
MAmeen said:
hey can you please share the solution I'm also facing same problem after updating my firmware on oppo a15s
Click to expand...
Click to collapse
The solution is what I posted above: "Magisk". Really sorry I don't have more details for you -- that post was from 2019 and I've since upgraded to a different phone. Unfortunately, my Nexus 6 broke. I can scarcely remember what happened yesterday let alone from several years ago. What I do recall is that side-loading Magisk gives you controls to override some of the underlying restrictions. You should install it and play around with it if you're trying to get this to work.