Android 10、API 29更新后,安卓震动应用无法正常工作。

9
几个月前,我开发了一个应用程序,帮助我改善睡眠问题。由于我有睡眠问题,所以我用这个应用程序在睡觉时通过震动手机来让自己专注于入睡,现在它是我睡眠例行的重要组成部分。
然而,昨天我升级了我的Android 10手机,结果这个应用程序完全崩溃了。以前,当我点击开始按钮时,该应用程序会通过后台服务、广播接收器和唤醒锁定来持续震动,并在我锁定手机后仍会保持震动。但现在,一旦我锁定手机,该应用程序就停止震动,而控制台也没有显示任何原因。
如果有人能给出建议,告诉我可以在代码中进行哪些更改或者其他方法,那将不胜感激,因为我已经完全不知道该怎么办了,而我必须设法让它工作起来。
以下是处理开始服务振动的MainActivity中的函数代码:
// Event for when the VIBRATE button is pressed
public void beginVibration(View view) {
    // Given either of the bars are not 0
    if (durationBar.getProgress() != 0 || delayBar.getProgress() != 0) {
        // Get the values for each bar and set them accordingly in the vibration value array
        long[] pattern = {0, durationBar.getProgress(), delayBar.getProgress()};

        // Setup the ServiceConnection to monitor the Vibrate service
        c = new ServiceConnection() {
            @Override
            public void onServiceConnected(ComponentName name, IBinder service) {
                m_service = ((Vibrate.MyBinder)service).getService();
            }

            @Override
            public void onServiceDisconnected(ComponentName name) {
                m_service = null;
            }
        };

        // Bind the service to the connection
        bindService(i, c, BIND_AUTO_CREATE);

        // Insert the pattern into the intent itself
        i.putExtra("pattern", pattern);

        // Start the vibrate service
        this.startService(i);
    }
}

振动服务类:

public class Vibrate extends Service {

// Vibration object
private Vibrator v;

/*
THESE THREE ARE FOR PREVENTING THE VIBRATION FROM STOPPING AFTER THE PHONE IS PUT TO SLEEP
*/
// Wake Lock object
private PowerManager.WakeLock wl;

// Manager for the notifications
private NotificationManagerCompat m_notificationManager;

// BroadcastReceiver object
public BroadcastReceiver re;

public AudioAttributes audioAttributes;

// Not gonna lie, Idk what this does just know it is part of the binding process within MainActivity
public class MyBinder extends Binder {
    public Vibrate getService() {
        return Vibrate.this;
    }
}

@Override
public void onCreate() {
    super.onCreate();

    // Acquire the Wake Lock
    PowerManager pw = (PowerManager) getSystemService(POWER_SERVICE);
    wl = pw.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, "WL:");
    wl.acquire();

    // Get the vibration service
    v = (Vibrator) getSystemService(VIBRATOR_SERVICE);
    AudioAttributes audioAttributes = new AudioAttributes.Builder()
            .setContentType(AudioAttributes.CONTENT_TYPE_SONIFICATION)
            .setUsage(AudioAttributes.USAGE_ALARM)
            .build();

}

@Override
public int onStartCommand(Intent i, int flags, int startId) {

    // Ensure that an intent with a long array has been passed
    if (i != null && i.getExtras() != null) {
        // Get the array
        final long[] pattern = i.getExtras().getLongArray("pattern");
        // Begin the vibration
        v.vibrate(pattern, 0);

        // Intialize the BroadcastReceiver and set it to trigger when the screen is turned off,
        // thus triggering the vibrations
        re = new BroadcastReceiver() {
            @Override
            public void onReceive(Context context, Intent intent) {
                if (intent.getAction().equals(Intent.ACTION_SCREEN_OFF)) {
                    Log.i("VIZZY: ", "VIBRATION STARTED");
                    v.vibrate(pattern, 0, audioAttributes);
                    Log.i("VIZZY: ", "VIBRATION BEGUn");
                }
            }
        };

        // Add a listener for when the screen turns off and register the receiver
        IntentFilter filter = new IntentFilter(Intent.ACTION_SCREEN_OFF);
        registerReceiver(re, filter);
    }

    return Service.START_STICKY;
}

@Override
public void onDestroy() {
    // If the phone was put to sleep, cancel the notification keeping the vibration going
    if (m_notificationManager != null) {
        m_notificationManager.cancel(001);
    }

    // Release the Wake Lock, unregister the BroadcastReceiver, and stop the vibrations
    wl.release();
    unregisterReceiver(re);
    v.cancel();
}

@Override
public IBinder onBind(Intent intent) {
    return null;
}

private void addNotification() {
    // create the notification
    Notification.Builder m_notificationBuilder = new Notification.Builder(this)
    .setContentTitle("VIZZY")
    .setContentText("VIBRATING")
            .setSmallIcon(R.mipmap.ic_launcher);





    // create the pending intent and add to the notification
    Intent intent = new Intent(this, Vibrate.class);
    PendingIntent pendingIntent = PendingIntent.getActivity(this, 0, intent, 0);
    m_notificationBuilder.setContentIntent(pendingIntent);

    m_notificationManager = NotificationManagerCompat.from(this);

    // send the notification
    m_notificationManager.notify(001, m_notificationBuilder.build());
}

提前感谢任何人的帮助。

2个回答

23

我遇到了相同的问题。后来我发现从目标版本29开始,只有在将适当的音频属性传递给该方法时,振动才能在后台工作:

public void vibrate(VibrationEffect vibe, AudioAttributes attributes);

您可以尝试以这种方式使用它:

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) { 
    vibrator.vibrate(VibrationEffect.createWaveform(pattern, 0), 
            new AudioAttributes.Builder()
                    .setContentType(AudioAttributes.CONTENT_TYPE_SONIFICATION)
                    .setUsage(AudioAttributes.USAGE_ALARM)
                    .build()); 
} else { 
    vibrator.vibrate(pattern, 0);
}

2
这对我有用!我不喜欢Android框架给我们提供贫乏的反馈,而且只是默默地失败。 - BabyishTank
太好了,这个解决方案让我省了很多时间,因为我不用再费力去弄清楚为什么我的应用程序突然停止震动了。 - Malcolm Bryant

0

它可能不关心这些指令:

IntentFilter filter = new IntentFilter(Intent.ACTION_SCREEN_OFF);
registerReceiver(re, filter);

所以它可能应该是类似这样的:

if (android.os.Build.VERSION.SDK_INT < android.os.Build.VERSION_CODES.Q){
    IntentFilter filter = new IntentFilter(Intent.ACTION_SCREEN_OFF);
    registerReceiver(re, filter);
} else {
    /* whatever it takes to make it work >= API level 29 */
}

Intent.ACTION_SCREEN_ONIntent.ACTION_SCREEN_OFF通常需要应用程序在运行中。但是,Android 10的行为更改没有提到类似的内容,因此很难判断。同时,接收广播也没有提到任何最近的更改。


你好,感谢你的帮助!结合你所说的和其他一些线程,我最终成功让它正常运行了。我最终改变了发出通知的方式,并启动了两个前台服务来强制手机震动。我不确定这是否有意义,我甚至不完全理解它是如何工作的。但还是非常感谢你的帮助! - geniye
确实可能是发送或接收方的问题,当意图没有正确接收时。使用两个服务(这似乎很奇怪),它最终也可能会注册唤醒锁和接收器两次。 - Martin Zeitler

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接