IssueTracker

[Comment deleted]

Oh, and I'm seeing this on both the emulator and a Galaxy Nexus. Simply launching an activity that does something like this is enough to reproduce:

ClipboardManager manager = (ClipboardManager) getSystemService(CLIPBOARD_SERVICE);
manager.addPrimaryClipChangedListener(new ClipboardManager.OnPrimaryClipChangedListener() {
    @Override
    public void onPrimaryClipChanged() { }
});

Could you please give full steps to reproduce, including the app to run that is causing it?  The crash here shows it failing when setting the clipboard, which generally works; I need to to be able to see more specifically what this particular app is doing.

Also the API demo "Clipboard/Data Types" does use addPrimaryClipChangedListener() and doesn't have this problem, and the stack crawl originally shown doesn't have anything about addPrimaryClipChangedListener() in it, so there is some information I am missing.

Thanks!

What application are you trying to copy text from after adding a listener? I'm copying text from other apps like Messaging or Search and not the application the listener itself is from.

I have no idea if I'm on the right track, but my personal hypothesis is that this is caused because AppOpsService's uid verification is trying to verify the uid for the *listener's* application but the calling uid (Binder.getCallingUid()) is that of the application the text is being copied from. This leads to the permission check for UPDATE_APP_OPS_STATS which will obviously fail.

The code snippet I posted is basically the full "application" you should be able to reproduce this with. So this should be it:

1. Create a new Android app in $IDE_OF_CHOICE

2. Add a new OnPrimaryClipChangedListener in the onCreate of that application's activity -- it's contents don't matter

3. Install and launch the activity

4. Copy text from any other application

5. Crash.

I'm experiencing similar bug. for example, go to message app, tap and hold a message and copy text. the app will crash (the copy will save in clipboard though)

I have the same problem, I have an app that starts observing clipboard and since I updated to 4.3 that app crashes with similar exception to this from the first post (android.permission.UPDATE_APP_OPS_STATS)
then every other app that tries to copy something crashes with this exception:

W/dalvikvm(5446): threadid=1: thread exiting with uncaught exception (group=0x419c0700)
W/clipboard(431): Exception:
W/clipboard(431): java.lang.IllegalStateException: beginBroadcast() called while already in a broadcast
W/clipboard(431):       at android.os.RemoteCallbackList.beginBroadcast(RemoteCallbackList.java:229)
W/clipboard(431):       at com.android.server.ClipboardService.setPrimaryClip(ClipboardService.java:165)
W/clipboard(431):       at android.content.IClipboard$Stub.onTransact(IClipboard.java:62)
W/clipboard(431):       at com.android.server.ClipboardService.onTransact(ClipboardService.java:123)
W/clipboard(431):       at android.os.Binder.execTransact(Binder.java:388)
W/clipboard(431):       at dalvik.system.NativeStart.run(Native Method)
E/AndroidRuntime(5446): FATAL EXCEPTION: main
E/AndroidRuntime(5446): java.lang.IllegalStateException: beginBroadcast() called while already in a broadcast
E/AndroidRuntime(5446):         at android.os.Parcel.readException(Parcel.java:1439)
E/AndroidRuntime(5446):         at android.os.Parcel.readException(Parcel.java:1385)
E/AndroidRuntime(5446):         at android.content.IClipboard$Stub$Proxy.setPrimaryClip(IClipboard.java:171)
E/AndroidRuntime(5446):         at android.content.ClipboardManager.setPrimaryClip(ClipboardManager.java:125)
E/AndroidRuntime(5446):         at android.content.ClipboardManager.setText(ClipboardManager.java:208)
E/AndroidRuntime(5446):         at com.google.android.apps.authenticator.AuthenticatorActivity.onContextItemSelected(AuthenticatorActivity.java:927)
E/AndroidRuntime(5446):         at com.google.android.apps.authenticator.AuthenticatorActivity.access$200(AuthenticatorActivity.java:73)
E/AndroidRuntime(5446):         at com.google.android.apps.authenticator.AuthenticatorActivity$3.onActionItemClicked(AuthenticatorActivity.java:353)
E/AndroidRuntime(5446):         at android.widget.AbsListView$MultiChoiceModeWrapper.onActionItemClicked(AbsListView.java:6058)
E/AndroidRuntime(5446):         at com.android.internal.policy.impl.PhoneWindow$DecorView$ActionModeCallbackWrapper.onActionItemClicked(PhoneWindow.java:2569)
E/AndroidRuntime(5446):         at com.android.internal.app.ActionBarImpl$ActionModeImpl.onMenuItemSelected(ActionBarImpl.java:962)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:735)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:152)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:874)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.ActionMenuView.invokeItem(ActionMenuView.java:547)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.ActionMenuItemView.onClick(ActionMenuItemView.java:115)
E/AndroidRuntime(5446):         at android.view.View.performClick(View.java:4240)
E/AndroidRuntime(5446):         at android.view.View$PerformClick.run(View.java:17721)
E/AndroidRuntime(5446):         at android.os.Handler.handleCallback(Handler.java:730)
E/AndroidRuntime(5446):         at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime(5446):         at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(5446):         at android.app.ActivityThread.main(ActivityThread.java:5103)
E/AndroidRuntime(5446):         at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(5446):         at java.lang.reflect.Method.invoke(Method.java:525)
E/AndroidRuntime(5446):         at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
E/AndroidRuntime(5446):         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime(5446):         at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(431):   Force finishing activity com.google.android.apps.authenticator2/com.google.android.apps.authenticator.AuthenticatorActivity

or similar. Once I disabled clipboard monitoring app and rebooted Nexus 7 the copying worked for sometime.

[Comment deleted]

Yes, It's happening to my NEXUS 4 also. Once you launch any app monitoring clipboard then copying in any app crashes the app.

i've noticed that even if app crashes, copying still works and I can paste copied data. So I've changed code in my app to:

public static void setClipData(Context context, String text) {
        try {
                ClipboardManager clipboard = (ClipboardManager) context.getSystemService(Context.CLIPBOARD_SERVICE);
                ClipData clip = ClipData.newPlainText("", text);
                clipboard.setPrimaryClip(clip);
                Toast.makeText(context.getApplicationContext(), R.string.url_copied, Toast.LENGTH_SHORT).show();
        } catch (Exception e) {
                Toast.makeText(context.getApplicationContext(), R.string.url_copying_error, Toast.LENGTH_LONG).show();
                e.printStackTrace();
        }
}

But copying from contextual action bar still crashes and observing clipboard doesn't work at all. I think this is because of http://www.androidpolice.com/2013/07/25/app-ops-android-4-3s-hidden-app-permission-manager-control-permissions-for-individual-apps/ :)

I face the same issue on my Galaxy Nexus. I have an app "Clipper" (clipboard manager) running in background. The moment some text is copied from any app, that particular app would crash. After uninstalling app "Clipper" (a clipboard manager), the crashes stopped. I had to reboot after uninstalling.

Could someone *please* post complete steps to reproduce.  This means either:

(1) Attaching a complete code project that can be built and run to cause the problem to happen, or
(2) A pointer to an app on the play store to install with steps to reproduce in that app.

Thanks.

Diana Install https://play.google.com/store/apps/details?id=org.rojekti.clipper set it to have it monitoring in the notifaction bar then try copying anything from anywhere ;)

As I mentioned here[1], it happens on pretty much any app, Google's included, in example:

1. Open YouTube (I have version 4.5.17).
2. Open a video (any video).
3. Overflow menu > Copy URL

Same with GMail:

1. Open GMail (I have version 4.5.2-714156).
2. Open a conversation
3. Long press on text to action bar mode to appear
4. Tap on copy action


1. https://plus.google.com/103638111379552295023/posts/hZMgjN2qSUU

Diane,

I've attached a sample application. Like I mentioned before, it's just a blank activity that attaches a listener to the clipboard service.

Once you've built, installed and run this application and its activity, simply open any other application and copy something. For example, open Google Search, type anything in the search bar, copy it and a crash will occur.

The important part here is that the copying must occur in _another application_ separate from the listener. This causes the uid mismatch in AppOpsService's verifyIncomingUid and throws an exception.

Alternatively, install the Clipper application linked in #13, complete the tutorial so that it registers a listener, and copy from any other application. A crash will occur.

[Comment deleted]

After clearing Google Services Framework 3 times I got the 4.2.1 1.1MB update, announced as version 4.2...
Google is definitely not working with pride and determination.
December returned to the calendar and Google Music shows the folders in a kind of 3D way with a cute slide effect.
What I really wanted them to fix is untouched. :mad:
Shame on you Google. Wifi together with bluetooth is essential for someone to take advantage of their tablet or phone.
My Nexus 7 32GB is eagerly awaiting for Google's paid devs to FIX this Monster bug. Tried Skype after updating and I almost went deaf with the distortion and cuts in the sound.
So PRETTY PLEASE WITH SUGAR ON TOP release 4.2.2 ASAP before I and many other people decide to RMA their devices.
I won't root to downgrade. It's up to Google to fix this without asking users to take unnecessary risks.
Godspeed Google.

Thank you for reading.

Basically it happens with any app monitoring clipboard. 100% reproducible and very much easy to repro.

1) install https://play.google.com/store/apps/details?id=net.daum.android.dictionary
2) launch the app
3) launch or switch to other app(Chrome, Gmail, ''') which has texts can be copied to clipboard
4) copy text then the app crashes.

Thanks for the help in reproducing!  We now have a fix.

I am also having this issue on the n
New Nexus 7 (2013)

Can confirm that my Nexus 7 2013 has this bug. Every time I copy the app being copied from crashes. Google or non-violent, makes no difference.

I am also having this issue on my Nexus 4 after the 4.3 update. I use the clipboard very often, the only way I find to solve the issue is to do a factory reset (Settings -> Backup & Reset -> Factory data reset)

Folks, there is no need to comment further. :)  This bug has been marked as fixed, as noted.

Not fixed on my Nexus 7 2013. Where is the note?

The bug may be fixed on some internal development version of Android, but in reality there are tens of thousands of affected devices out there right now. I am starting to get bad ratings over this bug and the clipboard is rendered unusable for many people.

When can we expect device updates to correct the issue? Are we talking about days, weeks or months? Will other device manufacturers ship the same broken code with their own updates?

Still experiencing this bug.

Bug still happening on my nexus 10.  

I have the same problem. Apps (Chrome, GMail, Phone) crashes after copying text. But after crash the text still in clipboard, and I can paste it. Nexus 4.

Still happening on my Nexus 7

Could someone shut down comments on this, please? :)
It's been marked as fixed, just not released yet.

@#30 nat.abbo...@gmail.com
and @ all googlers

shut down comments? why? Imho thousands of comments and complaints should pile here.

Breaking Copy and Paste is breaking one of the most basic properties of any computer system. It worked before, it worked when i bought the phone/tablet, and I want it back! ASAP

hack...@android.com said there is a fix. What is the problem to release the fix? Why is the OTA, that not all users have received yet, updated asap? Why not a second OTA (and that must be a really small one) to all 4.3 users? At the time of writing only NEXUS users are affected.
Do all the (e.g.) Samsung S4 users get the same bug when they receive the 4.3 update as veeti.paananen asked in post #25, or is it fixed there?

You broke it, you fix it, AND YOU SHALL DEPLOY IT ASAP!

But you don't care, right? Average time with google is 1.1 years I read this week. Fixing bugs is not in favour of your careers. Better working on new fancy features that the management ist focussing on. No older code gurus that live with the code and can maintain them.

tl;dr : Don`t call a bug fixed, before the fix is deployed

P.S.: Please excuse my bad english, I am not an native speaker and I not amused at this very moment

I'm not sure you understand how code works, or what this site is.

This is a developer issue tracker, for developers, not users who don't actually know what goes on behind the scenes.

You aren't helping anything or anyone by complaining, you're just spamming. Google reports that the issue is fixed, it just needs to be pushed to devices. Presumably, they're testing internally first, to ensure the fix is safe for a larger staged rollout.

They are deploying it ASAP. You know what that means, I assume? "As Soon As Possible." That doesn't mean immediately, it means once it is *possible* for them to safely deploy it.

tl;dr: stop spamming, you aren't helpful.

>I'm not sure you understand how code works, or what this site is.

I coded 6502 assembly on the Commodore C64 when you were still in the goolies (a word I learned right now) of your father.

>This is a developer issue tracker, for developers, not users who don't actually know >what goes on behind the scenes.

Hey insider, tell me, what goes on behind the scenes? Perhaps you can tell me why the new Motorola does not debut with 4.3 but 4.2 instead. Fights amongst googlers I heared?

>You aren't helping anything or anyone by complaining, you're just spamming. Google >reports that the issue is fixed, it just needs to be pushed to devices. Presumably, >they're testing internally first, to ensure the fix is safe for a larger staged >rollout.

Question: When should I report that I have a fix? When I think that I have a fix or when I tested that fix, so that it it worth to be called a fix?

>They are deploying it ASAP. You know what that means, I assume? "As Soon As >Possible." That doesn't mean immediately, it means once it is *possible* for them to >safely deploy it.

Yeah, I know the definition of ASAP, I also know snafu and fubar, both come in to my mind when I think of android development in the past year (-> and YES, this is spamming, but i fed the troll)
 
>tl;dr: stop spamming, you aren't helpful.

perhaps not helpful fixing this bug, but highlighting the bad situation android development faces right now. There are several (imho mission critical) bugs open for YEARS. But no one cares, new features, new features, thas's what they call for.

> Presumably, they're testing internally first, to ensure the fix is safe for a larger staged rollout.

Well, if that is the case, then how come you rolled out the 4.3 without fixing this bug? Clipboard management is such a basic part of the OS. It makes one wonder about the quality of the so called "internal testing".

BTW, aren't we, the so called "non-developers", supposed to report bugs here? Then don't we have a say on issues when we face one?

And please don't proclaim "Fixed", just saying "Fixed" gives a wrong idea. You could have rather said "Noted/Confirmed, will be fixed in future release", or something to that effect.

My 2p.

Just received an email about this very issue with one of my apps and 4.3. Yep definitely crashes. Hope Google rolls out a fix soon.

I have the same problem with Clipboard Monitoring on BlueDict.
Android 4.3

How lame is that!

also having this problem

I understand this issue has been marked as fixed but even after the recent update to Build JWR66Y I'm still having the clipboard bug, from what I've read online this minor update to 4.3 was supposed to fix the bug.  Not the case so far :(

My Galaxy Nexus got updated to the new build this morning. Its just been a few times that I have tested it, and apparantely this issue seems to be resolved. If other users could share their experience, it could help others.

FYI, I am using "ClipNote" app for Clipboard monitoring. I haven't tested with any other Clipboard monitoring app.

I've just installed the newest update to android 4.3, which reportedly contained the fix, but there is no change to the crash, and the copy-paste features still fail to function!

Why is the fix only on the 4.3_r2.2 branch and not on the 4.3_r1.1 branch? This seems to mean that the fix is only going out to the 2013 Nexus 7. Please push out this update to all Nexus devices.

As mentioned in my previous post, I am using Galaxy Nexus and there are no crashes on copying from any app (tested with GoSMS, WhatsApp, Gmail) after the update to JWR66Y, with "ClipNote" running in the background. But it seems that other users are experiencing crashes still.

Attaching 2 screenshots. First one shows the "About phone" screen and the second one shows the clippings that I copied without any crashes since last few days and the recent ones today.

I have a Nexus 4, Build JWR66Y I too am having the clipboard bug.

Oli

Got update. Still crash.

I think the fix is waiting for Apple approval:)))

Updated Nexus 7. Still clashes on copy.

Sent from my Android Nexus 7

Jim Flanagan
Cell:  773 396-4638
Beaver Island                    Chicago
219.448.2109                    773.463.5494
37700 Font View Ct.          4439 N.  California
Beaver Island, MI.              Chicago, IL.

I have a similar issue when sending a notification on a user's Galaxy Nexus running 4.3. Not sure how to reproduce this, I only see the crash with no user info. Here is he crash log:

java.lang.SecurityException: uid 10157 does not have android.permission.UPDATE_APP_OPS_STATS.
        at android.os.Parcel.readException(Parcel.java:1431)
        at android.os.Parcel.readException(Parcel.java:1385)
        at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:380)
        at android.app.NotificationManager.notify(NotificationManager.java:136)
        at android.app.NotificationManager.notify(NotificationManager.java:109)
        at com.levelup.touiteur.BackgroundTouitLoader$1.run(BackgroundTouitLoader.java:274)
        at android.os.Handler.handleCallback(Handler.java:730)
        at android.os.Handler.dispatchMessage(Handler.java:92)
        at android.os.Looper.loop(Looper.java:137)
        at android.app.ActivityThread.main(ActivityThread.java:5306)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:525)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:743)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:559)
        at dalvik.system.NativeStart.main(Native Method)

Updated to the most recent build.

My Nexus 4 can now copy from apps without crashing.
My Nexus 7 (1st gen) still crashes when copying.

Trying to track down the app that it triggering the crashing so I can uninstall it for the time being until the "fix" is fixed.

I can confirm, that

NotificationManager notificationManager = (NotificationManager)
...
context.getSystemService(Context.NOTIFICATION_SERVICE);
notificationManager.notify();

let GT-I9300, GT-I9505 crash with

.lang.SecurityException: uid 10140 does not have android.permission.UPDATE_APP_OPS_STATS

Nexus 4, Build JWR66Y. I can confirm that the problem persists basically with any app from which you want to copy and paste, let it be a google app or a third party app.

This type of bugs are unacceptable, start paying attention to details.

Me too: JWR66Y on Nexus 4, still crashes on copy.

Had this issue on my Play version of HTC ONE for 3 weeks now.  Last night I took a leap of faith and updated my Nexus 7 from a 4.3 to a newer 4.3 JWR66Y and also broken what was perfectly fine.

This is not a minor obscure function.  Its been marked fixed for over a month now and as of last night the bad update that WILL break your copy function is still being pushed OTA.  

Please be sensitive of the timing of this issue.  Nexus 7 2 already has issues, and the big Apple event is just next week.  This doesn't exactly bond well....

Hey google, you know why i bought an android phone in the first place?  Copy and paste.  I kid you not.  Please bump the priority on pushing this out and stop saying it's fixed until it's in our hands - until it's 'out' your job isn't done.  Thanks

Can anyone @ google confirm whether or not we'll see this fix before 4.4 KitKat?  Is that the cause of the delay in deployment?

I strongly hope the fix is released as a part of Android 4.3, not in KitKat
as soon as possible because:

* This issue is too serious. We don't want our app to be crashed by other
apps.
* We need to wait KitKat upgrade which will not be provided from carriers,
or provided after a year from the launch of KitKat
 2013/09/05 6:57 <android@googlecode.com>:

I can verify this with Nexus 4 and lastest Android update. First I thought that my qrcode scanner app is broken. But I was not: Because it copied the scanned text automatically to the clipboard the scanner app crashed after every scan. Other app with barcode or qrcode scanner like the Amazon app don't crash because they do not copy to clipboard.

Same issue on my Nexus 7, Android 4.3. The simple way fix it without ROOT:
1. find out what app have clipboard listening requirements, uninstall it.
2. reboot your device,that's all.

This clipboard issue appear on my device after i installed a app called Select Translator to it.

How exactly is one meant to determine what app has a clipboard listener installed?

"How exactly is one meant to determine what app has a clipboard listener installed?"

For non-techies like me that would be very useful to know. It might be that I can temporarily live without whatever app or widget is triggering this. Any advice on hunting down the culprit without wiping everything?

"It might be that I can temporarily live without whatever app or widget is triggering this."

Most common would be any type of downloader app that watches for video/audio links.  In most of these apps, you can disable the clipboard watcher.

"Most common would be any type of downloader app that watches for video/audio links.  In most of these apps, you can disable the clipboard watcher."

Thanks very much for that. Disabling sounds much better than uninstalling. I'll experiment with my podcatcher.

"Most common would be any type of downloader app that watches for video/audio links."

I have zero apps of this nature

For me the culprit turned out to be the otherwise excellent ConvertIt! Pro Unit Converter. It has a "Copy-Convert" function which evidently watches the clipboard. You can turn this off in the settings.

This problem is repeatably triggered for me by EverClip 1.0.8. If I uninstall that app and reboot, the problem goes away. If I reinstall that app, the problem reappears. Hopefully this helps some of the people encountering this issue.

Why is it Google claim that this is fixed and the issue is closed and they're now ignoring this thread.. but they still haven't released an update for their nexus devices?

Don't you guys communicate between departments?  Isn't there some mechanism by which you can flag this fix as critical for the end user experience and it should be pushed asap instead of having to wait for the next bundle of updates?  Or is it a case that this mechanism DOES exist but you just don't feel it's urgent enough to warrant it because you're not directly affected by it like we are?

Hey guys i've met this problem for serveral days.

I found someone said ClipNote may cause crash and app that watches links may cause crash too, so i disabled my Mdict's auto watch feature then restart my phone.

It worked! Hope this'll be helpful.

my problem is that the clipboard doesn't even open up in chrome. no crash but can't past into chrome.

Nexus 4, Build JWR66Y same issue.  Any app.  Copying crashes the app you're copying in, but the data is successfully copied to the clipboard.

When will be fix released? Still having this issue on nexus 7 2012, Ver. 4.3 kernel build from 11Jun.

just find the culprit app, for me it was the app 'CONVERTIT!' , once I
disabled the copy - conversion feature found in the settings the issue was
fixed.

From what I can see, currently builds JSS15Q (android-4.3_r2.2) JSS15R (android-4.3_r2.3) have the fix, the rest of the 4.3 builds don't. See: http://source.android.com/source/build-numbers.html

In my case the app "convertIt" causes my copy&paste crashes. I disabled the option "copy conversation" and my problem was solved.

wow... The thread started in July... and Google/android are not able to deploy a fix yet...

It s u c k s.

I don't understand why it is not released yet. JWR66Y which I have on Nexus 7 and Galaxy Nexus are still affected with this bug and according to https://developers.google.com/android/nexus/images Nexus 4 and 10 are also affected :/

I can confirm. I've this bug on Nexus 4. JWR66Y.
It's very disappointing. Please Google fix it.
No way to copy text in no applications.

I'm starting to think they are just going to put the fix in 4.4. I certainly hope not but it has been quite a while so that seems to make sense.

Nexus 7 here, broken as well.

It only started recently, so I think I'm going to start going through apps and uninstalling a bunch.

Assuming that's the Google approved fix right now...

Whenever I use the copy or cut function in any application, it crashes the application.
However, the content is still in the clipboard and I can paste it afterwards without an issue.

LG Nexus 4
Androd 4.3
Kernel version: 3.4.0-perf-gf43c3d9
Build Number: JWR66Y

this is a major issue and no matter what there are still a few millions with Jelly bean, i dont understand why most of the Apps didnt release a patched version for the meanwhile, the patch is very simple, you should add Catch when listening to the clipboard , the pasted value will be waiting in the CLIP_BOARD var.

i did it for my app and although it is a major bug the simple fix managed to make me forget and forgive to Google. :)

Listener is not fired and after using it system apps and contextual action bar will crash. That is my code, and I never see this log msg.

@Override
public void onCreate() {
        super.onCreate();
        try {
                ClipboardManager clipBoard = (ClipboardManager) getSystemService(CLIPBOARD_SERVICE);
                clipBoard.addPrimaryClipChangedListener(this);
        } catch (Exception e) {
                e.printStackTrace();
        }
}

@Override
public void onPrimaryClipChanged() {
        Log.d("ClipboardMonitorService", "onPrimaryClipChanged");
        readClipboard();
}

Since you won't update Galaxy Nexus to 4.4 as I suspected... then please at least release 4.3.1 to Galaxy Nexus because a lot of ppl will still use it.

Hi there,

In the beginning I could also paste the text from clipboard even after the app having force closed, but I am in a quite inconvenient situation now, as I can't copy ANYTHING by now.

Excuse me, but is this right? It is like I'd have a car with only 3 tyres. Omg..

Nexus 4 4.3 JWR66Y Unrooted, Locked, full factory phone..

Guys, the issue solved itself as it seems.

I was just about to do a factory reset (backed up everything to PC), then before I would reset the thing, I tried copying again and it worked o_0

Is this issue the same as a problem I'm having here?:

I am using Tasker to collect a Voice Search %CLIP, however when I run Voice Search in "Free form" nothing is sent to the clipboard... Is this a problem with the clipboard or a problem with Voice Search?

Any help would be much appreciated... I want my phone to be able to record speech to text in the clinical setting to avoid transmission of diseases from patient to patient and aid my charting.

Hello,
I inform this happens also on Samsung Galaxy Tab 2 10 1.

[Comment deleted]

Happening on Nexus 7

[Comment deleted]

This looks to be resolved in Android 4.4

It is now working fine again on my Nexus 5 with Android 4.4.

Copy clip doesn't cause a crash, rather it just fails to work.  In older Android versions it was a simple long press that would result in the capture and manipulation of whatever you were trying to copy.  Since I got my Galaxy S4 a month ago (and whatever version of Android it was on until the other day when it went to ver 4.3) long pressing only causes a pop up of paste and clipboard.  EPIC FAIL!!!!!!!!

[Comment deleted]

"For me the culprit turned out to be the otherwise excellent ConvertIt! Pro Unit Converter. It has a "Copy-Convert" function which evidently watches the clipboard. You can turn this off in the settings."

ConvertIt! Is the problem for me! Deactivated...reboot...solved! Thxxxx!!!!

[Comment deleted]

Not crashing anymore after removing convertit ... Thank capuanof...@gmail.com

Indeed, the ConvertIt app was the culprit. After removing the app from my phone and rebooting, the problem went away.

Did someone contact the ConvertIt developers to let them know?

Does anyone know a way to programmatically check whether a device is potentially affected by this bug?  I want to warn the user before setting the primary clip listener, but only if necessary.  I know that some 4.3 devices are not affected.

NotificationManager issue mentioned in #48 and #50 happens also on Galaxy S IV:

Device: SCH-R970
API Level: 18
Build: JSS15J.R970TYUEMK2

So no "fix" 4 gnex ryt?

Steps to reproduce this bug after Chrome for Android has crashed before.

1. Just copy any text. See if there's a prompt saying "Failed to copy to clipboard."

2. If yes, just copy the URL. It will definitely crash.

Always happen when I'm copy/pasting news articles to my forums every single time.

A lot of #48 and #50 in my app's Google Play crash reports.

I guess APP_OPS was not intended to be a public facing feature, but who's going to explain that to my users?

java.lang.SecurityException: uid 10210 does not have android.permission.UPDATE_APP_OPS_STATS.
at android.os.Parcel.readException(Parcel.java:1431)
at android.os.Parcel.readException(Parcel.java:1385)
at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:338)
at android.app.NotificationManager.notify(NotificationManager.java:139)
at android.app.NotificationManager.notify(NotificationManager.java:112)

Devices:

Galaxy Note 10.1 2014 Edition
Galaxy Note3 (hlte)
Galaxy Note3 (hlteatt)
Galaxy Note3 (hltevzw)
Galaxy Note3 (hltecan)
Galaxy S4 (ja3g)
Galaxy S4 (jfltevzw)
Galaxy S4 (jflte)
Galaxy S4 (jfltetmo)

All with 4.3

Think I see a pattern here.

How much longer will Google allow Samsung to screw up the operating system with its "enhancements" and "modifications?"

This has been creating enormous pain for third party developers, for years, and clearly the end users are affected too ("my new expensive Android phone keeps crashing"), no?

If the CTS is not a suitable match for the "creativity" of Samsung's firmware developers, maybe Google needs to have a few people just for this: 1) testing 2) reviewing source code 3) whatever else is necessary to improve the situation?

I just bought an HP Slate 21 Pro for which the latest Android is 4.3 and it is afflected with the same bug. Once this is triggered I have to reboot to safely copy again.

I expect the chance that HP will provide an OS update is negliable. Is there a way or an app I can run as a user to find out which app has added a listener so a user can work around the problem?

[Comment deleted]

[Comment deleted]

[Comment deleted]

any update on this ?

What's happen to my mobile?

The problem is still present on Galaxy nexus 4.3.


BUT, I do not use clipboard listener. note that I do use OnEditorActionListener.


the bug happen when opening the clipboard context menu (long press). It happen only once in a while, not always.

stack:

java.lang.SecurityException: uid 10069 does not have android.permission.UPDATE_APP_OPS_STATS.
at android.os.Parcel.readException(Parcel.java:1431)
at android.os.Parcel.readException(Parcel.java:1385)
at android.content.IClipboard$Stub$Proxy.setPrimaryClip(IClipboard.java:171)
at android.content.ClipboardManager.setPrimaryClip(ClipboardManager.java:125)
at android.widget.TextView.setPrimaryClip(TextView.java:8466)
at android.widget.TextView.onTextContextMenuItem(TextView.java:8221)
at android.widget.Editor$SelectionActionModeCallback.onActionItemClicked(Editor.java:2818)
at com.android.internal.policy.impl.PhoneWindow$DecorView$ActionModeCallbackWrapper.onActionItemClicked(PhoneWindow.java:2569)
at com.android.internal.view.StandaloneActionMode.onMenuItemSelected(StandaloneActionMode.java:133)
at com.android.internal.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:735)
at com.android.internal.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:152)
at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:874)
at com.android.internal.view.menu.ActionMenuView.invokeItem(ActionMenuView.java:547)
at com.android.internal.view.menu.ActionMenuItemView.onClick(ActionMenuItemView.java:115)
at android.view.View.performClick(View.java:4240)
at android.view.View$PerformClick.run(View.java:17721)
at android.os.Handler.handleCallback(Handler.java:730)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5103)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)

Issue still current, occurring on HP Slatebook X2.

Stock 4.2.1 on Nexus 4 here. Notice it most in my car with Chimes (Blink 182 =)

Still a noticeable tinny sound with stock 4.2.2 on both my Galaxy Nexus and Nexus 7. Never encountered it with 4.1.

#110...not what I wanted to hear. Is there still compression in the upper frequencies on 4.2.2.

#110.... bad news!  I was really looking forward to 4.2.2 to have this resolved.  Seriously Google?  

I don't think this is as highly reported simply because people probably don't know what good quality sound is.  It's seriously frustrating.

#110 - i'm gonna flip my shit if this isn't resolved in 4.2.2.  I was hoping all I had to do was wait for CM to merge 4.2.2 to fix this issue.  I'm hoping you're mistaken!

I tested with a bluetooth adapter and the Nexus 7 with 4.2.2 in my car.  I can confirm that this issue still exists.  It is not as bad as before, but it is still there.

Unfortunately, distortion in the high frequencies has not been fixed with 4.2.2. Sound quality still sounds like shit. This is really upsetting. I miss streaming music through Bluetooth. I also have to ask, how have Google engineers not noticed the poor sound quality? It used to sound fantastic before.

I guess I am stuck on 4.1.2 a little longer. Come on Google!

Has anyone upgraded to 4.2.2 and noticed an improvement?

[Comment deleted]

Can verify that Bluetooth still sounds distorted in 4.2.2. Don't notice an improvement.

Updated to 4.2.2 yesterday, and everything seems to have been fixed.

Updated to 4.2.2. Don't notice an improvement.

#120 This issue is with the quality of sound. Not the dropping the connection. I updated to 4.2.2 and didn't notice any improvement. Still clipping in the high frequencies. Hook your phone/tablet up to a decent stereo and you will notice it. Listen to something with a lot of high frequencies. Cymbal crashes and splashes along with high hat work really accentuate the distortion.

with nexus 7, android 4.2.2 and creative bluetooh speaker the issue don't fixed :(

Galaxy Nexus, 4.2.2, still disappointing bluetooth audio streaming quality. I was sure that this issue would be fixed with this update. I miss my neo v. Is there any way to fix this?

Just upgraded android to 4.2.2 on Nexus 4, having same issues - crackling sound from speaker during phone calls (without bt headset). Disappointing - hope it's fixed soon. What is the best way of getting Google's attention on this?

Urgh, 4.2.2 on GN still not fixed. Audio still sounds terribad.

124. The only way that I know is to revert to 4.1.2,which isn't even an option for Nexus 4 users.

I just upgraded my Galaxy Nexus to 4.2.2 and can also confirm that high-frequency clipping and distortion is still present. I love Bluetooth streaming in my car but 4.2 has made it unusable. No amount of volume leveling on either phone or stereo resolves the issue either.

Just got a nexus 4. The quality of music via bluetooth is really bad. Please help us google! It sounds like certain frequencies crackle.

Just installed a 4.2.2 ROM. I can confirm what the others have said.... the crackle/distortion is still present.  It doesn't seem better to me, unlike what a few others have said.  You've got to be kidding me Google.

Come on....this should be fixed by now!!!

Un frikkin believable. I waited for this update on my N4 and the bluetooth audio static is still there. I guess I just pissed away $375. Looks like Apple that I despise is my only alternative or revert to an android device that will run 4.1.2. Sad sad sad for a multi BILLION dollar company.

How is the priority level raised with issues like this one. Of the bugs in 4.2.2, I have to imagine this is fairly high up the list.

WTF! I thought 4.2.2 would fix this!

Come on Google!!!!!

Why oh why did I replace my iphone with this crappy android shit. Well, maybe you are not supposed to listen to music on your android smartphone?

It stills disconnect also at least after turning on/off airplane mode. Tried now for 2 days. Turn on airplane mode for the night turning off in the morning. Connect BT headset with phone it disconnects randomly and have to turn/off/on both the headset and bt on the phone in order for it to work again until the next time..:( I didn't have any of these problems with 4.1.2. (Galaxy NExus 4.2.2 with Nokia BH-218)

I have updated my Galaxy NExus from 4.2.1 to 4.2.2 but while I had no problems with 4.2.1 connecting and using it with my car (a 2012 Renault Megane), now i do and the bluetooth stack seems to hang. Usually I have to disable bluetooth and enable it again to make ik connect. Sometimes I lose connection, and other times I still appear to be connected even though I'm miles away from my car.
Biggest problem ( apart from not being able to properly using bluetooth) is this bluetooth stack hanging seems to be related to wakelocks (12 hours and only 20% battery left. This is with only 1,5 hours screen time but with android OS wakelocks for close to 9 hours.

#136 This thread is about the bluetooth quality. More specifically, the clipping in the high frequencies that seems to effect every 4.2+ device. People who aren't complaining simply don't notice it. (aka. Having a tin ear)

On my Nexus 7 on 4.2.2 the Bluetooth audio in the car still does the hiccup/hesitation, but I would say it's not as frequent as before...I can go 5 or 10 minutes in between hiccups.  with 4.2.1 it was every few seconds.  On 4.1 it was rare when the sound did this hesitation/hiccup.

JF

[Comment deleted]

The same issue here after flashing 4.2.1 rom on ONE X. I miss BlueZ BT stack, the new one - rewritten by Google is cr*p :(( Come on Google, my 8 years old Nokia streams cristal clear audio! :(

This thread is about problems with audio QUALITY! Please report your stuttering issues in the respective thread ( http://code.google.com/p/android/issues/detail?id=39633 ) and do not flood this one.

Cymbals are terrible splashing. Tought 4.2.2 would solve the problem, but it didin't.

I was hoping this was fixed with 4.2.2 as well, and still no go.

I've found a situation that makes the problem worse than music: my wife's bluetooth headset lets road noise through, and that ends up getting amplified so much that it sounds as if she's talking through a walkie talkie she swallowed, drowned out by lots of static.  It sounds fine if I listen through the phone speaker.

This isn't a mere inconvenience, and it needs to get fixed.

My Nexus 4 has been updated to 4.2.2. I cannot connect to my toyota camry. I am highly inconvenienced as I cannot take phone calls.

I have this Issue on a SGS2 running 4.2.2
(CM10.1 nightly as of 16.2.2013)

The issue is there since quite some time, I can't remember exactly when it started.

Symptoms:

Several Persons I talked to through my bluetooth headset reported that they receive very low voice quality. "as if it comes from a 1970s transistor radio" describes it best.

Also "my wife's bluetooth headset lets road noise through, and that ends up getting amplified so much that it sounds as if she's talking through a walkie talkie she swallowed" sounds like an appropriate description.

Galaxy Nexus user confirms the 4.2.2 did NOT fix the quality issue with A2DP streaming.

Restoring (again) back to 4.1.2...

HTC One XL with Samsung HS3000 apt-x bluetooth headset and Shure SE215s, sounded as clear as a wired connection on 4.1.2. Updated to 4.2.1 and it's now unlistenable.

Given that 4.2.2 on my Nexus 7 has the same problem, and seeing how long it takes for even minor Android updates to filter down non-Nexus devices, even via custom ROMs, I'm not optimistic about seeing a fix any time soon.

4.2.3, please?

Distorted high frequency in music, like in high vocals and cymbals. Using Galaxy Nexus 4.2.2 with Skoda Superb car audio (Amundsen+). E.g., Boston - More Than a Feeling at 0:50 when the chorus starts.

My Nexus 4 was out for repairs for the past few weeks, so I only got to upgrade to 4.2.2 last night.  I can also confirm that Bluetooth Audio quality still has the same distorted sound for high frequency music such as high vocals & cymbal crashes.

Matthew Xie, this defect has been assigned to you for over 3 months.  Could you maybe get around to fixing it at some point?

Same problem here with LG Nexus 4, distorted sounds on my car (Peugeot)
Please fix! :(

I grew tired of this issue keeping me from retiring my Android 4.1 ROM, so I started looking into it.  There seems to be *2* problems with bluedroid A2DP when compared with Android 4.1's blue-z implementation.

The first is the calculation used for the bitpool size. bluedroid is reverse engineering this value based on a default and quite arbitrary quality level, which is set to MEDIUM (229) instead of HIGH (328) for the 44.1Khz sample rate.  This can be seen in the external/bluetooth/bluedroid/btif/src/btif_media_task.c file [android-4.2.2_r1 branch] -- find "DEFAULT_SBC_BITRATE".  Blue-Z would use a bitpool of 53 for stereo A2DP, bluedroid ends up using 31, and the sound quality suffers greatly .. just like the old days.

Based on the A2DP spec, the bitpool for JOINT_STEREO "Medium Quality" at 44.1Khz should also be 35 rather than 31, but that's not really important :)  My proposed fix for this part is to change that DEFAULT_SBC_BITRATE value in btif_media_task.c to 328.  This will cause the resulting bitpool calculation to become 53, which is now correct for the default 44.1Khz sample rate.  [This of course doesn't help anyone that isn't compiling from AOSP ... sorry]

The second part is the gain/output volume. It's notably higher than it was in Android 4.1, which causes clipping and distortion, at least on my A2DP receiver.  I've found that setting the A2DP volume (which will be remembered by Android) to around 80% will provide the same output levels as Android 4.1 did at maximum volume.  I haven't really looked into this part any further yet, but my guess is that it's either a limitation of my A2DP receiver and not really a problem OR it's another very simple fix once somebody smart at Google looks into it.

The big big big improvement comes from changing that simple quality constant, though.  The secondary issue is quite easy to work around ... just turn the volume up until it clips, then back it off!

@ #151:

I changed it in the source for AOKP.  I used Task's build for my i747 device, and he builds from AOKP.  I'm still trying to get used to github..... but hopefully I submitted the patch correctly.

Google you need to fix this. Audio quality is unbearable. Can't make car calls anymore.

Another victim here.  Resorting to my CDs now while I'm driving.  Looking to downgrade to 4.1 just for this.

Re #151 (also me)

I bought a new A2DP receiver (Rocketfish RF-BTR212) today and tested both my custom 4.2.2 ROMs (Verizon Fascinate and Verizon Galaxy Nexus) with the quality set to 328 and they both sound really good.  It seems my statement about the gain was erroneous and it was indeed my old receiver not being able to handle whatever bluedroid is doing as compared with Blue-Z.  Still a hint of scratchiness at max volume, but one tick down and it cleared up.

Anyway, I'm still pretty convinced that one setting is the ticket to resolve the bulk of the quality issue here.  It's too bad that bluedroid doesn't seem to be as compatible with A2DP receivers as Blue-Z was, maybe in time.

Good luck to everyone, I hope this information has been useful and helps to lead to a real and verifiable fix from Google/Broadcom in the near future.

@ #151 and #155: Would you be able to provide a link to your Galaxy Nexus ROM? I'd like to test it out.

Re: #156 .. certainly.

** NOTE FOR FUTURE READERS AFTER 2013-03-03: VOLATILE DOWNLOAD LINKS THAT WILL NOT EXIST FOREVER! **

Here's my latest VZW Galaxy Nexus build "kit".  It's generally private and I only share for a couple co-workers, but you are welcome to it to do what you want.  It's a huge download (> 500MB) since it includes the stock 4.1.1 image so they can back it out (noobs, what can you do? LOL).  It's the same AOSP baseline as my "GeeWiz 4.2" baseline for the Fascinate (find on XDA if you care), just compiled for Toro.  Buyer beware, ok?  This isn't Cyanogenmod here, it's a fastboot-based full-wipe setup, so it may not be what you're looking for ...

http://www.mediafire.com/file/5ul18qfkmgesyda/galaxynexus-lte-djp952-20130301.zip

Given that I don't share that ROM with the public and is intended for a full-wipe scenario with fastboot over Windows, you may be happier with just the /system/lib/hw/bluetooth.default.so file itself from that build, so I zipped that up and posted it for you.  Provided the ROM/build you are running is based from am AOSP 4.2.2/JDQ39 Toro build, this may be sufficient.  Put the file in /system/lib/hw and then chmod it to 0644 and reboot.

http://www.mediafire.com/file/ujll8gtbhxnz32b/4.2.2-toro-aosp-bluetooth.default.so.zip

I hope this is enough to be of assistance, but I fear it may not be since every build/ROM is different.  Please feel free to point the developer/compiler of the ROM you use to this very simple 1-line commit on github: https://github.com/djp952/android-platform-external-bluetooth-bluedroid/commit/2ee778598e3b2e3f826e3f6b4eeafbb11005b21b.  If we're lucky, that's all they need to do to restore A2DP to its former glory.  I have no delusions that this will work for every device/receiver, I just think it's a step forward.

Good luck my friend!  I've been cranking A2DP on my GNex build for hours now and it's been phenomenal.  I truly hope your results are the same.

#157 Thank you for your post.  I set up a build environment for 4.2.2-r1 for the Nexus 4 and built an entire AOSP image with the DEFAULT_SBC_BITRATE adjustment just to get to that file.  I pushed it into the path you listed on my Nexus 4, changed the permissions, and now my bluetooth no longer has the distortion at high frequencies.  Sound quality is very much improved.  Is it the best it can be?  Who knows since Google has not released an official fix, but it sounds way better now.  

I have attached the file to this post for anyone else to push to their Nexus 4.  If anyone wants to try it feel free, it should work on any Nexus 4, but I am not guaranteeing that.  If there is a better way to get the file out there, please let me know.

@ #157 & 158:

I pasted each of your files (one at a time, obviously) to where they should go, verified correct permissions, and definitely noticed a change.  However, I get a 'popping' sound during playback (like popcorn).  The audio also seems slowed down for some reason.  I'm still messing with it, so I'll report back if I can fix it.

However, I am on an ATT GS3, not a nexus, so that's likely why....

I'm running an AOKP ROM (based on AOSP).

Re #159: I looked and AOKP changed the Bluetooth code to use 48Khz as their default sampling rate rather than 44.1KHz, that's causing it to sound slow when you replace the bluetooth library file.  You would need to get an unmodified A2DP audio HAL library (/system/lib/hw/audio.a2dp.default.so) to match it, or wait until somebody has a bluetooth.default.so file with the same 48KHz sampling rate set.

It sounds like this is a generally positive change, I'm sure it won't be long at all before it becomes available for various ROMs.

#158 I just tried your file into my N4, running lastest Paranoid ROM. The sound quality is better, but the 'popping' it's still there.

#158
To clarify: do we need to rebuild the ROM or is it okay if we just replace the file (bluetooth.default.so) and set the correct permissions?

Thanks heaps to everyone working on this!

#161, #159, #160, #161.  I built it from AOSP using the full_mako lunch target (profile), so I suspect this would work best running on a stock or AOSP Nexus 4 (I am running stock, not AOSP).  I'm not sure what, if any, differences Paranoid ROM or AOKP would have to cause the popping. I'm posting the audio.a2dp.default.so file that I ended up building with bluetooth file, but if this does not help, then I suspect #160 is right.  The bluetooth file would need to be built with that sampling rate in mind, or just make a similar bitrate adjustment in the Paranoid and AOKP sources.

#162, if you're running AOSP or stock N4, it should be enough to just replace the file and set the permissions.  That is what I did.

Side Note: if AOKP or CM10.1 are using 48khz as the default sampling rate, I would definitely ask to see if they would switch it to 44.1khz from now on.  Most music is in 44.1khz and resampling to 48khz would degrade sound quality unless a high quality resampler was used (I highly doubt it is).  I have found that resampling removes some of the power and impact from snare drum hits and shrinks the stereo image a bit.  That's my experience at least on other devices.

@ #160 I swapped in your bluetooth.default.so and it sounds great. Thank you! I had been trying to find how to modify the bitpool settings everywhere, but nobody was diving deep enough to modify the .so files. I don't have that knowledge myself, so I'm glad you were able to find it. I can't understand why Google would put a lower-than-maximum value as the default.

I haven't listened enough to be able to notice a speed difference due to the sampling rate, but it the high-end distortion is completely gone.

@ #162 Replacing the file worked fine for me.

@yuxu
Thanks for your effort, your files work like a charm on my Samsung SII (AOKP 4.2.2)!
CPU usage is also in line with what it used to be on my previous ROM (ICS), and as a far as my non-musician ears can tell, there's no degradation in sound quality.

@Thread
The change seems to be pretty device-independent, so give the files in @158 and @163 a try.

Alright AOKP Users:

I have created a zip file with instructions to revert the 48khz based .so audio files back to 44.1khz so the posted bluetooth.default.so files will work properly with no popping and no slowing down of the audio.  However, THERE ARE ISSUES.

I have had the A2DP audio get really distorted after a few minutes of playback.  This may be related to CPU settings, though I'm not sure yet.  

Also, turning off bluetooth has locked up my phone.  Just hold the power button and restart.  Not sure why it's ocurring....

This is a really dirty way of fixing it because I'm not terribly familiar with android yet.  The original issue of distortion is gone though.  I'll post back if I can fix the issues I presented that are associated with this change.

The ZIP file is posted, please read the instructions!

FYI, I'm running Task650's i747 (ATT GS3) ROM.  

[Comment deleted]