Hi guys,
I've updated the phone to the last global beta - 7.12.28 and noticed one big issue and a few other smaller ones. I hope someone might have ideas on how to fix them.
The WiFi turns on as soon as the screen is off. What I've done so far is to make sure no app has permission to turn the WiFi on (using the built in permission manager). I've cleared cache and rebooted the phone several times.
Another issue is the MIUI memory optimization is always disabled, no matter if you change it to something else or not.
And the third one that I can think of right now is the region - it always reverts back to China. Now this has been outgoing for a while, so it might be something with my phone.
What I've done on the phone is to root it and have Xposed install and active. I've also ran Unbloatmi, great script to get rid of apps you don't need. I haven't tried alternative roms like Lineage.
Recently I installed floppy kernel, but the wifi issue remains with the stock kernel too.
I'm open to suggestions
Issue resolved with the next update.
I suggest to you to use global stable. It's old, but global dev is always bugged for this phone. Do what you want, but my experience is bad
Yeah it's always preferred to use stable roms on phones in production environment. But I like to live on the edge And I got into the routine to remove most of the unnecessary apps right after the update. So overall - the phone is quite stable. But now it has the same MAC as my wife's phone. Go figure...
I am considering Putting Lineage OS on my S9+ but am unsure of a few things.
I have read many threads on the subject and see that there are a number of things that can go wrong. Unfortunately, the answers use many abbreviations which means I have no idea what they are talking about. Also they talk about flashing the stock firmware to get the camera working. This seems to be different to the OS.
I did successfully install CyanogenMod on my Galaxy S2 and was very happy with it. I'm particularly unhappy with the direction of Samsung's updates. Every new update seems to break something else I use regularly.
My alternative to installing Lineage OS is to downgrade to Android 9, but remembering how snappy and clean CyanogenMod was on my S2 I'd certainly prefer Lineage as long as key functions work.
With that in mind, here are my questions:
1/ Can the Bixby button be configured to operate the flashlight without unlocking the phone? I currently have an app that does that, although it's a little unreliable and sometimes takes 3 presses.
2/ If for some reason I don't like Lineage, is it reasonably easy to go back to a stock OS? (My phone is no longer under warranty.)
3/ I understand the camera does not work as well. Is this a problem with basic picture quality or is it just some of the more advance features that are missing?
4/ Is Lineage OS compatible with Google Daydream? Samsung removed Daydream support with the Android 10 update and this is the main reason I want to go to the effort of changing the OS on my phone.
5/ Is star2lite the correct version of Lineage for my phone, SM-G965F?
5 yes. See supported model
https://wiki.lineageos.org/devices/star2lte/
2 should be fine with odin. But knox keeps triggered
All other questions
https://forum.xda-developers.com/ga...evice-development/rom-lineageos-17-1-t4083325
kurtn said:
5 yes. See supported model
https://wiki.lineageos.org/devices/star2lte/
2 should be fine with odin. But knox keeps triggered
All other questions
https://forum.xda-developers.com/ga...evice-development/rom-lineageos-17-1-t4083325
Click to expand...
Click to collapse
Thanks for your reply.
I couldn't find any mention of the Bixby button in that thread, but installed Lineage anyway. So far I have not had any luck getting access to the Bixby button. I've tried Bxactions and Button Remapper. BxActions requires Bixby on the device and seems to work by detecting Bixby starting, so that's not a solution. Button remapper looks promising, but refuses to activate. I just get in a loop of being told to run the PC software. Everything looks OK, but when I come out of the setting it's still switched off.
As for Daydream, it runs but looks like at a very low frame rate. I tried both reduce blur and reduce flicker, but both are not pleasant to use. Also, Skybox video player doesn't work at all. It starts and connects, but just presents a blank display.
As an experiment I tried to use Odin go back to a stock Samsung Android 9, but the boot loader is locked at 10 so I guess I can't do that either.
Looks like a phone I originally chose because of its good VR support is just going to be a basic device. Not having the torch on the Bixby button is something i'm going to sorely miss. I use the torch many times a day for work and not having to unlock the phone was great.
Mike Warren said:
Thanks for your reply.
I couldn't find any mention of the Bixby button in that thread, but installed Lineage anyway. So far I have not had any luck getting access to the Bixby button. I've tried Bxactions and Button Remapper. BxActions requires Bixby on the device and seems to work by detecting Bixby starting, so that's not a solution. Button remapper looks promising, but refuses to activate. I just get in a loop of being told to run the PC software. Everything looks OK, but when I come out of the setting it's still switched off.
As for Daydream, it runs but looks like at a very low frame rate. I tried both reduce blur and reduce flicker, but both are not pleasant to use. Also, Skybox video player doesn't work at all. It starts and connects, but just presents a blank display.
As an experiment I tried to use Odin go back to a stock Samsung Android 9, but the boot loader is locked at 10 so I guess I can't do that either.
Looks like a phone I originally chose because of its good VR support is just going to be a basic device. Not having the torch on the Bixby button is something i'm going to sorely miss. I use the torch many times a day for work and not having to unlock the phone was great.
Click to expand...
Click to collapse
I'm sure the bootloader is mot locked in lineageOS 17.1
kurtn said:
I'm sure the bootloader is mot locked in lineageOS 17.1
Click to expand...
Click to collapse
I'm not having any luck with loading either a 9 image or a 10 image using Odin. Is there another way?
Every time I try the phone displays: SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 9. BINARY: 7
Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.
You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s
nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).
Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.
roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?
For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".
jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.
Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.
Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.
jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.
Hi I have the OnePlus 9 pro running Android 12. Stock, with all updates. I have gotten fed up with the operating system resetting my choices on battery optimization and permissions. This is related to notifications. I do not receive notifications from apps unless I have both made them a battery optimization exemption, and manually given them all requested permissions. But every time I restart my phone, or if there is an update, the operating system resets all of these changes to default, effectively silencing all notifications from these apps until I manually change them again. It's upsetting enough that I have to make these changes in order to get notifications. The fact that the system resets them all of the time is just annoying. Can I disable the system resetting these changes if I root my phone only? Or is it necessary for me to install a Rom that doesn't do this to my apps? On a side note I use Nova launcher because I dislike the lack of customization from OnePlus operating system. Thank you for any advice you can give me
TL;DR: OnePlus resets my battery optimization choices and my permission choices regularly. Can I fix this If I root or is a new ROM necessary to stop this?
DuchessOfAvon said:
Hi I have the OnePlus 9 pro running Android 12. Stock, with all updates. I have gotten fed up with the operating system resetting my choices on battery optimization and permissions. This is related to notifications. I do not receive notifications from apps unless I have both made them a battery optimization exemption, and manually given them all requested permissions. But every time I restart my phone, or if there is an update, the operating system resets all of these changes to default, effectively silencing all notifications from these apps until I manually change them again. It's upsetting enough that I have to make these changes in order to get notifications. The fact that the system resets them all of the time is just annoying. Can I disable the system resetting these changes if I root my phone only? Or is it necessary for me to install a Rom that doesn't do this to my apps? On a side note I use Nova launcher because I dislike the lack of customization from OnePlus operating system. Thank you for any advice you can give me
TL;DR: OnePlus resets my battery optimization choices and my permission choices regularly. Can I fix this If I root or is a new ROM necessary to stop this?
Click to expand...
Click to collapse
That's really odd that it's doing this to you. Never had this issue on any of my OP devices. Including stock OOS and custom ROM's. Which variant do you have, which firmware are you running, have you tried factory resetting then setting up your device and seeing if the issue persists?
TheKnux said:
That's really odd that it's doing this to you. Never had this issue on any of my OP devices. Including stock OOS and custom ROM's. Which variant do you have, which firmware are you running, have you tried factory resetting then setting up your device and seeing if the issue persists?
Click to expand...
Click to collapse
Thank you for replying. My phone says it's Android 12 with the August 5, 2022 security patch.
Build # is LE2125_11_C.63,
Baseband version is Q_V1_P14,
kernel version is 54147-qgki-g2f286f199c5a,
Hardware version is LE2125_12.
I have not tried factory resetting yet, and if I get a new software that would happen anyway, so I suppose it's worth a shot. The phone also likes to reset some apps. Like the Twilight blue light filter app. I woke up one day to find the phone had reset the app back to default, and I had to set it up and all it's permissions up all over again. I didn't realize this wasn't normal because when I searched, I couldn't find anyone with the same problem. I just thought the battery optimization was super extreme this time around. I'll backup my favorite apps and try a reset and see if that works. Thank you again for responding.
DuchessOfAvon said:
Thank you for replying. My phone says it's Android 12 with the August 5, 2022 security patch.
Build # is LE2125_11_C.63,
Baseband version is Q_V1_P14,
kernel version is 54147-qgki-g2f286f199c5a,
Hardware version is LE2125_12.
I have not tried factory resetting yet, and if I get a new software that would happen anyway, so I suppose it's worth a shot. The phone also likes to reset some apps. Like the Twilight blue light filter app. I woke up one day to find the phone had reset the app back to default, and I had to set it up and all it's permissions up all over again. I didn't realize this wasn't normal because when I searched, I couldn't find anyone with the same problem. I just thought the battery optimization was super extreme this time around. I'll backup my favorite apps and try a reset and see if that works. Thank you again for responding.
Click to expand...
Click to collapse
Weird that when I woke up, Repainter reset my system theme I was using and even though it's still enabled app-side, it's disabled system-side. Now I gotta figure out why lol. I would recommend factory resetting for sure first to see if that helps at all. Make a full system/internal backup and copy it to your PC before doing so. Feel free to reach out if it worked or didn't work for you.
DuchessOfAvon said:
Hi I have the OnePlus 9 pro running Android 12. Stock, with all updates. I have gotten fed up with the operating system resetting my choices on battery optimization and permissions. This is related to notifications. I do not receive notifications from apps unless I have both made them a battery optimization exemption, and manually given them all requested permissions. But every time I restart my phone, or if there is an update, the operating system resets all of these changes to default, effectively silencing all notifications from these apps until I manually change them again. It's upsetting enough that I have to make these changes in order to get notifications. The fact that the system resets them all of the time is just annoying. Can I disable the system resetting these changes if I root my phone only? Or is it necessary for me to install a Rom that doesn't do this to my apps? On a side note I use Nova launcher because I dislike the lack of customization from OnePlus operating system. Thank you for any advice you can give me
TL;DR: OnePlus resets my battery optimization choices and my permission choices regularly. Can I fix this If I root or is a new ROM necessary to stop this?
Click to expand...
Click to collapse
Look here https://dontkillmyapp.com/oneplus#user-solution
Thanks, I did go through that page already. Most of those menu options aren't present in the OnePlus 9 pro on Android 12, and the rest I tried but nothing changed. For example, I have my blokada app locked in the recent apps, but choosing "close all" closes it in spite of this. Just another mark against OnePlus' software.
DuchessOfAvon said:
Thanks, I did go through that page already. Most of those menu options aren't present in the OnePlus 9 pro on Android 12, and the rest I tried but nothing changed. For example, I have my blokada app locked in the recent apps, but choosing "close all" closes it in spite of this. Just another mark against OnePlus' software.
Click to expand...
Click to collapse
I think you jinxed me. Repainter hasn't been working all day and the xda app won't let me login for some reason. It logs in, but still shows the key icon and none of my subscribed threads load. That's really odd that when you lock an app in recents, it still clears regardless. Which launcher are you using? When I was on OOS, I used Nova and when I locked apps in recents and hit 'clear all', said app would still remain. I didn't care to use OOS12, once I realized there was no color code theme option, I went back to OOS11 until I took the plunge to update my fw to use Nameless again.
TheKnux said:
I think you jinxed me. Repainter hasn't been working all day and the xda app won't let me login for some reason. It logs in, but still shows the key icon and none of my subscribed threads load. That's really odd that when you lock an app in recents, it still clears regardless. Which launcher are you using? When I was on OOS, I used Nova and when I locked apps in recents and hit 'clear all', said app would still remain. I didn't care to use OOS12, once I realized there was no color code theme option, I went back to OOS11 until I took the plunge to update my fw to use Nameless again.
Click to expand...
Click to collapse
I'm sorry! I have innate bad luck, sometimes it runs off on people. I was using the OnePlus launcher at first but after I switched to Nova it stopped happening I think. I've reset my phone now, hoping it is fixed.
DuchessOfAvon said:
I'm sorry! I have innate bad luck, sometimes it runs off on people. I was using the OnePlus launcher at first but after I switched to Nova it stopped happening I think. I've reset my phone now, hoping it is fixed.
Click to expand...
Click to collapse
I guess so! Still can't login to xda for some reason... Well that's good that so far it's working right. Sorry you had to reset your phone and everything just to get it to work again. I hate when I have to do that. Feel free to reach out again if it starts happening again.
Edit: rebooting seemed to fix the xda/repainter issues. Just sucks I lost my 10+ days uptime streak lol
I recently upgraded from LOS 18.1 to 19.1. I was having issues with battery drain and finally decided to upgrade. The battery issues are completely fixed. A new issue cropped up with my profiles however. I have a "home" profile that disables the lock screen when my phone connects to my home wifi.
Since the upgrade, when my lock screen is disabled, my home and recent apps button stop working. Other things stop working as well like being able to copy paste between apps. My somewhat usable workaround for now has been to enable the recent apps screen when double tapping the home button, for some reason this works. I can return home by tapping the outer edge of the recent apps screen. This is what I'm running for device and OS:
Device - Poco X3 Pro (Vayu)
OS - LineageOS 19.1 microg Oct. 24, 2022 release(from https://lineage.microg.org/)
Recovery - TWRP
I found a bug report on Gitlab for the exact same issue here: https://gitlab.com/LineageOS/issues/android/-/issues/5189
They're reporting it as fixed for the most recent builds, which I'm currently running and still having the problem.
I'd really like to avoid a device wipe and reinstall as I have some MFA apps for work that would be a big pain to get going again. Does anyone know of any fixes? I'm guessing it's permissions related of some kind as it's like the device is only half unlocked or something. I've tried creating a new profile as well as disabling profiles, rebooting, and trying again, nothings worked so far. Should I just open another bug report on Gitlab? Appreciate any help.
This seems to have stopped, but I have little idea as to why. I noticed it stopped after I connected my phone to my PC with a USB to transfer files. After I did that, for some reason the lock screen disable is working fully as intended now. All nav buttons work, copy+paste, etc.