Develop Bugs

[Q] Netflix on Cm12 based Roms???

I have tried several AOSP roms and have not gotten Netflix to work on any of them. I have tried liquidsmooth and PacRom but I keep getting Error (-9). Does anyone know of a fix for this? Please help..Thanks.

jmayer846 said:
I have tried several AOSP roms and have not gotten Netflix to work on any of them. I have tried liquidsmooth and PacRom but I keep getting Error (-9). Does anyone know of a fix for this? Please help..Thanks.
Click to expand...
Click to collapse
Using SELinuxModeChanger app, you can set to permissive and give it a go, it sometimes work.
Another method is to delete a lib file within
/system/vendor/lib
Liboemcrypto.so, you can rename or simply delete, then reboot the device.

Spark91 said:
Using SELinuxModeChanger app, you can set to permissive and give it a go, it sometimes work.
Another method is to delete a lib file within
/system/vendor/lib
Liboemcrypto.so, you can rename or simply delete, then reboot the device.
Click to expand...
Click to collapse
I personally didn't have luck with the permissive change and couldn't find the liboemcrypto.so file you spoke of. Is that specific to the Galaxy Note 4?

No sir, most ROMs don't have the lib, and what ROM are you using ?

Using liquid smooth on a moto xt926. I've noticed this problem on various cm12 ROMs I've tried. They had Netflix running for a while then it kind of stopped for recently then I think the last one I tried that I worked on was bliss pop 3.2. Jump over to liquid smooth because. Was pretty laggy and causing me a little pain. Back to a loading screen. Never comes up. I will say I thought it was a host file or ad block problem because I could get it going on WiFi. Just not on cellular data.

Think pulling and using the apk from a nexus device would change anything?

Beats me, I think that it probably is not an issue with the apk itself.
My best guess is that it is ROM related. Didn't cm ROMs have some DRM related issues a year or so ago? Wouldn't surprise me if it's something along those lines.
BTW, forgot to mention that you can't even get to netflix.com and browser. just more thoughts as to why I don't think it's actual program related it something in the ROM.

It is ROM/Kernel related for the Note 4 before I think @Mod57 fixed it but all it was is to change a build.prop line. Try and see if this works for you as well.
persist.hwc.mdpcomp.enable=false
If the value is already there and it says True, change it to false.

Did this on a previous build (cm12 5-8-2015 I believe), seems to work although more testing is needed to determine consistency. Failed first time worked second.
Sure hope that's it....!

Has anyone had better luck finding a solution for this? I came from DU's latest and now on CM12.1 6/25 nightly, everything is working great except for Netflix. I was never able to get it to work in DU so I won't be terribly heartbroken if I can't get it fixed, but I do not have Lyboemcrypto.so file or that specific persist line in my build.prop. Any other suggestions? I was getting a -504 error when attempting to install a couple apps, turning flight mode on/off took care of that, so I tried that as well as wifi on and off both for Netflix but cannot get it to initialize, all I get is the constant red spinning circle of the first screen. Thanks

Workaround
Install the module xposed cm10.1 Netflix workaround under xposed framework. Works perfectly on t0lte.
Edit: working on cm12.1

Netflix fix
Deleted

Android Auto - Something went wrong. Google play services doesn't seem to be working

I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.

jjcdennis said:
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
Click to expand...
Click to collapse
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. I will capture a logcat and post.
Thanks
Click to expand...
Click to collapse

steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Well I wiped cache, Dalvik, system and then formatted data, installed the 15.1 UsU rom, then installed Gapps, rebooted to recovery and installed the Lineage addonsu. I rebooted, went through setup and the first thing I did was open the Playstore install Android Auto and run it - immediate error again. Also the addonsu did not root the phone. And to top it all I did not disable the pin code.
Back to the drawing board.
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
I run LOS 15.1 build 20181002 and at the time of installing that ROM version I used this opengapps version: open_gapps-arm64-8.1-nano-20180705.zip (download)
AA works here yes. I run it now for several days, daily, no issues here.
My version of AA is 3.7.584044 (attached: View attachment com.google.android.projection.gearhead-ffadc269cc39417e152ffcdd22183045.apk)
Not sure what you mean by "the more options *" but I've attached 2 screenshots of the app settings which may show what you meant.. if not show a pic of that setting.
oh you may meant the gear symbol at the top right? Here it opens fine but as that opens google stuff it makes sense that it fails on yours
.
Click to expand...
Click to collapse

Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.

jjcdennis said:
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
Click to expand...
Click to collapse
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-

steadfasterX said:
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
Click to expand...
Click to collapse
H812 on the UsU Oreo build H812 build.
So I can copy what you have, other than I'm using the H812 versus the H815 LOS rom.
Thanks steadfasterX

steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.

jjcdennis said:
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
Click to expand...
Click to collapse
Use my latest preview version of TWRP then you can backup your data AND internal storage . you can first try without format. if you still have issues try to format it and if it doesn't fix anything you can restore by TWRP but ensure that you use build 144 or higher
Sent from my LG-H815 using XDA Labs

OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.

jjcdennis said:
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
Click to expand...
Click to collapse
Gave it a go, but as soon as I tapped on AA the error came up. I did format data to start from clean and used the older versions of AA and Google Play.
Update - I reinstalled all my apps via Titanium Pro (not AA) and set things up. I decided to tryy AA one more time before removing it and bingo it opened. Kinda waking on broken glass here and unsure whether or not the app will continue to function. Hooefully this fixed things.
Thanks again steadfasterX.

Lineage OS 16.0 Setup Wizard won't finish

Keeps resetting at the Bring your data from... step.
Whether I tap 'Don't Copy' or 'A backup from the cloud'. It attempts it, then just goes back to the same screen. Then after a second or third attempt it says Android Setup keeps stopping and I can only close the app.
Everything seems to be fine though, I can use my phone like normal. Just every time I pull down notifications, there is that bug blue notification that I need to continue with Setup.
I installed the mini MindTheGapps package if that could have anything to do with it.
Should I just reset everything and start over? Dont want to if possible since I have set up everything else at this point heh...
I have read other threads about this issue over the years but nothing has seemed to help.
Not sure if relevant but this in on a Oneplus One
Thank you all.

Thats a GApps issue. I don't use that Google APPs

The only solution I've seen to that is reinstall LOS (and twrp 3.3.3 if you want), reboot to recovery, install gapps, reboot to system. I believe I got that flow from one of the install guides.
I'm going to assume you also didn't get the full google login experience setting language and account and all that jazz either.
I've had to do the same as above for a LOS update too which is a bit annoying. But I have not experimented too much.

Problems after first update of LineageOs 17.1 install

First update since installing Lineageos on Lenovo P2.
The navigation bar along the bottom disappeared. Couldn't be swiped up - had been fixed previously.
Then found other things as well. Fingerprint sensor not working. Pixel launcher failing. Had been using Nova launcher and foolishly removed it thinking I'd reinstall to see if it restored the nav bar. But now stuck with a failing launcher and can't start anything - including Play to reinstall Nova. Just says 'Pixel Launcher keeps stopping, App info, Close App.' Cleared cache from App info as that was all I could do but no difference.
I haven't read it anywhere but are updates cumulative? Ie, can I skip one if I miss it and get all updates rolled up into the next one. I hope so because that's what I did. Jumped from something like 9th August to 30th.
Any ideas?

Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.

alirazaagha said:
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
Click to expand...
Click to collapse
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.

bind00 said:
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
Click to expand...
Click to collapse
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.

alirazaagha said:
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
Click to expand...
Click to collapse
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.

bind00 said:
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
Click to expand...
Click to collapse
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.

alirazaagha said:
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
Click to expand...
Click to collapse
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers

bind00 said:
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
Click to expand...
Click to collapse
Built in update works as required but if it messes with system partition then you better download update and install it through recovery.
GApps can be restored after update but the point is that you don't need it. System update only replaces the older system files with new ones without touching gApps files. Whereas, Magisk is automatically installed after update if it's in the same folder.

Call screening not enabling on lineageOS 18

Hey guys,
I know theres not too many people left on here but figured I'd check anyway. I just switched my Pixel to the latest LineageOS nightly build. Everything works great except the Google phone app will not allow me to enable the call screening feature. It just says I need to be connected to wifi to enable it, which of course I am. I have tried several things from joining beta, making sure it is a system app, reinstalling it, changing some flags in an XML file, installing the framework magisk module. None of which have worked. If you guys have any suggestions I'd greatly appreciate anything you could contribute to helping.
Thanks.

Nevermind I figured it out. I installed lineage and the Minthegapps Gapps package. Turns out I just needed to have the Google phone app installed as a system app under system/priv-app and it worked like a charm!