Hi all,
The latest official update for the Pixel 5 dropped the FEATURE_VR_MODE_HIGH_PERFORMANCE system feature flag.
I don't have one of these devices myself, but I'm wondering if at least the display mode is still available when rooted.
If someone's running the latest AOSP on their Pixel 5, can you do an ls on /sys/class/backlight/panel0-backlight/ and see if there's a vr_mode in there? I reckon writing 0/1 to that file should enable/disable it.
I've got an AOSP ticket requesting that "low persistence" just be exposed as a display preference, so I'm interested if there are devices that have the display option still even without flagging FEATURE_VR_MODE_HIGH_PERFORMANCE.
Google Issue Tracker
issuetracker.google.com
Thanks!
Related
A few days ago, I started getting random apparently blank MMS messages from unknown urls in Hangouts. Looks like my phone / number is being targeted by someone trying to leverage one of the recent Stagefright vulnerabilities. I've got auto-downloading of MMS messages disabled in Hangouts and the stock Sony Messaging client, so probably (?) no immediate danger. But I am only on the last Kit Kat rom because I've been bitten before by abysmally bad battery life in Lollipop.
So options...
5..1.1 - sounds like battery life is better now than it was originally in LP. Can anyone verify that all the Stagefright vulnerabilities are even fixed in the latest for the Z3c? I have a Z1C test phone around the office here, and last I checked its latest 5.1.1 rom did not resolve all of those issues.
6.0 Concept - looks promising....but early MM wasn't immune to Stagefright problems either. Can anyone check if whatever anyone not part of the early program can install is free of this vulnerability?
Unfortunately, I need to run a secure app platform / email app for work, which means that I can't root or run xposed - stock roms only.
johdaxx said:
A few days ago, I started getting random apparently blank MMS messages from unknown urls in Hangouts. Looks like my phone / number is being targeted by someone trying to leverage one of the recent Stagefright vulnerabilities. I've got auto-downloading of MMS messages disabled in Hangouts and the stock Sony Messaging client, so probably (?) no immediate danger. But I am only on the last Kit Kat rom because I've been bitten before by abysmally bad battery life in Lollipop.
So options...
5..1.1 - sounds like battery life is better now than it was originally in LP. Can anyone verify that all the Stagefright vulnerabilities are even fixed in the latest for the Z3c? I have a Z1C test phone around the office here, and last I checked its latest 5.1.1 rom did not resolve all of those issues.
6.0 Concept - looks promising....but early MM wasn't immune to Stagefright problems either. Can anyone check if whatever anyone not part of the early program can install is free of this vulnerability?
Unfortunately, I need to run a secure app platform / email app for work, which means that I can't root or run xposed - stock roms only.
Click to expand...
Click to collapse
The whole stagefright vulnerability affects a huge percentage of devices running LP, while Android has claimed to have "fixed" most of the vulnerabilities some still remain in 5.1 but they are really not that impactful when it comes to using the phone.
With regards to security, you are never really "safe". The very fact you download apps like Facebook or Youtube already makes your internet life an open book, probably right now your phone sends anonymous data to Sony at set intervals.
True enough - no phone anyone really wants to hack into is 100% secure, and the more popular, the more they're going to be targeted. Specifically, I was wondering if anyone had run this tool:
https://play.google.com/store/apps/details?id=com.zimperium.stagefrightdetector
on either 5.1.1 or 6.0 Concept? I have access to a few different phones that pass all these checks, but several that don't. The standard 4.4.4 on the Z3c fails all but one. A small comfort - but figured it was worth checking.
As for PI leakage, true, but different issue. I'm personally much happier with Google's methods where we have a dashboard that shows what information they're slurping up by the second, than others (like many manufacturers) that bury it in a massive T&C. We at least have some control over that vs. exposure to these security holes.
I have bought lots of phones in the last half a year, all of them with the same failure: some calendar notifications are missing without a reason. And all of that phones came with Android 6 or 7. In Android 5 I don't have such a problem, in fact I have a phone with that version but it is old and I need to renew it. My suspicion is that doze makes some notifications to fail and not show. But it is impossible to completely disable it. I can only select individual apps and that doesn't work. Currently I have an application called Boeffla doze control and it seems to be working but I have to keep attentive all of the days that doze keeps disabled for being able to receive all of the notifications. What I want to do is to stop worrying about it. So my question is: how can I really remove completely doze from the operating system? I will do anything, don't mind if I have to flash a patch or even a custom ROM.
i ask myselfI Is worth doing a root?? pixel 4 xl?
Because of excellent sound without a root and a good camera even without a root so if there are other good things if I do a root??
oraned said:
i ask myselfI Is worth doing a root?? pixel 4 xl?
Because of excellent sound without a root and a good camera even without a root so if there are other good things if I do a root??
Click to expand...
Click to collapse
This might help you decide
https://forum.xda-developers.com/pixel-4-xl/help/rooted-t4004915
Badger50 said:
This might help you decide
https://forum.xda-developers.com/pixel-4-xl/help/rooted-t4004915
Click to expand...
Click to collapse
Thanks
I would wait until you get the Dec security update next week.
If you are a Google Pay user, then rooting may not be worth it. Rooting will break Google Pay and while there can be ways to fix it, it will always be a battle.
If you don't use Google Pay, then I think rooting is great! I use it for these reasons:
- HBM (High Brightness Mode) - everyone complains about the Pixel 4 max screen brightness being too low, well HMB will push the max brightness higher than stock. (The Pixel 3a has the same lowered max stock brightness)
- Viper4Android - the BEST audio app there is
- Ad Away - block ads - even in apps - a real "must have"
- Youtube Vanced - remove ads from Youtube - this is a must have as well
- Active Edge Mod - set to OEM settings for everything but the camera. When using the camera I can press the active edge and it will activate the shutter. This really helps when holding the phone with one hand.
- ACC Controller - a battery charging mod that helps extend the overall life of batteries by changing the charging characteristics.
- Tasker - some things I need root for.
- I run a custom kernel (mainly to allow HBM, but I might get some increased battery life too)
- Magisk module Debloater to remove unwanted system apps (like Chrome because I use another browser).
With the Pixel 4, having the ability to remap the Soli gestures might be interesting too.
I know some people really get into the themes too, but I haven't tried it yet.
If losing Google Pay is a deal-breaker, you can always purchase the Samsung Gear S3 watch. You can load your payment cards onto the watch via the Samsung Gear Pay plugin, then use the watch for all the payments. It's better than Google Pay imo because the S3 works with both magnetic stripe readers and newer NFC readers. It's rare to find a credit card terminal that the S3 can't work on, whereas GPay is about 50/50. (Note, the newest Samsung watch doesn't support magnetic readers).
Thank you
sic0048 said:
If you are a Google Pay user, then rooting may not be worth it. Rooting will break Google Pay and while there can be ways to fix it, it will always be a battle.
If you don't use Google Pay, then I think rooting is great! I use it for these reasons:
- HBM (High Brightness Mode) - everyone complains about the Pixel 4 max screen brightness being too low, well HMB will push the max brightness higher than stock. (The Pixel 3a has the same lowered max stock brightness)
- Viper4Android - the BEST audio app there is
- Ad Away - block ads - even in apps - a real "must have"
- Youtube Vanced - remove ads from Youtube - this is a must have as well
- Active Edge Mod - set to OEM settings for everything but the camera. When using the camera I can press the active edge and it will activate the shutter. This really helps when holding the phone with one hand.
- ACC Controller - a battery charging mod that helps extend the overall life of batteries by changing the charging characteristics.
- Tasker - some things I need root for.
- I run a custom kernel (mainly to allow HBM, but I might get some increased battery life too)
With the Pixel 4, having the ability to remap the Soli gestures might be interesting too.
I know some people really get into the themes too, but I haven't tried it yet.
Click to expand...
Click to collapse
In my country motion not work so who the Pixel 4, having the ability to remap Soli gestures ghost work?
oraned said:
In my country motion not work so who the Pixel 4, having the ability to remap Soli gestures ghost work?
Click to expand...
Click to collapse
If you root, you can turn Soli on in countries where it isn't active by default. https://www.androidpolice.com/2019/...-enable-motion-sense-in-restricted-countries/
sic0048 said:
If you root, you can turn Soli on in countries where it isn't active by default. https://www.androidpolice.com/2019/...-enable-motion-sense-in-restricted-countries/
Click to expand...
Click to collapse
Because I do this in the past and it's don't work for me the ADB access denied
setprop failed to set property??
oraned said:
Because I do this in the past and it's don't work for me the ADB access denied
setprop failed to set property??
Click to expand...
Click to collapse
If ADB access is denied, that is a different issue.
For one, make sure you are using the absolute latest version of ADB. If you had another Android phone prior to the Pixel 4 and are still using the ABD version you installed originally with the prior phone, it is out of date and won't work with the Pixel 4. You must upgrade the ADB to the latest versions to ensure it works with the Pixel 4 devices.
Also, you need root. I get the impression you haven't rooted your phone yet. If this is the case, then obviously those mods won't work until you actually root the phone.
sic0048 said:
If ADB access is denied, that is a different issue.
For one, make sure you are using the absolute latest version of ADB. If you had another Android phone prior to the Pixel 4 and are still using the ABD version you installed originally with the prior phone, it is out of date and won't work with the Pixel 4. You must upgrade the ADB to the latest versions to ensure it works with the Pixel 4 devices.
Also, you need root. I get the impression you haven't rooted your phone yet. If this is the case, then obviously those mods won't work until you actually root the phone.
Click to expand...
Click to collapse
You know how to solve the problem with ADB??
I do root and a it's still I do a problem why??
sic0048 said:
- ACC Controller - a battery charging mod that helps extend the overall life of batteries by changing the charging characteristics.
Click to expand...
Click to collapse
Is ACC working for you? Cause it doesn't for me. It doesn't stop charging. :/
Some already tell their opinions so i make it, too.
For me root is mandatory and i always root all my phones due of the following reason:
Every normal stock rom has a massive privacy problem because of the spyware services/apps from Google and to minimize this you need root unless you change to a custom rom with pure aosp.
And depending on the Apps which you use on an AOSP Rom Root is really usefull, too.
Personally i'm not willing anymore to sell my privacy to google so i use Apps as AdAway and AfWall+ together with a pure AOSP GSI on my pixel 4 xl.
So if you need really the Google Services, the Apps or Google Pay etc and can't live without them then it's better to avoid Root.
But if not and you want the highest protection and control then it's definitly worth to Root the phone.
This is just a simple Xposed module that disables pulling down the notification shade / quick settings tiles while on the lock screen (but doesn't break media player controls on lock screen). Only tested on Pixel 4 and Pixel 4 XL on Android 10 (more on this later).
Background: This has always been an annoying aspect of Android for me, and it's dumb from a security standpoint. Being able to pull down the quick settings tiles on a locked phone is dumb. Why hasn't Android natively built this in yet? Using this and Gravity Box to disable power menu on lock screen makes me feel a lot better in the event my phone ever gets lost or stolen. It's dumb that anyone can steal your phone and immediately toggle your settings (turn off WiFi, Mobile Data, toggle Airplane Mode, etc) and/or turn the phone off... I've been spoiled for years by the OG HTC devs (particularly LeeDroid and Team Venom) and their ROMs with these features baked in, so it's back to using Xposed to fill that gap for me and my wife, lol. Anyway, I pair these mods along with the Lockwatch app from Play Store and it gives me more peace of mind. Hey, anything to increase the chances of recovering a lost or stolen phone, am I right?
Credits / Technical Details: This module is based off of char101's published Xposed Repo module, and all credits and thanks should go to him. This is the first app / APK I've compiled so it was a nice learning experience, but it was all based off of his source and I really just needed to remove a few lines of code to get it to work properly with our phones. His mod worked fine and disabled the quick settings pull down on the lock screen, as intended. The problem was that it would also prevent media player controls from functioning (and I would assume other possible functions as well). To fix this, I just removed DISABLE2_NOTIFICATION_SHADE references from the code, leaving DISABLE2_NONE and DISABLE2_QUICK_SETTINGS untouched. The mod still works perfectly as intended. Only tested on Pixel 4 / 4 XL on Android 10. I'm sure it would work on other devices as well.
I really just did this on a whim for me and my wife's own phones and wasn't planning on sharing it, but I figure other people may have also wanted this for their P4's as well, so enjoy. Again, all thanks go to @char101!
Installation:
- Download .APK file attached to this post.
* If you have char101's original module installed already, I would highly recommend uninstalling it first.
- It's an Xposed module. Install the APK and enable in your Xposed Manager.
- Reboot and test.
Based on: https://repo.xposed.info/module/com.github.char101.qslock
Source for modified module: https://github.com/i5lee8bit/xposed-qslock-P4mod
thanks for this!!! any difference between this one and the one posted on the XL forums?
vdevl said:
thanks for this!!! any difference between this one and the one posted on the XL forums?
Click to expand...
Click to collapse
Nope, they are exactly the same. I have a 4 XL and got my wife the regular 4, and so I've been posting on both forums to share some of my findings on both devices. I just figured most 4-only owners probably won't be checking the 4 XL forums, and since this mod worked perfectly on my wife's phone I wanted to share with both communities. Glad to help though!
PS: Please try to refrain from quoting the entire OP, it makes the thread kind of cluttered. Just for future reference. =)
thanks much dude! gonna try edxposed with this module for 1st time after kitkat days. Miss those easy android days.
Appreciate the effort youre putting for sharing mods and patched boot imgs. Cool guy
i5lee8bit said:
This is just a simple Xposed module that disables pulling down the notification shade / quick settings tiles while on the lock screen (but doesn't break media player controls on lock screen). Only tested on Pixel 4 and Pixel 4 XL on Android 10 (more on this later).
Background: This has always been an annoying aspect of Android for me, and it's dumb from a security standpoint. Being able to pull down the quick settings tiles on a locked phone is dumb. Why hasn't Android natively built this in yet? Using this and Gravity Box to disable power menu on lock screen makes me feel a lot better in the event my phone ever gets lost or stolen. It's dumb that anyone can steal your phone and immediately toggle your settings (turn off WiFi, Mobile Data, toggle Airplane Mode, etc) and/or turn the phone off... I've been spoiled for years by the OG HTC devs (particularly LeeDroid and Team Venom) and their ROMs with these features baked in, so it's back to using Xposed to fill that gap for me and my wife, lol. Anyway, I pair these mods along with the Lockwatch app from Play Store and it gives me more peace of mind. Hey, anything to increase the chances of recovering a lost or stolen phone, am I right?
Credits / Technical Details: This module is based off of char101's published Xposed Repo module, and all credits and thanks should go to him. This is the first app / APK I've compiled so it was a nice learning experience, but it was all based off of his source and I really just needed to remove a few lines of code to get it to work properly with our phones. His mod worked fine and disabled the quick settings pull down on the lock screen, as intended. The problem was that it would also prevent media player controls from functioning (and I would assume other possible functions as well). To fix this, I just removed DISABLE2_NOTIFICATION_SHADE references from the code, leaving DISABLE2_NONE and DISABLE2_QUICK_SETTINGS untouched. The mod still works perfectly as intended. Only tested on Pixel 4 / 4 XL on Android 10. I'm sure it would work on other devices as well.
I really just did this on a whim for me and my wife's own phones and wasn't planning on sharing it, but I figure other people may have also wanted this for their P4's as well, so enjoy. Again, all thanks go to @char101!
Installation:
- Download .APK file attached to this post.
* If you have char101's original module installed already, I would highly recommend uninstalling it first.
- It's an Xposed module. Install the APK and enable in your Xposed Manager.
- Reboot and test.
Based on: https://repo.xposed.info/module/com.github.char101.qslock
Source for modified module: https://github.com/i5lee8bit/xposed-qslock-P4mod
Click to expand...
Click to collapse
thanks, mate, it's working perfectly on poco f3 android 12.1 lineageOS
Thank you so much for sharing this!!!!!!!
i5lee8bit said:
Nope, they are exactly the same. I have a 4 XL and got my wife the regular 4, and so I've been posting on both forums to share some of my findings on both devices. I just figured most 4-only owners probably won't be checking the 4 XL forums, and since this mod worked perfectly on my wife's phone I wanted to share with both communities. Glad to help though!
PS: Please try to refrain from quoting the entire OP, it makes the thread kind of cluttered. Just for future reference. =)
Click to expand...
Click to collapse
are you able to update the app to work with android 13. Am using a pixel 6 and the app doesnt work
v.konvict said:
are you able to update the app to work with android 13. Am using a pixel 6 and the app doesnt work
Click to expand...
Click to collapse
I was able to modify the code to run in android 13, see my reply at https://forum.xda-developers.com/t/...n-on-lock-screen.4076593/page-2#post-88165351
Hello.. I'm trying to research an issue (or known change) with the Notifications on my OnePlus 10 Pro running latest Android 12. This problem was first noticed on my OP8T after upgrading it to Android 12. Since I just got a 10 Pro I'm posting here, since that' s my current phone and the one for which I'd like resolution (sold the 8T).
After upgrading the OP8T, my notifications no longer let me go straight to an app. I'll use Gmail for example. Before the upgrade if I had multiple new email, I'd have a single notification. I would swipe down and see it, and I could one of two things. 1. I could just click on the notification and it would take me to my Inbox. Or 2. I could tap the little side button that expanded the notification and click on one of the emails to be taken directly there.
Since Android 12 upgrade, I no longer have option 1. I bought a OnePlus 10 Pro - it came with Android 12 installed, and I have the exact same issue.
I am not seeing this behavior with a Sammy on Android 12, so it has to be something in with Oxygen OS.
Anyone else seeing this, and do you see it as issue? Is there a way to set it so when you click on the notification, it just opens the App like you were clicking the App's icon? I TRULY MISS THIS
Yes this is a very big feature and product miss. Not able to understand why this is not blown up yet.