Related
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
app is good. i got it on my op3 stock and it works fine. looks like its an rom related problem.
doesn't work on my OnePlus 2 with RR 7.1.1
sasanksai said:
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
Click to expand...
Click to collapse
had the same issue , turns out it's failing a safetynet issue .
install magisk SU to pass safetynet issue and it should work fine.
See my sig, works with that system.
pawanraju said:
had the same issue , turns out it's failing a safetynet issue .
install magisk SU to pass safetynet issue and it should work fine.
Click to expand...
Click to collapse
Yes did that too. My magisk passed safetynet also i tired hiding magisk for mario. Didn't help tho
sasanksai said:
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
Click to expand...
Click to collapse
Sam here
its a problem with supersu root, if you use Magisk (you can hide it inside official app) won't have problems. I can play to Pokemon GO and SM Run without problem using it
MasterJack1697 said:
Sam here
Click to expand...
Click to collapse
enter in Magisk app - Settings - Magisk Hide
enable it and enjoy the game
Spector_Prophet said:
its a problem with supersu root, if you use Magisk (you can hide it inside official app) won't have problems. I can play to Pokemon GO and SM Run without problem using it
enter in Magisk app - Settings - Magisk Hide
enable it and enjoy the game
Click to expand...
Click to collapse
Same with that, doesn't work..
I think it would be interesting to kow if ppl who say it fails to work use OxygenOS or something else. My configuration works for PKMN Go and Mario Run without ANY problems at all.
ManuBBXX said:
Same with that, doesn't work..
Click to expand...
Click to collapse
are you using custom rom? because some roms have root included and you manage it in developer options.
With Magisk configurated and included root turn off, you should play without problems
Spector_Prophet said:
are you using custom rom? because some roms have root included and you manage it in developer options.
With Magisk configurated and included root turn off, you should play without problems
Click to expand...
Click to collapse
I use latest BJRR RR from Eliminater, wich includes by default magisk
Rooted systemless with magisk, safetyCheck pass, magisk hide enabled !
ManuBBXX said:
I use latest BJRR RR from Eliminater, wich includes by default magisk
Rooted systemless with magisk, safetyCheck pass, magisk hide enabled !
Click to expand...
Click to collapse
ouch..... I haven't more ideas
hope someone can help you
How to install Magisk on RR 7.1.1?
Hi! I have a one plus one and I am running Lineage OS 14.1-20170130 (7.1.1) and I can't play aswell.
I get the red Nintendo splash screen and it closes.
Running latest lineage weekly with zenith EAS 004 kernel and magisk and no issues whatsoever, I was able to start up the game and make a profile and play without any craziness
Update the magisk to latest version11.6 ! It helped me....
Hope it helps you. Thanks!
Yep, just tried with magisk and it worked. I found it on this reddit just after my previous post. At the r/LineageOS subreddit (the name of the post is "Super Mario Run came out about minutes ago, but crashes on start (Kenzo)" ). (I can't post urls yet)
Doesn't work on latest RR with latest magisk, safetyCheck pass and hide too.
I was on my previous install with latest RR AND superSU
I dirty flashed the ROM to remove superSU and work root with magisk
Is dirty flash is enough to remove superSU ?
ManuBBXX said:
Same with that, doesn't work..
Click to expand...
Click to collapse
-Deleted-
Hi guys,
Since the last few days my snapchat keeps getting temporarily blocked, I'm on a SM-G960F (Galaxy S9_9.0_JULYSecurity) rooted with Magisk and flashed with latest Ambasadii Rom(19.0). The first 3 weeks using snapchat with root & custom rom there weren't any problems at all. Can somebody help me?
Grtzz
Koovah_SC said:
Hi guys,
Since the last few days my snapchat keeps getting temporarily blocked, I'm on a SM-G960F (Galaxy S9_9.0_JULYSecurity) rooted with Magisk and flashed with latest Ambasadii Rom(19.0). The first 3 weeks using snapchat with root & custom rom there weren't any problems at all. Can somebody help me?
Grtzz
Click to expand...
Click to collapse
A lot of people are having the same issue. Magisk Hide doesn't seem to work with the latest versions of Snapchat. No matter what you do you will keep getting locked out of your Snapchat account. I'm a bit of a NOOB when it comes to this stuff but here is what has worked for me so far. Firstly, you have to serve your penance. There's nothing you can do about that. My most recent ban was 2 weeks. When your access has been restored delete the Snapchat app. Download an older version of Snapchat from apkmirror.com and install it. Version 10.540.31 worked for me. **IMPORTANT** You must untick auto-update of the Snapchat app in Goggle Play. Hide the Snapchat app with Magisk and then hopefully you should be OK. It's only a workaround but it's the only solution I've come across that works. Having said that, it's only been several days but so far so good. If I get locked out again I'll let you know. Good luck.
bulky68 said:
A lot of people are having the same issue. Magisk Hide doesn't seem to work with the latest versions of Snapchat. No matter what you do you will keep getting locked out of your Snapchat account. I'm a bit of a NOOB when it comes to this stuff but here is what has worked for me so far. Firstly, you have to serve your penance. There's nothing you can do about that. My most recent ban was 2 weeks. When your access has been restored delete the Snapchat app. Download an older version of Snapchat from apkmirror.com and install it. Version 10.540.31 worked for me. **IMPORTANT** You must untick auto-update of the Snapchat app in Goggle Play. Hide the Snapchat app with Magisk and then hopefully you should be OK. It's only a workaround but it's the only solution I've come across that works. Having said that, it's only been several days but so far so good. If I get locked out again I'll let you know. Good luck.
Click to expand...
Click to collapse
Same issue here and Im on a SM-G960FD with lightROM v23 and magisk 19.3. I tried randomly with 10.60.5.0 but it didnt work. I will try with version 10.540.31 of snapchat when my 2 day ban is over.
It's been 2 weeks and Snapchat hasn't locked me out using my workaround. So far so good. :good::good:
How to use Snapchat with magisk (After Ban)
Koovah_SC said:
Hi guys,
Since the last few days my snapchat keeps getting temporarily blocked, I'm on a SM-G960F (Galaxy S9_9.0_JULYSecurity) rooted with Magisk and flashed with latest Ambasadii Rom(19.0). The first 3 weeks using snapchat with root & custom rom there weren't any problems at all. Can somebody help me?
Grtzz
Click to expand...
Click to collapse
bulky68 said:
A lot of people are having the same issue. Magisk Hide doesn't seem to work with the latest versions of Snapchat. No matter what you do you will keep getting locked out of your Snapchat account. I'm a bit of a NOOB when it comes to this stuff but here is what has worked for me so far. Firstly, you have to serve your penance. There's nothing you can do about that. My most recent ban was 2 weeks. When your access has been restored delete the Snapchat app. Download an older version of Snapchat from apkmirror.com and install it. Version 10.540.31 worked for me. **IMPORTANT** You must untick auto-update of the Snapchat app in Goggle Play. Hide the Snapchat app with Magisk and then hopefully you should be OK. It's only a workaround but it's the only solution I've come across that works. Having said that, it's only been several days but so far so good. If I get locked out again I'll let you know. Good luck.
Click to expand...
Click to collapse
drowsy_fish said:
Same issue here and Im on a SM-G960FD with lightROM v23 and magisk 19.3. I tried randomly with 10.60.5.0 but it didnt work. I will try with version 10.540.31 of snapchat when my 2 day ban is over.
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account :crying: and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
MODIFIED EXCLUSIVELY FOR MOTO G7 PLAY
WARNING
Do not try to install this via fastboot, remove the magisk, to remove just reinstall the Stock Rom
MAIN FEATURES
Root modified by Spaceminer
More speed
Added multiple apps
Several useless apps removed
Black theme automatically enabled in all supported applications
Gapps already installed
Notch fix
And more
DOES NOT WORK
Fingerprint
Automatic brightness
INSTALLATION INSTRUCTION
1. Download and extract
2. Put the GSI on your memory card
3. Restart your phone in Bootloader / Fastboot mode
4. Open fastboot on your computer
use the command: fastboot -w
use the command: fastboot boot twrp.img
5. TWRP: Install> Install image> Choose image file> Flash on the system
DOWNLOADS
TWRP by Spaceminer: https://mega.nz/#!roRzBCTK!THHq0VMWqgtowJNkY-Id3b9S9H9dhzsJhE83k0Kvt2k
GSI: https://www.drive.google.com/file/d/1000HaJJqMdGyOtEd7ribp4n5Eb9l-3my/view
Works great apart from when I make calls the microphone doesn't work...whatsapp calls are fine it only seems to be a problem on cellular!
When I select the image I get 4 options and it does not let me install with any
With this my G7 play stay 32bits or can change for 64 bits?
RafaelItape said:
With this my G7 play stay 32bits or can change for 64 bits?
Click to expand...
Click to collapse
until we get a 64 bit kernel, it'll stay 32. i want to build a 64 kernel cause i want to bring ubuntu touch to this phone, that requires a 64 bit boot image, if we are to use erfan's (only method for android 9 devices rn)
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
CFKod said:
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
Click to expand...
Click to collapse
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
BobbyBlunt said:
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
Click to expand...
Click to collapse
yup... sorry, forgot to post... I assumed it was after installing modules.
Lockscreen not work for me, in all gsi roms.
Only stock works.
rom works great, feels like a new phone.
model XT1952-4.
not working unfortunately is the FM radio.
based on the error message when trying to install FM apps, it looks like the kernel driver was not included in the rom?
I can deal with the fingerprint not working, it would be really nice to get the FM driver included so I don't have to use data.
Overall the phone is so much better with this rom, Thank You!!!!
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Thanks for all the work
Everything seems stable been using on daily driver for 2 days now. Only issue is bluetooth audio not working. I'm wondering if the Motorola face unlock app would work however current version isn't available.
gadolf said:
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Click to expand...
Click to collapse
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
XxLilJeepXx said:
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
Click to expand...
Click to collapse
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
workin on fixing phone
yashor said:
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Click to expand...
Click to collapse
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
XxLilJeepXx said:
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
Click to expand...
Click to collapse
Why not just boot into bootloader mode and fast boot stock firmware to recover your device ?
PoochyX said:
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
Click to expand...
Click to collapse
Hi,
From your experience which GSI is better for MOTO G7 Play 1952-2:
Havoc or Lineage ?
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
PoochyX said:
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
Click to expand...
Click to collapse
Thank you for your reply.
I favor stability and performance over Magisk.
In my case, do your recommend Lineage as my best option to try?
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on crackling
Official Download link:
LineageOS Downloads
115ek's test builds (for testers only)
Downloads
Recommended Google Apps package:
Open GApps (pico only)
Changelog:
Changes for crackling
Bug reports:
How to submit a bug report
Donate to support development:
Donate via PayPal to LineageOS
reserved
reserved2
The "old" Lineage 17.1 thread got lost during some xda server maintenance. It's not really clear to me what happened.
It couldn't be brought back for several weeks now, so I decided to create a new thread.
I'd also like to inform you that I'll provide some test builds here. Before merging bigger changes I'd like to ensure the builds are okay (not just for me).
It would be nice if some of you could test a bit. Only caveat: You won't be able to switch between test builds/official builds easily as different signature keys are used and a factory reset is needed (alternatively flashing a migration file could save you from resetting the device (more info)). However, these test builds are thought for interested persons only
You'll find the first test build here.
Changes:
switch to userspace lmkd (more info here)
It would be interesting if you experience any differences in memory management (how many apps can be opened in background, how fast is app switching, when are apps closed...).
And of course if the system is usable at all.
Recovery
Can the lineage-recovery.img do nandroid backups now that twrp can't?
petexd said:
Can the lineage-recovery.img do nandroid backups now that twrp can't?
Click to expand...
Click to collapse
Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.
115ek said:
Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.
Click to expand...
Click to collapse
I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).
petexd said:
I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).
Click to expand...
Click to collapse
What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.
Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.
Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.
115ek said:
What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.
Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.
Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.
Click to expand...
Click to collapse
Thanks for the info. That's exactly what's happening but I have no idea how to apply that patch. I don't really want to install an unoffical rom: that's how I discovered twrp wasn't working properly, testing one of my builds then hoping to go back to your offical from restore.
Any way I'm happy to wait for your next issue.
Thanks for doing a great job.
I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.
libove said:
I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.
Click to expand...
Click to collapse
Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.
Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.
Certification Status on 17.1
Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.
Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?
Thanks!
Must sideload, not enough space to push and install from local, I feel silly...
Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.
Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).
Anyway, many thanks!
-Jay
115ek said:
Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.
Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.
Click to expand...
Click to collapse
zappbrannigan62 said:
Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.
Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?
Thanks!
Click to expand...
Click to collapse
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;
https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr
didyou said:
Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;
https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr
Click to expand...
Click to collapse
Have you installed Gapps or MicroG on your system ?
Cerealekillers said:
Have you installed Gapps or MicroG on your system ?
Click to expand...
Click to collapse
Yes, installed pico GAPPS.
Works
115ek said:
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Click to expand...
Click to collapse
I flashed the latest nightly + pico gapps using TWRP and
everything is working beautifully
Playstore reports the device to be certified
So thanks a lot!
libove said:
Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.
Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).
Anyway, many thanks!
-Jay
Click to expand...
Click to collapse
115ek said:
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Click to expand...
Click to collapse
Can verify that my Play Store, on 17.1, reports my ridiculously modded Swift as certified without having to do anything to achieve that.
Sorry, I know I am a real dunderhead when it comes to these things and I apologise for such a basic question. But...
I have a Swift 2 X which is working on Oreo. If I replace this with LineageOS 17 do I have to do anything "fancy" to get Google Pay to work after I've installed LineageOS?
I've installed LineageOS on my Oppo R5 which doesn't have NFC so this can't use "Tap 'n' Pay" anyway. I've installed LineageOS on mine and my Wife's Nextbit Robin and Google Pay - "Tap 'n' Pay" - worked without doing anything more than install and go.
It's just that I do really like the facility of Google Pay and wouldn't want to lose that just for the sake of system wide dark mode.
Sorry again for being so dense as to not understand.
Hello,
I have a brand new device which has not officially been released yet. Therefore, there is no stock firmware image available or recovery image. Just wanted to get that out of the way. I could not remove a lot of the manufacturers bloatware because i could not root or port TWRP without a stock image or recovery image.
I stumbled onto Project Treble. I flashed phh treble and it worked. Well, I managed to get everything to work with some workarounds. The only thing I am having trouble with is when I install phh with gapps. After booting I get the "Your device is not Google certified" message repeatedly spammed.
The only workaround I have been able to get to work for the uncertified device message is to remove phh superuser. I have tried using the Google device registration page. It does not work for my device. I want to keep root so I can pull the recovery image and port TWRP for this device. Are there any other fixes that will work? In order to pick up in some of my games I think I need Google Play?
Thanks,
Rocky
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
LR7875 said:
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
Click to expand...
Click to collapse
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
bigroc2223 said:
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
Click to expand...
Click to collapse
No no no, you need to patch boot.img for magisk, not system. Go to www.apkmirror.com (app repository), search and download 'magisk ' app(that is magisk manager), click and install the downloaded .apk file, allow install from browser, and after installing use the app to patch the boot.img(search Google), and flash patched boot.
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
bigroc2223 said:
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
Click to expand...
Click to collapse
I am sorry to hear that.It is pretty much beyond what I can solve so I will try find similar threads.