How Android Q improves Privacy and Permission Controls over Android Pie
https://www.xda-developers.com/android-q-privacy-permission-controls
#android #q #permissions
https://www.xda-developers.com/android-q-privacy-permission-controls
#android #q #permissions
XDA Developers
How Android Q improves Privacy and Permission Controls over Android Pie
Android Q will bring a revamp to permission management and enhancements to protect user privacy. Here's what Google has changed since Android Pie.
RIP Clipboard Managers: Android Q blocks background clipboard access
https://www.xda-developers.com/android-q-blocks-background-clipboard-access
#android #q #clipboard
https://www.xda-developers.com/android-q-blocks-background-clipboard-access
#android #q #clipboard
XDA Developers
RIP Clipboard Managers: Android Q blocks background clipboard access
On the previous versions of Android, any app could access the clipboard.That could cause serious security issues. Android Q is changing that.
John Wu @topjohnwu
Magisk Developer
https://mobile.twitter.com/topjohnwu/status/1105947979679191041
Bad news: Android Q root won't come anytime soon. Android Q has switched to logical partitions for the system block, which means there is no easy way to mount the block by any means. I'm currently thinking of what tricks can I do other than implement everything from scratch....
Things are not looking good 😅, even if I could, I might have to create a complete new Magisk just for Android Q. Android Q switched to this stupidly complicated logical device (device-mapper) + overlayfs madness just to support "Previewing GSIs" from data partition.
It will take me an extreme amount of time to figure out how to workaround all this mess. I won't expect Magisk to be even able to boot on Q in months.
After stepping back and taking a breath, I think I'll just have to figure out how to mount logical partitions and things should work. With normal EXT4 Android Q system images, things works just fine as previously demonstrated. Time to read some device-mapper documents...
#magisk #root #android #q
Magisk Developer
https://mobile.twitter.com/topjohnwu/status/1105947979679191041
Bad news: Android Q root won't come anytime soon. Android Q has switched to logical partitions for the system block, which means there is no easy way to mount the block by any means. I'm currently thinking of what tricks can I do other than implement everything from scratch....
Things are not looking good 😅, even if I could, I might have to create a complete new Magisk just for Android Q. Android Q switched to this stupidly complicated logical device (device-mapper) + overlayfs madness just to support "Previewing GSIs" from data partition.
It will take me an extreme amount of time to figure out how to workaround all this mess. I won't expect Magisk to be even able to boot on Q in months.
After stepping back and taking a breath, I think I'll just have to figure out how to mount logical partitions and things should work. With normal EXT4 Android Q system images, things works just fine as previously demonstrated. Time to read some device-mapper documents...
#magisk #root #android #q
Here are the new Android Q features that Google announced
https://www.xda-developers.com/android-q-new-features
#android #q #features
https://www.xda-developers.com/android-q-new-features
#android #q #features
XDA Developers
Here are the new Android Q features that Google announced
We've already talked a lot about the new features coming to Android Q, but Google has shared some details about the big ones in this beta.
patch.sh
3.8 KB
Signature Spoofing patching for Android Q
- All the credit to Darknecromonger for discovering this method -
Basically some tools (namely DexPatcher) have been updated that now allow us to patch Android Q for sigspoofing without using shady stuff like SmaliPatcher.
Setialpha knows about it already and it will probably be in the next ND patcher release.
Meanwhile, here's a handy little shell script to be run from a PC. It'll pull, patch and push a sigspoof patched services.jar by itself.
Prerequisites:
- A deodexed ROM
- A PC with java and adb installed
Instructions:
- Connect the device to your PC with a cable and authorise ADB
- Run patcher.sh
[Tested on Debian, but should be distro agnostic]
Troubleshooting:
- ADB can't access USB for your user? Search online how to fix it. Or you can run with sudo, but that's just bad practice
📡 @NoGoolag
#sigspoof #q #patch #patcher
- All the credit to Darknecromonger for discovering this method -
Basically some tools (namely DexPatcher) have been updated that now allow us to patch Android Q for sigspoofing without using shady stuff like SmaliPatcher.
Setialpha knows about it already and it will probably be in the next ND patcher release.
Meanwhile, here's a handy little shell script to be run from a PC. It'll pull, patch and push a sigspoof patched services.jar by itself.
Prerequisites:
- A deodexed ROM
- A PC with java and adb installed
Instructions:
- Connect the device to your PC with a cable and authorise ADB
- Run patcher.sh
[Tested on Debian, but should be distro agnostic]
Troubleshooting:
- ADB can't access USB for your user? Search online how to fix it. Or you can run with sudo, but that's just bad practice
📡 @NoGoolag
#sigspoof #q #patch #patcher
LOS for microG 17.1 building tools
In light of problems the official LOS4µG project is facing to build Android Q,
Project: https://gitlab.com/fremontt/minimal-docker-for-lineageos
Discussion thread: https://redd.it/h8cwpg
#los4µG #microg #los #lmg #losmicrog #lineage #lineagemicrog #Q #docker
In light of problems the official LOS4µG project is facing to build Android Q,
ooOOooOoo has created a docker image and automation scripts to patch official LOS sources with sigspoof and integrate the microG with the community's Q fixes.Project: https://gitlab.com/fremontt/minimal-docker-for-lineageos
Discussion thread: https://redd.it/h8cwpg
#los4µG #microg #los #lmg #losmicrog #lineage #lineagemicrog #Q #docker