Related
Hi. somebody can tell if i can install sprint navigation in to AOSP 1.6 ?
shouldn't be a problem.
Google Nav is also available for this build of Android.
i tried this already. It installed fine. It opened fine. It found me fine. But as soon as it tried to navigate it said lost gps signal and it stayed lost the whole time. I have tried a few different times and got the same results. Not sure why though. FYI I also tried sprint tv and it worked fine, no hiccups with it all all.
dont quote me but i think i've read reports of gps not working with 3rd party apps, like weatherbug and crap like that on 1.6.
im probably wrong but dont feel like reading the whole thread again.
Hello All,
I hope that someone can help me because I have a strange problem.
I have just bought a LG GW910 phone. The phone seems to work fine (calls, web-surfing, wifi etc) but if I am using my data connection (NOT WIFI) I cannot connect to any HTTPS sites. This also means that I cannot sync my phone with my exchange server across my data connection.
I have testes if across WIFI and it works fine.
I have also tested it by turning off the SSL (and making the necessary mod on the server of course) and then it also works fine, but I don't want to leave it sending my password in cleartext.
Can anyone help? Is this a bug in WP7 or should I send my phone back.
I would be very grateful if people could answer asap so that I can arrange to send this phone back if necessary.
Thanks.
nebc100
given that you're the first to report it i might suggest speaking with your carrier about it?
Thanks for the comment! I would have thought the same thing if everything had not been working perfectly with my Touch Pro 2.
I cannot explain it, but I have managed to solve the problem.
I had tried resetting the phone and it hadn't helped.
I then tried (just to see how well it worked) doing a remote wipe of the phone (I had temporarily configured by exchange server not to require SSL). I then pannicked for about 40 minutes while my phone sat there with the LG logo and not starting.
FINALLY (YES... it takes AGES!!!) it started, and I configured it EXACTLY the same way as before, and now it works.
I honestly cannot explain it!
If anyone can come up with an explanation, I would LOVE to know.
Nick
well good to see you got it solved.
if i may: where did you acquire an LG GW910. is that not a developer phone? as in, not in the market? (it was actually the one WP7 that enchanted me the most.)
Hello,
I bought the device on ebay for €200. The price was certainly interesting!!
Sadly however, the problem that I was having yesterday has started again!! It is very strange!! It worked perfectly for approx 2 hours, and then at 00:40 this morning, it stopped. Now, again, I cannot access any form of https site (for exemple: www.live.com won't work as it directs me to an https site.) if I use the data signal. If I use WIFI it works fine!!
I am just trying another remote wipe of the phone to see if this solves the problem again.
Does anyone have any idea what could be causing this? Bad memory chip????
WORKING!!!!!!!
Hello All,
Problem officially solved now... phone been running fine since Saturday Morning.
It seems that the problem was partially due to my service provider, and partially due to a mistake that I made.
I connect through Orange Luxembourg (Formerly VOX). They have 3 APNs: vox.lu (their old APN that still worked perfectly with my Touch Pro 2), iphone3g.lu (which they implemented when they got the iphone) and then one that I have never used before: orange.lu
I had tried vox.lu and iphone3g.lu and they both worked fine for HTTP, but not for anything secured (HTTPS, SSL etc).
On Saturday morning, I suddenly remembered that there was the orange.lu APN and I tried it. The phone has been working perfectly since then!!
I can't explain why this APN works and the others don't, but I am not going to complain. It is now working fine, and to be honest, I am very happy with WP7. OK... it has some missing functionality, but I am sure the MS will sort out some of these issues given time.
So I land in Orlando on vacation, get my rental car, and enter the hotel address into Maps ready to push the navigation button as soon as I'm out of the garage. I do this and gps can't get a fix. I start driving in a random direction assuming it'll get a fix soon. Long story short, it never does!
I've been using gps, maps, navigation all with no issues until now. Had my phone since mid July. Tried restarting, tried battery pull, of course gps on/off a million times. Downloaded a free gps test app - if I was reading it right it seemed to show about 8-12 satellites it was picking up but 0 fixes. It's like the gps hardware is working fine but it won't get a fix on my location.
I'm on stock ROM. Haven't done anything weird or installed any new apps other than a fee games.
Any suggestions? I was counting on having maps/navigation while on vacation.
hollywoodfrodo said:
So I land in Orlando on vacation, get my rental car, and enter the hotel address into Maps ready to push the navigation button as soon as I'm out of the garage. I do this and gps can't get a fix. I start driving in a random direction assuming it'll get a fix soon. Long story short, it never does!
I've been using gps, maps, navigation all with no issues until now. Had my phone since mid July. Tried restarting, tried battery pull, of course gps on/off a million times. Downloaded a free gps test app - if I was reading it right it seemed to show about 8-12 satellites it was picking up but 0 fixes. It's like the gps hardware is working fine but it won't get a fix on my location.
I'm on stock ROM. Haven't done anything weird or installed any new apps other than a fee games.
Any suggestions? I was counting on having maps/navigation while on vacation.
Click to expand...
Click to collapse
The only thing I can think of is reprovision/factory reset. *2767*3855#. You'll lose EVERYTHING on your phone though. Make a backup first. If that doesn't work I don't know of any other way to fix GPS.
It sounds like the GPS receiver is working if it shows satelites, it just needs to download the catalog. You might try going outside and running some GPS software for an hour and getting a good download. Or you should be able to download a program like GPSstatus. then go to menu, tools, manage a-gps. From there do a RESET, then a DOWNLOAD. Then go outside for a while and you should start seeing fixes on satellites.
I like worwig's suggestion. I'm not familiar with GPS fixes, so it's great if what he said will work. Reprovisioning tends to fix anything related to radio problems (if IMEI was never lost)
GPS Woes Continue
Zalithian said:
The only thing I can think of is reprovision/factory reset. *2767*3855#. You'll lose EVERYTHING on your phone though. Make a backup first. If that doesn't work I don't know of any other way to fix GPS.
Click to expand...
Click to collapse
Tried this. Problem still persists. Can't get lock in Maps unless I let it go for over a minute. If I use GPS Test or GPS Status, it IMMEDIATELY reports 27 satellites in view, but shows connected to 0 for a good 20~30 seconds, then slowly starts to connect to one at a time.
Again, fully stock, non-rooted, locked bootloader.
try this in the Market:
https://play.google.com/store/apps/details?id=com.androidlab.gpsfix&feature=search_result#?t=W10.
its been listed in other forums that it works, and as i haven't used it myself, will go by what others say that works.
if nothing else, its free
goldsmitht said:
try this in the Market:
https://play.google.com/store/apps/details?id=com.androidlab.gpsfix&feature=search_result#?t=W10.
its been listed in other forums that it works, and as i haven't used it myself, will go by what others say that works.
if nothing else, its free
Click to expand...
Click to collapse
This is the ONLY app I have not tried on the market and I finally got a working gps on my S3 with Synergy Rom & Unlocked bootloader (of course) ... So thank you for the mention of the app!
Thanks to everyone who's tried to help. I've tried everything here except for a factory reset which was my last resort. So far nothing has worked. The first time I did the GPS Test thing, it worked, but then 5 minutes later when I went to use maps, it wasn't working again. I tried the other app - GPSfix as well - nothing. Also spent an hour on the phone with a Verizon Tech trouble shooting - not that I thought they'd know more than I could find on my own here, but figured it was worth a try.
I'll be factory resetting in a week or so (don't wanna do it now cause I don't have time to reset up everything on my phone right now). When I do I'll report back. Also I did find over on droidforums that there are several people who've had this exact same issue with their S3 - GPS worked fine then suddenly didn't work at all. So it may be a bigger glitch that's triggered somehow in some phones. All I know is I need my gps working and reliable on my phone...
If anyone else has had this issue and figured it out, let us know. Otherwise, I'll report back after the factory reset...
GPS Issue
hollywoodfrodo said:
Thanks to everyone who's tried to help. I've tried everything here except for a factory reset which was my last resort. So far nothing has worked. The first time I did the GPS Test thing, it worked, but then 5 minutes later when I went to use maps, it wasn't working again. I tried the other app - GPSfix as well - nothing. Also spent an hour on the phone with a Verizon Tech trouble shooting - not that I thought they'd know more than I could find on my own here, but figured it was worth a try.
I'll be factory resetting in a week or so (don't wanna do it now cause I don't have time to reset up everything on my phone right now). When I do I'll report back. Also I did find over on droidforums that there are several people who've had this exact same issue with their S3 - GPS worked fine then suddenly didn't work at all. So it may be a bigger glitch that's triggered somehow in some phones. All I know is I need my gps working and reliable on my phone...
If anyone else has had this issue and figured it out, let us know. Otherwise, I'll report back after the factory reset...
Click to expand...
Click to collapse
Hollywood,
Just out of curiosity, were you ever running Synergy?
With my situation, it took three calls to VZW, and an hour-long phone call to Samsung (which resolved nothing) to get a new phone shipped to me. The only good thing that came from the Samsung phone call was that I used it as ammunition when calling VZW the last time ("Look, I was even on the phone with Samsung tech support for an hour today, and they couldn't help me."). The Samsung rep had never even heard of the term "GPS Lock" and didn't understand the concept. She was totally convinced that if the blue arrow came up in Google Maps, that my GPS was working as it should, despite the still-flashing GPS icon and the "Searching for GPS" message in the pull-down screen. Also, she didn't think it was a problem that my positional accuracy never got closer than 3,400 meters.
A complete factory reset didn't help me; I even used Odin to reload stock, non-rooted, locked bootloader OTA ROM with original kernels, recovery, radios, etc.
I also tried the re provisioning dialer code, which didn't help.
I tried the GPS Fix program, GPS Test, GPS Status, and everything else I thought looked promising. Nothing helped.
GPS Fix helped after initial lock, but only while it kept GPS control. Once it released "fix", Maps would go back to having the same problem getting a lock after a while.
Good luck!
Search for the agps patch. Any forum will work. It works on all android. I just flashed it and I'm running beans. It also works for like cm. I used the 3.1 cwm flashable patch. It locks gos on instantly.
Sent from my SCH-I535 using Tapatalk 2
GPS Issues
So now that I have my new SGS3 on the way (should be here in two days) my GPS starts working again out of the blue. No changes to my phone, no new apps. Too weird that after three weeks of it not working right, it suddenly works perfectly again.
At least the issue shouldn't repeat once the completely new phone arrives.
check this link out
http://forum.xda-developers.com/private.php?do=showpm&pmid=8541888
Ryezen said:
So now that I have my new SGS3 on the way (should be here in two days) my GPS starts working again out of the blue. No changes to my phone, no new apps. Too weird that after three weeks of it not working right, it suddenly works perfectly again.
At least the issue shouldn't repeat once the completely new phone arrives.
Click to expand...
Click to collapse
My phone is doing something very similar, it's finding various satellites and finding a fix on 3 of them. Although, in Google Maps and Navigation, it will stay stuck on searching for GPS. This phone has been great since day 1 including GPS, strange that it will stop working just like that. I tried clearing data for Maps, running other GPS utilities, and a factory reset to no avail.
Decided to phone Verizion, and they will send me another S3 (refurb).. Hoping the new one works as it should.
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Lagarde said:
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
nasch007 said:
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
Click to expand...
Click to collapse
Appreciate you looking at that. I haven't tried 18.1 yet, as I'm a bit gunshy after how bad 17.1 went for me. I'm strongly suspecting most of my issues go back to Project Fi...but it's not the SIM. I've actually bought 2 extra SIMs over the years trying to resolve this very issue. They all do the same thing on LOS.
Hadn't seen the splitting of gapps. That's news to me. Will look into that, as Project Fi requires the largest of the gapps...which is too big to fit into the system partition.
Lagarde said:
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
shaunoleary said:
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
Click to expand...
Click to collapse
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
AsItLies said:
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
Click to expand...
Click to collapse
Not using TWRP, I'm just using LOS recovery. Sadly, it doesn't allow for doing backups, but it does the job otherwise.
Just an update BTW - currently running into issues with Google Pay/SafetyNet, but it's due to Google playing silly buggers with GPay again, not the fault of LOS.