Today Lumos 1.0 final is released, besides other changes now has better support for HVGA in settings dialog.
never tried this on other phones, but it sounds fantastic
going to give it a whirl and see if anything improves
Well, I was about 6 monthes with previous release and it really helps to save battery.
Just played a little to make own backlight profile.
to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?
I’ve tried ‘LumosWizard’ 5 month ago but I’ve never managed to make it work correctly
So that, I use ‘Mylostblog Mylight’ now.
Not the same but its easy to use with a shortcut in "Cookie’s Home Tab".
Well, just try run calibration correctly, my sensor's range is 0..1904,
minimum level 1, maximum level 5.
There are issues with g-sensor games - lookup the original Lumos thread.
tkur said:
to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?
Click to expand...
Click to collapse
I finally moved back to Android and opted to go w/ the Note 4. While the hardware itself is brilliant, TW is still awful.
My actual problem is this: Every time I power on the screen, it begins "Finding Location" and the notification icon pops up in the tray and the notification bar. This literally happens EVERY time I power the screen back up. It doesn't seem to be affecting battery life, as I'm only using about 25% over a 12hr period (rather impressive, IMO)...but it certainly is annoying. Is this just a by-product of TW?
While I know I can turn off location, I do use a few things that make it optimal to have it on (nav, weather, etc.).
<tangent>
Having had the Note 10.1 for about 2 years, I really thought I could live with TW. I barely scrape things where I see it on the Note 10.1. However, I'm finding myself rather disappointed with just how ugly it is and how much crap they have messed around with in the Settings world. I'd honestly think HTC had Android prettier back in the original Evo days (Sense > TW...IMO). I'm really on the fence about keeping this handset, and may very well go back to my Lumia 928 for now until handsets with Lollipop drop. I actually like Windows Phone (what is wrong with me!?!) and would have gladly stayed there if they had the apps I want/need (Nest and Sonos).
</tangent>
It is my understanding that the reason for that is the S Health app. Do you still have it enabled?
ssj4gogeta2003 said:
It is my understanding that the reason for that is the S Health app. Do you still have it enabled?
Click to expand...
Click to collapse
Interesting. I'm not using it, but I never disabled it either. Let me give that a go!
I disabled S Health and put the location back to High, and now it never seems to lock in, even after a restart. This makes no sense, as Maps appears to be able to lock in on my exact location quite quickly.
ETA: OH SNAP. I'm such a dolt. Turns out it was a widget looking to pull GPS data for weather EVERY time the screen wakes. I feel like a true idiot.
Ah, I apologize for steering you in the wrong direction. I will make a note of it.
basilray said:
I disabled S Health and put the location back to High, and now it never seems to lock in, even after a restart. This makes no sense, as Maps appears to be able to lock in on my exact location quite quickly.
ETA: OH SNAP. I'm such a dolt. Turns out it was a widget looking to pull GPS data for weather EVERY time the screen wakes. I feel like a true idiot.
Click to expand...
Click to collapse
Not an idiot at all, and thanks for letting us know. This is the best way to share info and we all learn!
gave you a thanks for letting us know...
I just tried turning on the 'Show surface update' option under 'Developer Options'. The screen flashes randomly even if I just keep the screen on without touching or doing anything with the phone.
I have a Xperia T2 Ultra, and if I try the same thing, the screen will only flash if I touch the screen, it doesn't flash the screen randomly like the ZUK Z2 does.
Is it happening to everyone on Stock Nougat ROM or just me? I am mainly concerned with the touch sensitivity of the phone, cause sometimes I feel, I'm missing out some screen swipes.
Any advice or suggestions?
I don't think the 'Show surface updates' setting is actually intended to show when the screen is touched. I believe it is used to indicate when the content of the screen changes; for example it might flicker if one of the icons in your statusbar changes like mobile/Wi-Fi signal strength or the clock. I guess the option you're actually thinking about is the one which says 'Show taps' under the Input heading, which displays a spot on the screen when the display panel is touched. (I don't know whether this is available in ZUI since i'm running AEX 4.5)
P650SE said:
I don't think the 'Show surface updates' setting is actually intended to show when the screen is touched. I believe it is used to indicate when the content of the screen changes; for example it might flicker if one of the icons in your statusbar changes like mobile/Wi-Fi signal strength or the clock. I guess the option you're actually thinking about is the one which says 'Show taps' under the Input heading, which displays a spot on the screen when the display panel is touched. (I don't know whether this is available in ZUI since i'm running AEX 4.5)
Click to expand...
Click to collapse
Thank you for the reply. Whatever you said makes complete sense. But the issue is, I have got few Android phones running kitkat, lollipop and marshmallow, these devices only shows surface update on statusbar area if I don't touch the screen. In Z2's case it flashes the complete screen randomly and frequently, I tried leaving it in settings, a picture opened in full screen etc, but same result.
I don't mind if it's a bug with the ROM, I can flash a custom ROM. But if it's caused by a hardware issue, mostly related to touch, then I'm planning to send the device back for repair or replacement. Just going to be 1 week since I bought this device.
Any suggestions?
sixth.pr1m3 said:
Thank you for the reply. Whatever you said makes complete sense. But the issue is, I have got few Android phones running kitkat, lollipop and marshmallow, these devices only shows surface update on statusbar area if I don't touch the screen. In Z2's case it flashes the complete screen randomly and frequently, I tried leaving it in settings, a picture opened in full screen etc, but same result.
I don't mind if it's a bug with the ROM, I can flash a custom ROM. But if it's caused by a hardware issue, mostly related to touch, then I'm planning to send the device back for repair or replacement. Just going to be 1 week since I bought this device.
Any suggestions?
Click to expand...
Click to collapse
I don't think there's anything to be worried about. I actually upgraded to a new phone today, and so flashed the Indian version of ZUI (2.5.104 ST) back onto my ZUK Z2 in preparation for selling it on Gumtree. (Which is the British equivalent of Craigslist, for those in the US) I had chance to test what you were talking about and sure enough, the same thing happens on mine; where the entire screen will occasionally flicker even with an image displayed in fullscreen, so that the statusbar icons are hidden. So unless you are noticing any actual problems whilst using the device, I don't believe there's anything to be concerned about at this stage.
P650SE said:
I don't think there's anything to be worried about. I actually upgraded to a new phone today, and so flashed the Indian version of ZUI (2.5.104 ST) back onto my ZUK Z2 in preparation for selling it on Gumtree. (Which is the British equivalent of Craigslist, for those in the US) I had chance to test what you were talking about and sure enough, the same thing happens on mine; where the entire screen will occasionally flicker even with an image displayed in fullscreen, so that the statusbar icons are hidden. So unless you are noticing any actual problems whilst using the device, I don't believe there's anything to be concerned about at this stage.
Click to expand...
Click to collapse
Thanks a lot for checking it out for me, really do appreciate it. Was getting increasingly worried about this issue. You are a lifesaver. Thank you again :highfive:
Hello,
I'm from Morocco and currently using a XIAOMI REDMI NOTE 8, (64Go/4Go), running the latest version of MIUI 11.0.11.0 Global stable with Android 9.
So i'm having this really annoying problem whith the notification when the phone is closed. So basiclly the sound of the notification should come at the time of recieving the notification but in my case there is a delay of 2 to 3 min or even more than that sometimes. And even sometimes the sound is not heard at all even with the notification is recieved. Only the light bulbe for the notification is blinking.
This problem happened especially with the Whatsapp application. Everything in the notifications seetings is on, all permission are granted, locked the app in the recent app, turned on autostart, disabled battery saver even though i don't use it at all, put no restriction on the app, turned on background data. I've tried to use different network connection still the same problem. I don't seem to find a reason why would this happend and find a solution for that. I did perform a factory reset but doesn't seem to be fixed. Everything in the begining was working fine no issue at all. I don't seem to remember when it start to happend, I've asked my freinds owning the same device if they are facing the same issue all of them denied. So the question is if all the devices have the same software that they are operating on they should have the same bug or problem if i wan't to say. But not in this case. I have not installed any 3rd party app that has to do with the battery at all.
I do use my mom's phone to test this out. The phone is on everything works perfectly. I locked the phone and the problem start. It's like ther is something that shut the notifications immediately when i close the phone (dnd is not activated also battery saver as i mentioned earlier). So if there is any kind of solution to this problem please help me with or if there is a dev please let them know to fix this issue. I did reported it in the feedback section on the phone 10 times in the time of writing this thread. I'm currently waiting for the new update hoping that it will fix the problem otherwise this is really disappointing. The best selling phone in the market facing issue like this, that's not very acceptable at all. This made me miss a lot of important notifications. Hope that it will be fixed as soon as possible.
If you want to help me and you need any more info please leave me a comment and i will send them to you (screenshots of the settings etc....).
Thanks for your time.
Stay safe.
Have a nice day.
Hamza_note8 said:
Hello,
I'm from Morocco and currently using a XIAOMI REDMI NOTE 8, (64Go/4Go), running the latest version of MIUI 11.0.11.0 Global stable with Android 9.
So i'm having this really annoying problem whith the notification when the phone is closed. So basiclly the sound of the notification should come at the time of recieving the notification but in my case there is a delay of 2 to 3 min or even more than that sometimes. And even sometimes the sound is not heard at all even with the notification is recieved. Only the light bulbe for the notification is blinking.
This problem happened especially with the Whatsapp application. Everything in the notifications seetings is on, all permission are granted, locked the app in the recent app, turned on autostart, disabled battery saver even though i don't use it at all, put no restriction on the app, turned on background data. I've tried to use different network connection still the same problem. I don't seem to find a reason why would this happend and find a solution for that. I did perform a factory reset but doesn't seem to be fixed. Everything in the begining was working fine no issue at all. I don't seem to remember when it start to happend, I've asked my freinds owning the same device if they are facing the same issue all of them denied. So the question is if all the devices have the same software that they are operating on they should have the same bug or problem if i wan't to say. But not in this case. I have not installed any 3rd party app that has to do with the battery at all.
I do use my mom's phone to test this out. The phone is on everything works perfectly. I locked the phone and the problem start. It's like ther is something that shut the notifications immediately when i close the phone (dnd is not activated also battery saver as i mentioned earlier). So if there is any kind of solution to this problem please help me with or if there is a dev please let them know to fix this issue. I did reported it in the feedback section on the phone 10 times in the time of writing this thread. I'm currently waiting for the new update hoping that it will fix the problem otherwise this is really disappointing. The best selling phone in the market facing issue like this, that's not very acceptable at all. This made me miss a lot of important notifications. Hope that it will be fixed as soon as possible.
If you want to help me and you need any more info please leave me a comment and i will send them to you (screenshots of the settings etc....).
Thanks for your time.
Stay safe.
Have a nice day.
Click to expand...
Click to collapse
1. Turn off miui optimization under developer options
2. Give all permissions, no battery optimization to google play services and framework. Before doing this, clear data of those apps(removes google account!).
3. Check if it's added to game turbo or not
These are some more possible solutions. After checking all those, reboot once and check if the problem is solved or not.
Pavello said:
1. Turn off miui optimization under developer options
2. Give all permissions, no battery optimization to google play services and framework. Before doing this, clear data of those apps(removes google account!).
3. Check if it's added to game turbo or not
These are some more possible solutions. After checking all those, reboot once and check if the problem is solved or not.
Click to expand...
Click to collapse
Hello,
Thanks for you response. I've already done what you did sggest to me but still the samething always late notification sound.
It's not added to game turbo i don't even use it and it's disabled. Google play services and framework don't have any kind of restrictions whatsoever. I don't want turn off miui optimization cuz it mess up with a lot of visuals.
I think it's a software issue. Because sometimes when i want to change the ringtone and i tap on a different one it took a lit bit of time to play it same thing when changing the notification. This problem is happening when the phone is locked only.
I'm cuurently waiting for the new update with a hope that it will fix it.
Thanks again.
have a nice day.
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.