I forced the update with the Indonesian VPN trick and I am observing the system lacks some new options like the battery percentage, or the swiping down in the fingerprints detector to roll down the bar (that I had implemented in the last Oreo update).
I factory reseted the system and it wasn't fixed. Is anyone of you having this issue?
{
"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"
}
Sent from my Mi A2 Lite using Tapatalk
aguadilu said:
I forced the update with the Indonesian VPN trick and I am observing the system lacks some new options like the battery percentage, or the swiping down in the fingerprints detector to roll down the bar (that I had implemented in the last Oreo update).
I factory reseted the system and it wasn't fixed. Is anyone of you having this issue?
Click to expand...
Click to collapse
It happened to everyone that updated to Pie.
The fingerprint can't help you however, for the battery percentage, you can get from the play store this app and enable it: https://play.google.com/store/apps/details?id=com.bryancandi.android.uituner
Related
I didn't have On-Body Detection when I upgraded to Lollipop OB6, but I just checked my Security settings today and now I do have it! I didn't notice or accept any new system updates, so I don't know how or when I got it. It might be worth a check to see if you have it too.
Here's a link to the story: http://androidcommunity.com/google-...ody-detection-mode-to-android-users-20150323/
JimSmith94 said:
I didn't have On-Body Detection when I upgraded to Lollipop OB6, but I just checked my Security settings today and now I do have it! I didn't notice or accept any new system updates, so I don't know how or when I got it. It might be worth a check to see if you have it too.
Here's a link to the story: http://androidcommunity.com/google-...ody-detection-mode-to-android-users-20150323/
Click to expand...
Click to collapse
Oh the battery drain....
EDIT: Yep it's there now.
{
"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"
}
I saw on another forum that this was added as part of an automatic update to Google Play Services.
Still locked and stock right now, but used ADB commands to enable wakelock detector lite (no root needed), noticed the following wakelocks pretty consistently:
OnePlus Launcher
*job*/com.android.launcher3/.quickpage.weather.WeatherService
UID
bluedroid_timer
The first seems to be related to the OnePlus launcher shelf weather service, which I don't even have enabled nor use. Not sure what the second is.
Any idea how to mitigate these without root or xposed?
Same problem (OxygenOS 2.3.7)
{
"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"
}
I dont know how fix this with root and oos 3.2.7
wojtek5379 said:
I dont know how fix this with root and oos 3.2.7
Click to expand...
Click to collapse
Freeze the stock launcher or uninstall it and use some other launcher.
U can try 2 turn off the weather in shelf. For me the problem was fixed than (when i was using OOS 3.x.x).
About the bluedroid_timer wakelock, maybe the following thread will be useful:
http://forum.xda-developers.com/oneplus-3/help/deep-sleep-vs-awake-screen-off-t3494097/page1
Hi, I've got some problems with my 5x lately, and the problem is that one core of the cpu runs at 100% and the only solution is reboot. It's pretty annoying, because it slows down the device and the battery is draining quicker. I don't have root or unlocked bootloader and I'm running on stock 7.0 with november security patch. Does anyone have/had problem like this and found some solution?
{
"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"
}
try a factory reset
Most likely a rogue app. Think to when this problem started happening and try to remember if you installed any new apps or if any apps were updated around then. Then disable or uninstall those apps and see if the problem ceases.
I agree most likely one of your apps.
Next time it happens use Settings > Developer Options > Running Services and catch it in the act.
Is it true that the march security updates were the last for S9 phones? So would it be wise to move on now?
quitnau said:
Is it true that the march security updates were the last for S9 phones? So would it be wise to move on now?
Click to expand...
Click to collapse
Why? You triple vaxed and believe everything you're told?
If you're running Android 9 or higher the device is relatively secure unless you do something stupid.
No saving dumb bunnies.
You are what you install and download. Know the vulnerabilities of the firmware and take steps to mitigate them like disabling wifi, using a firewall and keeping trashware like WhatsApp, FB, etc off the phone. Keep all adware off the phone.
This stock N10+ is running on Pie, current load will be 2 yo this June. Still fast, stable with minimal maintenance. Security has not been an issue.
Global ad blocking mod:
{
"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"
}
Hi there,
Red Magic 8 Pro users, Does anyone else have this large bulb icon that's stuck at the bottom left part on the lockscreen? I'm not sure what it's related to so I don't know how to remove it. Anybody else having this issue? I hoped the latest software update that came on on Feb 22nd would have fixed it but no luck.
{
"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"
}
Other user reported it as a “google home” icon, sort of a bug
Alextakatu said:
Other user reported it as a “google home” icon, sort of a bug
Click to expand...
Click to collapse
Ooh interesting, well the would make sense if that is the case as I definitely use the Google Home app often. The phones so new I know bugs are par for the course so I'll just wait for the next update. Thanks for the reply!