Status Update
Comments
lb...@gmail.com <lb...@gmail.com> #2
Information redacted by Android Beta Feedback.
ad...@google.com <ad...@google.com>
ad...@google.com <ad...@google.com> #3
What
More information
It turns out, this issue happens almost every time. If it crashes a certain way (probably if it's happening too quickly or too many times), the device will reboot. Last time, it took me to the Android recovery saying along the lines of "Can't load Android ... Your data might be corrupted" and the options were try again or factory reset.
The screen recording was done on the first attempt. Thankfully I can unlock after the lock screen crashes using the pin or fingerprint. Fingerprint can also work right from AOD.
But when after a few crashes, some worse than others (the display doesn't stay on and I had to press the power button), the device rebooted and entered me into a recovery screen. The second bug report was taken after that.
When
Time and frequency
Time when bug report was triggered: Mar 14, 2025 5:26 AM GMT+07:00
Where
Build and device data
- Build Number: google/panther_beta/panther:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250960035 (25.09.60 (260400-732198584))
System App (Updated)
Android System WebView
com.google.android.webview
Version 704901443 (135.0.7049.14)
System App (Updated)
Network operator: Telkomsel
SIM operator: Telkomsel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ch...@gmail.com <ch...@gmail.com> #4
Information redacted by Android Beta Feedback.
lf...@gmail.com <lf...@gmail.com> #5
This is quite bad. Now it happens every time.
The crash also sometimes happen when turning off the screen. In which case, the AOD likely won't work. I have to turn on the display before unlocking but thankfully looks like it doesn't crash again if it crashes when turning off the screen.
New bug report and screen recording on next post.
de...@gmail.com <de...@gmail.com> #6
What
More information
While on the home screen, it crashes when turning off the display. Somehow, I can't replicate this while recording, and I had to turn on Do Not Disturb (Bedtime) for it to crash when turning off again.
Later in the recording, the crash happens repeatedly. Every time this happened previously, the lock screen and AOD didn't recover and the phone rebooted.
The last one happened while I was attempting to record this, and I saw the old white "Power Off" dialog with the spinning circle UI before it rebooted to the same recovery screen again. I couldn't find that recording after.
The bug report was taken after the attached (successful) recording.
Where
Build and device data
- Build Number: google/panther_beta/panther:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250960035 (25.09.60 (260400-732198584))
System App (Updated)
Android System WebView
com.google.android.webview
Version 704901443 (135.0.7049.14)
System App (Updated)
Network operator: Telkomsel
SIM operator: Telkomsel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
we...@gmail.com <we...@gmail.com> #7
Information redacted by Android Beta Feedback.
co...@gmail.com <co...@gmail.com> #8
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
lb...@gmail.com <lb...@gmail.com> #9
ar...@gmail.com <ar...@gmail.com> #10
Turning off AOD seems to avoid the issue on my P7 too, so far. It's a bit inconvenient but necessary for now. Thank you for the suggestion.
ha...@okta.com <ha...@okta.com> #11
lb...@gmail.com <lb...@gmail.com> #12
What
More information
As I turned off the AOD, the unexpected shutdowns have completely disappeared
When
Time and frequency
Time when bug report was triggered: Mar 17, 2025 5:57 AM GMT+05:00
Where
Build and device data
- Build Number: google/bluejay_beta/bluejay:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250933035 (25.09.33 (260400-736501638))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699803933 (134.0.6998.39)
System App (Updated)
Network operator: PAK - PL
SIM operator: ZONG
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
go...@gmail.com <go...@gmail.com> #13
Information redacted by Android Beta Feedback.
he...@gmail.com <he...@gmail.com> #14
el...@gmail.com <el...@gmail.com> #16
What
More information
I followed the steps from the linked similar issue and turned off AOD and can confirm it no longer crashes the phone.
Where
Build and device data
- Build Number: google/cheetah_beta/cheetah:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250962035 (25.09.62 (260400-736577381))
System App (Updated)
Android System WebView
com.google.android.webview
Version 704901443 (135.0.7049.14)
System App (Updated)
Network operator: YES OPTUS
SIM operator: YES OPTUS
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ch...@gmail.com <ch...@gmail.com> #17
Information redacted by Android Beta Feedback.
ru...@gmail.com <ru...@gmail.com> #18
f5...@gmail.com <f5...@gmail.com> #19
What
More information
Now the phone is going to the factory reset boot screen.
Where
Build and device data
- Build Number: google/husky_beta/husky:16/BP22.250221.010/13193326:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 250933035 (25.09.33 (260400-736501638))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699803933 (134.0.6998.39)
System App (Updated)
Network operator: Koodo
SIM operator: Koodo
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
fe...@gmail.com <fe...@gmail.com> #20
Information redacted by Android Beta Feedback.
qu...@gmail.com <qu...@gmail.com> #21
cy...@gmail.com <cy...@gmail.com> #22
What
More information
As the previous comment says, the issue seems to still be present on Beta 3.1 (BP22.250221.013). It happens a tiny bit less frequently on my P7, but AOD is still unusable for me on this build.
When
Time and frequency
Time when bug report was triggered: Mar 19, 2025 5:30 AM GMT+07:00
Where
Build and device data
- Build Number: google/panther_beta/panther:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 251033035 (25.10.33 (260400-736521774))
System App (Updated)
Android System WebView
com.google.android.webview
Version 704901443 (135.0.7049.14)
System App (Updated)
Network operator: Telkomsel
SIM operator: Telkomsel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
te...@gmail.com <te...@gmail.com> #23
Information redacted by Android Beta Feedback.
ga...@gmail.com <ga...@gmail.com> #24
What
More information
phone crashed again this morning triingto wake from sleep
When
Time and frequency
Time when bug report was triggered: Mar 19, 2025 8:27 AM GMT-07:00
Where
Build and device data
- Build Number: google/lynx_beta/lynx:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250933035 (25.09.33 (260400-736501638))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699803933 (134.0.6998.39)
System App (Updated)
Network operator: ROGERS
SIM operator: ROGERS
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
an...@gmail.com <an...@gmail.com> #25
Information redacted by Android Beta Feedback.
ma...@marcardar.com <ma...@marcardar.com> #26
What
More information
Even after the update yesterday, it still does it, but less frequently
Where
Build and device data
- Build Number: google/tokay_beta/tokay:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250933035 (25.09.33 (260400-736501638))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699803933 (134.0.6998.39)
System App (Updated)
Network operator: Koodo
SIM operator: Koodo
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
p....@gmail.com <p....@gmail.com> #27
Information redacted by Android Beta Feedback.
lb...@gmail.com <lb...@gmail.com> #28
What
More information
Lock screen flickers does not want to open, crashes and restart.
When
Time and frequency
Time when bug report was triggered: Mar 20, 2025 10:18 AM GMT-04:00
Where
Build and device data
- Build Number: google/tokay_beta/tokay:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250933035 (25.09.33 (260400-736501638))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699803933 (134.0.6998.39)
System App (Updated)
Network operator: Koodo
SIM operator: Koodo
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
th...@gmail.com <th...@gmail.com> #29
Information redacted by Android Beta Feedback.
lb...@gmail.com <lb...@gmail.com> #30
What
More information
Newer bug report with fresh crash just before report made.
Where
Build and device data
- Build Number: google/caiman_beta/caiman:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 251061035 (25.10.61 (260400-738233885))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699810833 (134.0.6998.108)
System App (Updated)
Network operator: Circles
SIM operator: Circles
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
lb...@gmail.com <lb...@gmail.com> #31
Information redacted by Android Beta Feedback.
jo...@halfreal.de <jo...@halfreal.de> #32
Latest beta (16B3.1 IIRC) does not resolve this.
ma...@marcardar.com <ma...@marcardar.com> #33
What
More information
Please find the screen received after device reboot
Where
Build and device data
- Build Number: google/husky_beta/husky:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 251132035 (25.11.32 (260400-738162387))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699804033 (134.0.6998.40)
System App (Updated)
Network operator: mobily
SIM operator: BSNL Mobile
Network operator: stc ksa
SIM operator: stc
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
lb...@gmail.com <lb...@gmail.com> #34
Information redacted by Android Beta Feedback.
ma...@marcardar.com <ma...@marcardar.com> #35
What
More information
It switches out at the lockscreen. It has become worse after the update
Where
Build and device data
- Build Number: google/lynx_beta/lynx:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250934035 (25.09.34 (260400-738842635))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699804033 (134.0.6998.40)
System App (Updated)
Network operator: airtel
SIM operator: airtel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
lb...@gmail.com <lb...@gmail.com> #36
Information redacted by Android Beta Feedback.
ma...@marcardar.com <ma...@marcardar.com> #37
What
More information
When Always on Display is disabled doesn't crashes anymore. Maybe the bug has to be with the animation when you press the power button or any form of unlocking the phone while AOD is enabled.
Where
Build and device data
- Build Number: google/husky_beta/husky:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Servicios de Google Play
com.google.android.gms
Version 250934035 (25.09.34 (260400-738842635))
System App (Updated)
Android System WebView
com.google.android.webview
Version 699810933 (134.0.6998.109)
System App (Updated)
Network operator: Megamovil
SIM operator: Megamovil
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ma...@marcardar.com <ma...@marcardar.com> #38
Failed to process file bugreport-husky_beta-BP22.250221.013-2025-03-28-06-15-51_GMT-07:00.zip
ma...@marcardar.com <ma...@marcardar.com> #39
lb...@gmail.com <lb...@gmail.com> #40
si...@gmail.com <si...@gmail.com> #41
is...@gmail.com <is...@gmail.com> #42
cy...@gmail.com <cy...@gmail.com> #43
So, if that's an appropriate solution for Chrome, why is it not an appropriate solution for Android apps? Many of us (small businesses and developers) have been eagerly awaiting a response from the Android team on whether we're likely to get a permission request ability (so users can make an informed decisions about whether they want an app to be able to monitor the clipboard or not). Please respond so we can decide whether our apps and businesses have a future or not.
As a reminder, there are millions of installs of clipboard manager apps (some of them paid apps). There is clear demand for these products and this use case.
*
*
*
*
tr...@tellient.com <tr...@tellient.com> #44
lb...@gmail.com <lb...@gmail.com> #45
See the rudeness?
Google removed any good way to monitor clipboard for clipboard managers to sync between Android and PC (and other features), and yet added something similar for its own web browser...
br...@gmail.com <br...@gmail.com> #46
The world is moving towards and ecosystem where devices can **more easily** share files, data, and information, and where I can seamless move from one device to the other.
Just for example, I could copy text or a graphic on my desktop or laptop, and paste it in my Android device.
This policy moves us in the exact opposite and wrong direction.
It's a move back towards the days when the best way to transfer information between your computer and your mobile device was to email it to yourself.
sl...@gmail.com <sl...@gmail.com> #47
Hopefuly this will get fixed before Android 11.
lb...@gmail.com <lb...@gmail.com> #48
1. If you are a clipboard-manager app developer, for some reason using SAW with focusable on-top-view will still let you monitor the clipboard. Sadly Google plan to remove this permission someday, though, and replace it with a useless API (Bubble), which looks very similar to the hated Facebook chat-heads.
2. If you are a user, try keyboard apps that offer clipboard handling, like Gboard. It's not the same at all, and many features are missing, but it's something.
mi...@gmail.com <mi...@gmail.com> #49
lb...@gmail.com <lb...@gmail.com> #50
gr...@gmail.com <gr...@gmail.com> #51
rd...@gmail.com <rd...@gmail.com> #52
mr...@gmail.com <mr...@gmail.com> #53
za...@gmail.com <za...@gmail.com> #54
tr...@gmail.com <tr...@gmail.com> #55
ym...@gmail.com <ym...@gmail.com> #56
Take the ramp..
ra...@gmail.com <ra...@gmail.com> #57
dv...@gmail.com <dv...@gmail.com> #58
tn...@gmail.com <tn...@gmail.com> #59
st...@gmail.com <st...@gmail.com> #60
At the very least, you are losing revenue because of the apps that you've rendered useless and/or crippled are going away.
ru...@gmail.com <ru...@gmail.com> #61
their excuse. google is rotten and greedy and wants to make sure the only
thing reading our copy / paste is them, for further data mining. They had
more than ample time to add permissions, they didn't even try.
On Mon, Sep 30, 2019 at 3:45 PM <buganizer-system@google.com> wrote:
--
rustygh
ha...@gmail.com <ha...@gmail.com> #62
p....@gmail.com <p....@gmail.com> #63
gy...@gmail.com <gy...@gmail.com> #64
cr...@gmail.com <cr...@gmail.com> #65
adb -d shell appops set com.catchingnow.tinyclipboardmanager SYSTEM_ALERT_WINDOW allow;
adb -d shell pm grant com.catchingnow.tinyclipboardmanager android.permission.READ_LOGS;
adb shell am force-stop com.catchingnow.tinyclipboardmanager;
sl...@gmail.com <sl...@gmail.com> #66
lb...@gmail.com <lb...@gmail.com> #67
It's about SYSTEM_ALERT_WINDOW .
And it's the same workaround as I wrote on #48.
You don't need adb for it.
sl...@gmail.com <sl...@gmail.com> #68
I imagine there is some code workaround that needs to be written besides following these instructions for apps that monitor the clipboard, right? or are these instructions enough and require no further changes for apps that previously worked, besides them adding the READ_LOGS permission to their manifest?
lb...@gmail.com <lb...@gmail.com> #69
Just use SAW instead, together with a real focusable floating View and a foreground service.
And again, this is just a workaround, because sadly Google plans to ruin SAW permission too, some day.
he...@gmail.com <he...@gmail.com> #70
Also I strongly suggest to put the focus of the discussion back to Google, not any app.
lb...@gmail.com <lb...@gmail.com> #71
At least for SAW you can have a tiny view somewhere or even almost invisible, and still allow normal users grant it.
What's "a11y " ? If you mean accessibility, I already tested it and didn't notice it doing anything.
Have you really tried using READ_LOGS alone, without SAW, and it worked for you?
If so, it's really weird, because the docs say about focused apps, and logs have nothing to do with it...
he...@gmail.com <he...@gmail.com> #72
SAW + READ_LOG / SAW + a11y works fine.
SAW only will destroy the system behavior such as back key.
I still hope that the discussion will focus on getting Google to change the current rude practices, not the specific implementation of an app.
lb...@gmail.com <lb...@gmail.com> #73
And why do you use SAW together with others, if you said you don't want to use SAW, and I tell you that SAW is enough?
Why do you think it will destroy the back key? It has nothing to do with it.
he...@gmail.com <he...@gmail.com> #74
lb...@gmail.com <lb...@gmail.com> #75
One of them is why do you think it will do this ("disturbing the system gestures and back key").
gm...@gmail.com <gm...@gmail.com> #77
hw...@gmail.com <hw...@gmail.com> #78
sm...@gmail.com <sm...@gmail.com> #79
cy...@gmail.com <cy...@gmail.com> #80
Thanks to everyone who starred this issue or left a comment to help get this on Google's radar.
st...@gmail.com <st...@gmail.com> #81
ro...@gmail.com <ro...@gmail.com> #82
lb...@gmail.com <lb...@gmail.com> #83
Here, attached this sample after updating to latest sdks and also added clipboard monitoring inside (shows content on logs), to show that it's possible to use SAW alone (with foreground service to keep it nicely alive).
ba...@gmail.com <ba...@gmail.com> #84
eb...@googlemail.com <eb...@googlemail.com> #85
cu...@gmail.com <cu...@gmail.com> #86
I've been disappointef and dissatisfied with Android 10 so far. Many of the apps and features that worked great just a few days ago before updating, are now clumsy and more difficult to use. Please continue your hard work and allow others to do the same, especially if they are doing great.
cc...@gmail.com <cc...@gmail.com> #87
si...@gmail.com <si...@gmail.com> #88
da...@gmail.com <da...@gmail.com> #89
fa...@gmail.com <fa...@gmail.com> #90
re...@googlemail.com <re...@googlemail.com> #91
sg...@gmail.com <sg...@gmail.com> #92
Very Respectfully,
Surinder
ph...@gmail.com <ph...@gmail.com> #93
ir...@gmail.com <ir...@gmail.com> #94
si...@gmail.com <si...@gmail.com> #95
ba...@gmail.com <ba...@gmail.com> #96
There's a reason I use Android and not iOS and removing functionality and locking down the OS diminishes that reason.
Removing clipboard functionality is another step closer to making iOS equal competition, damaging your user base and market attraction
cy...@gmail.com <cy...@gmail.com> #97
1. We're asking for a permission request for clipboard access, following the solid pattern that Android has developed for other sensitive data (mic, camera, location, etc.).
2. Clipboard apps are popular and some users have paid for clipboard apps. Android 10 breaks these apps and robs the user of the value that they paid for since developers don't have any path to get access to the users' clipboard in Android 10.
3. Chrome has upcoming support to prompt the user for clipboard access with the Clipboard API (
Please help us keep Android awesome and distinct from iOS. This talk at Android Developer Conference yesterday (
se...@gmail.com <se...@gmail.com> #98
it's a great tool and I would like it back please. Don't restrict people from using their devices how they want to.
as...@gmail.com <as...@gmail.com> #99
ym...@gmail.com <ym...@gmail.com> #100
ms...@gmail.com <ms...@gmail.com> #101
ro...@gmail.com <ro...@gmail.com> #102
no...@gmail.com <no...@gmail.com> #103
ab...@gmail.com <ab...@gmail.com> #104
When I eagerly updated to Android 10 on my Pixel 3, I had no idea that clipboard access was to be suddenly taken away. I'm a regular user of Clipper+.
Why is it that some IMEs like your own Gboard for example, still have the ability to access clipboard content but third party apps like Clipper+ are not trustworthy? I specifically searched out the app and installed it from the Google Play Store because I'm an end user who knows what he wants: full time access to all the text copied before. That's the reason I installed the app. I trust it with my data, I'm not copying any passwords or nuclear codes or defense secrets. I gave the app I downloaded the permission because I know what I'm doing. Now who are you to decide for me what's best for me when I expressly gave the app the permission to take care of this thing for me?
Breaks my trust in the Android ecosystem as a whole that you're now becoming more controlling than Apple, the very thing we took pride in, we're throwing away every day...
st...@gmail.com <st...@gmail.com> #105
di...@gmail.com <di...@gmail.com> #106
rc...@gmail.com <rc...@gmail.com> #107
su...@gmail.com <su...@gmail.com> #108
¡Háganlo por los usuarios!
Thanks.
cb...@gmail.com <cb...@gmail.com> #109
cb...@gmail.com <cb...@gmail.com> #110
si...@gmail.com <si...@gmail.com> #111
cj...@gmail.com <cj...@gmail.com> #112
ur...@gmail.com <ur...@gmail.com> #113
sp...@gmail.com <sp...@gmail.com> #114
sp...@gmail.com <sp...@gmail.com> #115
pb...@gmail.com <pb...@gmail.com> #116
I think these people make a pretty strong argument that this was a bad idea.
to...@gmail.com <to...@gmail.com> #117
so...@gmail.com <so...@gmail.com> #118
jo...@gmail.com <jo...@gmail.com> #119
yh...@gmail.com <yh...@gmail.com> #120
si...@gmail.com <si...@gmail.com> #121
jt...@gmail.com <jt...@gmail.com> #122
fr...@gmail.com <fr...@gmail.com> #123
ky...@gmail.com <ky...@gmail.com> #124
kh...@gmail.com <kh...@gmail.com> #125
co...@gmail.com <co...@gmail.com> #126
ha...@gmail.com <ha...@gmail.com> #127
ra...@gmail.com <ra...@gmail.com> #128
gl...@gmail.com <gl...@gmail.com> #129
Android used to be peerless precisely because of its flexibility. Every year, it gets less and less useful, and that's a shame.
Enough with the random, arbitrary feature deprecations. Throw clipboard access behind a security control, and bring it back.
ro...@gmail.com <ro...@gmail.com> #130
As for specifics on how to fix this issue, I support adding a new run time permission that has to be granted by the user. This still feels like overkill for something so trivial like the clipboard but it's an adequate compromise.
sl...@gmail.com <sl...@gmail.com> #131
f....@gmail.com <f....@gmail.com> #132
tg...@gmail.com <tg...@gmail.com> #133
ha...@gmail.com <ha...@gmail.com> #134
ra...@gmail.com <ra...@gmail.com> #135
a8...@gmail.com <a8...@gmail.com> #136
mc...@gmail.com <mc...@gmail.com> #137
Either allow those apps or provide that function withon Android!
vi...@google.com <vi...@google.com>
le...@gmail.com <le...@gmail.com> #138
re...@gmail.com <re...@gmail.com> #139
Now it's become pretty much USELESS due to your recent change. Please allow clipboard managers have access to the Android clipboard.
js...@gmail.com <js...@gmail.com> #140
As a business owner, my phone is definitely a computer. I run my entire business from it and my laptop which is Windows based, and if Microsoft can pull it off, you most certainly can.
Please tell me you aren't letting Microsoft, your public enemy number 1... Best you? Evidently they are because their clipboard and history manager in Windows 10 actually works quite well and I'm calling you out about it. Shame shame Google. (Wagging finger)
Blocking this is ridiculous. It makes my use of my phone MORE dangerous because when mobile I cannot QUICKLY recall common things like my signature from my clipboard. Instead I have to use another app like OneNote or Google Keep to create my own clipboards which get LOST within load time and my plethora of other notes. It's a nightmare, that you've created and that has reduced my corporate efficiency multi fold. Just makes me want to switch back to an iPhoney.
di...@gmail.com <di...@gmail.com> #141
sa...@gmail.com <sa...@gmail.com> #142
mi...@gmail.com <mi...@gmail.com> #143
le...@gmail.com <le...@gmail.com> #144
ke...@gmail.com <ke...@gmail.com> #145
hs...@gmail.com <hs...@gmail.com> #146
st...@gmail.com <st...@gmail.com> #147
me...@gmail.com <me...@gmail.com> #148
ka...@gmail.com <ka...@gmail.com> #149
this and other stupid things the Android product managers are doing.
Karl
On Sun, Dec 22, 2019 at 11:16 PM <buganizer-system@google.com> wrote:
me...@gmail.com <me...@gmail.com> #150
pl...@gmail.com <pl...@gmail.com> #151
I'm going back to 9. Who on earth signed off this utterly stupid idea?
Roll that back. Above are valid technical reasons. if they not matter, do it for emotional reasons: I hate this! I rely on clipboard 80% of my user scenarios. You added a myriad of clicks to my life. thanks for nothing, asshats.
co...@gmail.com <co...@gmail.com> #152
Stop it..
al...@gmail.com <al...@gmail.com> #153
Google should specifically examine what some of these clipboard managers do and probably address that on need basis.
Easy copy, for instance, one of the best clipboard managers can be given an exclusion.
kg...@gmail.com <kg...@gmail.com> #154
Who was the genius who decided to sign this off not thinking of the trade-offs of productivity and ease of use? Where was the human-centered design logic in doing this?
Really disappointed after upgrading to Android 10 and I will advise people not to do it.
go...@gmail.com <go...@gmail.com> #155
di...@gmail.com <di...@gmail.com> #156
te...@gmail.com <te...@gmail.com> #157
95...@gmail.com <95...@gmail.com> #158
ie...@gmail.com <ie...@gmail.com> #159
ja...@gmail.com <ja...@gmail.com> #160
ge...@gmail.com <ge...@gmail.com> #161
ce...@gmail.com <ce...@gmail.com> #162
ja...@gmail.com <ja...@gmail.com> #163
lu...@gmail.com <lu...@gmail.com> #164
ps...@gmail.com <ps...@gmail.com> #165
cy...@gmail.com <cy...@gmail.com> #166
lg...@gmail.com <lg...@gmail.com> #167
sp...@gmail.com <sp...@gmail.com> #168
as...@gmail.com <as...@gmail.com> #169
in...@gmail.com <in...@gmail.com> #170
jc...@gmail.com <jc...@gmail.com> #171
People who actually use Android thoroughly obviously know how important this is. The restriction of this feature only tells us the devs are not using this feature at all.
tr...@gmail.com <tr...@gmail.com> #172
im...@gmail.com <im...@gmail.com> #173
And why can't I decide - should I give an app access to clipboard or not?
Please bring clipboard back.
ju...@gmail.com <ju...@gmail.com> #174
pa...@gmail.com <pa...@gmail.com> #175
tm...@gmail.com <tm...@gmail.com> #176
pr...@gmail.com <pr...@gmail.com> #177
le...@gmail.com <le...@gmail.com> #178
ra...@gmail.com <ra...@gmail.com> #179
mo...@gmail.com <mo...@gmail.com> #180
gs...@gmail.com <gs...@gmail.com> #181
ev...@gmail.com <ev...@gmail.com> #182
ed...@gmail.com <ed...@gmail.com> #183
At the very least you should let me disable this change if I want. You sure did not warn me before the update began.
Please help me with this,
Ed Grossheim
ak...@gmail.com <ak...@gmail.com> #184
jo...@gmail.com <jo...@gmail.com> #185
Honestly this is the kinda of petty tweeking I would expect from apple not from Android. Please reinstate this function
ju...@gmail.com <ju...@gmail.com> #186
Get Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, January 16, 2020 2:10:03 PM
To: b-system+-187731804@google.com <b-system+-187731804@google.com>
Cc: justinenicole2012@gmail.com <justinenicole2012@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
hotlist (+): Google Domain<
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker<
status: Assigned
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346<
duplicate issue: 128582282<
hotlist: [AOSP] assigned<
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
ja...@gmail.com <ja...@gmail.com> #187
ni...@gmail.com <ni...@gmail.com> #188
gi...@gmail.com <gi...@gmail.com> #189
st...@gmail.com <st...@gmail.com> #190
sp...@gmail.com <sp...@gmail.com> #191
ve...@gmail.com <ve...@gmail.com> #192
fi...@gmail.com <fi...@gmail.com> #193
fi...@gmail.com <fi...@gmail.com> #194
ch...@gmail.com <ch...@gmail.com> #195
Download an app... blocked?!?!?!
WTF?
ro...@gmail.com <ro...@gmail.com> #196
ya...@gmail.com <ya...@gmail.com> #197
co...@gmail.com <co...@gmail.com> #198
na...@gmail.com <na...@gmail.com> #199
ar...@gmail.com <ar...@gmail.com> #200
How do I starr an issue btw
bi...@gmail.com <bi...@gmail.com> #201
ne...@gmail.com <ne...@gmail.com> #202
Really miss having a clipboard manager for my Pixel 2 XL.
Thank you.
tu...@gmail.com <tu...@gmail.com> #203
Rather than disallowing them, please consider simply adding a checkbox--along with some information explaining the risks and how to mitigate them--that the user must check in order to grant this permission.
PLEASE GIVE BACK OUR CLIPBOARD MANAGERS ! ! !
ra...@gmail.com <ra...@gmail.com> #204
dh...@gmail.com <dh...@gmail.com> #205
cy...@gmail.com <cy...@gmail.com> #206
st...@gmail.com <st...@gmail.com> #207
On Tue, Jan 28, 2020, 2:57 PM <buganizer-system@google.com> wrote:
ba...@gmail.com <ba...@gmail.com> #208
Please.... Please
mo...@gmail.com <mo...@gmail.com> #209
dr...@gmail.com <dr...@gmail.com> #210
ba...@gmail.com <ba...@gmail.com> #211
fi...@gmail.com <fi...@gmail.com> #212
and Android 10 has exploded many of the best and most needed apps. At the
same time, 10 has incorporated inferior watered-down versions of these apps
as built-in features.
On Mon, Jan 27, 2020, 12:42 AM <buganizer-system@google.com> wrote:
ga...@gmail.com <ga...@gmail.com> #213
en...@gmail.com <en...@gmail.com> #214
eh...@gmail.com <eh...@gmail.com> #215
My next Phone will be an IPHONE with IOS.
Till now doesn't any Reason to change the System, but just now. Even this features does not exist in IOS too, but there are better security and filemanagement.
Adios GOOGLE and ANDROID!
be...@gmail.com <be...@gmail.com> #216
ju...@gmail.com <ju...@gmail.com> #217
Get Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Sunday, February 2, 2020 11:35:07 PM
To: b-system+-187731804@google.com <b-system+-187731804@google.com>
Cc: justinenicole2012@gmail.com <justinenicole2012@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
be...@gmail.com added
What the hell is this? Literally, who asked for this? Terrible idea. This will be a clear indicator if google listens to their users.
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker<
status: Assigned
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346<
duplicate issue: 128582282<
hotlist: [AOSP] assigned<
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
dh...@gmail.com <dh...@gmail.com> #218
I share to email (mine) at the moment. I am looking at search and accessibility as hacks.
Note that share allows a functional programming paradigm. With one extra click.
Q: Developers: What options are available with overl ays and floating widgets?
I recommend share plus your existing UI. Am I wrong? Problems?
dh...@gmail.com <dh...@gmail.com> #219
ta...@gmail.com <ta...@gmail.com> #220
sp...@gmail.com <sp...@gmail.com> #221
jo...@gmail.com <jo...@gmail.com> #222
la...@gmail.com <la...@gmail.com> #223
I copy paste 10 sentences and their translation into my Anki flashcard app.
Already since I got a new phone I lost the default clipboard functionality to stay available easily. Nowadays every time I lose focus by changing my entry box to get to the next one, i had to tap and tap and tap and look for the line i wanted to copy. So after searching I found this amazing app Smart Clip that has an overlay that stay on top until i close it, and it is so much quicker to do my menial tasks.
ENTER ANDROID 10 and now I have a cool black look I didnt ask for, security protection I cannot bypass, but can't use my phone to accomplish my daily tasks. I've had to use my old Samsung S7 with it's smashed screen to do my work. I have an Android phone rather than an iphone because of the freedom to do what I want, productively. If I wanted a phone for numpties I' d get an iphone.
Please make these security options bypassable for trusted apps rather than deciding for us.
Thanks for all the work so far on Android, most of my user experience has been great.
tu...@gmail.com <tu...@gmail.com> #224
We used to have it, we are used to having it, we want it back!
WE NEED IT !!! We DESPERATELY WANT IT BACK ! ! ! PRETTY PLEASE!?!?!?
On Tue, Jan 28, 2020 at 10:57 AM <buganizer-system@google.com> wrote:
sr...@gmail.com <sr...@gmail.com> #225
jc...@gmail.com <jc...@gmail.com> #226
jo...@gmail.com <jo...@gmail.com> #227
mb...@gmail.com <mb...@gmail.com> #228
os...@gmail.com <os...@gmail.com> #229
ra...@gmail.com <ra...@gmail.com> #230
I use an app that depends on it trip work.
ha...@gmail.com <ha...@gmail.com> #231
hi...@gmail.com <hi...@gmail.com> #232
It's nonsense... please start app.. its my day to day app. Which i use for many activities...
ju...@gmail.com <ju...@gmail.com> #233
dh...@gmail.com <dh...@gmail.com> #234
ka...@gmail.com <ka...@gmail.com> #235
clipboard? It's OURS, NOT YOURS. We decide how secure it needs to be, not
you. Stop trying to be like Apple when you grow up! My son dumped his
android phone for an iPhone last week because of this kind of evil crap. Do
No Evil used to be your slogan. It appears you dumped that and now it's "Do
Logs Of Evil To Our Users"
Do you not know we pay your salaries?
GIVE US OUR STUFF BACK!!!
---
Karl L. Pearson | karlplds@gmail.com
My "ComeUntoChrist.org" profile:
<
---
On Sun, Feb 16, 2020 at 9:32 AM <buganizer-system@google.com> wrote:
ul...@gmail.com <ul...@gmail.com> #236
el...@gmail.com <el...@gmail.com> #237
cy...@gmail.com <cy...@gmail.com> #238
as...@gmail.com <as...@gmail.com> #239
jr...@gmail.com <jr...@gmail.com> #240
Clipboard access has slipped under the radar where any app could declare the permission yet the user is never prompted when an app feels like using the permission. LineageOS' Privacy Guard was a solution but it was clunky at best. I don't want yet another choice to toggle for all apps just because "clipboard manager" apps want to read the clipboard. It's too niche.
I realize some people are upset but you can adapt. You have no way of knowing how many apps have been reading your clipboard for the past decade.
ro...@gmail.com <ro...@gmail.com> #241
text between apps, to compose or fill forms, primarily. As it was, I
could choose from a list of copied items in the clipboard manager,
perhaps numerous copies in one app or in various apps, to perform this
task. As it is, now, I can only have one item on the clipboard to
paste, then go back to the different app to copy/paste the next, one at
a time, over and over. This usage scenario must represent a fairly
large "niche", iianm.
I appreciate there are security concerns and, always, financial
concerns. I am not a software engineer but one of the end users who
spend thousands of dollars on the end product, such as my Pixel 3. It
would be nice if Google software engineers could devise a solution that
serves security and the practical needs of end users like myself at the
same time. WRT "financial concerns", it has been my end user
experience over many years that Google "support" is more concerned with
that than anything else and I've come to believe that, were I on fire,
Sergey wouldn't be moved to piss on me to put the fire out unless there
was a nickel in it for him. So, please, "adapt", exactly, how, other
than the standard expectation of the end user to bend over and lube?
Rolf
On 2/21/20 5:29 AM, buganizer-system@google.com wrote:
jr...@gmail.com <jr...@gmail.com> #242
ma...@gmail.com <ma...@gmail.com> #243
Instead of "fixing" a problem in a feature by nuking the feature and telling every user of it to suck it up, maybe the problem can be fixed instead by tackling the issue itself: make the clipboard permission explicitly granted.
People who support badly thought-out knee-jerk reactions that undermine many people's needs while a real solution that works for everyone is ignored, are why we can't have nice things.
jr...@gmail.com <jr...@gmail.com> #244
Adapted.
ma...@gmail.com <ma...@gmail.com> #245
Why should people have to adapt and change their workflow, lose the apps they're familiar with and possibly have no replacement for, when instead the problem can be solved at its root much more simply and leave everything users want to keep just as it is? Why choose an inferior solution? Storage access is also a sensitive permission, even more so than clipboard access, and that works just fine as a regular prompted permission. The same can be done with clipboard access, and then _everyone_ would be happy without losing anything (just hit a 1-time prompt as people already need to do for everything else)
jr...@gmail.com <jr...@gmail.com> #246
ro...@gmail.com <ro...@gmail.com> #247
In search of efficient utility from that for which I already incur
sufficient workload to support.
On 2/21/20 5:57 AM, buganizer-system@google.com wrote:
jp...@gmail.com <jp...@gmail.com> #248
di...@gmail.com <di...@gmail.com> #249
ma...@gmail.com <ma...@gmail.com> #250
jr...@gmail.com <jr...@gmail.com> #251
Do you know how many passwords are copied to the clipboard? Does your clipboard manager app have Internet access yet no apparent sync features? Could that same developer make a second app that takes the clipboard manager contents and send them elsewhere? 5 of the 5 clipboard manager I just installed all do either of those things. You do realize the Angry Birds game on your device could have been reading and uploading your clipboard contents encrypted to somewhere for the past 10 years
ma...@gmail.com <ma...@gmail.com> #252
Just make clipboard access the same as the other five dozen permissions: explicit and prompted. No more sneaky access and stolen data, unless you mistakenly trust a malicious app, which is the risk users sign up for with _all_ permissions. No use cases undermined or changed, no need to re-tool yourself, no new apps needed, no technical burdens, extremely minor inconvenience added (1-time permissions prompt the likes of which everyone already expects to get with every app install). It boggles my mind that this isn't what google went with and I have no idea as what kind of ridiculous contraption you visualize my simple suggestion in your mind.
jr...@gmail.com <jr...@gmail.com> #253
Let's hypothetically make both of us happy. Promote it to a user facing toggle. Toggled off by default. And it must request clipboard access per app where the originating text was copied. If I copy a bank account number from one app I would like that not to end up in my clipboard manager app. I also do not want my clipboard manager to have network access. So Internet access must also be a permission we see, toggled off by default. I also want an advanced firewall to block the third party ad networks embedded within the clipboard manager from reading the clipboard contents as well, so I would like to restrict network connectivity to just those destinations needed for clipboard syncing to function.
All of this because you want to save a few bucks
ma...@gmail.com <ma...@gmail.com> #254
As for your "both of us happy" post, you just made up an entire highly contrived usecase/mechanism that isn't currently in use, and then dismissed that as too contrived to be worth it. How is this an argument exactly? And what few bucks are you talking about?
I just want my clipboard history and cross-device-sharing to keep working as-is, while everyone can have privacy-consciousness in the form of clipboard access being an explicit permission just like all other data access permissions. There's really no need to overengineer these things nor nuke usecases from orbit, and highly contrived situations hardly outweigh common use cases.
ma...@gmail.com <ma...@gmail.com> #255
bj...@gmail.com <bj...@gmail.com> #256
cy...@gmail.com <cy...@gmail.com> #257
st...@gmail.com <st...@gmail.com> #258
wo...@gmail.com <wo...@gmail.com> #259
vo...@gmail.com <vo...@gmail.com> #260
du...@gmail.com <du...@gmail.com> #261
ki...@gmail.com <ki...@gmail.com> #262
eu...@gmail.com <eu...@gmail.com> #263
ki...@gmail.com <ki...@gmail.com> #264
Get rid of the competition first ?? 🤬
This decision sucks !!
It SEVERLY impacts my ability to run / manage my FB groups
- I'll have to move back to a PC instead of mobile / tablet
cy...@gmail.com <cy...@gmail.com> #265
Google... please listen to the people who have voiced their opposition to this policy change and rebalance the policy. Many good alternatives have been proposed at this point: exceptions for foreground services, a prominent permission request, etc. It's your job to balance security/privacy and functionality. This is an area where you clearly were beating iOS for enabling creative apps to tackle REAL use cases and deliver value to users but this policy change destroyed that competitive advantage and turned Android into a copycat of iOS. What's worse is that this policy is completely inconsistent with other platforms you control! Chrome extensions for desktop allows reading the clipboard without any permission request, even when Chrome is in the background. Even on Android, Accessibility permission allows apps to read the entire screen of a user. Yes it has a scary permission request screen, but a lot of users who want the value of an app will jump through whatever hoops are put in their way. Your argument against a clipboard permission request was that "it would be inappropriate because users wouldn't understand what they were agreeing to" (I'm paraphrasing). That argument is thin, however, because if apps like Amazon Assistant ask the user for Accessibility permission to read the user's screen and users LOVE that app (high ratings, lots of installs). That is CLEAR evidence that some developers are able to create apps that "exploit" a permission to create new, novel, VALUABLE apps. It's these apps that are only available on Android that give you and advantage over iOS, not copying their privacy policies.
Lastly: if a security vector is theoretically vulnerable but never actually exploited... is it actually a threat? I haven't heard of any bad actor ever actually using the clipboard to retrieve and build lists of passwords or other sensitive information. Can you reference a case of this ever happening? On the contrary, OnePlus had a huge story for a minute because there was suspicion that they were doing something nefarious with clipboard data (it turned out to be nothing):
This is to make the point that people are more savvy than you give them credit for. Bad actors will be thwarted by either an individual user reading negative reviews/ratings, reading and understanding a required permission request that describes an app "having access to information that's copied and pasted" or a media outlet will discover a bad actor and shine light on them (at which point you can remove them from the app store).
ti...@yahoo.com <ti...@yahoo.com> #266
ka...@gmail.com <ka...@gmail.com> #267
ka...@gmail.com <ka...@gmail.com> #268
pr...@gmail.com <pr...@gmail.com> #269
se...@gmail.com <se...@gmail.com> #270
You remove all access that makes valuable difference from ios... This is not true strategy... We like Android as flexible..
dh...@gmail.com <dh...@gmail.com> #271
.
RE YOUR GARBAGE DEFAULT CLIPBOARD UI.
.ARE YOU KIDDING ME!!!
.
RE YOUR GARBAGE DEFAULT CLIPBOARD UI.
.
As a user, completing a large block of text.
As I simply type THREE CHARACTERS OF A WORD!!!
For crying out loud. You do this on most words.
.
Your random lazy clipboard control, which pops up randomly nearly anywhere when it shouldn't have been triggered...
.
RESULTS IN MY LOSING LARGE BLOCKS OF IMPORTANT TEXT!
.
HOW?
In the space to 1.5 seconds.
The first character is typed.
The CB control is wrongly popping up on top of the KB.
The strike of the second character does not hit character #2,
It hits SELECT ALL!
The garbage Google CB controls vanishes.
The rapid habituated typing of character #3 of any word...
Causes the entire text to be replaced with character #3...
Thus destroying an entire long post.
Where your only way to back this post up is to use the clipboard to make a copy.
.
YOU IDIOTS.
.
Yes. We get it. We know. You have no concern nor regard for marginal power users.
.
But you even have no regard for basic users and the developers having difficulty getting thier controls working with your unstable poorly implemented changes providing an extremely low quality CB UI control.
.
YOUR ARROGANCE IS SIMPLY ASTOUNDING.
DULY NOTED
EXPECT THIS RESPONSE TO APPEAR ACROSS SOCIAL MEDIA..
NOT YOURS. THE ALTERNATE PRESS.
As a user, completing a large block of text.
As I simply type THREE CHARACTERS OF A WORD!!!
For crying out loud. You do this on most words.
.
Your random lazy clipboard control, which pops up randomly nearly anywhere when it shouldn't have been triggered...
.
RESULTS IN MY LOSING LARGE BLOCKS OF IMPORTANT TEXT!
.
HOW?
In the space to 1.5 seconds.
The first character is typed.
The CB control is wrongly popping up on top of the KB.
The strike of the second character does not hit character #2,
It hits SELECT ALL!
The garbage Google CB controls vanishes.
The rapid habituated typing of character #3 of any word...
Causes the entire text to be replaced with character #3...
Thus destroying an entire long post.
Where your only way to back this post up is to use the clipboard to make a copy.
.
YOU IDIOTS.
.
Yes. We get it. We know. You have no concern nor regard for marginal power users.
.
But you even have no regard for basic users and the developers having difficulty getting thier controls working with your unstable poorly implemented changes providing an extremely low quality CB UI control.
.
YOUR ARROGANCE IS SIMPLY ASTOUNDING.
DULY NOTED
EXPECT THIS RESPONSE TO APPEAR ACROSS SOCIAL MEDIA..
NOT YOURS. THE ALTERNATE PRESS.
da...@gmail.com <da...@gmail.com> #272
gp...@gmail.com <gp...@gmail.com> #273
Do not remove clipboard functinality. NO. It's Essentials for many useful applications
da...@gmail.com <da...@gmail.com> #274
da...@gmail.com <da...@gmail.com> #275
de...@gmail.com <de...@gmail.com> #277
fr...@gmail.com <fr...@gmail.com> #278
Now Im having tireble time copying and pasting cells and formula in Excell.. That I have to retype all formula a hundred times or more over and over again. It seems my phone is not a smartphone anymore.
This Android 10 clipboard banned update doesnt help me at all.
ml...@gmail.com <ml...@gmail.com> #279
tr...@gmail.com <tr...@gmail.com> #280
I WANT MY CLIP STACK!!! I NEED MY CLIP STACK!!! PLEASE FIX IT! PRETTY PLEASE!
za...@gmail.com <za...@gmail.com> #281
----from a heavy user of dictionary apps which rely on this permission to run properly.
ma...@gmail.com <ma...@gmail.com> #282
I am the only Android user in my family; everyone else uses of The limited world of ios. I have stayed with Android due to the flexible operating system alarm me to utilize my device in the way I wish.
Removing third party access to the clipboard functionality is outrageous and has significantly decreased the usability of my device.
Please restore 3rd party access!
ha...@gmail.com <ha...@gmail.com> #283
Omg... Why google even put issue tracker function anyway if thy dont bother to checked 😓😓😓
mo...@gmail.com <mo...@gmail.com> #284
cc...@google.com <cc...@google.com> #285
lf...@gmail.com <lf...@gmail.com> #286
Even if you had "advanced permissions", and disallowed these apps on your store (similar to UWP restricted capabilities), that would be fine. It's the fact that you're adding in OS-level restrictions that annoys me, because you are taking away functionality that I have paid for, and I do not have any good options for getting it back. If I have to sideload useful apps, so be it, but you are even getting in the way of that.
I just don't see how you can find this to be an acceptable way to treat your users or the developers building for your platform. If I wanted an iPhone, I would have bought one. It's about time that Google stopped trying to clone that experience on Android.
lb...@gmail.com <lb...@gmail.com> #287
The moment that an app gets focused, it has access to the clipboard. There is no security/privacy benefit. It's not safest.
And only keyboard apps and system apps get access to the clipboard.
For no reason whatsoever.
What about all apps that developers made using official API? What about all users that got those apps?
Now I can't sync clipboard with PC anymore. Some apps had this as a core function.
What about backward compatibility?
Why not present a real alternative? Those apps can't be converted to keyboard apps.
"Android has a number of user permissions that were implemented in Android 10 to enhance platform safety"
Incorrect about clipboard. It has no user permission for clipboard. It doesn't make it safer.
It only ruins apps.
You should always present a way for apps to evolve and not let them die just because you think something could make things safer.
When you blocked HTTP, you had both HTTPS working and still presented a flag for using HTTP if you really wanted.
This is much more serious and yet you provided both alternative and backward compatibility solutions.
And there are more examples.
Even for storage permission you said that SAF can usually replace it, but then planned to still let apps get access to it if they really need it.
So there is a default behavior which you allow to override if users/developers really want.
If you want, you can be nice for developers and users.
You can enhance the OS without ruining experience, without breaking apps, and without causing harm to users and developers.
Did you compensate users and developers for this decision?
What's so hard in adding a white list management for clipboard access ?
Don't you see how many users and developers have starred this issue? How many people care about it?
Here, made an alternative request:
jo...@gmail.com <jo...@gmail.com> #288
lb...@gmail.com <lb...@gmail.com> #289
This means Google just killed plenty of apps for no good reason and no alternative, without any warning and without any compensation for both users and developers.
jk...@gmail.com <jk...@gmail.com> #290
I've been in the computer consulting business full-time since DOS 1.0, and as an industry, the bigger the companies get, the more they try to "fix things that aren't broken," or cater to the minority, or make decisions by committees of OTHER computer programmers, that understand things and can do things that most end-users cannot. You forget that the END-USER is the ONLY one that counts, since without end-users you have no revenue and have NO JOBS. I agree with
When I design custom databases or other applications for clients, I have a rule I NEVER break when changes need to be made. I can ADD to what they have, that in some cases will help and be used, but not always. But I will NEVER take AWAY functionality, or even how to GET to that functionality, since in doing so I'll KILL some percentage of the users of my programs' ability to either use the program at ALL (like Google is trying to do as we speak), or cause them to have to waste time learning from scratch how to find and use the "new & improved" features I may have installed. If I did as Google and ALL of the other giants that were FORTUNATE ENOUGH to become giants, and have apparently forgotten how they GOT where they are, I'd be out of business! Take Microsoft Word as a simple example (really the entire company, since they make so many changes I can barely use ANYTHING they have, since I'm in perpetual relearn mode!). I'm still using Word 2003 because I can use it blindfolded. I can access the menu barely without looking. I think after that version is when they went to their new menu, which is LITERALLY, as determined by MOST users, BARELY usable in an EFFICIENT way. So MUCH so, Microsoft had to write a program that would make the newer versions revert BACK to the old menu because so many people were complaining. You people meaning ALL large companies, even beyond the computer industry), have GOT TO STOP FIXING THINGS THAT AREN'T BROKEN! You're KILLING your users, and guess what's next? LOSING your users. People can only take so much. There are only 24 hours in a day and most people can't get everything they need to do done as it is, but when companies like Google make changes based on an INTERNAL COMMITTEES of technical people, many that apparently have no COMMON SENSE, though they may otherwise be brilliant, with NO CONSIDERATION for the millions of users that have their systems setup and working EXACTLY like they want them, you're making them work HARDER for the same thing that the day before was a no-brainer, and burning up more of their VALUABLE TIME. My last example of EASILY one of the dumbest (no offense) decisions Google has EVER made (with the clipboard issue being #2 if you proceed), is KILLING Picasa! That was by far the easiest, most intuitive, most organized way to edit and store photographs, both locally AND in the Cloud. Like most, I save my 70,000 (does Google know that some people have that many, or do you "assume" that "oh, this won't matter to people with 100 photos?" photos in LOGICAL TO ME folders, consistently named and formatted for quick retrieval. It uploaded to the Google Cloud using the SAME FOLDER NAMES, so whether locally or in the Cloud out in a rowboat, I could FIND my dang photos in 2 seconds. And what was Google's genius solution to "fixing" Picasa? First it was the SO popular Google+, and we all know where that landed. Now it's Google Photos, uploads my photos ONLY AS UNORGANIZED SINGLE FILES, NO FOLDERS! The ONLY way I can find any of my MASSIVE number of photos is to know the DATE on which I took them!!!! REALLY? Who can remember the date they took a picture 10-15 years ago? My folders were tiered, meaning I had subfolders that further made it easier for me to find what I wanted. I might have a parent folder called SUNSETS, then subfolders for locations, and under locations I'd name the folder using the date at that location the photos were taken. Now what do I have? Google Photos Sync WILL sync the individual photos from ANY number of subfolders I might have locally, but it REMOVES them from ALL folders and stores them as just one gigantic "pile of files," where if I need a photos from 10 years ago, it might take me HOURS to find it... if EVER! And don't get me started on what Google KILLED in editing capabilities, and replaced it with in Google Photos! What LITTLE editing you can do, isn't the LEAST bit intuitive, so I had to abandon using editing with Google altogether and go to an outside program, which WASTES MY TIME! It's been YEARS since Picasa was killed and I'm STILL mad about it, and STILL haven't found a solution that will upload my photos retaining their FOLDER AND SUBFOLDER structure! Please pass on my thanks to whomever at Google made that genius decision.
Yes, I realize photos are not part of this discussion, but the discussion is about Google KILLING OFF programs and/or functionality in the name of "security." News Flash? No matter WHAT ANY programmer does to secure ANY system in the world, if a hacker wants in, they're going to GET in- PERIOD. Just like crime on the street, it hasn't changed and won't change, because every time the good guys zig, the bad guys zag. So I IMPLORE you Google, to FIRST, since you've "fixed" so many other things I can barely use, to at LEAST leave the Clipboard alone! As my friend
ba...@gmail.com <ba...@gmail.com> #291
A quick glance at this thread shows how many users are impassioned to persuade you to change your minds. No doubt, my point has already been laid out more eloquently & detailed than I can, so I'm merely adding my two cents to what is already a windfall of reasons.
Let's not be like Apple; return this choice to us 🙏
an...@gmail.com <an...@gmail.com> #292
ka...@gmail.com <ka...@gmail.com> #293
st...@gmail.com <st...@gmail.com> #294
implemented. It's just not surprising in the least that you didn't pay
attention to what the customers actually need. Please give it back to us.
Please pay attention to real-world users.
On Wed, Mar 18, 2020, 3:36 PM <buganizer-system@google.com> wrote:
ja...@gmail.com <ja...@gmail.com> #295
I've read today that the clipboard permission might be removed or granted only for system apps.
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
ja...@gmail.com <ja...@gmail.com> #296
I've read today that the clipboard permission might be removed or granted only for system apps.
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
ja...@gmail.com <ja...@gmail.com> #297
I've read today that the clipboard permission might be removed or granted only for system apps.
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
ja...@gmail.com <ja...@gmail.com> #298
I've read today that the clipboard permission might be removed or granted only for system apps.
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
sl...@gmail.com <sl...@gmail.com> #299
va...@gmail.com <va...@gmail.com> #300
mo...@gmail.com <mo...@gmail.com> #301
kh...@gmail.com <kh...@gmail.com> #302
db...@ausdbs.com <db...@ausdbs.com> #303
ja...@gmail.com <ja...@gmail.com> #304
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
ja...@gmail.com <ja...@gmail.com> #305
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
ja...@gmail.com <ja...@gmail.com> #306
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
ja...@gmail.com <ja...@gmail.com> #307
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
ja...@gmail.com <ja...@gmail.com> #308
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.
qr...@gmail.com <qr...@gmail.com> #309
علوش
qr...@gmail.com <qr...@gmail.com> #310
علؤش
qr...@gmail.com <qr...@gmail.com> #311
علؤش الفقير
jo...@gmail.com <jo...@gmail.com> #312
Jdbdkdbdlamsosndbals s
ka...@gmail.com <ka...@gmail.com> #313
to iPhone as my kids are starting to do, one by one, as Google keeps
violating their motto, "Do No Evil"...
---
Karl L. Pearson | karlplds@gmail.com
For more information:
---
On Fri, Mar 27, 2020 at 4:45 PM <buganizer-system@google.com> wrote:
dr...@gmail.com <dr...@gmail.com> #314
Please grant us the possibility, at least to decide whether we would like to intentionally grant access for the Clipboard apps to read data or not..
So the decision to grant access for the apps is up to us and not Google instead..
Please consider our inputs Google
Because we love Android for its limitless capabilities to help us as users to achieve the best in everything we do,, and Clipboard application is an excellent & helpful app to help us manage our copied text much better..
Thank You
ko...@gmail.com <ko...@gmail.com> #315
er...@gmail.com <er...@gmail.com> #316
gl...@gmail.com <gl...@gmail.com> #318
Options that could be provided in this case:
0. Disallow any communication/network permission and clipboard permision to be allowed together. So app with clipboard permission could read it, but not send anywhere
1. Grant this permission explicitly only through system settings interaction
2. Periodically notify user about apps using "not safe" permissions
3. Limit number of apps who can use this permission to one
4. Leave permission only in developer options
5. Leave possibility to activate through adb
6. Leave only for rooted users
Also I'm not sure if you are aware, but workarounds for many many apps around more and more restrictive permission model in Android, use Accessibility Service. So they are still breathing. Once you will start limiting that service, many of them will start to die.
Clipboard managers are the biggest productivity improvement in general mobile phone usage. Please reconsider reopening and providing some real solution.
ch...@googlemail.com <ch...@googlemail.com> #319
sa...@gmail.com <sa...@gmail.com> #320
ja...@atlas.cz <ja...@atlas.cz> #321
st...@gmail.com <st...@gmail.com> #322
od...@gmail.com <od...@gmail.com> #323
me...@gmail.com <me...@gmail.com> #324
si...@gmail.com <si...@gmail.com> #325
wh...@gmail.com <wh...@gmail.com> #326
ja...@gmail.com <ja...@gmail.com> #327
Focused ones is just the current app, right?
I've tested it and it seems as such.
The only workaround that I've found is to have an on-top view with foreground service, but this is too much to ask from the user. Plus what would you show the user...
ja...@gmail.com <ja...@gmail.com> #328
Focused ones is just the current app, right?
I've tested it and it seems as such.
The only workaround that I've found is to have an on-top view with foreground service, but this is too much to ask from the user. Plus what would you show the user...
ja...@gmail.com <ja...@gmail.com> #329
Focused ones is just the current app, right?
I've tested it and it seems as such.
The only workaround that I've found is to have an on-top view with foreground service, but this is too much to ask from the user. Plus what would you show the user...
ja...@gmail.com <ja...@gmail.com> #330
Focused ones is just the current app, right?
I've tested it and it seems as such.
The only workaround that I've found is to have an on-top view with foreground service, but this is too much to ask from the user. Plus what would you show the user...
zo...@gmail.com <zo...@gmail.com> #331
And here I was wondering why my friends have been switching to iphones.
al...@gmail.com <al...@gmail.com> #332
dt...@gmail.com <dt...@gmail.com> #333
pl...@gmail.com <pl...@gmail.com> #334
When I saw Clip Stack reported some moron blocked background clipboard access on Android 10, after Samsung A50 received an update, I imidietlly thought how can I downgrade to A9. If it was not for reseting it to factory setting, I would have returned it at once and never look back.
Even A9 is crap for not allowing me to store contact names with all the recorded calls I store on purpose so I can know what I promised to do or what info someone provided, and now this crap...
ja...@gmail.com <ja...@gmail.com> #335
ni...@gmail.com <ni...@gmail.com> #336
jh...@gmail.com <jh...@gmail.com> #337
e....@gmail.com <e....@gmail.com> #339
And i don't understand how this small app is creating issue.
ma...@gmail.com <ma...@gmail.com> #340
I've always used a clipboard manager on my Windows and Linux workstations so it was great to have it on my Android smartphone too.
Please Google bring back this feature!
di...@gmail.com <di...@gmail.com> #341
soon we have to create another linux based os for mobile devices
bl...@gmail.com <bl...@gmail.com> #342
I've lost count of how many clipboard manager applications I've purchased, but I'm currently running 4, and actively using 3 -- I have invested
more time and money in the Android ecosystem over the years compared to iOS, but this will make iPhones and iPads vastly more attractive
many thanks for your consideration=)
to...@gmail.com <to...@gmail.com> #343
mo...@gmail.com <mo...@gmail.com> #344
br...@gmail.com <br...@gmail.com> #345
ah...@gmail.com <ah...@gmail.com> #346
sa...@gmail.com <sa...@gmail.com> #347
bi...@gmail.com <bi...@gmail.com> #348
da...@gmail.com <da...@gmail.com> #349
ad...@gmail.com <ad...@gmail.com> #350
Clipboard manager is very useful. You could simply not allow the developers to copy content and not remove the clipboard managers from android.
Make it optional also for each user to allow or not copy content from developer.
ad...@gmail.com <ad...@gmail.com> #351
Soon if you continue like this, I will turn to Samsung Play Store. I hope you make clipboard managers available soon. Have you got any idea, how many hours these developers have spent to make these clipboard managers? And in a second you close all their efforts, by your immature decisions. Also have you got any idea how many hours the clipboard managers, save for the users? I am a research scientist and these applications save me a lot of hours.
Simply make optional for each user to choose that permission or simply do not allow developers to copy content from clipboards. You allow photos and videos to be viewed from developers and you thought the clipboard content to be a problem? Become logical.
im...@gmail.com <im...@gmail.com> #352
So please stop these kind of cheap ideas and think and after reviewing so something different.
Regards,
Atif
sc...@gmail.com <sc...@gmail.com> #353
wi...@gmail.com <wi...@gmail.com> #354
I expect to see Google step up and realize that taking away our clipboard managers does not please the majority of your ccustomers.
Please address this issue quickly and maka your loyal customers very happy.
wilsona1993@gmail.com
st...@gmail.com <st...@gmail.com> #355
They have proven over and over again that they do not care about their users.
It's almost enough to make one hold their nose and buy Apple products.
lb...@gmail.com <lb...@gmail.com> #356
I am truly against what Google did, but I don't think Google looks here anymore.
If you really want to make it a new one, press on "Create" and publish here a link to it.
ka...@gmail.com <ka...@gmail.com> #357
already.
The new bug would be to demand reinstatement of user-controlled clipboard
content and access.
IT IS OUR DATA! GIVE IT BACK NOW!!!
Is someone in this recipient list in a position to raise a new bug?
Do you agree or disagree?
Thank you for your consideration. I don't think Google, or anyone there
gives a damn about this bug. Or likely, this issue. Like all of the big
tech companies, they believe they are now God and their opinion is law....
This is one time I wish the government would step in and break them up into
their component parts so they might start listening to their customers.
I've raised this issue with both my senator and congressman, and they are
working nehind the scenes to get that on the road map, and moved forward.
---
Karl | karlplds@gmail.com
For more information:
---
On Sun, May 17, 2020 at 3:40 PM <buganizer-system@google.com> wrote:
pm...@gmail.com <pm...@gmail.com> #358
in...@gmail.com <in...@gmail.com> #359
ra...@gmail.com <ra...@gmail.com> #360
lj...@gmail.com <lj...@gmail.com> #361
Sent from Outlook Mobile<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Tuesday, May 26, 2020 3:22:00 AM
To: b-system+663841872@google.com <b-system+663841872@google.com>
Cc: ljohnson329@gmail.com <ljohnson329@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
ra...@gmail.com added
I need clip stack
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker<
status: Intended Behavior
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346<
duplicate issue: 128513320<
hotlist: [AOSP] assigned<
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
ab...@gmail.com <ab...@gmail.com> #362
lj...@gmail.com <lj...@gmail.com> #363
Sent from Outlook Mobile<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Wednesday, May 27, 2020 8:05:46 AM
To: b-system+663841872@google.com <b-system+663841872@google.com>
Cc: ljohnson329@gmail.com <ljohnson329@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
ab...@gmail.com added
F
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker<
status: Intended Behavior
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346<
duplicate issue: 128513320<
hotlist: [AOSP] assigned<
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
ka...@gmail.com <ka...@gmail.com> #364
keyboard.
On the top row are extra options, over of which is the 3 vertical buttons.
Tap that and one of the features is clipboard items. I've just discovered
it so don't know how extensive it's going to be. You can add items to the
clipboard. I see only my most recent cut item right now...
I hope this will become what the others were. Hopefully Google will
purchase one of the two I used to use, like they did with Waze...
---
Karl L. Pearson | karlplds@gmail.com
Pardon brevity or typos. Sent from my phone.
---
On Wed, May 27, 2020, 9:01 PM <buganizer-system@google.com> wrote:
al...@gmail.com <al...@gmail.com> #365
[Deleted User] <[Deleted User]> #366
cb...@gmail.com <cb...@gmail.com> #367
pa...@gmail.com <pa...@gmail.com> #368
je...@gmail.com <je...@gmail.com> #369
the other phones all the time as well as mine and Android apps department
of our phones needs to know that.
On Sun., Jun. 7, 2020, 2:22 p.m. , <buganizer-system@google.com> wrote:
be...@gmail.com <be...@gmail.com> #370
be...@gmail.com <be...@gmail.com> #371
The only reason for me to use android is because of my Freedom to use my choice of apps and if I can't any more than it's better for me to go Beck to Apple iPhone
jo...@gmail.com <jo...@gmail.com> #372
no...@gmail.com <no...@gmail.com> #373
Smartphones and tablets can only thrive productivity-wise with workarounda like multiple keyboards, split screens, UX improvements while sharing, additional contextual menus to bind common actions etc.
Please don't cripple the process and just add this as a separate permission apps should request.
ha...@gmx.de <ha...@gmx.de> #374
Means that when I want to copy multiple texts between apps I need to switch between apps for every single piece I want to copy!
la...@latsoudislaw.com <la...@latsoudislaw.com> #375
2FA is no longer fun....
hd...@gmail.com <hd...@gmail.com> #376
Couldn't believe that this is now blocked by default! Why not using a separate permission for the clipboard access?
Please give us users back the choice to allow who can access our clipboard.
cy...@gmail.com <cy...@gmail.com> #377
th...@gmail.com <th...@gmail.com> #378
hs...@gmail.com <hs...@gmail.com> #379
sh...@gmail.com <sh...@gmail.com> #380
mu...@gmail.com <mu...@gmail.com> #381
in...@gmail.com <in...@gmail.com> #382
I'm facing many problems due to it.
mo...@gmail.com <mo...@gmail.com> #383
ar...@gmail.com <ar...@gmail.com> #384
el...@gmail.com <el...@gmail.com> #385
to...@gmail.com <to...@gmail.com> #386
themselves to the buganizer-system@google.com
I would like to contribute further Details & Data relevant to the Issue I
reported. It's been an agonizing task. I would also would share logs and
discuss any relevant information not excluding my Google domain SECURITY,
Audits, investigations, and I assure these Databases are most relevant to
this and other similar bug reports.
Thank you,
Antonio Gonzalez Admin xtch.llc
tonyvg@xtvgtech.com
tonyvg2013@gmail.com
On Sun., Jul. 5, 2020, 4:32 a.m. , <buganizer-system@google.com> wrote:
ae...@gmail.com <ae...@gmail.com> #387
bl...@gmail.com <bl...@gmail.com> #388
an...@gmail.com <an...@gmail.com> #389
ba...@gmail.com <ba...@gmail.com> #390
Please stop blocking it.
lj...@gmail.com <lj...@gmail.com> #391
Get Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Tuesday, July 14, 2020 8:21:27 AM
To: b-system+663841872@google.com <b-system+663841872@google.com>
Cc: ljohnson329@gmail.com <ljohnson329@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
ba...@gmail.com added
This is a very helpful Al for me. Gh
Please stop blocking it.
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker<
status: Intended Behavior
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346<
duplicate issue: 128513320<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: Developer
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
hw...@gmail.com <hw...@gmail.com> #392
lj...@gmail.com <lj...@gmail.com> #393
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"Edwardian Script ITC";
panose-1:3 3 3 2 4 7 7 13 8 4;}
@font-face
{font-family:"Leelawadee UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Great!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Edwardian Script ITC"'>Lawrence Johnson<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Segoe UI Emoji",sans-serif'>📞</span>(863) 354-0329<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Segoe UI Emoji",sans-serif'>📞</span>(863) 852-5601<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Segoe UI Emoji",sans-serif'>📠</span>(973) 215-8605<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:buganizer-system@google.com">buganizer-system@google.com</a><br><b>Sent: </b>Wednesday, July 15, 2020 2:43 PM<br><b>To: </b><a href="mailto:b-system+663841872@google.com">b-system+663841872@google.com</a><br><b>Cc: </b><a href="mailto:ljohnson329@gmail.com">ljohnson329@gmail.com</a><br><b>Subject: </b>Re:
br...@gmail.com <br...@gmail.com> #394
wa...@gmail.com <wa...@gmail.com> #395
Don't take stuff away unless you are providing a replacement!
ja...@gmail.com <ja...@gmail.com> #396
ma...@gmail.com <ma...@gmail.com> #397
Do not remove it from the thursted app
I need it
ia...@gmail.com <ia...@gmail.com> #398
br...@gmail.com <br...@gmail.com> #399
wa...@gmail.com <wa...@gmail.com> #400
We are Google and we are brilliant!
m4...@gmail.com <m4...@gmail.com> #401
ca...@gmail.com <ca...@gmail.com> #402
jm...@gmail.com <jm...@gmail.com> #403
Google - you've lost a customer
If I'm going to live with these sorts of restrictions I'll go with Apple next time. Bye.
sc...@googlemail.com <sc...@googlemail.com> #404
You are making this once great system unusable!
To remove clipboard managers is ridiculous, as a user with short term memory problems, I rely on the clipboard to fill out forms etc!
How much more will you cripple android, I've already uninstalled a regularly used app because YOU removed it's access!!
Also another thing you've crippled is music remote control via Android wear watch, what is the point if you pause the music with the screen off, to have to turn on the screen before you can play again! - the whole point of the watch is to leave the phone in your pocket!!
PLEASE STOP MAKING ANDROID UNUSABLE!!
te...@hotmail.com <te...@hotmail.com> #405
Please please please sort it out 🙏🙏🙏
bl...@gmail.com <bl...@gmail.com> #406
Lots of people have brought up plenty of valid use cases for clipboard managers, and many of them have heavily invested in the Android ecosystem to enhance their productivity.
We all fail to see the issue with treating clipboard access in the background as advanced on-request-only permission. If the OS is as transparent as possible to the user of what an app does, and the user accepts the risks, then the OS should get out of the way. Things are supposed to be as simple as this. The higher levels of freedom are one of the main reasons that drive people to buy Android instead of Apple devices, you know. Also, there are many ways apps can access a user's personal information in the background - does it mean that any permission that can be used to access PIIs in the background will slowly be removed?
When I read many of the comments above I see an amazing community of developers and power users who want to be more involved in these macroscopic decisions, propose possible solutions and are struggling to be heard.
When I read your (sole) answer (and many other answers, or lack of them, on other issues and tickets) I only see an arrogant company of self-entitled jerks who take all the decisions without listening to their users, and probably dismiss the real issues of thousands of users who spent their money for your products in a single product meeting, without even bothering to provide any context outside of a telegraphic "it's for security reasons".
And I know that your arrogance and carelessness comes from the belief that both developers and users, despite all the barking, won't leave Android anyway, because of the lack of comparable alternatives out there - and those who do and decide to buy a PinePhone or install Ubuntu Touch are a negligible minority.
Let me just tell you that such a company of jerks doesn't deserve such a wonderful community. If you piss off the developers that build software for your platform too many times then those developers will start building an alternative - and that's how all monopolies usually collapse.
mo...@gmail.com <mo...@gmail.com> #407
ny...@gmail.com <ny...@gmail.com> #408
im...@gmail.com <im...@gmail.com> #409
گوگل پلس کا کباڑا کیا وہ اب اس اینڈرائیڈ کے درپے ہوئے ہوئے ہیں
ٹیکسٹ کوکاپی کرنے سے تعلیمی میدان میں بہت فائدہ اٹھایا گیا. مختلف ویب سائٹس اے ڈیٹا کاپی کرنا اور نوٹس بنانا یہ کلپ بورڈ مینجر جیسے فوائدبہت متاثر کن تھے .
gr...@gmail.com <gr...@gmail.com> #410
l3...@gmail.com <l3...@gmail.com> #411
And stop using google services, google has become the evil that they always told them selves to not be
re...@gmail.com <re...@gmail.com> #412
ca...@googlemail.com <ca...@googlemail.com> #413
mo...@gmail.com <mo...@gmail.com> #414
stopped working. Because their own app cannot read the clipboard as
well! This is crazy!
lb...@gmail.com <lb...@gmail.com> #415
Or make new ideas. For now it doesn't seem like Google read here anymore, for a long time.
sa...@gmail.com <sa...@gmail.com> #416
at...@gmail.com <at...@gmail.com> #417
le...@gmail.com <le...@gmail.com> #418
li...@gmail.com <li...@gmail.com> #419
You guys need to focus on getting the baseline functionality of your products down, and stop sprinting towards every half-formed idea. This company is turning to shit, and has been for a long time.
to...@gmail.com <to...@gmail.com> #420
st...@gmail.com <st...@gmail.com> #421
Google has no intention of fixing this issue for the users.
ru...@gmail.com <ru...@gmail.com> #422
jo...@gmail.com <jo...@gmail.com> #423
Even so that doesn't have to mean that you must render the most basic & fundamental functions of the OS! Security is good, but there's got to be a way to maintain security without disabling the clipboard- this is a crucial feature of an OS going back decades that has always been available to all the apps & processes running. Don't break that legacy for smart devices, that will really make them DUMB!
This is really such an obvious, blatant move by Google to limit & control what a user can do on a device he or she has already purchased. It's pathetic, shameful & disgusting!
tl...@fernandomiguel.net <tl...@fernandomiguel.net> #424
Keep in mind keyboards can do this function very easily.
Both gboard and SwiftKey have clipboard functionality
Give it a try
dr...@gmail.com <dr...@gmail.com> #425
Thanking you
ra...@gracelifechapel.co <ra...@gracelifechapel.co> #426
s7...@gmail.com <s7...@gmail.com> #427
br...@gmail.com <br...@gmail.com> #428
lj...@gmail.com <lj...@gmail.com> #429
Best regards,
Lawrence Johnson
📞(863) 354-0329
📞(863) 852-5601
📠(973) 215-8605
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Monday, September 7, 2020 11:53:01 PM
To: b-system+663841872@google.com <b-system+663841872@google.com>
Cc: ljohnson329@gmail.com <ljohnson329@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
br...@gmail.com added
Multiple clips in the clipboard please - I use this function all the time during sales
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker<
status: Intended Behavior
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346<
duplicate issue: 128513320<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: Developer
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
ge...@gmail.com <ge...@gmail.com> #430
during sales
On Thu, Sep 3, 2020, 10:23 AM <buganizer-system@google.com> wrote:
i....@gmail.com <i....@gmail.com> #431
That is the another proof.
cl...@gmail.com <cl...@gmail.com> #432
st...@gmail.com <st...@gmail.com> #433
They do not understand the consequences of their actions on the actual users.
They've decided that we are useless sheep who cannot make our own decision on this aspect of our security.
na...@gmail.com <na...@gmail.com> #434
n....@gmail.com <n....@gmail.com> #435
cl...@gmail.com <cl...@gmail.com> #436
em...@gmail.com <em...@gmail.com> #437
G.P.Esposito 70j
no...@gmail.com <no...@gmail.com> #438
no...@gmail.com <no...@gmail.com> #439
jr...@gmail.com <jr...@gmail.com> #440
ag...@gmail.com <ag...@gmail.com> #441
av...@gmail.com <av...@gmail.com> #442
Please give users the option to allow clipboard access for specific trusted apps, e.g. kdeconnect.That will help to make two factor authentication more widespread, i.e. it will improve overall security.
ma...@gmail.com <ma...@gmail.com> #443
re...@gmail.com <re...@gmail.com> #444
cr...@gmail.com <cr...@gmail.com> #445
bo...@gmail.com <bo...@gmail.com> #446
yr...@gmail.com <yr...@gmail.com> #447
jm...@gmail.com <jm...@gmail.com> #448
re...@gmail.com <re...@gmail.com> #449
i need to share the clipboard. pls give back this feature!
al...@gmail.com <al...@gmail.com> #450
ma...@googlemail.com <ma...@googlemail.com> #451
te...@gmail.com <te...@gmail.com> #452
to...@gmail.com <to...@gmail.com> #453
𝙂𝙤𝙤𝙜𝙡𝙚, 𝙖𝙨 𝙖 𝙡𝙤𝙣𝙜 𝙩𝙞𝙢𝙚 𝙘𝙪𝙨𝙩𝙤𝙢𝙚𝙧 𝙤𝙛 𝙮𝙤𝙪𝙧𝙨, 𝙄 𝙖𝙢 𝙪𝙥𝙨𝙚𝙩 𝙖𝙣𝙙 𝙖𝙥𝙥𝙖𝙡𝙡𝙚𝙙 𝙗𝙮 𝙮𝙤𝙪𝙧 𝙘𝙝𝙤𝙞𝙘𝙚 𝙩𝙤 𝙗𝙖𝙣 𝙘𝙡𝙞𝙥𝙗𝙤𝙖𝙧𝙙 𝙢𝙖𝙣𝙖𝙜𝙚𝙧𝙨. 𝙄 𝙧𝙚𝙡𝙮 𝙤𝙣 𝙩𝙝𝙚 𝙆𝙞𝙣𝙜𝙨𝙤𝙛𝙩 𝙘𝙡𝙞𝙥𝙗𝙤𝙖𝙧𝙙 𝙖𝙥𝙥𝙡𝙞𝙘𝙖𝙩𝙞𝙤𝙣 𝙛𝙤𝙧 𝙨𝙘𝙝𝙤𝙤𝙡 𝙖𝙣𝙙 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨. 𝙔𝙤𝙪𝙧 𝙢𝙖𝙠𝙞𝙣𝙜 𝙩𝙝𝙚𝙨𝙚 𝙖𝙥𝙥𝙡𝙞𝙘𝙖𝙩𝙞𝙤𝙣𝙨 𝙤𝙗𝙨𝙤𝙡𝙚𝙩𝙚 𝙞𝙨 𝙣𝙚𝙖𝙧𝙡𝙮 𝙞𝙡𝙡𝙚𝙜𝙖𝙡. 𝙄𝙛 𝙨𝙤𝙢𝙚𝙤𝙣𝙚 𝙞𝙨 𝙣𝙤𝙩 𝙙𝙤𝙣𝙚, 𝙄 𝙬𝙞𝙡𝙡 𝙛𝙞𝙡𝙚 𝙖𝙣 𝙞𝙣𝙟𝙪𝙣𝙘𝙩𝙞𝙤𝙣.
pj...@gmail.com <pj...@gmail.com> #454
If you do not intend to put a native clipboard manager in your OS do not remove the option for those of us who want/ need one. We know the risks and if we decide to take them then it's on us. This kind of "upgrade" sure doesn't feel like one.
ba...@gmail.com <ba...@gmail.com> #455
Maybe it's time to join the Apple family????
wo...@gmail.com <wo...@gmail.com> #456
ENOUGH OF YOUR SPY & TRACKING CRIMES.
I DO WISH GOOGLE WOULD BE DISMANTLED MORE THEN MICROSOFT WAS.
It's criminal monopoly imposing the users being controled and spied on them for making money on their meta data passed to those who pay for it.
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app.
Do not remove this, and do not grant this ability only to system apps, google criminals!
wo...@gmail.com <wo...@gmail.com> #457
google must be dismantled into damn pieces.. much more than microsoft was when bill gates tried his monopoly system implement..
too much power to the corporate criminals, so that is to google..
i'm happy to see that the US government finally began its investigation on google's monopoly..
i hope google will be done, and other smaller companies will cooperate n give us better with more freedom service..
it's outrageous to see criminal monopoly behavior of googl gangster corporation
va...@gmail.com <va...@gmail.com> #458
al...@gmail.com <al...@gmail.com> #459
As a user of various clipboard manager apps, I really hope Google will find a way to allow apps to continue to have clipboard access.
st...@gmail.com <st...@gmail.com> #460
be obvious. Give us our clipboards back.
On Fri, Nov 6, 2020, 2:16 PM <buganizer-system@google.com> wrote:
jn...@gmail.com <jn...@gmail.com> #461
Please bring back clipboard management permissions ASAP.
jm...@gmail.com <jm...@gmail.com> #462
-------- Original message --------From: buganizer-system@google.com Date: 2020-11-08 10:23 p.m. (GMT-05:00) To: b-system+1742600667@google.com Cc: jmacknmo@gmail.com Subject: Re:
Changed
jn...@gmail.com added
I've long used an earlier tablet that had an enhanced clipboard manager as one of the pre-installed apps. I came to rely on the features of this app as essential. Now I find with the new tablet I have purchased, running Android 10, does not allow any kind of enhanced clipboard manager.Please bring back clipboard management permissions ASAP.
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker
status: Intended Behavior
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346
duplicate issue: 128513320, 128582282, 137878823, 151168542, 162347586
hotlist: [AOSP] assigned, Platform
retention: Component default
ReportedBy: Developer
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.
cb...@gmail.com <cb...@gmail.com> #463
st...@gmail.com <st...@gmail.com> #464
ridiculous.
On Sun, Nov 8, 2020, 8:07 PM <buganizer-system@google.com> wrote:
sv...@gmail.com <sv...@gmail.com> #465
te...@gmail.com <te...@gmail.com> #466
go...@gmail.com <go...@gmail.com> #467
la...@gmail.com <la...@gmail.com> #468
st...@gmail.com <st...@gmail.com> #469
to only care about control, power and the dollar. They know that their
decision on this issue is wrongheaded. And they choose to ignore the users.
Confidence is low that they will ever admit they were wrong and do
something about it.
On Sun, Nov 15, 2020, 3:24 PM <buganizer-system@google.com> wrote:
ag...@gmail.com <ag...@gmail.com> #470
jo...@gmail.com <jo...@gmail.com> #471
si...@gmail.com <si...@gmail.com> #472
I understand that security plays a large factor in this decision but I rely on clipboard for my new vocabulary list
st...@gmail.com <st...@gmail.com> #473
in the corporate or billionaire class.
That was sarcasm.
On Mon, Nov 30, 2020, 12:07 PM <buganizer-system@google.com> wrote:
co...@gmail.com <co...@gmail.com> #474
ob...@gmail.com <ob...@gmail.com> #475
tn...@gmail.com <tn...@gmail.com> #476
ni...@gmail.com <ni...@gmail.com> #477
ni...@gmail.com <ni...@gmail.com> #478
ni...@gmail.com <ni...@gmail.com> #479
lo...@gmail.com <lo...@gmail.com> #480
dr...@gmail.com <dr...@gmail.com> #481
pg...@gmail.com <pg...@gmail.com> #482
jf...@gmail.com <jf...@gmail.com> #483
4s...@gmail.com <4s...@gmail.com> #484
bz...@gmail.com <bz...@gmail.com> #485
jm...@gmail.com <jm...@gmail.com> #486
On Tue., Dec. 22, 2020, 8:35 a.m. , <buganizer-system@google.com> wrote:
ws...@gmail.com <ws...@gmail.com> #487
> Status: Won't Fix (Intended behavior)
r....@gmail.com <r....@gmail.com> #488
bu...@gmail.com <bu...@gmail.com> #489
ch...@gmail.com <ch...@gmail.com> #490
ch...@gmail.com <ch...@gmail.com> #491
vi...@gmail.com <vi...@gmail.com> #492
ma...@gmail.com <ma...@gmail.com> #493
ro...@gmail.com <ro...@gmail.com> #494
dj...@gmail.com <dj...@gmail.com> #495
I have an idea for an app concerned with privacy. Letting my app access clipboard data isn't necessary for my app to function as intended. However granting my app Clipboard access will yield much better user experience. I also plan to make my app open source so people can see for themselves that I don't collect data. I appreciate the security concern but there is a way to mitigate the security problem in and issue. Make accessing the clipboard a permission just like storage and location. Unless Google doesn't want competetors collecting data.
jo...@gmail.com <jo...@gmail.com> #496
when you go to the box where you enter the code, it automatically shows it
above the keyboard like the word suggestions. I'm curious if you would be
able to access those codes using the clipboard permission and thus why
Google removed the permission from non-standard apps?
On Fri, Jan 8, 2021, 9:29 PM <buganizer-system@google.com> wrote:
vk...@gmail.com <vk...@gmail.com> #497
st...@gmail.com <st...@gmail.com> #498
But it sure would be easier if the clipboard was automatically synchronized.
an...@gmail.com <an...@gmail.com> #499
Please fix this.
jn...@gmail.com <jn...@gmail.com> #500
If there are subtle security issues you are still working to resolve, at least please provide a more feature rich standard clipboard system that includes a clip tray while you are working on security concerns.
wa...@gmail.com <wa...@gmail.com> #501
Android.
If there are subtle security issues you are still working to resolve, at
least please provide a more feature rich standard clipboard system that
includes a clip tray while you are working on security concerns.
On Sun, Jan 17, 2021, 8:52 PM <buganizer-system@google.com> wrote:
wa...@gmail.com <wa...@gmail.com> #502
br...@gmail.com <br...@gmail.com> #503
ch...@gmail.com <ch...@gmail.com> #504
se...@gmail.com <se...@gmail.com> #505
Its so annoying
ca...@gmail.com <ca...@gmail.com> #506
ma...@gmail.com <ma...@gmail.com> #507
Thanks for any consideration.
ws...@gmail.com <ws...@gmail.com> #508
ch...@gmail.com <ch...@gmail.com> #509
Bring it back!
ne...@gmail.com <ne...@gmail.com> #510
jo...@gmail.com <jo...@gmail.com> #511
st...@gmail.com <st...@gmail.com> #512
On Sun, Jan 31, 2021, 1:06 PM <buganizer-system@google.com> wrote:
ed...@gmail.com <ed...@gmail.com> #513
rule is the new fashion. Vote for Trump ❓
On Monday, January 18, 2021, <buganizer-system@google.com> wrote:
sa...@gmail.com <sa...@gmail.com> #514
bu...@gmail.com <bu...@gmail.com> #515
dj...@gmail.com <dj...@gmail.com> #516
ro...@gmail.com <ro...@gmail.com> #517
On Tue, Feb 23, 2021, 1:06 PM <buganizer-system@google.com> wrote:
al...@gmail.com <al...@gmail.com> #518
Because it is a very usefull function to have on a smartphone.
If Google restricts more and more functions in the Android UI,
people will go over to other alternatives.
su...@gmail.com <su...@gmail.com> #519
ks...@gmail.com <ks...@gmail.com> #520
ai...@gmail.com <ai...@gmail.com> #521
on...@gmail.com <on...@gmail.com> #522
ro...@gmail.com <ro...@gmail.com> #523
deserves an ACK.
It's here, in case the citation gets stripped:
20-odd years ago, I viewed google as a valuable, educational search
resource. Gradually, steadily, increasingly, that objective usefulness
has been diluted, eroded, and corrupted by greed for wealth, greed for
power, IMO. Top search results are bought. "Help" is comprised of
cheap, "community" billboards such as this one. There is no interaction
with functionaries, save the occasional condescending snark that,
probably, serves the compensation calculus for devs having a bad day.
If you were on fire, Sergey wouldn't piss on you unless there was a
nickel in it for him.
Worse, unmitigated success and greed has brought us election meddling,
censorship, erasure of any thought, person, or (historical) fact that
does not serve the NARRATIVE. All of Big Tech seem to be of the same
mind. Critical thinking, productive discourse, individuality, the
rights and freedoms enumerated and protected by the Constitution, the
Rule of Law, itself, all are rapidly being destroyed by a malicious
megalomania.
Wake up.
Rolf Pedersen
On 3/4/21 5:35 AM, buganizer-system@google.com wrote:
ra...@gmail.com <ra...@gmail.com> #524
Why is it too hard for us to have articles of discussion in a clipboard?
re...@gmail.com <re...@gmail.com> #525
Don't be EVIL google ... And do NOT become APPLE...if we wanted these kind of futures removed we could get stupid toys like iphone... For the illusion of privacy u killed many useful apps...shame! Shame!
ol...@gmail.com <ol...@gmail.com> #526
[Deleted User] <[Deleted User]> #527
So many play store apps exist because you guys never really seem to understand how people use their phones... There's a difference between "nice to have" task specific apps and critical functionality. We get why you do things like kill call recording, and now this, all premised on security, a good thing when it does its job in prevents rogue apps from stealing data.. but you punish us by breaking these critical functionality apps that you won't build yourself.
AJ...@hotmail.co.uk <AJ...@hotmail.co.uk> #528
ma...@gmail.com <ma...@gmail.com> #529
su...@gmail.com <su...@gmail.com> #530
cl...@gmail.com <cl...@gmail.com> #531
bo...@gmail.com <bo...@gmail.com> #532
al...@gmail.com <al...@gmail.com> #533
ro...@gmail.com <ro...@gmail.com> #534
st...@gmail.com <st...@gmail.com> #535
chances that Google gave a crap about how we feel about clipboards. And
nothing has changed my opinion.
On Thu, Apr 8, 2021, 1:58 PM <buganizer-system@google.com> wrote:
ko...@gmail.com <ko...@gmail.com> #536
st...@gmail.com <st...@gmail.com> #537
se...@gmail.com <se...@gmail.com> #538
su...@gmail.com <su...@gmail.com> #539
1l...@gmail.com <1l...@gmail.com> #540
adb -d shell appops set com.catchingnow.tinyclipboardmanager SYSTEM_ALERT_WINDOW allow; adb -d shell pm grant com.catchingnow.tinyclipboardmanager android.permission.READ_LOGS; adb shell am force-stop com.catchingnow.tinyclipboardmanager;
How am i supposed to do this on a computer if thr app is on a mobile. You haven't provided instructions on how to do 5his to get your app to work again?
lb...@gmail.com <lb...@gmail.com> #541
I wonder
wo...@gmail.com <wo...@gmail.com> #542
our choices.
Quite the same as it's been attacking our civil liberties and free speech.
It's high time to begin eliminating the traitors of our freedoms!
On Wed, Apr 14, 2021, 16:14 <buganizer-system@google.com> wrote:
zw...@email.de <zw...@email.de> #543
The only thing we can do to point google to this issue is to open new issues with the request to fix this.
All of them have to be reviewed by a google worker. They will be marked as duplicate to this issue, but at least they are forced to look at this issue.
The more of these duplicates have to be marked, the more google will have to have a look at this issue.
So everyone: Write new issues with this request, not only once, but regularly. I don't know if this can change anything, but it's worth a try.
Sorry google, but simply setting this to "won't fix" despite all the remaining problems and all the good comments of an alternate behaviour is a bad thing. You have to reconsider your opinion.
ka...@gmail.com <ka...@gmail.com> #544
most recent update of the Android OS, I have to say that Google has handled
this fairly decently in the native Pixel clipboard.
If you click on the paste clipboard in the line of characters above the
keyboard, you'll notice that your recent history of copies are there. If
you long-press one of those items, you have the option to pin that item and
it will stay in your clipboard indefinitely. Anything you don't pin will
expire within a few days keeping the clipboard clean.
Frankly, I like that option more than either of the two clipboard managers
I've used in the past because it takes no extra space on my phone and also
works very well.
I hope this doesn't make me horribly unpopular, but I applaud Google for
how they have filled a gap for me, at least, and encourage you to get to
know how they have done it. If you have a non-google phone, you need to
talk to them about using the native clipboard functionality as provided by
Google. It really is quite nice.
---
Karl L. Pearson | karlplds@gmail.com
Pardon brevity or typos. Sent from my phone.
---
On Wed, Apr 14, 2021, 10:37 AM <buganizer-system@google.com> wrote:
ar...@gmail.com <ar...@gmail.com> #545
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Wednesday, April 14, 2021 5:46:23 PM
To: b-system+-1204855705@google.com <b-system+-1204855705@google.com>
Cc: arro1834@gmail.com <arro1834@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
ka...@gmail.com added
I wish to give some input on this. As the user of a pixel phone with the
most recent update of the Android OS, I have to say that Google has handled
this fairly decently in the native Pixel clipboard.
If you click on the paste clipboard in the line of characters above the
keyboard, you'll notice that your recent history of copies are there. If
you long-press one of those items, you have the option to pin that item and
it will stay in your clipboard indefinitely. Anything you don't pin will
expire within a few days keeping the clipboard clean.
Frankly, I like that option more than either of the two clipboard managers
I've used in the past because it takes no extra space on my phone and also
works very well.
I hope this doesn't make me horribly unpopular, but I applaud Google for
how they have filled a gap for me, at least, and encourage you to get to
know how they have done it. If you have a non-google phone, you need to
talk to them about using the native clipboard functionality as provided by
Google. It really is quite nice.
---
Karl L. Pearson | karlplds@gmail.com<mailto:karlplds@gmail.com>
Pardon brevity or typos. Sent from my phone.
---
On Wed, Apr 14, 2021, 10:37 AM <buganizer-system@google.com<mailto:buganizer-system@google.com>> wrote:
_______________________________
Reference Info: 123461156 Request: Do not remove clipboard permission and do not let only system apps have it
component: Android Public Tracker<
status: Intended Behavior
reporter: lb...@gmail.com
assignee: cc...@google.com
cc: da...@google.com, lb...@gmail.com
type: Feature Request
priority: P1
severity: S3
blocked by: 123500346<
duplicate issue: 128513320<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: Developer
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
lb...@gmail.com <lb...@gmail.com> #546
ag...@gmail.com <ag...@gmail.com> #547
mu...@gmail.com <mu...@gmail.com> #548
sh...@gmail.com <sh...@gmail.com> #549
Is this America and we are capable of making our own decisions or is this a fucking dictatorship and you decide what we can and cannot use on devices WE pay for???? Seriously, you need to let go of the all powerful is complex and allow people to CHOOSE wtf they want to use and not use. Or better yet since you feel the need to have your hand in EVERYTHING provide the damn services yourselves that you keep fckin taking away from consumers as well as from developers. Has it occured to you if you offered an equivalent clipboard option people wouldn't feel the need to seek it elsewhere??? This is the shit that makes me people go elsewhere or start seeking and using illegal softwares and shit, hence defeating the purpose of your bullshit ass so called "safety precautions". God damn, let it go. You don't run the fckin world.
ro...@gmail.com <ro...@gmail.com> #550
Godgle, CCP, et al are working on it. Give em time. Or, stand in defiance.
dr...@gmail.com <dr...@gmail.com> #551
Gboard sucks
jo...@gmail.com <jo...@gmail.com> #552
It s tune to leave the dining ski
ba...@gmail.com <ba...@gmail.com> #553
ma...@gmail.com <ma...@gmail.com> #554
adb -d shell pm grant com.catchingnow.tinyclipboardmanager android.permission.READ_LOGS;
adb shell am force-stop com.catchingnow.tinyclipboardmanager;
ne...@fartbeans.com <ne...@fartbeans.com> #555
oa...@gmail.com <oa...@gmail.com> #556
Clipboard history is a valuable resource for every user.
Appart for many uses, it can also work as rescue information at sometimes.
I cannot imagine working without clipboard manager.
bl...@gmail.com <bl...@gmail.com> #557
mo...@gmail.com <mo...@gmail.com> #558
sa...@gmail.com <sa...@gmail.com> #559
na...@gmail.com <na...@gmail.com> #560
The whole point of an open source OS like Android, is for 3rd party dev's to fill in the gaps missed by the OS itself. Hell, you already scrape 15-30% of the revenue off the backs of devs, let them operate.
I get there are bad actors, however "blanket banning" is not the answer. Permissions are permissions. Find a better way. Stop killing 3rd party dev, UX, and ultimately yourselves in the process.
lo...@gmail.com <lo...@gmail.com> #561
ro...@gmail.com <ro...@gmail.com> #562
na...@gmail.com na...@gmail.com #560Jun 27, 2021 04:07PM Re-enable clipboard access and stop banning 3rd party app functionality! This is anti-trust! The whole point of an open source OS like Android, is for 3rd party dev's to fill in the gaps missed by the OS itself. Hell, you already scrape 15-30% of the revenue off the backs of devs, let them operate. I get there are bad actors, however "blanket banning" is not the answer. Permissions are permissions. Find a better way. Stop killing 3rd party dev, UX, and ultimately yourselves in the process.
This hit the nail on the head! Same concern with Phone Call Recording and the accessibility blitz that about got Tasker removed (with little to no communication with devs, I might add).
po...@gmx.de <po...@gmx.de> #563
st...@gmail.com <st...@gmail.com> #564
On Thu, Jul 8, 2021, 12:38 PM <buganizer-system@google.com> wrote:
jb...@gmail.com <jb...@gmail.com> #565
zo...@gmail.com <zo...@gmail.com> #566
aj...@gmail.com <aj...@gmail.com> #567
eg...@gmail.com <eg...@gmail.com> #568
re...@gmail.com <re...@gmail.com> #569
ny...@gmail.com <ny...@gmail.com> #570
Have always had the Clipstack widget on my screen.
I do not copy to it.
I SHARE to clipstack.
Works perfect.I can open the actual app and export everything, delete entries,edit my list or indiv.entry......etc.
Works wonderful.
Kind of a bandaid instead of a tourniquet.
But life is like that.
If you need any other help on this, just post, happy to help fine tune.
fr...@gmail.com <fr...@gmail.com> #571
Fr. Tom Frink, SJ
P.O. Box 10000, PMB 538
Saipan, MP 96950-8900
---------------------
Google Voice: (978) 361-2715
Skype: Frinkt1
WhatsApp: Fr. Tom Frink, SJ
Facebook: Tom Frink, SJ
Be a Jesuit! <
On Sun, Jul 25, 2021 at 11:39 PM <buganizer-system@google.com> wrote:
ba...@gmail.com <ba...@gmail.com> #572
ne...@gmail.com <ne...@gmail.com> #573
sw...@outlook.com <sw...@outlook.com> #574
li...@gmail.com <li...@gmail.com> #575
( . Y . )
8===D.
de...@gmail.com <de...@gmail.com> #576
To anyone who wants clipboard monitoring functionality back can install this app from
fa...@hotmail.com <fa...@hotmail.com>
fe...@gmail.com <fe...@gmail.com> #577
ma...@gmail.com <ma...@gmail.com> #578
wa...@gmail.com <wa...@gmail.com> #579
wa...@gmail.com <wa...@gmail.com> #580
wa...@gmail.com <wa...@gmail.com> #581
ki...@gmail.com <ki...@gmail.com> #582
lj...@gmail.com <lj...@gmail.com> #583
ms...@gmail.com <ms...@gmail.com> #584
st...@googlemail.com <st...@googlemail.com> #585
Add my name to the list of dissatisfied Google users at having this feature affected.
thank you
lj...@gmail.com <lj...@gmail.com> #586
ze...@gmail.com <ze...@gmail.com> #587
Add my name to the list of dissatisfied Google users at having this feature affected.
thank you
co...@gmail.com <co...@gmail.com> #588
ANYBODY
On Sat, Aug 28, 2021, 7:54 PM <buganizer-system@google.com> wrote:
yi...@gmail.com <yi...@gmail.com> #589
Clipboard restriction sucks.
ma...@gmail.com <ma...@gmail.com> #590
I need to copy paste my answers everytime i gave feedback on my email, my bussines account or anything else.
I use Clip Stack app to reuse common answers and mow its impossible. What a heck!
wo...@gmail.com <wo...@gmail.com> #591
I just keep my best not to have anything to do with that corporate
prostitute of traitors to us the people.
Millions of others like me will be there when Google faces criminal
charges, and we'll all vote for the death of Google gangster corporation
and those who rule that crime family.
No begging for anything!
Just move away from that stinky garbage google.
Move to other OSs, platforms, search engines, free speech space, etc., and
wait for the time to pay back to those technowhore Luciferian corporate
bitches.
On Sat, Sep 18, 2021, 19:29 <buganizer-system@google.com> wrote:
va...@yagati.com <va...@yagati.com> #592
as...@gmail.com <as...@gmail.com> #593
lo...@gmail.com <lo...@gmail.com> #594
ja...@gmail.com <ja...@gmail.com> #595
I'm going to call this move regarding the clipboard (and can also be applied to other things that others have shared) 'secupidity', or security by stupidity. When removing a feature to make things more secure, what really happens is that the device becomes less useful since now in order to complete tasks more steps are needed if at all possible. I'm totally in favor of increasing security, hell who wants calculators that need the location to work?, and that if you not grant the permission they don't work at all?. So yes, perfectly in favor of increasing security, but that is done through permissions, maybe permissions that the app can not automatically request or even now the status of it (so they can not stop working if the user doesn't grant it); but in the end the user has to have the control over it.
I have read several people complaining in this thread about the apps they use no longer working and some of them even stating that they will move to iOS. I try to avoid Apple because of the closed ecosystem, but I agree with the views in this post Google Android is looking more and more like a closed system; so totally understand their point.
As of me, just starting with a new phone, and when I started to use one of my core apps, KDEConnect; I see that the most basic thing, copying from the cellphone to the PC does not work, just great. I already considered a problem the high customizable UIs from different manufacturers on top of Android to be an issue (I was for 5+ with the same phone in plain Android just because I didn't want to have customizations on top of Adnroid), but seems like even plain Android itself is going backwards. At this rate, I suspect my next phone will be in the cheaper segment and one that has good support for LinageOS or any other variation that doesn't impose a gated system.
Final thoughts, I would like to encourage to take this kind of changes very seriously and proceed with extreme caution when removing features; even if this clipboard support gets restored in a next version (fingers crossed), due to the short support from manufacturers (from 1 to maybe 3 yeras?) that means that many devices won't receive the fix and thus will remain providing subpar experiences to their owners (in this front seems more likely that an iOS user might have more lack since Apple at least supports their devices for a somewhat reasonable time). So yeah secupidity in its fullest.
pa...@gmail.com <pa...@gmail.com> #596
kh...@gmail.com <kh...@gmail.com>
ze...@gmail.com <ze...@gmail.com> #597
wl...@gmail.com <wl...@gmail.com> #598
mf...@att.net <mf...@att.net> #599
ea...@gmail.com <ea...@gmail.com> #600
ms...@gmail.com <ms...@gmail.com> #601
re...@gmail.com <re...@gmail.com> #602
Still broken in Android 12.
he...@gmail.com <he...@gmail.com> #603
I also have my phone rooted. I don't know if that has anything to do with it.
ba...@gmail.com <ba...@gmail.com> #604
my...@gmail.com <my...@gmail.com> #605
[Deleted User] <[Deleted User]> #606
Android 9 - blocked recording
Android 10 - blocked clipboard
looks like AOSP with root will be on my device from now on ...
gm...@gmail.com <gm...@gmail.com> #607
di...@gmail.com <di...@gmail.com> #608
Yes, Google Please allow this app to proceed as intended.
de...@gmail.com <de...@gmail.com> #609
This may look like a promotion but is intended as a help to those who are looking to gain this functionality back.
You can use XClipper -
It is a clipboard manager app with lots of features & works for Android 10+ devices that require no root or any kind of adb commands to enable clipboard monitoring again. It works by you to first enable an Accessibility service where it recognizes some touch events that might consider as a copy event & saves the required text data into the local database.
It also has a Windows companion app you can
Also, the app is open source and hosted on Github -
no...@gmail.com <no...@gmail.com> #610
no...@gmail.com <no...@gmail.com> #611
rb...@gmail.com <rb...@gmail.com> #612
zu...@gmail.com <zu...@gmail.com> #613
lu...@gmail.com <lu...@gmail.com> #614
cl...@gmail.com <cl...@gmail.com> #615
ol...@reply.io <ol...@reply.io> #616
av...@gmail.com <av...@gmail.com> #617
lu...@gmail.com <lu...@gmail.com> #618
tr...@gmail.com <tr...@gmail.com> #619
I can't use the clipboard now to create new contacts in my phone from data I've copied, such as, email address, first & last name, etc, simple stuff that use to work. I'd rather roll back my device's OS to the previous version than not have what should be simple access to my clipboard. What the Hell!
Fix it, PLEASE!
[Deleted User] <[Deleted User]> #620
ar...@gmail.com <ar...@gmail.com> #621
pe...@gmail.com <pe...@gmail.com> #622
wa...@gmail.com <wa...@gmail.com> #623
ri...@gmail.com <ri...@gmail.com> #624
de...@gmail.com <de...@gmail.com> #625
I need my Clipstack app working again!
ki...@gmail.com <ki...@gmail.com> #626
Clipboard managers area important !!
as...@gmail.com <as...@gmail.com> #627
mz...@gmail.com <mz...@gmail.com> #628
fa...@gmail.com <fa...@gmail.com> #629
[Deleted User] <[Deleted User]> #630
sa...@gmail.com <sa...@gmail.com> #631
Link says "trial" so I dunno if it'll stay free. And to use clipboard you have to drag down and click the persistent notification or click the floating dot that at 50% opacity level, which kinda defeats the purpose depending on how you look at it (imo I don't think so but everyone's different).
ab...@gmail.com <ab...@gmail.com> #632
Solve it Google
ja...@gmail.com <ja...@gmail.com> #633
go...@gmail.com <go...@gmail.com> #634
We paid hafthy amount to purchase high end Android device just to see that Android at it's own wish removes application permission without even informing or consulting their users.
It's really shameful on Google part.
I request Google to restore the clipboard app's background subc capabilities a soon as possible.
fr...@gmail.com <fr...@gmail.com> #635
hi...@gmail.com <hi...@gmail.com> #636
I added a video from last night and today of me testing it out, below and a third video on how to go to the settings to set it, but a trdl: On the sidebar on the S22, open it, then at the bottom click the gear button which opens up the sidebar settings, and from there you click "Clipboard". Then, if you're fine with seeing the clipboard thingie there, whenever you copy, cut or screeshot, the clipboard contents will be THERE ready for you to copy again if needed.
NOTE: In the first video I briefly speak and added English subs: I have a slight accent and speak more articulately in my other language so...
How to enable the clipboard sidebar on S22.mp4 -
Works with 3rd party keyboards 1.mp4 -
Works with 3rd party keyboards 2.mp4 -
ki...@gmail.com <ki...@gmail.com> #637
af...@gmail.com <af...@gmail.com> #638
sl...@gmail.com <sl...@gmail.com> #639
I wanna thank you Clipstack for bringing me right here where feedback is taken for granted.
Next i want to remind google people that we need a mobile version of the issue tracker. That'll speed up the process for free as far as i'm concerned.
Next is the fact we need to collect the same data google collect about us and have access to it and mess around with it because it is ours. This is gune cost some heavy duty nightwork. But we need that too
You see the thing is ... you people are not synchronized with the process tree for the AI to learn from and trust based on where it will land in the future 😉
Be Quick. Be Nice
Bbye
ma...@tobischaefer.com <ma...@tobischaefer.com> #640
kr...@gmail.com <kr...@gmail.com> #641
99...@gmail.com <99...@gmail.com> #642
What a joke
no...@gmail.com <no...@gmail.com> #643
ph...@gmail.com <ph...@gmail.com> #644
[Deleted User] <[Deleted User]> #645
I can understand closing loopholes, but not giving *US* the choice on what to do with *OUR* devices is arrogant and offensive.
Android had a great development community because of it's openness. It's no coincidence the Unix hackers are giving up. "Send patches?" your chromeos team says... Why should we?
My CPU monitoring widget was really handy. You killed that (the required access to /proc could easily have been made into a permission). Now clipboard actions? Obviously your roadmap is to completely turn android into a dumb OS for dumb users, but you can do that without impeding things for those who want more than dumb.
What next? 'developers menu', adb? (of course adb has gotten more restrictive since the early days already)
pa...@btinternet.com <pa...@btinternet.com> #646
wo...@gmail.com <wo...@gmail.com> #647
Google doesn't give a damn!
Google has become nothing, but a fascist controller and supporter for
fascist dictatorial regimes.
This is exactly how corporations work on the orders of the state
governments aiming to enslave their nations.
I stopped using Google services as much as I could, and I've been learning
how to degoogle any possible devices that still are using these despicable
Google services.
They're also other mobile OSs!
They're getting more and more popular.
Death to tyranny!
We're still fee people!
On Sun, Sep 4, 2022, 19:39 <buganizer-system@google.com> wrote:
wo...@gmail.com <wo...@gmail.com> #648
Like yesterday, actually.
Everybody can see why the G would've done this, it's so transparent to most.
al...@gmail.com <al...@gmail.com> #649
ra...@gmail.com <ra...@gmail.com> #650
ra...@gmail.com <ra...@gmail.com> #651
mr...@gmail.com <mr...@gmail.com> #652
jb...@gmail.com <jb...@gmail.com> #653
mn...@gmail.com <mn...@gmail.com> #654
pi...@gmail.com <pi...@gmail.com> #655
n3...@gmail.com <n3...@gmail.com> #656
st...@gmail.com <st...@gmail.com> #657
They have ignored the users for years. They have no intention of doing
right by us.
On Mon, Oct 31, 2022, 7:23 AM <buganizer-system@google.com> wrote:
no...@gmail.com <no...@gmail.com> #658
da...@gmail.com <da...@gmail.com> #659
st...@gmail.com <st...@gmail.com> #660
On Fri, Dec 16, 2022, 7:19 PM <buganizer-system@google.com> wrote:
de...@gmail.com <de...@gmail.com> #661
My phone is my most important business tool, and this is app (tiny clipboard) is a critical part of my workflow :-(
iv...@gmail.com <iv...@gmail.com> #662
It would be so easy and clean to let the user decide if an app may access the clipboard or not.
Google, please just solve it. Most certainly it would be regarded as a strength of yours to admit the mistake and just fix it.
th...@stellantis.com <th...@stellantis.com> #663
na...@gmail.com <na...@gmail.com> #664
si...@gmail.com <si...@gmail.com> #665
Let people choose. Secondly, if you want to block a thing, better provide a free better alternative and prove its better and then let people choose
zi...@gmail.com <zi...@gmail.com> #666
On 11, the version 1.8.1 or earlier, using accessibility settings, do not work reliably, contrary to what someone here reported. Same for Xclipper. On Android 13 people say adb will be needed after every reboot. Sad.
I could use an app where selected text would be **silently** shared to a list, like it goes to Xclipper. But XClipper should add an option to define separators when merging clips.
Anyway, shame on Google to remove this feature.
ju...@gmail.com <ju...@gmail.com> #667
st...@gmail.com <st...@gmail.com> #668
situation by the intrepid engineers on the team. It's almost as if the
corporation doesn't care about the customer. Yeah that's a lot of sarcasm.
On Mon, Jul 10, 2023, 1:32 PM <buganizer-system@google.com> wrote:
bo...@gmail.com <bo...@gmail.com> #669
mp...@gmail.com <mp...@gmail.com> #670
Blocking apps from using establish pathways and methods, is not a good approach; rather there could be a much better and secure way. (Frankly, I have never understood why it was not done from the very beginning).
From the start to gain usefull access to one's device, one had to root one's device, which is stupid. (This also shows a lack of foresight on the part of the Android developers)
Rather than running and unsecured and vunerable Rooted device, the use and adoption of the Secured Linux command and technique of the use of su do and sudo (it should have been implemented, from the beginging).
Breaking someone else products and efforts, to secure Android is scurrilous. Rather by the implementation of the linux sudo or su do commands (as a standard practice and procedure) and the use of a app like Remote ADB Shell (no addional computer required) it would allow such (beloved and usefull) apps to still be used with little effort on the parts of the user and app creator.
Another, thing to consider is the marketing opportunities that would be openend to Alphabet.
Right now, users (with out rooting) can only backup thier apps (not apps data) and some of their library content, and when they are forced to do a factory reset, they lose mostly everything. (Which actually means in reality, the device is very insecured).
I imagine that the inabillity to do a true backup and recovery, (considering all the grief and cost, that this results in), could become the bases of a class action.
But, hey what do I know.
Thanks.
2023/08/21 12:21 Hrs EDT
28...@gmail.com <28...@gmail.com> #671
ss...@gmail.com <ss...@gmail.com> #672
towards the developer on this issue. That said, I'd like to understand the.
Reasoning for a blanket restriction as opposed to the restriction Or ban.
for developers Who abuse it. Understanding the security risks. I would have
to know the numbers on the breaches Do to this.
Vulnerability. Thanks for any light. You can shed on this Issue.
On Wed, Feb 28, 2024, 1:02 PM <buganizer-system@google.com> wrote:
el...@gmail.com <el...@gmail.com> #673
el...@gmail.com <el...@gmail.com> #674
rh...@gmail.com <rh...@gmail.com> #675
wo...@gmail.com <wo...@gmail.com> #676
shit about anybody's rights or thoughts.
I'm happy to see that corporate scumbag in the courts on the way of
dismantling it eventually.
Millions of people look to other opinions like total de- Google of their
phones, so do I.
I'm sick and tired of that communist Google tracking and spying on me for
years now.
On Mon, Jul 10, 2023, 16:32 <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #677
Ok
ni...@gmail.com <ni...@gmail.com> #678
ni...@gmail.com <ni...@gmail.com> #679
ns...@gmail.com <ns...@gmail.com> #680
ni...@gmail.com <ni...@gmail.com> #681
to use Microsoft extra spyware Phone Link which is granted this permission
by Samsung as a preinstalled app), haven't switched to Linux yet). I
already have clipboard history. On the keyboard I'm typing this on. Futo
Keyboard. Yep, it's great. And I update all my apps using Obtainium so it
can even update stuff with just apks in GitHub releases without needing an
F-Droid repo (through it can also act as an F-Droid client).
On Thu, Oct 3, 2024, 8:08 PM <buganizer-system@google.com> wrote:
Description
Such a thing will break a lot of apps that rely on this permission, including apps that their whole purpose is to manage copied clipboard content and present us a nicer UI to choose from recent clipboard items, such as this app:
Please do not remove this, and do not grant this ability only to system apps.
It's not just damaging developers. It's damaging users, who will now have much less choice of what to use.