Obsolete
Status Update
No update yet.
Comments
sm...@google.com
The rate limiter was an intentional introduction in Jelly Bean (4.1) and the settings can not be altered by users. Device manufacturers have the ability to alter this limit in their firmware, but they have to balance heavy texters against protecting users against malicious premium rate SMS sending applications.
You may wish to contact your device manufacturer to see if they can raise the limit in their firmware.
You may wish to contact your device manufacturer to see if they can raise the limit in their firmware.
ri...@gmail.com
OK, just as information I'm a Galaxy Nexus user therefore writing this here instead anywhere else.
However the 'protection' mechanism is plain wrong - instead of dealing with malicious software in the market end-users are 'punished' with such limitations ruining the, otherwise great, experience of using Android. Also it won't help with such limitations because any malicious software can be aware of such restrictions thus pacing the rate of sending premium texts to avoid being noticed by the user (until the bill comes or one runs out of credit on pre-paid) and even if Google set this to hilarious 1 text per hour user still could not be aware that anything is wrong because noone is keeping track of their texting timing.
Bottomline - such restriction won't help nor solve the problem but can only be highly annoying to regular users.
However the 'protection' mechanism is plain wrong - instead of dealing with malicious software in the market end-users are 'punished' with such limitations ruining the, otherwise great, experience of using Android. Also it won't help with such limitations because any malicious software can be aware of such restrictions thus pacing the rate of sending premium texts to avoid being noticed by the user (until the bill comes or one runs out of credit on pre-paid) and even if Google set this to hilarious 1 text per hour user still could not be aware that anything is wrong because noone is keeping track of their texting timing.
Bottomline - such restriction won't help nor solve the problem but can only be highly annoying to regular users.
sm...@google.com
Completely agree with wojek.k. Terrible user-experience. I have unlimited texts so why would I care if I've been sending a lot of text messages. Soon we'll have to answer security questions to send a text message...
ri...@gmail.com
Ive gotten it a few times now and it's very irritating. Im part of the text generation and friends and I trigger off text messages like crazy, especially with those that aren't on G+. How am I suppose to text someone I like (wink) only to get cockblocked from Android itself. #fail
sm...@google.com
That is probably the worst "feature" I've ever seen on a phone. Why would a phone EVER limit its usage for anything? I pay for unlimited texting and I pay for my phone, why should I have to deal with this? No other phone, including the iPhone, has such a stupid limit. Clearly this does nothing to prevent spam. Please, AT LEAST let the end-user decide if they want that limit or not. It's just stupid.
sm...@google.com
sy...@google.com
is...@google.com
Mu...@postuf.com
I believe that the this feature should be an option allowing users to either limit or not limit their number of texts. In my opinion that would be the best for of action. But if it is not possible to remove/bypass it, can you tell us how to remove it in our custom roms.
cc...@google.com
I agree with others here. This is a HORRIBLE implementation. I'm not even a heavy texter, but occasionally I WILL send out eg. a party invite to a group of friends, easily passing the limit of "allowed" messages (especially since a long message will count as 2-6 messages all by itself times perhaps 10 invites.
If this was at least user-definabale (like the "allow non-market apps to install" option, that would be one thing. You'd "protect" the non-savvy users, while allowing me and others to keep using our phone as we want to, but making it hard-coded like this is EXTREMELY annoying. And yes - I too have a Galaxy Nexus so I can't "talk to my carrier" - I got it precisely because I wanted the full android experience - not to get friggen told how I can't use my own phone by it.
If this was at least user-definabale (like the "allow non-market apps to install" option, that would be one thing. You'd "protect" the non-savvy users, while allowing me and others to keep using our phone as we want to, but making it hard-coded like this is EXTREMELY annoying. And yes - I too have a Galaxy Nexus so I can't "talk to my carrier" - I got it precisely because I wanted the full android experience - not to get friggen told how I can't use my own phone by it.
Description
* What device you are testing with: emulator
I'm trying to get a Wear 2.0 (stand-alone) app to run in kiosk mode, but when I try
adb shell dpm set-device-owner <myComponent>
I get:
java.lang.IllegalStateException: Not allowed to set the device owner because this device has already paired
at android.os.Parcel.readException(Parcel.java:1692)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:4707)
at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:148)
at com.android.commands.dpm.Dpm.onRun(Dpm.java:96)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
at com.android.commands.dpm.Dpm.main(Dpm.java:41)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)