Database Info

Marshamallow piece of crap

Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This

Have you done a factory reset? that solves most problems.

jazf78 said:
Hi,
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
Click to expand...
Click to collapse
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dialer doesn't filters out contacts I decided to not show on the Contact app.
-(Not really a MM issue, but instead related to Cyanogenmod.) No call recording (another essential feature for me)!
The phone part of our "smart" devices is becoming worse and even more worse every update . Maybe it's time to come back to a Nokia 3310 or a Qtek 9090 like in the good old days

jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.

ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse

Nazeerchauhan said:
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.
Click to expand...
Click to collapse
im from México.

eemgee said:
Have you done a factory reset? that solves most problems.
Click to expand...
Click to collapse
i haven´t but i read somewhere else that a factory reset would not downgrade android version. since it also changed its firmware..
dont know if thats true or false.. did you or anyone reading this has actually done a factory reset and their android device downgraded itself? need to be sure, dont want to waste time, backing **** up, doing factory reset
only to notice it still marshmallow and then redownload and restore everything so i can use the phone and still have the problem.
thanks

jazf78 said:
ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse
I wasn't so much off-topic, it was something related to the thread title (Marshmallow piece of crap), but OK! I respect your statement. Last reply I make on this thread.
Hope tomorrow will be a better and happier day for you
Click to expand...
Click to collapse

jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
I think downgrading will be a more difficult task than a factory reset. A factory reset should clear all your issues.

Is this the dreaded lag issue (necessitating an RMA)?

About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer

computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance

crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?

computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example

crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.

Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?

I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!

computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha

crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer

computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.

Android Auto issues on Poco F1 Custom Roms

On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.

krilok said:
On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.
Click to expand...
Click to collapse
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.

MikelFuchs said:
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.
Click to expand...
Click to collapse
Please read the title: on custom roms, not miui...

You wrote on Oreo stock ROM it was present to.

oiseau1201 said:
You wrote on Oreo stock ROM it was present to.
Click to expand...
Click to collapse
Yes, and it was (plenty of comments on MIUI forums and over the net, if you want to take a look...) They fixed it on Pie, and if you're still running Oreo and don't have issues, then I guess they fixed it there, too.
This poll, topic and thread is for the issues still affecting Aosp based custom roms, such as Crdroid, PE, Lineage, etc.

Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.

Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta

aghilvr said:
Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.
Click to expand...
Click to collapse
I'm currently on Crdroid, and in my opinion it's the one that works best. As for the AA issue, it's present on all custom roms, but for the time being, I'm using the workaround I mentioned on OP and can use AA fully.

rn74 said:
Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta
Click to expand...
Click to collapse
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...

krilok said:
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...
Click to expand...
Click to collapse
Edit: just noticed. Are you using Waze for navigation? If you are, there's an ongoing location issue with the app running on MIUI...

Having the same issue running PIxelExperience and it's driving me nuts.
krilok said:
, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
Click to expand...
Click to collapse
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin

bob*nwk said:
Having the same issue running PIxelExperience and it's driving me nuts.
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin
Click to expand...
Click to collapse
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...

One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?

gella1992 said:
One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?
Click to expand...
Click to collapse
Wouldn't be able to confirm that, although I did read somewhere that if you're using any Dual apps on MIUI, AA won't work correctly. Are you using two WhatsApp accounts by any chance...?
I can tell you though that on the current rom I'm using (crdroid), they do work and appear on the cars screen, although most of the time there's no notification ringtone whenever they arrive. Since that was happening on my previous phones too, be it on nougat, oreo and pie, I guess that's a problem with AA itself...

Thanks for your quick reply.
Happy to hear that it is generally working.
Not using dual Apps. Will try to flash a custom Rom in the next days

krilok said:
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...
Click to expand...
Click to collapse
If you buy it, I guarantee you will be using it for a lot more than just that...

papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I can confirm this. Best $5,- I spent on an app ever.

papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I understand and appreciate the recommendation, but I've already got Macrodroid for other automation functions...

I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware

mf76130 said:
I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware
Click to expand...
Click to collapse
Works for me and others as well, although someone did mention on another thread he couldn't get this workaround to work either...
This is my setup:
USB debugging on and hardware overlays disabled.
In AA developer options, enable 720, 1080, unknown sources.
If it still won't work, then Im guessing it could maybe be due to different screen panels or something...

Two issues. One-handed mode puts phone to sleep, and where's the volume control?

My phone kept "falling asleep" for what seemed to be at random times when using the phone. I finally determined it was because of the one-handed mode. When I drag from the side, to the middle, which is supposed to activate the mode, it turns off the phone display off as if I pressed the button to do that, or double tapped it (which I have activated) - is anyone else experiencing this??
The other issue I have is that I recall having the open to pull the notification area down, and along with the brightness, it showed the volume too. I know that you are "supposed to" go to where the pen icon is to edit....but when I press on the three dots, the only option is brightness, so it's not even as if I have the option to enable that, even if I wanted to!
Thoughts? Is there a developer option I need to enable?
PS: I beg that you don't ask me for phone specifics if you're not sure that it would resolve the issue. I have no issue sharing that information with anyone. But if you don't know if Oreo, for example, is the cause...I'd rather not try to locate information that may never be used to troubleshooting, which would waste both of our times.

1: it should not turn off. Are you on an aftermarket display?
2: probably software issue. Did you flash update or OTA install?

GordenW said:
1: it should not turn off. Are you on an aftermarket display?
2: probably software issue. Did you flash update or OTA install?
Click to expand...
Click to collapse
Hi, thank you for the reply.
No I am not on an aftermarket display. I purchased this through Verizon.
Along those lines, all updates have been through the automated process built into the phone.
I agree that it appears to be software, or at least software that may have been installed. Is there a way to search by install date on my device? I may have to reverse engineer what application was installed when this happened (maybe about two months ago, probably less) - my only concern is I may uninstall that software but whatever change was made remains. Wondering if there is a "rollback" feature on the phone where I can just put it back to a certain point in time.

daveaphoto said:
Hi, thank you for the reply.
No I am not on an aftermarket display. I purchased this through Verizon.
Along those lines, all updates have been through the automated process built into the phone.
I agree that it appears to be software, or at least software that may have been installed. Is there a way to search by install date on my device? I may have to reverse engineer what application was installed when this happened (maybe about two months ago, probably less) - my only concern is I may uninstall that software but whatever change was made remains. Wondering if there is a "rollback" feature on the phone where I can just put it back to a certain point in time.
Click to expand...
Click to collapse
I would say the easiest is just to use lg UP to flash a slightly earlier version. I can't tell too much and I don't think an app being installed/uninstalled would matter.

Android 12

It's here people

dan0zone said:
It's here people
Click to expand...
Click to collapse
I am from the Philippines using an unlocked T Mobile V60. After reading this post, I checked the update in settings and saw this too. I am not sure I want to press the button though. I'll wait for braver souls to try it first I guess.

I like it so far. Even snappier. Mic and camera controls are nice.

One bug already: screenshot share and edit buttons do not do anything.

stardomains said:
One bug already: screenshot share and edit buttons do not do anything.
Click to expand...
Click to collapse
Have you made a factory reset? It's always recommend after a major software update

stardomains said:
One bug already: screenshot share and edit buttons do not do anything.
Click to expand...
Click to collapse
So I took the plunge and updated to 12. Screenshot edit and share works with no problems. I didn't do a factory reset.

siakgayyem said:
So I took the plunge and updated to 12. Screenshot edit and share works with no problems. I didn't do a factory reset.
Click to expand...
Click to collapse
I just found the problem: I had all animations to 0 in developer options. They need to be on at least .5 for share and edit of screenshots.

I was unable to type using any keyboard when using Naver Whale browser. Other browsers worked fine though. I had to manually update Naver Whale browser to enable typing again. This only happened after upgrading to 12.

Hi,
i have a t-mobile v60. i checked the system update page and i can see it but the download will not work. can anyone please send me the link to download the update so i can manually flash my phone?

I just got bought a used v60 TMobile variant and I'm trying to get it unlocked for my carrier here in Canada....I tried one site and they were unable to provide an unlock code (possibly the original owner didn't pay their bill). The IMEI comes up clean here when I ran it but I may be forced to have a remote unlock from what appears to be a reputable company online. They want to flash the v600vm kdz to unlock it.
It has android 12 update ready to download but I held off because
1. I don't know if it will affect being able to get it unlocked or flash the other variant firmware
2. I wanted to wait to see if there are issues with android 12 on it.
But I'm wondering if it's at all possible the android 12 firmware is no longer locked?
Any suggestions for my particular situation?

Has anyone else had camera problems since the android 12 update. The camera settings menu has dissapeared.

Anyone get display not registering movements/taps?
I thought that this was an issue with the drawing over other apps functionality that A12 has been cracking down on (Tasker, Pixel Filter, etc.), but even disabling/removing the aforementioned apps, this still happens intermittently, which renders that phone useless randomly. No matter how many times I lock/try to unlock the phone (via fingerprint), the screen just does not register taps/swipes...
And yes, this happened from A11-A12 upgrade, and is still present after doing a factory reset on A12.

I did a FDR and I still have several bugs.

pflatlyne said:
Has anyone else had camera problems since the android 12 update. The camera settings menu has dissapeared.
Click to expand...
Click to collapse
Can you be more specific? Are you in the photo or video mode for example? Have you tried deleting the cache (and/or data) of the camera app, and trying again?
EDIT: Are you using battery saver mode perhaps? I know when you are using extreme battery saver (or whatever it's called), camera app becomes real basic, and there is no settings menu.

BlackKnight23 said:
I did a FDR and I still have several bugs.
Click to expand...
Click to collapse
Like what?

nostrings said:
Like what?
Click to expand...
Click to collapse
Smart Lock notification was stuck in the settings menu, Bluetooth initial connection bug, when a folder is created to group apps and you click the plus to add + select the apps you want and click done, they are not added. These are the initial ones I've noticed. I've had a few times where I went to go back to a certain screen and it studders. Google Map when it's small cause you have to take a call or go to something else and try to click the square box won't maximize, you have to go to the app icon and select it. I do run Google bets apps. These apps didn't give me issues prior to update though.

AbbasIsmail said:
Hi,
i have a t-mobile v60. i checked the system update page and i can see it but the download will not work. can anyone please send me the link to download the update so i can manually flash my phone?
Click to expand...
Click to collapse
The update now available in the United States or maybe all of North America not sure... But there is a solution... try to change your location "VPN USA" and you will get the update

Can I update lg v60 demo unit to android 12?

ShaniquaLTE said:
Can I update lg v60 demo unit to android 12?
Click to expand...
Click to collapse
Yes I did it, with lg up following this metod, https://forum.xda-developers.com/t/v60-demo-unit-questions.4325951/page-5 first update to android 11 and then jump to 12. be carefull with the steps.