I have a strange issue where some ROMs have stopped syncing contacts. Didn't really notice until I made changes to some contacts on another phone. Jumped around from ROM to ROM on all the devices (multiboot on each) to check. Only on this device do I have this behavior.
Stock Nougat. Good.
AOSiP, microG, Google sync. Good.
Bootleggers, microG, DAVdroid. Good.
FrankenROM, OpenGapps. Last sync May 22.
GZOSP, Pixel-GApps. Last sync May 23.
Xtended, OpenGApps. Last sync June 3.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If there's a problem one usually gets an exclamation mark in the spinner and a message at the bottom. Nothing here. Doesn't even attempt to sync.
I've cleared cache and/or data of contacts items, forced Sync Now, removed & re-add account, to no avail. Not sure what's going on yet.
When I first installed the latest Pixel Experience ROM it also wouldn't sync contacts at all. On a later installation it did.
Four ROMs on the Axon 7 (Nougat and Oreo), two on the G3 (Lollipop). Contacts are good.
Reckon I better generate and peruse some logs.
Moto G5s Plus XT1806, MSM Xtended v2.0 ROM, MultiROM, Tapatalk 4.9.5
I'm still having contact sync trouble with my phone too (Sony Z5 Compact) - last synced on the 9th of June. I tried syncing contacts on my tablet a couple of days ago and it worked as expected, which made things more confusing for me, but I've tried to look for any differences between the devices.
Based on this thread I have a suspicion that it is a problem with Google Play Services. Both my devices have Google Play Services 12.6.85, but different subversions (if that's the right word to use?).
The tablet, which syncs correctly, has 12.6.85 (040300-197041431) which appears to be the package for arm-v7a, while my phone has 12.6.85 (040406-197041431), for arm-v7a + arm64-v8a.
I can see a newer version on APKMirror so I will try it and see if that fixes things. - No improvement with 12.6.88
edit: Before I do that, when I try to sync manually this error shows up in logcat: (SyncManager) failed sync operation ... com.android.contacts ... reason: 1000 [ numIoExceptions: 1] - unfortunately I have no idea what reason 1000 is!
@plusminus_, with no responses I assumed maybe it was just a me thing. Couple of days ago I wiped out all of the ROMs except for the one using microG.
Started fresh. Flashed four ROMs w/gapps but none were able to sync contacts. Searched the G5s+ Telegram group and discovered there's a fix. So I guess it is/was a known issue.
Flashed it and now syncing works. Bad timing though, finding the fix right after erasing the ROMs. ?
The fix copies a device_key to the Play Services data. Safe to assume only for this device (sanders).
https://drive.google.com/file/d/132ghcwBSOF5TJk69RjuyT5QQhEvx3SH-/view?usp=drivesdk
ZTE Axon 7 A2017U, Project New World, Multiboot, Tapatalk 4.9.5
marcdw said:
@plusminus_, with no responses I assumed maybe it was just a me thing. Couple of days ago I wiped out all of the ROMs except for the one using microG.
Started fresh. Flashed four ROMs w/gapps but none were able to sync contacts. Searched the G5s+ Telegram group and discovered there's a fix. So I guess it is/was a known issue.
Flashed it and now syncing works. Bad timing though, finding the fix right after erasing the ROMs.
The fix copies a device_key to the Play Services data. Safe to assume only for this device (sanders).
https://drive.google.com/file/d/132ghcwBSOF5TJk69RjuyT5QQhEvx3SH-/view?usp=drivesdk
ZTE Axon 7 A2017U, Project New World, Multiboot, Tapatalk 4.9.5
Click to expand...
Click to collapse
I'm glad you got sync working again!
I can't access the file, but I doubt I would be able to use it anyway, thanks though
I finally got my contacts to sync, and indeed it was the missing device_key file that was causing the problem! I came across this post this morning and fiddling with Xposed sorted things out. This is what I did (for future reference perhaps)
1. Disable Xposed Framework in Magisk and Xposed Installer (I think disabling it in the Installer was not needed but I'm replicating my steps here)
2. I also disabled one of the Xposed modules I was using, No Device Check
3. Clear Google Play Services data (Settings > Apps > Google Play Services > Storage > Manage Space > Clear All Data)
4. Reboot
5. Let the phone sync
6. Check that /data/data/com.google.android.gms/files/device_key exists now (I also backed it up)
7. Enable Xposed Framework in Magisk
8. Reboot
9. Enable Xposed Framework in Xposed Installer
10. Reboot again...
@plusminus_, nice find.
I always flash Xposed with a new ROM. On the next one I try today I'll wait and install Xposed after the ROM and Google are setup and sync is working.
Even though I have that fix zip I'm curious.
Never occurred to me that Xposed would mess with syncing.
Moto G5S Plus XT1806, Resurrection Remix ROM, AL-ice Kernel, MultiROM, Tapatalk 4.9.5
/data/data/com.google.android.gms/files/device_key not created
Can I somehow generate it manually?
gmikhail said:
/data/data/com.google.android.gms/files/device_key not created
Can I somehow generate it manually?
Click to expand...
Click to collapse
Depends. What is your device? If it's the G5S Plus you can use the zip I linked earlier. Flash it after you've been in the ROM at least once and after you've set up Google (otherwise the directory won't exist yet).
If on another device you can try some or all of what @plusminus_ posted to see if it shows up.
Moto G5S Plus XT1806, Lluvia OS v1.4, TridentExperience, MultiROM, Tapatalk 4.9.5
marcdw said:
Depends. What is your device? If it's the G5S Plus you can use the zip I linked earlier. Flash it after you've been in the ROM at least once and after you've set up Google (otherwise the directory won't exist yet).
If on another device you can try some or all of what @plusminus_ posted to see if it shows up.
Moto G5S Plus XT1806, Lluvia OS v1.4, TridentExperience, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
I came across a topic from Google. My device is Lenovo P70-A, LOS14.1 (android 7) but I had the same problem with contacts synchronization.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
OpenGApps (optional) (Download from here)
Magisk (optional) - (Download from here)
installation:
Install crDroid ROM and any optional zips you want to flash afterwards and reboot. ( Make sure to clean-install coming from ANDROID PIE )
Download:
ROM Download for hero2lte
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Kernel Source
Known issues:
You tell me.
Visit official website @ crDroid.net
ExpressLuke 8890 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Donate to ExpressLuke[/SIZE]
Thank Q
I have Downloaded, and clean installed, coming from an android pie rom.
Installed, as per instructions, using TWRP 3.3.0.1, one at a time, in the following order, rom, pico arm64 gapps, and magisk, and phone booted.
Originally tried with nano gapps but failed to boot, but may have just been me.
All seems smooth but will update once set up and using.
I dirty flashed on los 17 b5. No bugs so far.
Would pixelarity mod work with this?
So far so good. I have had a couple of random reboots though, but it's beta, so can live with that.
Battery life has been pretty good , and on the whole the rom is pretty stable, and smooth.
I always back up my apps using Titanium Backup, but am unable to restore them via that, probably because of the change from Pie to Android 10, backup folder shows as being empty, even though it's not.
We're usually advised to reinstall apps via the Play Store if changing android version anyway, so no big deal.
Can we flash a dual speaker mod now, or should that have been done on initial flash?
Good work so far, thank you.
thanks
Does this rom support Samsung gear 3
Thanks man... Love crdroid build
Sent from my ASUS_X00QD using Tapatalk
aldbeagle said:
I have Downloaded, and clean installed, coming from an android pie rom.
Installed, as per instructions, using TWRP 3.3.0.1, one at a time, in the following order, rom, pico arm64 gapps, and magisk, and phone booted.
Originally tried with nano gapps but failed to boot, but may have just been me.
All seems smooth but will update once set up and using.
Click to expand...
Click to collapse
Did you use Android 10 gapps or Android 9?
amadhatter said:
Did you use Android 10 gapps or Android 9?
Click to expand...
Click to collapse
I used 10, but have had a few problems today. For some reason, the phone just rebooted, but got stuck on the CRdroid logo.
Have had to wipe system, and then reflash rom, gapps, (10 again), and magisk.
Rom still worked when I rebooted, but for some reason a lot of the google apps force closed on opening, so maybe I needed 9 and not 10!!
Have uninstalled all of them, wiped caches in recovery, and reinstalled and all "seems" ok, at present.
aldbeagle said:
I used 10, but have had a few problems today. For some reason, the phone just rebooted, but got stuck on the CRdroid logo.
Have had to wipe system, and then reflash rom, gapps, (10 again), and magisk.
Rom still worked when I rebooted, but for some reason a lot of the google apps force closed on opening, so maybe I needed 9 and not 10!!
Have uninstalled all of them, wiped caches in recovery, and reinstalled and all "seems" ok, at present.
Click to expand...
Click to collapse
Thanks for the reply. I used 10 and all seems to be working ok. Sound could do with being a bit louder but that might just be down to my age lol. Very impressed so far. Obviously some Samsung apps don't work and it cannot connect with my Gear Fit2.
I'm gonna reinstall from scratch as very laggy since the earlier problems.
Unsure whether to use 9 or 10 for gapps, but am gonna go with 10 and see what happens.
Gonna flash a dual speaker mod too, to see if that helps.
Try to use flamegapps or bitgapps... No random reboot no stuck... If you want use magisk then flash it after first boot, don't flash along with ROM... Hope it helps
Sent from my SM-G935F using Tapatalk
d9ny said:
Try to use flamegapps or bitgapps... No random reboot no stuck... If you want use magisk then flash it after first boot, don't flash along with ROM... Hope it helps
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up.
Regarding gapps, 9, or 10?
aldbeagle said:
Thanks for the heads up.
Regarding gapps, 9, or 10?
Click to expand...
Click to collapse
Of course use gapps 10... You can use flame basic or full, or bitgapps basic..
Sent from my SM-G935F using Tapatalk
amadhatter said:
Thanks for the reply. I used 10 and all seems to be working ok. Sound could do with being a bit louder but that might just be down to my age lol. Very impressed so far. Obviously some Samsung apps don't work not can it connect with my Gear Fit2.
Click to expand...
Click to collapse
I don't own any Samsung watch. But if you google "gear fit2 not working on lineage os" you'll find the solution. Apparently changing these lines in build prop to non Samsung brand works.
I'm using opengapps(nano) from official website and it works fine. No reboots no fcs
sbappi said:
I don't own any Samsung watch. But if you google "gear fit2 not working on lineage os" you'll find the solution. Apparently changing these lines in build prop to non Samsung brand works.
I'm using opengapps(nano) from official website and it works fine. No reboots no fcs
Click to expand...
Click to collapse
Thanks I will investigate it.
Does this rom have the issue with the speaker very quiet after a phone call
Yes, do you show me how to fix it
Anyone having quiet audio try volume booster free from the playstore. Rebooted phone now wifi not working i switch it on and after 3-4 seconds it switches itself back off i have no idea why its started doing this any help much appreciated thanks
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today.We're mainly based on LineageOS so use custom kernels compatible with them!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FeaturesClick for feature listWhat's working:* WIFI* NFC* Bluetooth* Fingerprint* Camera* Sensor* Edge sense* Call & SMS* APN* Wireless Charging...........Not woking:* plz report meFirst time installation or check latest build instructions:
Make sure your pc has adb environment and you have backed up the necessary data！！！
unlock the BootLoader
Flash the boot image file
Reboot recovery
adb sideload magisk or gapps
Wipe data, cache and format data.
Boot crDroid and E N J O Y !
DownloadClick here !Maintainer's githubLb9457Thanks：crDroid ROMsLineage OSAOSPROM OS Version: 12LROM Kernel: android_kernel_google_msm-4.9Status: StableOTA:not support(UNOFFICIAL)Sec. Patches : 2022.03.05Created : 2022.2.10Last Updated : 2022.3.30-----------------------------------------------------------------------------------------------optional-----------------------------------------------------------------------------------------------Donwnload ➢GMSDonwnload ➢MagiskDonwnload ➢MicroG
Thanks so much for the support!!!
.......and for the GAPPS package!
gms is not included in the rom, after that I will release the rom-specific gms package in the form of a magisk module.
Just a noob question. How to install gapps in Crdroid android 12. I try everything, but nothing happen.
RealEmo said:
Just a noob question. How to install gapps in Crdroid android 12. I try everything, but nothing happen.
Click to expand...
Click to collapse
gms has been uploaded ！
Any chance we can get this pixel 3/ blueline
beanaman said:
Any chance we can get this pixel 3/ blueline
Click to expand...
Click to collapse
Check the sourceforge parent folder
I flashed the Blueline and it is AWESOME!
beanaman said:
Any chance we can get this pixel 3/ blueline
Click to expand...
Click to collapse
I don't have a blueline model but I've built it, I haven't tested it so I haven't released it yet.
AlexKarimov said:
Check the sourceforge parent folder
I flashed the Blueline and it is AWESOME!
Click to expand...
Click to collapse
Please help me test whether the active edge is working properly, thank you, and I will release the crdroid8.2 version today, the blineline may be delayed.
LB9457 said:
Please help me test whether the active edge is working properly, thank you, and I will release the crdroid8.2 version today, the blineline may be delayed.
Click to expand...
Click to collapse
So this isn't my daily driver, it's my dad's old phone that he dropped when the mobile data stopped working. So I can't test any network features but I'll check on the active edge. In the mean time, here's some screenshots:
After flashing gms with magisk modude (version 8.1), my google contact can not be sync with google account and apps not be able to restore from google back up, anyone having this problem? will try v.8.2 later and will leave a feed back. Thank you for your hard work and sharing
badboyblue said:
After flashing gms with magisk modude (version 8.1), my google contact can not be sync with google account and apps not be able to restore from google back up, anyone having this problem? will try v.8.2 later and will leave a feed back. Thank you for your hard work and sharing
Click to expand...
Click to collapse
I will test later
version 8.2 has the same problem not sync contacts & restoring apps from google back up
badboyblue said:
version 8.2 has the same problem not sync contacts & restoring apps from google back up
Click to expand...
Click to collapse
It has been removed, it is being actively resolved, and a new one will be released later
please release gapps included
so sorry....can you release the version that can install gapps via twrp recovery? revert to v8.1...so far contacts sync working just fine...
Ajih96 said:
so sorry....can you release the version that can install gapps via twrp recovery? revert to v8.1...so far contacts sync working just fine...
Click to expand...
Click to collapse
The rom is not built with gapps, and the rom itself does not guarantee that other gapps will work properly, so using magisk is the safest method. Using recovery to flash in errors will be irreversible, so I have no plans for this moment.
Could someone list the steps to get the Google contacts / app data restored after flashing the GMS Magisk module??
tkacer said:
Could someone list the steps to get the Google contacts / app data restored after flashing the GMS Magisk module??
Click to expand...
Click to collapse
After flashing gsm u maybe faced conecting error in google play. I solved it with newest google play apk and google services apk in apkpure ( u can google it), install. Reboot, everything work with me. Sorry for my bad English.
tkacer said:
Could someone list the steps to get the Google contacts / app data restored after flashing the GMS Magisk module??
Click to expand...
Click to collapse
For me, after i flashed google apps...go to the settings > apps > show system apps > go to google play services then grant all the permission. Then go to google contact sync and contact app, also grant all the permission. Make sure that all apps mentioned above can access internet and try to sync your account manually. I hope it will work for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
What's working:
Everything except bugs
Known issues / bugs:
- MTP (Menu from QS doesn't work. Developer option menu does.)
- Bluetooth audio (audio only)
- SELinux permissive
- Encryption (ROM is decrypted)
Notes:
- For MTP, enable developer options and select "Default USB configuration".
Flashing instructions:
1. Flash S001142 OTA (do NOT use different versions!)
2. Wipe Dalvik, Cache, Internal storage and Data. (do NOT wipe vendor).
3. Flash ROM.
4. Flash Gapps / Magisk (Optional.)
5. Reboot.
Device Sources
device_lenovo_X505L
Kernel is currently prebuilt due to Lenovo not releasing sources.
Big thanks to @ud4 for his help!
Download
Reserved.
can we flash it on x505x?
UDONTHAVERIGT said:
can we flash it on x505x?
Click to expand...
Click to collapse
Yes it should work on x505x.
I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip
What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)
sinhus said:
I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip
Click to expand...
Click to collapse
Please format data and enable ADB On boot.
DominicNoobAtRoming said:
What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)
Click to expand...
Click to collapse
I recommend upgrading to S001142 for safety reasons (since I'm not really sure about the changes Lenovo did between the updates).
tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.
How do i install the update safely becauss im worrying about bricking my tab
yukeiw said:
tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.
Click to expand...
Click to collapse
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?
henloboii said:
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?
Click to expand...
Click to collapse
I have same issue S001142, no WiFi on X505F, toggle just flicks on/off instantly.
However works fine without GApps (only because it wouldn't install, not enough system space Err70 apparently)
Same problem on my X505F, no WiFi. GApps worked well.
Can any X505F users send logs? I would like to take a look.
henloboii said:
Can any X505F users send logs? I would like to take a look.
Click to expand...
Click to collapse
happy to assist if you tell me what logs/where to pull them from, someone on telegram group said they were updating the image?
I tried this on my X505L and I couldn't get it to boot using S001142 and TWRP following the instructions exactly, is there a way to log or debug it if it doesn't boot, or do I have to reflash the firmware and hope for a better attempt?
Hi,
I tried it on my X505F and it was not as easy as I thought. I already had S001142 and started with installing TWRP as denoted here:
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Installing Magisk led to some problems, though, as the wipe of /data afterwards prevented me from flashing the ROM ("Magisk binaries not found"). I had to install Magisk again *and* create a symlink from /data/adb/magisk to /data/magisk to be able to uninstall it again (additionally to renaming it to uninstall.zip etc.). Then I was able to flash this LineageOS.
It didn't boot, though, but was stuck at the Lenovo logo (very early boot phase). I flashed it again, but it didn't help. What *did* help was installing Magisk via TWRP Now the tablet booted into LineageOS, but only with an Android popup that some internal error occured and I should contact my vendor.
After having a black screen for a minute or so the LinageOS setup UI appeared and I was able to set up the clock. When reaching the WiFi page, I wasn't able to switch it on (like the other reported).
Attached you find a logcat and the dmesg output. I hope that's what you need.
I would love to try this but i do use bt audio so i look forward to any updates. i dont think ill ever see this thing run anything past android 10, but im not too worried about that, i know its an old cheap tablet. are you able to expand internal storage to an sdcard? my number one complaint about this thing is it always complaining of low storage.
Hay dose anyone have a copy of the stock firmware (so
TB-X505F-S001142-210804_ROW.zip)
I had the exact same experience as this. Ah well... It would've been nice to strip out this Lenovo bloated ROM with something sleeker.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Razer Phone 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Razer Phone 2.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
aura - Official builds
aura - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Known bugs (won't fix):
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_razer_sdm845
Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?
runuts said:
Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?
Click to expand...
Click to collapse
it works on PE?
npjohnson said:
it works on PE?
Click to expand...
Click to collapse
No. This is why I switched from PE to Lineage 19.1 where it also didn't work. Flashed back to 18.1 and it is working.
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
Hint: I am working on m8 right now
npjohnson said:
Hint: I am working on m8 right now
Click to expand...
Click to collapse
That is good to know. I installed an unofficial LineageOS 18 ROM recently, but haven't played with it since then.
Just updated to LineagOS for MicroG 19.1 so far so good.
unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
If you read the install instructions this is normal behavior
npjohnson said:
Known Bugs:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Click to expand...
Click to collapse
Not really a bug as its an app in the stock ROM. The current solution is to root and install Logo+ and it works.
Should also list Dolby Atmos missing too
omega552003 said:
If you read the install instructions this is normal behavior
Click to expand...
Click to collapse
I did. It was not unexpected.
I followed the instructions to the letter upgrading from 18.1 and mine is stuck in boot. It's been showing the little logo animation for almost 10 minutes now. Mild panic has set in.
edit: Fixed it!
Had the wrong gapps package. Downloaded the correct one, (MindTheGapps12.1 arm64 for those lost souls still out there).
Fixing procedure if stuck on LOS logo loop:
1. Make sure your devices is still plugged into your computer and hold down power button until you see the fastboot landing page where it gives you the option to pause boot. PAUSE BOOT.
2. hold down power button again to turn phone off. You'll know it's off when you get the white and black charge animation
3. hold power and volume down until you get to the recovery page.
4. Choose recovery mode, recovery from adb, and then run adb sideload /path/to/zip to install the correct gapps package.
Hope no one else does the same dummy move I did but if they do I hope this helps.
P.S. I have no idea yet what my screw up did long term btw. Device is still finishing the update. I did have to reinstall messages and gmail but for all I know that would have needed to happen anyway.
Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?
edison said:
Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?
Click to expand...
Click to collapse
Yes, it should. I remember seeing some folks have similar issues with 18.1 but I don't recall what the issue was. Maybe check out the 18.1 forums and see if there's any applicable advice there
Coming from Pixel Experience and I am getting audio crackling/stuttering only when using game streaming apps such as Moonlight and PSPlay and the volume is less than 50%. I had the same issue on Pixel Experience but the dev had fixed it using this commit. Any chance the fix can apply here too?
With the most recent build I am seeing Location pings even though Location is off and no apps are granted Location permissions. It was difficult, but I did get a screen capture of the event. You can see the location pip in the status bar. What is going on?
How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager
Cylow333 said:
How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager
Click to expand...
Click to collapse
I was looking for the same information
This is working very well for me keep up the good work. One thing I have found however is that while on a call rtt or tty as it is known seems to be on. I have made sure it is off in accessibility settings so I am sure it's just a bug but wanted to make aware of it. Does anyone else have this issue? I am on verizon. Not sure if that matters.
marcxpr said:
I was looking for the same information
Click to expand...
Click to collapse
I was able to root by adb sideload and running adb sideload followed by the magisk.zip file
Official Lineage OS 19.1 is here, so there is no reason to continue these unofficial builds. That was fast!! Thank you for those who gave their support. If you were on this build, you should be able to update to the official August 28, 2022 build directly from the updater (or dirty flash it yourself).
Lineage OS 19.1 - Unofficial
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all. I noticed that there isn't official Lineage OS support for our OnePlus 8 Pro past version 18.1, so I decided to attempt building 19.1. Since it appears to be working correctly, I wanted to share it with anyone else who has an interest. I'm not changing anything about it (other than making it compile) and building straight from the Lineage OS sources. I'll attempt to build it roughly 1x per month, usually around the middle to allow for most security updates to take effect. I daily drive the ROM, so I'll only post updates when I see basic functionality working.
Latest ROM and recovery, August 11, 2022:
ROM
Recovery
Old Releases:
Older ROM/Recovery
Follow the official directions in order to flash the ROM and recovery files:
https://wiki.lineageos.org/devices/instantnoodlep/install
OTA Support:
I modified the built in updater to support updates from my unofficial source for all flashed builds after 8/11/22. I added an option under preferences to go back to the official source in the event that official builds are started. Just go to Settings -> System -> Updater to check. I plan on uploading to OneDrive and Dropbox for these updates (bandwidth might be temporarily limited). You can always manually flash without it from a PC.
Sources:
https://github.com/LineageOS
https://github.com/TheMuppets/proprietary_vendor_oneplus
https://github.com/LineageOS/android_device_oneplus_instantnoodlep
https://github.com/calsurferpunk/android_device_oneplus_sm8250-common
https://github.com/LineageOS/android_hardware_oneplus
https://github.com/LineageOS/android_kernel_oneplus_sm8250
https://github.com/calsurferpunk/android_packages_apps_Updater
https://github.com/calsurferpunk/lineageos_update
(roomservice.xml attached to this post for reference)
Based on OOS11 or OOS12?
doesn't recognise sim card
The_Lord_of_Lost said:
doesn't recognise sim card
Click to expand...
Click to collapse
I'm not sure what carrier you have, but I've been using AT&T in the United States without any issue.
keaheng said:
Based on OOS11 or OOS12?
Click to expand...
Click to collapse
It should be OOS12 if that's what the TheMuppets GitHub is using for the vendor (if that's the same thing). Otherwise everything is just straight from the Lineage OS GitHub.
calsurferpunk said:
I'm not sure what carrier you have, but I've been using AT&T in the United States without any issue.
Click to expand...
Click to collapse
Im using vodafone uk ,18.1 works perfectly fine but 19.1 is has slow response (especially settings options) and doesn't recognise sim
The lineageOS rom installs fine and looks good. I sideloaded the Mind the GAPPS package directly afterward before booting as directed with ver12.1 arm64 but there is no sign of Google play anywhere on the device. I have repeated 3x and downloaded package twice. Another GAPSS? Anyone else have this? I have not tried another GAPPS package but might do that
p-we said:
The lineageOS rom installs fine and looks good. I sideloaded the Mind the GAPPS package directly afterward before booting as directed with ver12.1 arm64 but there is no sign of Google play anywhere on the device. I have repeated 3x and downloaded package twice. Another GAPSS? Anyone else have this? I have not tried another GAPPS package but might do that
Click to expand...
Click to collapse
Have now tried several other GAPPS including NikGApps 12.1 but while it seems to install normally, not a trace of it on the phone itself
p-we said:
Have now tried several other GAPPS including NikGApps 12.1 but while it seems to install normally, not a trace of it on the phone itself
Click to expand...
Click to collapse
I've got GAPP's working. At least NikGApps 12.1 as I didn't verify the others. It wasn't clear in the instructions that you have to perform a recovery reboot between sideloading lineageOS and GAPP's.
Warp charging and wireless charger with quiet mode working?
Is face unlock on board?
everything works perfectly, to see if the battery life is good. Thanks!
New build for 8/11/22. See first/main post.
thanks
Installed this yesterday, with mindgapps and magisk. Works like a charm. Thanks for compiling this
Is there any progress on getting this to official status? I'm running official 18.1 but I'd really like to be on Android 12 at some point so I'm looking forward to being able to update, I just don't feel like wiping or having there be any hassle with data.
Got this installed yesterday with nikgapps and magisk. working great! warp charging doesn't say warp charging, but considering it went from 10% to 50% in 5 or 6 minutes, it's definitely there.
only thing, and it's not you, it's lineage, is not being able to change the display refresh rates. Hopefully that's something coming down the line..
What was sad was that Google backup and restore didn't see this as an IN2025 anymore. It shows as IN2023. But titanium backup kept my apps backed up enough
mattgyver said:
Got this installed yesterday with nikgapps and magisk. working great! warp charging doesn't say warp charging, but considering it went from 10% to 50% in 5 or 6 minutes, it's definitely there.
only thing, and it's not you, it's lineage, is not being able to change the display refresh rates. Hopefully that's something coming down the line..
What was sad was that Google backup and restore didn't see this as an IN2025 anymore. It shows as IN2023. But titanium backup kept my apps backed up enough
Click to expand...
Click to collapse
Afaik you can change the display refresh rate on lineage. They enabled a feature available in AOSP called "Smooth display"
Settings > Display > Smooth display
Keeping this off will have the device use the minimum refresh rate at all times (60hz). Turning it on will cycle between 60/120 depending on touch input.
You can also force the peak refresh rate by enabling "Force peak refresh rate" in developer options.
AnierinB said:
Afaik you can change the display refresh rate on lineage. They enabled a feature available in AOSP called "Smooth display"
Settings > Display > Smooth display
Keeping this off will have the device use the minimum refresh rate at all times (60hz). Turning it on will cycle between 60/120 depending on touch input.
You can also force the peak refresh rate by enabling "Force peak refresh rate" in developer options.
Click to expand...
Click to collapse
Thanks for that!
calsurferpunk said:
Official Lineage OS 19.1 is here, so there is no reason to continue these unofficial builds. That was fast!! Thank you for those who gave their support. If you were on this build, you should be able to update to the official August 28, 2022 build directly from the updater (or dirty flash it yourself).
Click to expand...
Click to collapse
Thanks for your work with the unofficial build. Greatly appreciated, at least from my perspective!
Are we going to still get security updates ? or its THE END? for 18.1?