Develop Bugs

Post issues found in the ICS Leak (I927UCLG9)

its real nice to finally have some ICS goodness on my phone, but i have found some issues.
my Motorola Roadster 2 bluetooth speakerphone does not work well with this version of ICS. will not let me use the call/text button.
i am finding some apps not working correctly, i.e. Pushover - the notifications do not make a sound. Not sure if that is an app issue, or an ICS issue.
*edit* ok so it seems that i am not getting any notification sounds. sms, voicemail, etc...
also the volume in general does not seem as loud as the 2.3.6 firmware was.
anyone else find any issues?
*UPDATE* after wiping within cwmr most of my issues were no longer present. the only problem i had still was that notification sounds didnt work after a couple hours. i dont know the cause, but i used audio manager widget and set the profile to loud, and restarted phone. havent had them go out since.

I have all these issues except tue bluetooth thing
Sent from my SGH-I927 using xda premium

jayjayjoker2 said:
I have all these issues except tue bluetooth thing
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
atleast it is not me.
i am going to reflash my phone to see if it may be an issue with not clearing out the phones memory and storage first...

My wifi didn't work for a while. It would see my access point but wouldn't connect. Reset the router and everything went back to normal. GPS works, Stereo BT/OBEX works, 4G works, camera works. Those were my big items, as I'm sure they are most people's.
My only issues are that I can't switch to 2g (At&t rom....) and how friggin Touch-wizzy everything is. I was expecting them to embrace the whole holo thing a lot more, but all the buttons feel like they belong in GB, same with the notification menu and the settings icons.
EDIT: I am on rogers, in case any rogers people see this so they know that everything works on our network

i wiped via cwmr and reflashed the ics rom. notifications work again. have not rooted yet, wondering if that may have been an issue with it...

Changing the lcd DPI causes the rom to corrupt i guess, since when i do it, after the reboot, i get to the samsung "logo" and then black screen, and it feels like the device has shut down. The only app that would say "success" when i change the value is Lcd Density Modder.
- i had the notification sound bug, but then i changed the notification sounds to my likings, and then i used Audio Manager widget to set the volume loud, no problems ever since.

ok rooted and all is fine. maybe i just had a bad flash. my bluetooth speakerphone still doesnt work, but that is an issue that i will have to research

For me, i had the only issue with ICS (excluding the known thing with the keyboard not flashing) - timezones from 2011 year with wrong summer times.
Luckyly fixed it with timezone fixer from google play.

Tethering doesn't work, seems to be broken and results in a blackscreen.. Both Usb and Wifi Hotspot give this issue.. Anyone else getting this

One weird thing my phone does is when it's been asleep for a while, the lockscreen clock will fall behind and when I wake it up, it'll catch up a couple dozen minutes at a time.
~Azrael's Kiss~

Wifi is slooow, getting 800k when I should be getting 20mbs
Sent from my SGH-I927 using xda premium

My wifi still not working
Tyfighter said:
My wifi didn't work for a while. It would see my access point but wouldn't connect. Reset the router and everything went back to normal. GPS works, Stereo BT/OBEX works, 4G works, camera works. Those were my big items, as I'm sure they are most people's.
My only issues are that I can't switch to 2g (At&t rom....) and how friggin Touch-wizzy everything is. I was expecting them to embrace the whole holo thing a lot more, but all the buttons feel like they belong in GB, same with the notification menu and the settings icons.
EDIT: I am on rogers, in case any rogers people see this so they know that everything works on our network
Click to expand...
Click to collapse
I'm on rogers too and my wifi is till giving me trouble. I haven't tried the resetting the router yet, but at work it doesn't connect too. Anyone else having this problem.

jvuong said:
I'm on rogers too and my wifi is till giving me trouble. I haven't tried the resetting the router yet, but at work it doesn't connect too. Anyone else having this problem.
Click to expand...
Click to collapse
I've rogers version but unlocked and working with a local carrier. Wifi is not a problem at all, i'm getting the same speed and used wifi continuously for over 2 hrs to download all my apps back after the update.

When typing with the keyboard, pressing the alt. Key once makes it select all the special characters. I liked the older one where if you press it once, it operates just once when selecting the special character, and pressing it twice makes it select more than one. Not that big of an issue but to some people it may be.
Also, the brightness thing. When I turn off the screen, and turn it on again, it flashes from the highest brightness to the current.
Sent from my SGH-I927 using xda premium

jvuong said:
I'm on rogers too and my wifi is till giving me trouble. I haven't tried the resetting the router yet, but at work it doesn't connect too. Anyone else having this problem.
Click to expand...
Click to collapse
On AT&T here, and having wifi issues as well... Once the phone drops wifi at idle, it doesn't want to pick it back up unless I turn wifi off and back on again. Setting the wifi to never sleep has been my only workaround.
Also having some issues with the button backlights. If I don't touch the phone long enough for the button backlight to turn off, touching the buttons won't turn the light back on. Touching the screen turns the backlight on again, but it's slightly annoying.

I haven't noticed any wifi issues and I use my Glide exclusively as a wifi device. I'm copying my backup of Inception v2 back right now though because the battery drain on the ICS ROM is definitely an issue. Losing like 10% an hour with my phone just sitting there with the screen off.

bobbinthreadbare said:
I haven't noticed any wifi issues and I use my Glide exclusively as a wifi device. I'm copying my backup of Inception v2 back right now though because the battery drain on the ICS ROM is definitely an issue. Losing like 10% an hour with my phone just sitting there with the screen off.
Click to expand...
Click to collapse
so weird everyone having battery problems. mine runs better than it did on stock 2.3.6 and the battery lasts longer....

inthepit said:
so weird everyone having battery problems. mine runs better than it did on stock 2.3.6 and the battery lasts longer....
Click to expand...
Click to collapse
Have you ever took note of your battery life with a custom ROM or kernel? When I picked up my Glide it had a stock ROM but I only had it for an hour before I put a custom on it. I didn't mess with the stock one at all so I can't compare to stock 2.3.5/6. But with Inception v2/ardatdat, it was definitely better.
I was going to restore my backup but copying it back to my phone made me realize how painful it is to copy backups with CWMR 6 compared to 5. That new blobs folder makes so many files that it took 3 hours to copy 3 of my backups over USB. Ouch.
But since last night, the battery life seems to be behaving better. Its been sitting here and not just dying. I'm wondering if it could be the battery stats file. Maybe I'll try wiping it. I'm sure once we get a lower voltage kernel and I can underclock with profiles for the screen-off and stuff, it'll be fine again.
Unrelated but has anyone taken a screenshot with the ROM yet? ICS is supposed to have it built in, power button + volume down at the same time for a few seconds from what I read, but didn't seem to work.
Edit: Its home + power button at the same time.

ninthsense said:
I've rogers version but unlocked and working with a local carrier. Wifi is not a problem at all, i'm getting the same speed and used wifi continuously for over 2 hrs to download all my apps back after the update.
Click to expand...
Click to collapse
Damn i hope its not my phones wifi:crying:

bobbinthreadbare said:
Have you ever took note of your battery life with a custom ROM or kernel? When I picked up my Glide it had a stock ROM but I only had it for an hour before I put a custom on it. I didn't mess with the stock one at all so I can't compare to stock 2.3.5/6. But with Inception v2/ardatdat, it was definitely better.
Click to expand...
Click to collapse
when you flashed ICS did you wipe everything then run the ics installer? my first install sound and such didnt work, so i wiped the phone in cwmr and reflashed ics and it is better that it was on 2.3.6

[Q] Freezing

Is anyone having any issues with their 2013 N7 freezing? I've had it completely freeze up on me once, and several time just today it has had major input lag (like 2-3 seconds later) or would just not accept input. It hasn't been localized to any particular app.
Is this a common problem? Should I just go exchange mine?

Seems like a software issue which can be easily remedied.

Username invalid said:
Seems like a software issue which can be easily remedied.
Click to expand...
Click to collapse
When I first got my new Nexus 7 I did notice some "freezes" and unresponsiveness. Touches that would go unrecognized (links in the browser, back button). did a factory reset and watched it in case I decided I needed to exchange it. But it is seemed to improve and I rarely run into the freezing.
I've so far not returned/exchanged it, but an still keeping an eyes on it.

I have most certainly experienced a heavy freeze period while typing on the onscreen keyboard. While typing in all the credentials on first set-up I experienced moments of almost 20 seconds of non-response, followed by all input entering as if it was lagged out network style.
Rooting and flashing a new rom, this has yet to happen. This is why I love Android so much... its community knows that it is Unix and treats it as such.

Yea mines freeze sometimes
Sent from my Nexus 7 using Tapatalk 4 Beta

yeah sometimes mine locks up for like a good 15 seconds.. hitting the power button doesn't shut the screen off either.. then when it unfreezes, it does everything I did lol like pull down the bar, hit home, and the screen off
Sent from my Samsung Galaxy S4 using Tapatalk 4 Beta

jayochs said:
yeah sometimes mine locks up for like a good 15 seconds.. hitting the power button doesn't shut the screen off either.. then when it unfreezes, it does everything I did lol like pull down the bar, hit home, and the screen off
Sent from my Samsung Galaxy S4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same issue. I think I will factory reset it + install cleanrom with the jassy kernel and see if it helps. If not, I will swap it. I love this thing! Its getting more love than my ipad atm, but I think I can make room for both of them in my already-gadget-overloaded life lol.

Gabik123 said:
Is anyone having any issues with their 2013 N7 freezing? I've had it completely freeze up on me once, and several time just today it has had major input lag (like 2-3 seconds later) or would just not accept input. It hasn't been localized to any particular app.
Is this a common problem? Should I just go exchange mine?
Click to expand...
Click to collapse
I have seen this several times with the Swipe keyboard. Since going back to SwiftKey it has not happened.

Gabik123 said:
Same issue. I think I will factory reset it + install cleanrom with the jassy kernel and see if it helps. If not, I will swap it. I love this thing! Its getting more love than my ipad atm, but I think I can make room for both of them in my already-gadget-overloaded life lol.
Click to expand...
Click to collapse
I was wondering if its really the kernal that's causing the freezing. My N7 2013 right now freezes after about 15 minutes of turning it on, and the only way to unfreeze is by holding down the power for 10 seconds. My tablet will constantly do this after each turn on, but once I placed it in safe-mode there is no freezing. I am thankful that mine doesn't have the touch screen issue though! but this freezing problem is really driving me bonkers.

I nodded off for a few minutes the other day when I had FBReader up and when I woke up and tried to exit it was non-responsive. I get the impression FBReader forces the screen to stay on, but perhaps everything else goes to sleep anyway? That's the only freeze I can remember seeing.

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

[Q] touch key lights bug

hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?

Install a custom rom like cyanogen or something stock based.

I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk

Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.

Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk

Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.

LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!

LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.

TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.

LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?

TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.

LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?

Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su

I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.

Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.

No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...

Uresponsive black screen after updating to Android 10

After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?

darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.

v12xke said:
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
Click to expand...
Click to collapse
I didn't have the issue on Pie and haven't installed any additional apps. It mainly happens after I haven't used the device for a while. It feels like it won't wake up so I have to hold the power button to force a reboot.

darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
Yes.
I was just peaking to a buddy with a 2xl and he is having the same issue since 10.

I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.

bobbyphoenix said:
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
Click to expand...
Click to collapse
I just had a random reboot while taking my dog for a walk. Was only listening to SiriusXM. Think I'm going back to Pie until Google gets the kinks ironed out on 10.

https://support.google.com/pixelphone/thread/14074635?hl=en

Booted into safe mode last night and had to force a reboot this morning to get the screen to respond. This is definitely an issue with 10 and not an app. I'm going back to Pie since having my phone turn off every night is unacceptable, especially since my phone is my alarm clock.

I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.

droidstyle said:
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
Click to expand...
Click to collapse
I flashed the A10 Oct factory image and wiped data. Still have the issue. The only thing that fixes it is going back to Pie.

So this happened to me twice now since being on 10. My screen would go black while using the phone, and then the phone would be unresponsive, so I would need to force a reboot, but after the Google splash screen it goes into recovery, and this message shows "Could not load Android OS. You can try again, or factory reset.". I did "Try again" both times, and it booted fine. Really irks me since I can't afford to do a factory reset since I use a lot of apps that have special info in them (Like Google Auth App that has many devices I need, and resetting I would have to redo every device). I hope Google can fix these issues with the next update.

I think my issue is due to the sensor bug that was introduced in 10. I have disabled the sensors on my phone and it hasn't froze since!! Hopefully Google fixes on the Nov update.

I'm having the issue that after my screen turns off, after a certain amount of time, I cannot get it to turn back on. The phone is still on, but is unresponsive to my input. I have to hard reset.
I have tried reflashing, and tried disabling sensors. I did not have an issue with the 10 September updated, but since updating to the November update, I had the issue non-stop all day.
Platform-Tools fully updated, not using gesture navigation, but the 2-button.

@MeetFace, yes! Same here since the November update. Something isn't right.

I'm still dealing with the black screen issue. Nov update didn't fix it.
https://issuetracker.google.com/issues/143288447

Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW

MeetFace said:
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
Click to expand...
Click to collapse
Can you share the tasker script? I love darkmode, but have never used tasker.

darkstar73 said:
Can you share the tasker script? I love darkmode, but have never used tasker.
Click to expand...
Click to collapse
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off

MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
How can you tell this is working? I've got it setup ??

MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
Thanks for this! Phone hasn't gotten a frozen black screen since I loaded the script!