Lineage OS 14.1 on Coolpad Note 3 crashes on important pages. - CoolPad Note 3 ROMs, Kernels, Recoveries, & Other

Installed lineage 14.1 with the latest pico gapps on my Coolpad Note 3 (after it seemed to work beautifully on my old Nexus 4)...
Have a few issues:
1. When I try to set a screen lock (of any kind) it crashes.
2. When I try to browse using the default browser, it crashes.
I was wondering if anyone else would have an idea about it. I can get around the browser issue by using different browsers, but I need a screen lock for sure.

Related

[Q] google camera

Have anyone tried the new google camera launched on play store 4 days ago.
I am using cm 11 temasek and it gives force close while using and then can't connect to any camera, and I have to reboot phone to get to work. Then all the same.
Samsung galaxy s3 4.4.2
P.s. I used in cm11 official and temasek, and same problem.

OK Google -OR- Android Auto, but not both

I am using a LeMax 2 running Lineage OS (14.1-20170503-Unofficial-x2). Everything is working very, very well. (please keep in mind, I'm coming from a Nexus 6, which had bad slowness and battery issues now, and I LOVED this phone!) However, I've run into a problem with "Ok, Google" and Android Auto.
If I update the Google App (I've tried both "normal" and beta) then it breaks the "OK, Google" hotword detection. I downgrade, and it works fine. I have Android Auto set to auto start when it connects to my bluetooth transmitter. If the Google app has been downgraded, Android Auto wants to update it, won't launch without it, and that always updates Google, breaking the hotword again.
I use both Android Auto and "Ok, Google" a lot, so I'd love to find a way to be able to use both. Any suggestions? I've tried downgrading Auto, and every combo I can think of with Google and AA, but I cannot get them to work at the same time.
ETA: I've since updated to the official Lineage OS, (the 05/19 Nightly) and still the same issue
ETA2: I did an uninstall updates. Version 7.1.29.21.arm64 com.google.android.googlequicksearchbox works fine with the hotword detection - until you open Android Auto. Then it stops altogether, even though it hasn't updated. This time, only one time, I got a toast message in Android Auto saying voice commands weren't available right now, but couldn't get it to do it again.
Delete...sorry
Mrs_B said:
I am using a LeMax 2 running Lineage OS (14.1-20170503-Unofficial-x2). Everything is working very, very well. (please keep in mind, I'm coming from a Nexus 6, which had bad slowness and battery issues now, and I LOVED this phone!) However, I've run into a problem with "Ok, Google" and Android Auto.
If I update the Google App (I've tried both "normal" and beta) then it breaks the "OK, Google" hotword detection. I downgrade, and it works fine. I have Android Auto set to auto start when it connects to my bluetooth transmitter. If the Google app has been downgraded, Android Auto wants to update it, won't launch without it, and that always updates Google, breaking the hotword again.
I use both Android Auto and "Ok, Google" a lot, so I'd love to find a way to be able to use both. Any suggestions? I've tried downgrading Auto, and every combo I can think of with Google and AA, but I cannot get them to work at the same time.
ETA: I've since updated to the official Lineage OS, (the 05/19 Nightly) and still the same issue
Click to expand...
Click to collapse
Could you please tell which Google app version do you have exactly? Mine is not working.
Enviado desde mi LEX829 mediante Tapatalk
I've tried several different version from apk mirror and just "un-updating" what I had. I've tried a full factory reset, then installing the official LOS nightly listed above. I've compared the Google app version to the working version (both Android Auto and the Ok, Google hotword) on my Nexus 6, and gotten as close as possible to it, or even newer versions (apk mirror again, then flashing Gapps, arm 64 7.1 Stock from 05/23) I can get one or the other to work, but not both Ok, Google and Android Auto. I've tried turning voice control off, then back on. I've deleted and re-recorded my voice commands. I cannot figure out how to make this work. Until I get it figured out, I'm using my Nexus 6, but it's about to need retiring.
Mrs_B said:
I've tried several different version from apk mirror and just "un-updating" what I had. I've tried a full factory reset, then installing the official LOS nightly listed above. I've compared the Google app version to the working version (both Android Auto and the Ok, Google hotword) on my Nexus 6, and gotten as close as possible to it, or even newer versions (apk mirror again, then flashing Gapps, arm 64 7.1 Stock from 05/23) I can get one or the other to work, but not both Ok, Google and Android Auto. I've tried turning voice control off, then back on. I've deleted and re-recorded my voice commands. I cannot figure out how to make this work. Until I get it figured out, I'm using my Nexus 6, but it's about to need retiring.
Click to expand...
Click to collapse
But which Google app version is working with Ok Google...
Enviado desde mi LEX829 mediante Tapatalk
jufece said:
But which Google app version is working with Ok Google...
Click to expand...
Click to collapse
That's my point. All but the one I'm using now have worked with it...until it insists on an update to the most recent.
All I know is that 7.3.16.21.arm64 com.google.android.googlequicksearchbox doesn't work. I'm sorry, I don't know the version that worked for sure, as I did a full factory reset to try and fix the problem. I promise, I'm not trying to be difficult. I just didn't know it was going to happen or I'd have noted the version numbers.
I've also tried it with the SIM in, and with the SIM out. Not sure why that would have anything to do with it, but worth trying.
I think the problem is to do with google assistant which comes with the newer versions of the Google app (replacing Google Now)
For me it's only working when turning ok Google recognizing off. Turning it on didn't work. Sound curious but it's real. Dunno what's wrong here. Ok Google also only works on main screen when mobile is unlocked. Having another app in foreground​ it does not trigger.
I don't know if this behavior belongs to me max 2 or to Google app. Anyone else can confirm this problem?
Linage needs to fix this on there end. They need to create a working gapps install.
Sent from my Le Max 2 using XDA Labs

Nexus 7 - Play My Library Widget missing in LineageOS?

Hi.
Apologies for the post out of the blue.
I salvaged an old Nexus 7 (2012) Grouper, with the aim of using it as a book reader for my wife, and after playing with it for a while in the stock ROM it was noticeably slow. After reading a bit about it, I ended up installing the latest unnoficial version of LineageOS 11.0 from here, hoping to speed it up.
I also installed the OpenGApps pico package, and then manually installed Google Play Books to access my library.
However, while everything seems to be working as smooth as butter so far, I struggle to find the "Play - My Library" widget on the widget selection screen. It used to be available on the stock 5.1 rom, and I believe it belongs to the Play Store application. In fact, in my other Nexus 7 Grouper on stock ROM that has that widget, it claims to be on
Play Store v7.8.16.P-all [0] [PR] 155590935
While the one I just flashed from OpenGApps seems to be even more recent:
v.7.9.30.Q-all [0] [PR] 157075589
I tried to install another version of the Play Store from apkmirror.com but it fails to install. I also can't remove the Play Store application, for some reason, so I'm kind of at a dead end.
I'd love to be able to use the "Play - My Library" widget to cover the whole screen, but I can't seem to make that happen. The "Play Books" widgets are just too small to be useful (1 book or 4 books).
Would anyone have any ideas on how to make this work? Does anyone have a similar configuration and have a different experience? I was trying to see if the P-all vs Q-all would make any difference, but I'm at a loss. Any pointers, help or guidance would be very much appreciated.
Thanks in advance for your time.
EDIT: Also, just checked, both devices have the same version of Google Play Services - 11.0.55 (230-156917137) and Play Books (3.13.17).
pjft said:
Hi.
Apologies for the post out of the blue.
I salvaged an old Nexus 7 (2012) Grouper, with the aim of using it as a book reader for my wife, and after playing with it for a while in the stock ROM it was noticeably slow. After reading a bit about it, I ended up installing the latest unnoficial version of LineageOS 11.0 from here, hoping to speed it up.
I also installed the OpenGApps pico package, and then manually installed Google Play Books to access my library.
However, while everything seems to be working as smooth as butter so far, I struggle to find the "Play - My Library" widget on the widget selection screen. It used to be available on the stock 5.1 rom, and I believe it belongs to the Play Store application. In fact, in my other Nexus 7 Grouper on stock ROM that has that widget, it claims to be on
Play Store v7.8.16.P-all [0] [PR] 155590935
While the one I just flashed from OpenGApps seems to be even more recent:
v.7.9.30.Q-all [0] [PR] 157075589
I tried to install another version of the Play Store from apkmirror.com but it fails to install. I also can't remove the Play Store application, for some reason, so I'm kind of at a dead end.
I'd love to be able to use the "Play - My Library" widget to cover the whole screen, but I can't seem to make that happen. The "Play Books" widgets are just too small to be useful (1 book or 4 books).
Would anyone have any ideas on how to make this work? Does anyone have a similar configuration and have a different experience? I was trying to see if the P-all vs Q-all would make any difference, but I'm at a loss. Any pointers, help or guidance would be very much appreciated.
Thanks in advance for your time.
EDIT: Also, just checked, both devices have the same version of Google Play Services - 11.0.55 (230-156917137) and Play Books (3.13.17).
Click to expand...
Click to collapse
what package of OpenGApps did you flash?
also, did you try looking for a newer LineageOS? like LOS 12.1, 13, OR 14?
maybe that widget doesn't work on KitKat, I'm not sure..
MigoMujahid said:
what package of OpenGApps did you flash?
also, did you try looking for a newer LineageOS? like LOS 12.1, 13, OR 14?
maybe that widget doesn't work on KitKat, I'm not sure..
Click to expand...
Click to collapse
Hi MigoMujahid, thanks for the prompt reply!
I tried the Pico ARM OpenGApps package. I may test the full one later and see how it goes.
I suppose trying a newer LineageOS version is a good recommendation, at least to try it out. The reason I was avoiding those is because the last "effective" well-performing OS on this old tabled is 4.4. And you may be right, it might be that the widget doesn't work on KitKat.
I'll try a new package, per your suggestion, and may test out a newer LineageOS package, hoping it won't affect the performance significantly.
I'll report back in case I succeed - or fail miserably
Have a good weekend, thank you!
Same here. OpenGApps 2017-06-02. PlayStore 7.9.30.Q - no widgets :-/
Edit: I installed now 7.8.74.P (from apkmirror) and the widget is back again.
klaust58 said:
Same here. OpenGApps 2017-06-02. PlayStore 7.9.30.Q - no widgets :-/
Edit: I installed now 7.8.74.P (from apkmirror) and the widget is back again.
Click to expand...
Click to collapse
Thanks!
Yes, I'm finding a similar behavior.
If I install from apkmirror the widget does return, though then Play Services keeps crashing on me.
What has worked for me so far is to start from an older Pico GApps release:
https://github.com/opengapps/arm/releases?after=20160423
It will then upgrade to the latest versions, and it seems to have the widgets.
I'm now just struggling to install Google Play Music, as I keep getting error -24, so I'm trying to configure the GApps installation.
But yes, progress.
So, I solved this by using the Aroma package, from the older date I just shared, and installing Play Music from there.
All is good now.
Sorry for the trouble, and I hope this helps others.
pjft said:
So, I solved this by using the Aroma package, from the older date ...
Click to expand...
Click to collapse
Yes of course...this is the hardcore solution
Just replacing Phonesky.apk in /system/priv-app is much quicker and easier

[HELP] Pixel Almost Unusable!

Hello,
My mother's Google Pixel (original) has just run into a somewhat common problem on Android Oreo. The problem and one working solution are mentioned in the following Reddit link:
https://www.reddit.com/r/GooglePixe...home_and_recent_buttons_stopped_working_dont/
I installed the Nova apk however when I went to choose the "Setup Wizard" activity, it is no longer there like it was a few months ago. I tried downloading older versions of Nova launcher to see if I could get it but I could not.
Does anyone know anyway in which I can force my pixel to the Setup Wizard?
Thanks!
Try with Factory Reset.

Mi 4/ Mi 3 Cancro instagram video`s keep buffering and doesn`t play at all

Hey yesterday i installed MK81.0-cancro-190321-RELEASE on my Xiaomi Mi 4. Installation was sucessful without any errors everything is working really well better then lineage os 14.1 for me i mostly use my mi 4 for Instagram and other social media services while using Instagram last night i noticed that video arent streaming at all just keeps buffering i tried clearing my cache from twrp also tried resetting network settings and also tried using Android system web view checked with chrome beta and stable but nothing is working. So if there is any fix for this bug please update me on that thank you.

Categories

Resources