Related
Many ROMs that are published on the ROMs forums, such as the unofficial CM13 one, tells Gapps (or Open Gapps) to be required.
I want to install a ROM such as the mentioned about without Gapps, can't I?
Yes you just have to flash the rom i think you know but just to be sur you won't have google play without gapps
Yes I know, I just want to go the F-Droid way.
Thanks
I'm using nijel8's Unofficial LineageOS 14.1 and am really pleased with it. My previous rom was the weekly Xiaomi.EU rom for Xiaomi Mi Max Helium.
When I updated my Xiaomi.EU Rom, I would reboot into recovery and then:
1. Backup > system/data/boot
2. Install new ROM.zip
3. Wipe > Advanced Wipe > Dalvik /ART Cache and Cache
4. Reboot.
Is it the same process with LineageOS 14.1? There are FIRMWARE.zips and I installed one during my initial installation of the rom. Do I need to updated the firmware again, then install the rom, or do I just skip it and install the ROM.zip?
I didn't think it was appropriate to litter the main thread with this question, so I'm hoping I get an answer here.
Thanks in advance.
Yep, same procedure + gapps, firmware update is up to you. You can skip it if you don't have problems but in general is good to be on the same firmware as the MIUI base.
nijel8 said:
Yep, same procedure + gapps, firmware update is up to you. You can skip it if you don't have problems but in general is good to be on the same firmware as the MIUI base.
Click to expand...
Click to collapse
OK. I will flash the new firmware and the rom update. Cheers!
But gapps? Can't I just leave the updating of Google stuff to the play store?
EDIT: I did some more Googling and now understand why. All is good. I backed up, flashed the most recent firmware just to be safe. Worked fine. Then I flashed the updated ROM and the Gapps I installed before and rebooted. Smooth as silk.
Is screen cast / Miracast working for you on this ROM?
nijel8 said:
Yep, same procedure + gapps, firmware update is up to you. You can skip it if you don't have problems but in general is good to be on the same firmware as the MIUI base.
Click to expand...
Click to collapse
sebr said:
Is screen cast / Miracast working for you on this ROM?
Click to expand...
Click to collapse
I don't use those features. Sorry.
Hi guys,
Hoping my noob self can get some guidance here.
Basically i followed this guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
But after doing so it seems that Magisk isnt working.
Is there anything i can do; installing a CROM, any work arrounds?
I've tried this as well but no avail: https://forum.xda-developers.com/apps/magisk/safetynet-fix-pass-safetynet-2017-07-17-t3637801
ChrisChan92 said:
Hi guys,
Hoping my noob self can get some guidance here.
Basically i followed this guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
But after doing so it seems that Magisk isnt working.
Is there anything i can do; installing a CROM, any work arrounds?
I've tried this as well but no avail: https://forum.xda-developers.com/apps/magisk/safetynet-fix-pass-safetynet-2017-07-17-t3637801
Click to expand...
Click to collapse
Google has just updated the play store, there is a topic on here with the commands you need to execute via adb or command prompt in order to get magisk working properly, but seems you already did that, what version of magisk and magisk manager are you using
sakumaxp said:
Google has just updated the play store, there is a topic on here with the commands you need to execute via adb or command prompt in order to get magisk working properly, but seems you already did that, what version of magisk and magisk manager are you using
Click to expand...
Click to collapse
I'm using Magisk v12.0 and Manager v5.05
Magisk 13.2 gives me a system could not be mounted error
ChrisChan92 said:
I'm using Magisk v12.0 and Manager v5.05
Magisk 13.2 gives me a system could not be mounted error
Click to expand...
Click to collapse
Then go into mount, check system then recheck it, that used to fix it for me
sakumaxp said:
Then go into mount, check system then recheck it, that used to fix it for me
Click to expand...
Click to collapse
I've tried it multiple times, even rebooting in between
The Pixel doesn't use the official version of Magisk so any instructions for how to get the official version working might not apply on the Pixel. For a while if you enabled core only mode in the unofficial version the Pixel would still pass Safety Net even though the official version had stopped working. I have no idea if this workaround still works or not since I went back to stock but if you haven't tried it yet its certainly worth a try. Since the official link for the unofficial Pixel version of Magisk is hosted in the Resurrection Remix rom thread and discussion of Magisk issues frequently goes on there as well you might want to check the later posts in the rom thread and see if there is updated info regarding unofficial Magisk.
jhs39 said:
The Pixel doesn't use the official version of Magisk so any instructions for how to get the official version working might not apply on the Pixel. For a while if you enabled core only mode in the unofficial version the Pixel would still pass Safety Net even though the official version had stopped working. I have no idea if this workaround still works or not since I went back to stock but if you haven't tried it yet its certainly worth a try. Since the official link for the unofficial Pixel version of Magisk is hosted in the Resurrection Remix rom thread and discussion of Magisk issues frequently goes on there as well you might want to check the later posts in the rom thread and see if there is updated info regarding unofficial Magisk.
Click to expand...
Click to collapse
Ressurection Remix is a custom rom? Do you know if it works with Pixel? Because i'm fine with installing custom rom its not a must for me to have stock
ChrisChan92 said:
Ressurection Remix is a custom rom? Do you know if it works with Pixel? Because i'm fine with installing custom rom its not a must for me to have stock
Click to expand...
Click to collapse
Resurrection Remix is a custom rom but there is no need to install it to use Unofficial Magisk. That's just where the official download link is hosted, probably because the dev has some link to that particular rom. But Unofficial Magisk is not included or integrated in any way into that rom--Magisk is downloaded and flashed separately from the rom and should work the same on that rom, a different custom rom or stock.
---------- Post added at 11:26 PM ---------- Previous post was at 11:18 PM ----------
As a side note there's nothing wrong with Resurrection Remix but if you did want to give a custom Rom a try I would personally recommend Dirty Unicorns or Screwed. They aren't hosted on XDA but don't let that bother you. A quick Google search will turn up where they are officially hosted and in my personal experience they are easily the best custom Roms available for the Pixel. That said, I went back to stock so I could try Android O and have stayed on stock so far.
jhs39 said:
Resurrection Remix is a custom rom but there is no need to install it to use Unofficial Magisk. That's just where the official download link is hosted, probably because the dev has some link to that particular rom. But Unofficial Magisk is not included or integrated in any way into that rom--Magisk is downloaded and flashed separately from the rom and should work the same on that rom, a different custom rom or stock.
---------- Post added at 11:26 PM ---------- Previous post was at 11:18 PM ----------
As a side note there's nothing wrong with Resurrection Remix but if you did want to give a custom Rom a try I would personally recommend Dirty Unicorns or Screwed. They aren't hosted on XDA but don't let that bother you. A quick Google search will turn up where they are officially hosted and in my personal experience they are easily the best custom Roms available for the Pixel. That said, I went back to stock so I could try Android O and have stayed on stock so far.
Click to expand...
Click to collapse
Only because I just found out, screwed doesn't support Pixel Google Photos Unlimited Upload at Original
pcriz said:
Only because I just found out, screwed doesn't support Pixel Google Photos Unlimited Upload at Original
Click to expand...
Click to collapse
That's true but it's probably temporary. The devs have been notified of that bug and they are usually pretty responsive. I could actually see Google changing their code to deny the unlimited original photo backup to Pixels that are altered--i.e. unlocked bootloader, root, custom recovery or custom rom since Google has made it pretty clear they don't want people doing these things on the Pixel, but I haven't read anything that indicates Google has done this. But don't be surprised if they do it in the future.
jhs39 said:
That's true but it's probably temporary. The devs have been notified of that bug and they are usually pretty responsive. I could actually see Google changing their code to deny the unlimited original photo backup to Pixels that are altered--i.e. unlocked bootloader, root, custom recovery or custom rom since Google has made it pretty clear they don't want people doing these things on the Pixel, but I haven't read anything that indicates Google has done this. But don't be surprised if they do it in the future.
Click to expand...
Click to collapse
I feel like the roms where it is working is just a matter of something NOT being changed in them and needing to find the delta but I agree I wouldn't be surprised if they look the stance of purposefully not allowing modded devices.
pcriz said:
I feel like the roms where it is working is just a matter of something NOT being changed in them and needing to find the delta but I agree I wouldn't be surprised if they look the stance of purposefully not allowing modded devices.
Click to expand...
Click to collapse
I'm not a programmer and can't say for sure but you might be right. I think the devs at Screwed (if I remember correctly) are the ones who say they create as lean of a rom as possible by removing useless code. They might have removed something they shouldn't have. It's still an excellent rom but that is a serious bug for people who rely on the photo at full quality backup feature and take a lot of pics.
Edit: clean install of LOS for microG and couldn't even get signal messenger to register. Never received a text with a code and never received the phone all. Switched back to opengapps for now.
I have a galaxy S5 sm-G900P (sprint) device running LineageOS for MicroG Kltedv may 25th 2018 build. Full device encryption is enabled. The device is running the latest firmware from OTA updates from sprint.
For about a month now, my push notifications for protonmail and signal messenger don't seem to come through unless I open the app and then I get hammered with them. These are the only two apps I allow to have GCM push notifications and Google registration enabled.
I tried making both of these ignore android battery optimizations, and I've tried over riding the notification priority for both apps to the highest setting. I've tried using the websockets version of signal and it didn't seem to help. I've reinstalled the apps a few times and that doesn't help either. I install apps via yalp store.
My wife has the exact same phone, with updated firmware, full encryption, except she's using Pico opengapps, and she does NOT have this problem with signal. So it seems to me it's something to do with microG.
Has anyone had this issue or does anyone have some suggestions for me to try?
Boggle247 said:
I have a galaxy S5 sm-G900P (sprint) device running LineageOS for MicroG Kltedv may 25th 2018 build...
Click to expand...
Click to collapse
I don't use the MicroG but, you may be able to obtain some feedback regarding it within one of the following MicroG threads.
https://forum.xda-developers.com/showthread.php?t=3217616
https://forum.xda-developers.com/showthread.php?t=3432360
The following is the Official LineageOS 14.1 thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3476433
If all else fails, and you don't receive any responses from any of the above threads, then your next best bet is to post your question within the following Q&A thread that's specific to the klte device variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Boggle247 said:
I have a galaxy S5 sm-G900P (sprint) device running LineageOS for MicroG Kltedv may 25th 2018 build. Full device encryption is enabled. The device is running the latest firmware from OTA updates from sprint.
For about a month now, my push notifications for protonmail and signal messenger don't seem to come through unless I open the app and then I get hammered with them. These are the only two apps I allow to have GCM push notifications and Google registration enabled.
I tried making both of these ignore android battery optimizations, and I've tried over riding the notification priority for both apps to the highest setting. I've tried using the websockets version of signal and it didn't seem to help. I've reinstalled the apps a few times and that doesn't help either. I install apps via yalp store.
My wife has the exact same phone, with updated firmware, full encryption, except she's using Pico opengapps, and she does NOT have this problem with signal. So it seems to me it's something to do with microG.
Has anyone had this issue or does anyone have some suggestions for me to try?
Click to expand...
Click to collapse
Is device registration enabled in microG settings?
kurtn said:
Is device registration enabled in microG settings?
Click to expand...
Click to collapse
Yes. I abandoned micro. Tried a clean install and I couldn't even register signal app.
PUSH notifications on LOS 15.1 Official
Hey, guys.
I asked the same question in my device thread, but not sure it is device specific.
Does anybody experience any issues with Push notifications?
After LOS 15.1 clean install (+OpenGApps Micro) I completely lost all notifications from everything.
I know that our devices are not certified for Play Market, so I followed instructions here: https://www.google.com/android/uncertified/
Added my GSF ID. But I see the following items in logcat.
Also, Google Play says that "Device is not certified".
I tried to clear Dalvik cache, cache partition, re-logged into my Google Account.
But no luck.
What's wrong?
RISING-STAR said:
Hey, guys.
I asked the same question in my device thread, but not sure it is device specific.
Does anybody experience any issues with Push notifications?
After LOS 15.1 clean install (+OpenGApps Micro) I completely lost all notifications from everything.
I know that our devices are not certified for Play Market, so I followed instructions here: <link removed>
Added my GSF ID. But I see the following items in logcat.
<link removed>
Also, Google Play says that "Device is not certified".
<link removed>
I tried to clear Dalvik cache, cache partition, re-logged into my Google Account.
But no luck.
What's wrong?
Click to expand...
Click to collapse
I have the same problem (identical logs) and no working push notifications immediately after I upgraded from LineageOS 14.1 to 15.1 on LG G2 D802. Both running a matching OpenGApps package.
I registered GSFA ID for my Google account and my device is marked as certified in Google Play. I upgraded to the latest nightlies of LineageOS 15.1 and OpenGApps, wiped caches, wiped Google Play Services storage.
Push notifications are still not working from me, though.
emkejovich said:
I have the same problem (identical logs) and no working push notifications immediately after I upgraded from LineageOS 14.1 to 15.1 on LG G2 D802. Both running a matching OpenGApps package.
I registered GSFA ID for my Google account and my device is marked as certified in Google Play. I upgraded to the latest nightlies of LineageOS 15.1 and OpenGApps, wiped caches, wiped Google Play Services storage.
Push notifications are still not working from me, though.
Click to expand...
Click to collapse
See my other messages below. You have to clean up the cache of a couple Google services.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's not working:
IMS (no volte)
Bixby button currently not set
Instructions:
Make sure twrp by afaneh92 is installed and functional.
Download the latest build (and optionally gapps).
Reboot to recovery
Wipe system, data, and cache (required if you switch from other ROMs)
Flash the latest build, gapps, and magisk.
Reboot
Downloads:
Galaxy S10 Snapdragon (G973U): https://github.com/klabit87/OTA/rel...eage-17.1-20201114-UNOFFICIAL-beyond1qlte.zip
Google Apps: https://opengapps.org/
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred.
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. For now please report any bug below.
Group:
Join this group for contacting me and bug reporting (typically fast response )
Unlocked Samsung US devices
https://t.me/joinchat/CG3Ojlb0TwDDrN-RY5UqmQ
Also dont forget to hit the thanks button!
Contributors
Thanks to @jrkruse and @afaneh92 for testing initial builds.
ROM Firmware Required: Minimum of Android 10 firmware
Based On: LineageOS
Version Information
Status: Beta
Source:
https://github.com/klabit87/android_device_samsung_beyond1qlte
https://github.com/klabit87/android_device_samsung_sm8150-common
https://github.com/klabit87/android_kernel_samsung_sm8150-common
https://github.com/klabit87/android_vendor_samsung_sm8150-common
Created 2020-11-14
Last Updated 2020-11-14
Reserved
Got it installed. Haven't had a chance to use as a daily driver, since I use volte. Hope it gets working eventually! Would definitely love to use as a daily driver after that!
Same. would love to see volte.
illspiritX said:
Same. would love to see volte.
Click to expand...
Click to collapse
I also had issuess with GPS on the sm-g973u, but that's something I testing with op, when he gets a new build made
Hi. I'm new here and I need some information. Do the fingerprint sensor and all the cameras work for this custom rom?
I am trying to root Lineage 18.1 on my S10.
Tried differtent versions of magisk without result. Is there a guid available for Lineage 18.1 for Galaxy s10?
pitchdown said:
I am trying to root Lineage 18.1 on my S10.
Tried differtent versions of magisk without result. Is there a guid available for Lineage 18.1 for Galaxy s10?
Click to expand...
Click to collapse
I've been working on a beta for s10. I'm hoping to share it this week. I planned to publish last week but I got busy with work.
klabit87 said:
I've been working on a beta for s10. I'm hoping to share it this week. I planned to publish last week but I got busy with work.
Click to expand...
Click to collapse
what will be shared?
Is it on a s10 not possible yet?
pitchdown said:
what will be shared?
Is it on a s10 not possible yet?
Click to expand...
Click to collapse
I have been working on a lineage 18.1 build for s10. Just be patient.
Will 18.0 qork
klabit87 said:
I have been working on a lineage 18.1 build for s10. Just be patient.
Click to expand...
Click to collapse
Will 18.0 work with Magisk?
I don't see why not. I haven't tested that yet though
klabit87 said:
I don't see why not. I haven't tested that yet though
Click to expand...
Click to collapse
until now magisk isn`t installed after flashing with 18.1
I hope your new version will have a help to this.
I am using 18.1 with magisk and have root and everything, my only issue with this rom is several of the google play apps i use won't even install on it saying it is incompatible, but they worked fine on stock. I do like the theme though and the personalization, great job! Just need to make it more compatible and i would love it.
Replicatorz said:
I am using 18.1 with magisk and have root and everything, my only issue with this rom is several of the google play apps i use won't even install on it saying it is incompatible, but they worked fine on stock. I do like the theme though and the personalization, great job! Just need to make it more compatible and i would love it.
Click to expand...
Click to collapse
You have to use the Magisk Hide option, and select everything with "com.google" in the package name.
Does this work with G9730 Chinese / Hong kong snapdragon variant?
Just got so sick of OneUI crashing all the time so I thought I'd give this a whirl. All good so far except for Google Maps can't seem to properly display. All the elements get huge when Maps is active, including the phone interface itself. Switching to any other app returns the normal look. I have googled as many different search terms as I could think of to see if anyone else is having this issue but I have come up with nothing. Screengrabs attached.
Google Photos has a similar issue only it just crashes after some screen difficulty.
BWhitmore said:
Just got so sick of OneUI crashing all the time so I thought I'd give this a whirl. All good so far except for Google Maps can't seem to properly display. All the elements get huge when Maps is active, including the phone interface itself. Switching to any other app returns the normal look. I have googled as many different search terms as I could think of to see if anyone else is having this issue but I have come up with nothing. Screengrabs attached.
Google Photos has a similar issue only it just crashes after some screen difficulty.
Click to expand...
Click to collapse
I encountered the same problem for Google Map when I'm in battery save mode.
Can i install this rom via TWRP? I cant see Install Lineageos Rom via TWRP guide. Thanks!
aceqdl0925 said:
Can i install this rom via TWRP? I cant see Install Lineageos Rom via TWRP guide. Thanks!
Click to expand...
Click to collapse
Yes, it's just like how you flash every other ROM. Check this.