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.
Related
Flashed from CM13 to CM14 without issues. However, every nightly after 11/16 causes my phone to not send txt messages. Have tried different apps, checked carrier settings, re-flashed, etc. Any help would be appreciated.
I think the Beanstalk thread gives us the best perspective on the issue. Probably early issues that will eventually get fixed.
Which baseband? This behaviour smells a lot like some of the other weirdnesses I've seen when I've had an image installed which was expecting a baseband other than the one I had in play. When I tried CM14 had the latest official O-something or other for the SM-G900P SPR and like a lot of folks, GPS was just not functional at all. So... after wiping the everythings (literally everything except my ejected microSD card) and reinstalling CM13 through TWRP certain operations (like initializing GPS) were still taking a good 30-45 seconds to initialize which wasn't the case previously with the late October nightly I was using. ...another sign that something has gone off the rails with the modem-y parts, and that they might be in a tizzy about being talked to with the wrong API.
So... just to reset everything I wound up reflashing the O-something stock firmware I had, then letting it upgrade itself via the two OTA patches to PK1. (Don't worry, I find the idea of tolerating Sprint's Crazy-Town modifications laughable.) Updated the profile and the PRL for giggles, and then reflashed in TWRP, wiped the everythings again and sideloaded the same CM13 nightly and Gapps.
I've just gotten things squared back away with CM13 and haven't had a chance to circle back around to try CM14 again (because all that other stuff takes a few hours and makes testing conflict with things like, sleeping and eating) with the new baseband, but the pass through stock and it's updates sorted out the strange 30-45s glitches. If anyone's actually tried CM14 with a PK1 baseband it would probably be worth hearing if they've got GPS and cellular traffic working simultaneously.
Update: Sure enough, after upgrading to the PK1 baseband (via a reflash to stock) CM14.1 seems to be able to handle cellular data and voice calls, wifi, bluetooth and GPS. There was a bit of weirdness with Allo making a terrible sound instead of beeping, but all things considered it looks like it's stable enough to be a daily driver for the SM-G900P now.
Hi all, long lurking rom-installer who can self-fix most problems here. Got a problem I can't fix that's bothering me. Recently upgraded to an S7 so naturally rooted it on day one and been trying to get it my-kind-of-working fully ever since. I do like to bugger about with things in a vain attempt to shield some private data from some orgs and realise I'm in a particularly specific hole that I'll probably have to climb out of on my own, but if you don't ask...
Internet using apps pretend to work, sometimes for days, then just refuse to open. Screenshot example of the second and persistent error (after simply "Lightning has stopped" the first time) is attached.
Model: G930F
Current ROM: ambasadii 7.0 TW Nougat (here)
Xposed: 88.2
Root: Magisk
Significant mods:
1) use xPrivacy
2) disabled significant number of remaining packages using Package Disabler Pro (list attached)
3) run Orbot
4) run AFWall
5) modify app permissions in Settings/Apps to restrict where I think I safely can
6) run BackgroundRestrictor
The behaviour still emerges even if I don't apply 4), 5) or 6), it has started prior to me finishing my tweaking.
I know xPrivacy is not supported for Nougat but it seems to work ok for the most part with some retweaking of settings since moving from Marshmallow on my old phone. I understand it could be the cause of the problem but I'm wedded to (some of) my privacy enough to persevere before abandoning it. For the record I've checked the usage log for restrictions on any calls around e.g. internet that might be interfering but I've been unusually generous with permissions trying to fix this and there's no restrictions on any apps with internet access around that, or much else really at this point. I've also had a look in general usage log rather than app specific, looking for system components that may be working alongside the app and failing with a restriction but can't see anything being denied. Any system apps haven't been touched by me, I fetched what I could from xprivacy crowdsourced restrictions on the base ROM apps and then only applied my template to apps I've downloaded myself.
Some other background on the problem: everything will be set up as I like it - ROM installed, debloated, all the rest of above modding applied. It will be working super-fine. Nice and fast, little bloat left, just enough Google to get Play Store, apps installed and working, all will be and appear fine. After an undetermined & fluctuating length of time all of the internet-facing apps will suddenly not open. This includes but isn't limited to the Browser (stock and Lightning, Brave, Pale Moon, etc.), Twitter, Signal and the Official TWRP App.
Interestingly, internet-connecting apps that will connect on demand but don't seem to make a call on every app open (mostly due to prior settings changes) do not fail. They will still open fine and work fine, connecting when asked and not crashing. For example, K9 Mail and Pocket.
Another weird data-point: Signal will fail but will often do so later than the other internet-connected apps - possibly it has a token with GCM or something that when it expires will try to renew on app open which is when it starts to fail like the others?
The apps will work again if uninstalled and reinstalled but once the behaviour starts again, and it will, it will repeat. Sometimes twice or more in a day. So reinstalling every time is not going to make for a usable phone. It's like they have an error renewing their wifi lease or something.
It can take up to three days to begin - this build it worked fine for days whilst I was away and slowly, progressively building the system back up with regular TWRP backups. I can restore a TWRP backup from about 6 hours before the problem started and it'll work fine again, but still wait a random amount of time before the problem begins again.
I did think it may be something to do with the router here and home WiFi as it behaved much better whilst away and didn't break until my return, though that is likely coincidence. I'm in pattern-observing mindframe so false positives are everywhere. I thought it was connecting to the PC via USB that was doing it at one point.
Last data point: it's happened with a different base rom too (Decent here), same thing, but came on sooner each time. I would change the base rom again to see if it's something there but I suspect that should be one of the last things I try given it's happened across two roms now.
Anyway, if anyone has any insight on Nougat TW ROMs on an S7 with this kind of set up and/or any clues or ideas as to why internet connects would suddenly be crashing all these apps... I'd be grateful. Otherwise I have many reinstalls and possibilities to eliminate. Which means waiting many sets of days before I can repeat, which makes progress frustratingly slow when you depend on the phone (Signal particularly) to connect with people.
AFWall stands out if you're having problem with net connections to apps etc
Yes good point, thank you. I think i've run the ROM with same problems without any rules applied but I've disabled it fully now just to be sure. Much obliged.
If it persists, the proper way of troubleshooting would be to clean install the ROM only, no tweaks, Xposed, firewalls or anything, just the ROM and your apps you're having problems with
If that all works together fine, then add ONE new thing to the mix, test for a few days, rinse and repeat until you add something that causes the problem again
With testing for a few days between each new addition you're be 100% sure what is causing it once it starts again
Thank you! Yes that's the plan but I thought I'd ask first as there's a lot of waiting down that route. I did do it to a point during last build but only waited overnight after each phase. I think I'll start that.now. I can always restore this backup if the solution presents in the meantime.
Yea that's what I was thinking, backup this ROM, clean install, work out the issue, restore this ROM and fix it
Good luck
Thank you I'll report back if/when I work it out, for any other possible future readers.
I changed the base ROM & installed Xposed in a different way and rooted in a different way and tweaked Permissions to be more permissive and and and... I've read rovo89's farewell so I won't say "It's xprivacy" but it's definitely how xposed & xprivacy interact, whether by flashable zip or systemless magisk. It'll work fine for a good while but then starts corrupting everything internet connecting. Removing it removes the problem & restores the app functionality.
Sadly it's the same even if you restrict nothing in xprivacy & just leave it installed & switched on. I've had to remove it. Considering trying to go back to MM as I know it worked on my previous phone.
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.
I was having some issues with my Galaxy s6, so I figured if they stopped supporting my phone, I might as well get a new OS on it myself.
I rooted and installed 9.0
https://forum.xda-developers.com/ga...20x-5x-nexusos-9-0-samsung-galaxy-s6-t3843199
At first I tried to install previous versions of Lineage, but kept having issues with registering through google, but this one worked pretty easily. I am now using Nova launcher.
The issues I have with it are:
Slower GPS location, like much slower. I am now traveling in Toronto, and it's ridiculously slow to find where I am compared when i was in NYC. I'll continue testing though, maybe it was just a temporary bug
Battery drain seems faster. I was hoping to get an improvement on this issue.
I get no notifications when I get messages through "google voice' I have to open the app to look at it
There is no number in a red circle next to the app to tell me number of messages for it
Substratum not working, keep getting "could not fall back to rooted mode" although according to root checker, I'm rooted. I have no experience with this app, but it seems like it's worth checking it out lol
I think there may be more 'issues' but those are the main ones right now.
I use the latest OFFICIAL LineageOS 14.1, these works fine for me.
Hey all, I have a OP 7 pro and ever since receiving the OTA update to 10.0.3 everything seems to be buggy. Soon after, 10.3.0 came along and is no better.
Some of my issues include:
- battery drain
- GPS not accurate
- Many apps showing no network connection even though I have internet
- apps crashing on their own
- play store and games won't stay logged in
There are other issues but I can't remember at there moment.
Is there a resolution for these? Can I download back to 9?
Thanks for any advice.
You are no lucky or you are a noob
Not sure how to analyze that answer.
I'm not lucky - sems to be quite a few out there who aren't lucky then... They are posts on many sites with users complaining about issues after this upgrade.
I'm a noob - relevant? Maybe I am, I used to have another XDA account which I don't use any more... Been a member since 2008 - installed my first rooted Rom - Valhalla for the Samsung Galaxy s 4g ( not the s4, the s 4g. - that was before the s2 came out).
Again, not sure what the relevance is, just trying to understand what went wrong with the OTA.
UnheardHawk said:
Hey all, I have a OP 7 pro and ever since receiving the OTA update to 10.0.3 everything seems to be buggy. Soon after, 10.3.0 came along and is no better.
Some of my issues include:
- battery drain
- GPS not accurate
- Many apps showing no network connection even though I have internet
- apps crashing on their own
- play store and games won't stay logged in
There are other issues but I can't remember at there moment.
Is there a resolution for these? Can I download back to 9?
Thanks for any advice.
Click to expand...
Click to collapse
Clear Cache in recovery, if that does not fix the issues, do a factory reset. Recommended to factory reset for maximum experience after big update., like from 9 to 10.
Did the clear cache... Still no joy
I was trying to avoid factory resetting. The upgrade on my OnePlus 5T went seamless. Oh well factory reset it is...
Just funny how Google apps seen to have the biggest issues... Lens always shows no network connection, and Google maps just plain won't pick up my location... Waze works fine which is the silly thing.
Have to wait till I get back home to do FR, thanks.
To be fair, there's not a whole lot one could say with the information given. Like are you completely stock? Rooted? What kinds of magisk modules if any? Etc...
All i can tell you is that i don't have any issues with the 10.0.3 update specifically or 10 in general.
But it does seem like your issues are related to gapps and services so I'd start there
Completely stock, I was thinking gapps... Will experiment and update
Get familiar with A/B slot partitions. It's a lot different from single slot systems.
Try a clean install through TWRP.
UnheardHawk said:
Hey all, I have a OP 7 pro and ever since receiving the OTA update to 10.0.3 everything seems to be buggy. Soon after, 10.3.0 came along and is no better.
Some of my issues include:
- battery drain
- GPS not accurate
- Many apps showing no network connection even though I have internet
- apps crashing on their own
- play store and games won't stay logged in
There are other issues but I can't remember at there moment.
Is there a resolution for these? Can I download back to 9?
Thanks for any advice.
Click to expand...
Click to collapse
Not entirely sure if this matters but are you using a carrier variant or unlocked straight from OnePlus? Also, I'm not one for factory reset, but if you were experiencing problems on 10.0.3 and now 10.3, I can only surmise that some bits were probably corrupt and a factory reset would do you some good. That or flash back to 9.5 and completely update back up. Someone mentioned in another thread, that you should install the full it's 2.1gb if you are running a custom kernel.
Sent from my OnePlus7Pro using XDA Labs
Straight from OnePlus.com on May 14...
I am on T-Mobile but didn't get it from them.