The new update for june 2022 is here.
It should include updates from may.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just to add a few problems we bumped into.
First night after update, no problems.
Second night after update, the phone had a reboot during the night, so my wake upclock did not go off.
Third night after update my phone went 'dead' during the night. Reviving it with Power button and Volume+ button did work.
After second night AND after third night the settings for the Screen Timeout where cleared and had to be set again.
This all happend on 2 different phones (my wifes and mine).
My wife had this update previous week and i had it this weekend.
So it seems to be 'normal' that his update will do these things.
This morning again my phone was dead.
My wife only had this ones.
So after reactivating, and changing the screen timeout again, i restarted my phone twice now.
Hope it now has stopped.
Anyone else have these problems after the update?
I'm having the exact same issue after updating. The phone froze up twice overnight already, requiring a hard reset to get it going again.
Sorry to her that, but i do not think that a hard reset was needed.
We only did a software reboot, and after that it all started to work again.
"known" bug of the latest software version.
Try activating the screen saver during battery charging, for my X20 it works (it seems that if the phone is running something while charging, and the screen saver somehow keeps it running, the bug does not appear)
Damn, last few day
abecedario_ said:
"known" bug of the latest software version.
Try activating the screen saver during battery charging, for my X20 it works (it seems that if the phone is running something while charging, and the screen saver somehow keeps it running, the bug does not appear)
Click to expand...
Click to collapse
Damn, the last few days multiple times a reboot during charging (at night).
I tried on my phone a trick from a previous Nokia (double tick to awake), but that did not help.
My wife tried your tip and had no trouble anymore (2 days in a row now) and i tried last night and it seems to work.
Thanks for the tip, this seems indeed to work now.
Related
So this has happened twice now. First on MeanBean and now on Sense 5 Port. Well here's my story
I wake up, then 3 hours later my battery life is dead. Looked at the battery consumption and usage and it was in fact Google Services.. again. I don't know how I fixed it the first time, but damn its annoying and it overheats my phone like no other. Is there a way to fix it?
Searching online I found that factory resets and all that work, as well as disabling google now, done both but still nothing. Do I just wait it out?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Clear data in Google play services and play store, then head to sync and accounts and turn Google sync off, reboot your phone, once the system is loaded go back and re-enable sync and wait for everything to sync, all of the Google services that you have selected should have a green checkmark, open play store and make sure you have the latest version... After that you should be good...
Sent from my EVO using xda app-developers app
realchinky said:
So this has happened twice now. First on MeanBean and now on Sense 5 Port. Well here's my story
I wake up, then 3 hours later my battery life is dead. Looked at the battery consumption and usage and it was in fact Google Services.. again. I don't know how I fixed it the first time, but damn its annoying and it overheats my phone like no other. Is there a way to fix it?
Searching online I found that factory resets and all that work, as well as disabling google now, done both but still nothing. Do I just wait it out?
Click to expand...
Click to collapse
I mentioned this in the original sense 5 thread, but check your playstore version. If it is below 4.1.10, then search for a more recent version. I think there is a leaked version of 4.2.3. That should do it.
Myself and many others have had crippling issues with bluetooth on CM-based roms and it has gone unfixed for a long time. Bluetooth suddenly just stops working. The icon disappears from the notification menu, and if you try to turn it on, it appears to turn on for a fraction of a millisecond and then shuts off. Rebooting doesn't fix it. Clearing cache from safe strap does fix it (temporarily), but it's a pain in the ass and takes a long time.
This has happened to me both in CM 10.1 and Carbon, and it happens about once a day. Once every two if I'm lucky.
Today I managed to restore bluetooth completely by simply force closing the "Bluetooth Share" app. I did tap "Clear Cache" first in the app's settings, but it didn't appear to do anything (cache remained at 12KB), so I don't know if that step is required. Bluetooth was immediately restored and the icon immediately reappeared in my notification bar. Why this worked but rebooting doesn't is beyond me. I would think since all apps get shut down on reboot, that a reboot would have the same effect... who knows.
Anyway, I just thought I would share my discovery with other frustrated Razr owners. I have only tried it once, but I will update this thread next time I attempt this and post my results.
1st Attempt: Success
2nd Attempt: ??? (will test without clearing app cache)
3rd Attempt: ???
If this does indeed work consistently, it may be possible to create a bandaid fix for this whereby an app running in the background constantly checks to see if bluetooth is turned on, and if not, executes a force close on the app, automatically bringing bluetooth back up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks a lot my friend at least it helps me to reuse my blue-tooth , later Better <than Ever
Best Regards
yeah this was discovered weeks ago in droid4 forums
i posted in the ParanoidAndroid thread a few days ago in RAZR as well
but good idea to make its own thread to spread awareness
Hey Guys,
I have just gotten a fresh Umidigi One Pro like 8 hours ago. Yay, at last, a brand new Phone.. Looks awesome and all BUT
Whenever it gets a Message via Email, Message or anything else that shortly lits up the screen, it will NOT go back to sleep, unless I open the Phone and turn it off again.
I had checked the settings and put Android inactivity thing to 30 Seconds where no inputs where made.
I have just now deactivated the messages on lockscreen completely and I am waiting for a information that I have received a new message (sent one for testing purpose).. and the screen STILL lit up again, even though not showing a message!
Any Ideas why Android isn't goint to sleep automatically? Because when it does not turn off, itgets more and more hot. I just had it only realized that i got DAAAAAMN hot, cuz it slid under the pillow.
I am completely puzzled about this, as my old MIUI usually turned off just after a few seconds (like 5-10 Secs latest) ...
It just now happened to happen AGAIN, my Email must have arrived, it does NOT show on the lockscreen, all in all i see like nothing beside Network+Wifi Signal, Battery, Time and Mic, Avatar and Camera Icon in the bottom.
It kind of pisses me off, as this would mess up Batterytime badly. I would love to keep the Phone, as it really looks awesome to me. Thats kind of a flaw, or maybe even damaged Phone?
I would love to hear from you that I just miss a feature and how to fix it.....
Thanks!
Mhm, the only way I found that would stop to lit up the Screen and not turning off again, is to turn off the processes in the background completely using DuraSpeed ... damn ... useless.
caylean said:
Mhm, the only way I found that would stop to lit up the Screen and not turning off again, is to turn off the processes in the background completely using DuraSpeed ... damn ... useless.
Click to expand...
Click to collapse
I must confirm this issue. After notification phone display is constantly on. Really annoying.
This is a problem... Potentially deal breaker. What's crazy is if you search for ambient display in settings it shows to be under the battery menu however, it's not there when I look for it.
I found an adb command that supposed to turn off wake screen on notification but I can't try it out right now for lack of computer.
If anyone wants you try, it's
adb shell settings put secure doze_enabled
Please let us know if it works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone has a very strange issue which I'm unable to fix. It happens totally randomly. Sometimes it occurs multiple times a day, then it won't happen for weeks.
It goes like this: Sometimes, even though I'm connected to my WiFi network, apps won't connect to the internet. However, the apps won't give me an error message telling me that I'm diconnected. As the WiFi symbol is active, the phone probably thinks it's online while it's actually not. All apps are affected.
At the same time, the battery drains rapidly (about 10% per hour in standby) and the phone gets slightly warmer. Maybe it is trying to connect all its services to the internet, fails constantly and therefore gets warmer?
This battery drain has also occured in flight mode, so it is not necessarily a WiFi problem. It has happened in various WiFi networks and my other devices don't get disconnected, so the reason must be within the phone.
I've done multiple factory resets but it didn't help. I'm tired of doing factory resets. The only way to temporarily fix it is turning the WiFi on and off again or rebooting the phone. I'm on Oreo btw.
I should add that this only begins when the phone is in standby. When the screen is on, i.e. I'm actively using the phone, I do of course notice the issue but it starts before waking up the phone from standby. That makes me believe it has something to do with standby / Android doze.
Someone on Reddit suggested that it might be due to Android Doze. I followed the advice there, went to Settings > General > Battery > Power saving exclusions, switched on the WiFi and restarted the phone. That was two days ago and there's still no improvement.
Apart from that, battery life is bad overall, even when the WiFi issue doesn't occur. Just see this screenshot from today below. It's almost as if the phone has a bad day sometimes and drains the battery for no apparent reason. Then, on other days, it's better but still nowhere where it could be according to other V30 owners' screenshots.
What can I do?
It is really really annoying!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not sure if this would help or not but try (from the playstore) Greenify. It works best if device is rooted but also works (give permissions through adb) without root.
Would it fix the problem? Oh no, doubt that. It *might* point to what's going on though?
Hi everyone,
I've just bought a brand new display for my sm-t860 that I haven't used for few months. After I installed it and turned it on I was happy when I saw familiar logon screen appearing. Unfortunately my joy only lasted for few seconds as screen switched off after android loaded up.
It happens every time I try to power it on. After system loads screen instantly switches off in the same manner like when you press the power button to turn off the display. It even makes the same sound even though the button wasn't pressed. You can see whole sequence on attached video.
Anyone have idea what could be the reason for this error? Tablet was fully functional before changing the display.
AwesomeGreg said:
Hi everyone,
I've just bought a brand new display for my sm-t860 that I haven't used for few months. After I installed it and turned it on I was happy when I saw familiar logon screen appearing. Unfortunately my joy only lasted for few seconds as screen switched off after android loaded up.
It happens every time I try to power it on. After system loads screen instantly switches off in the same manner like when you press the power button to turn off the display. It even makes the same sound even though the button wasn't pressed. You can see whole sequence on attached video.
Anyone have idea what could be the reason for this error? Tablet was fully functional before changing the display
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone has idea what this chip is? I noticed it was getting extremely hot when the home screen loaded before display went off like always. Then some absurd idea came to my head and I started tapping it repeatedly while booting. It did a trick as the chip were getting less hot and display stayed on for few more seconds. After few more series of this treatment display stayed on for 10 minutes and I thought the issue is solved. Unfortunately after I opened numerous tabs in web browser system froze and never recovered.
I couldn't even power it on after that so I laid it off for 30 minutes and it's working again but the chip is still getting hot. Tapping works but I need to find the source of this issue rather than try to deal with symptoms.
Damn this community is useless
AwesomeGreg said:
Damn this community is useless
Click to expand...
Click to collapse
Please share the text that is written on the IC.
Seems to be the power ic.