XuDeveloper.github.io/posts/a01c957e.html at master · XuDeveloper/XuDeveloper.github.io

History

1016 lines (483 loc) · 86.6 KB

Raw

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

379

380

381

382

383

384

385

386

387

388

389

390

391

392

393

394

395

396

397

398

399

400

401

402

403

404

405

406

407

408

409

410

411

412

413

414

415

416

417

418

419

420

421

422

423

424

425

426

427

428

429

430

431

432

433

434

435

436

437

438

439

440

441

442

443

444

445

446

447

448

449

450

451

452

453

454

455

456

457

458

459

460

461

462

463

464

465

466

467

468

469

470

471

472

473

474

475

476

477

478

479

480

481

482

483

484

485

486

487

488

489

490

491

492

493

494

495

496

497

498

499

500

501

502

503

504

505

506

507

508

509

510

511

512

513

514

515

516

517

518

519

520

521

522

523

524

525

526

527

528

529

530

531

532

533

534

535

536

537

538

539

540

541

542

543

544

545

546

547

548

549

550

551

552

553

554

555

556

557

558

559

560

561

562

563

564

565

566

567

568

569

570

571

572

573

574

575

576

577

578

579

580

581

582

583

584

585

586

587

588

589

590

591

592

593

594

595

596

597

598

599

600

601

602

603

604

605

606

607

608

609

610

611

612

613

614

615

616

617

618

619

620

621

622

623

624

625

626

627

628

629

630

631

632

633

634

635

636

637

638

639

640

641

642

643

644

645

646

647

648

649

650

651

652

653

654

655

656

657

658

659

660

661

662

663

664

665

666

667

668

669

670

671

672

673

674

675

676

677

678

679

680

681

682

683

684

685

686

687

688

689

690

691

692

693

694

695

696

697

698

699

700

701

702

703

704

705

706

707

708

709

710

711

712

713

714

715

716

717

718

719

720

721

722

723

724

725

726

727

728

729

730

731

732

733

734

735

736

737

738

739

740

741

742

743

744

745

746

747

748

749

750

751

752

753

754

755

756

757

758

759

760

761

762

763

764

765

766

767

768

769

770

771

772

773

774

775

776

777

778

779

780

781

782

783

784

785

786

787

788

789

790

791

792

793

794

795

796

797

798

799

800

801

802

803

804

805

806

807

808

809

810

811

812

813

814

815

816

817

818

819

820

821

822

823

824

825

826

827

828

829

830

831

832

833

834

835

836

837

838

839

840

841

842

843

844

845

846

847

848

849

850

851

852

853

854

855

856

857

858

859

860

861

862

863

864

865

866

867

868

869

870

871

872

873

874

875

876

877

878

879

880

881

882

883

884

885

886

887

888

889

890

891

892

893

894

895

896

897

898

899

900

901

902

903

904

905

906

907

908

909

910

911

912

913

914

915

916

917

918

919

920

921

922

923

924

925

926

927

928

929

930

931

932

933

934

935

936

937

938

939

940

941

942

943

944

945

946

947

948

949

950

951

952

953

954

955

956

957

958

959

960

961

962

963

964

965

966

967

968

969

970

971

972

973

974

975

976

977

978

979

980

981

982

983

984

985

986

987

988

989

990

991

992

993

994

995

996

997

998

999

1000

<!DOCTYPE html>

var NexT = window.NexT || {};

var CONFIG = {

root: '/',

scheme: 'Pisces',

version: '5.1.3',

sidebar: {"position":"left","display":"post","offset":12,"b2t":false,"scrollpercent":true,"onmobile":true},

fancybox: true,

tabs: true,

motion: {"enable":true,"async":false,"transition":{"post_block":"fadeIn","post_header":"slideDownIn","post_body":"slideDownIn","coll_header":"slideLeftIn","sidebar":"slideUpIn"}},

duoshuo: {

userId: '0',

author: '博主'

algolia: {

applicationID: '',

apiKey: '',

indexName: '',

hits: {"per_page":10},

labels: {"input_placeholder":"Search for Posts","hits_empty":"We didn't find any results for the search: ${query}","hits_stats":"${hits} results found in ${time} ms"}

}

};

</script>

<title>Android深入理解Notification机制 | Xu的博客</title>

</head>

Xu的博客

</a>

</div>

</div>

</button>

</div>

首页

</a>

</li>

标签

</a>

</li>

分类

</a>

</li>

归档

</a>

</li>

</ul>

</nav>

</div>

</header>

<h1 class="post-title" itemprop="name headline">Android深入理解Notification机制</h1>

发表于

2019-02-09

</time>

|

分类于

Android

</a>

|

阅读次数:

</div>

</header>

<h4 id="本文预计阅读时间为20分钟"><a href="#本文预计阅读时间为20分钟" class="headerlink" title="本文预计阅读时间为20分钟"></a>本文预计阅读时间为20分钟</h4><h2 id="本文需要解决的问题"><a href="#本文需要解决的问题" class="headerlink" title="本文需要解决的问题"></a>本文需要解决的问题</h2>笔者最近正在做一个项目，里面需要用到 Android Notification 机制来实现某些特定需求。我正好通过这个机会研究一下 Android Notification 相关的发送逻辑和接收逻辑，以及整理相关的笔记。我研究 Notification 机制的目的是解决以下我在使用过程中所思考的问题：

<ol>

<li>我们创建的 Notification 实例最终以什么样的方式发送给系统？</li>

<li>系统是如何接收到 Notification 实例并显示的？</li>

<li>我们是否能拦截其他 app 的 Notification 并获取其中的信息？</li>

</ol>

<h2 id="什么是-Android-Notification-机制？"><a href="#什么是-Android-Notification-机制？" class="headerlink" title="什么是 Android Notification 机制？"></a>什么是 Android Notification 机制？</h2>Notification，中文名翻译为通知，每个 app 可以自定义通知的样式和内容等，它会显示在系统的通知栏等区域。用户可以打开抽屉式通知栏查看通知的详细信息。在实际生活中，Android Notification 机制有很广泛的应用，例如 IM app 的新消息通知，资讯 app 的新闻推送等等。

<h2 id="源码分析"><a href="#源码分析" class="headerlink" title="源码分析"></a>源码分析</h2>本文的源码基于 Android 7.0。

<h3 id="Notification-的发送逻辑"><a href="#Notification-的发送逻辑" class="headerlink" title="Notification 的发送逻辑"></a>Notification 的发送逻辑</h3>一般来说，如果我们自己的 app 想发送一条新的 Notification，可以参照以下代码：

<figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 </pre></td><td class="code"><pre>NotificationCompat.Builder mBuilder = new NotificationCompat.Builder(this) .setSmallIcon(R.drawable.notification_icon) .setWhen(System.currentTimeMillis()) .setContentTitle("Test Notification Title") .setContentText("Test Notification Content!"); Intent resultIntent = new Intent(this, ResultActivity.class); PendingIntent contentIntent = PendingIntent.getActivity( this, 0, resultIntent, PendingIntent.FLAG_UPDATE_CURRENT ); mBuilder.setContentIntent(resultPendingIntent); NotificationManager mNotificationManager = (NotificationManager) getSystemService(Context.NOTIFICATION_SERVICE); // mId allows you to update the notification later on. mNotificationManager.notify(mId, mBuilder.build()); </pre></td></tr></table></figure>

可以看到，我们通过 NotificationCompat.Builder 新建了一个 Notification 对象，最后通过 NotificationManager#notify() 方法将 Notification 发送出去。

<h4 id="NotificationManager-notify"><a href="#NotificationManager-notify" class="headerlink" title="NotificationManager#notify()"></a>NotificationManager#notify()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 </pre></td><td class="code"><pre>public void notify(int id, Notification notification) { notify(null, id, notification); } // 省略部分注释 public void notify(String tag, int id, Notification notification) { notifyAsUser(tag, id, notification, new UserHandle(UserHandle.myUserId())); } /** * @hide */ public void notifyAsUser(String tag, int id, Notification notification, UserHandle user) { int[] idOut = new int[1]; INotificationManager service = getService(); String pkg = mContext.getPackageName(); // Fix the notification as best we can. Notification.addFieldsFromContext(mContext, notification); if (notification.sound != null) { notification.sound = notification.sound.getCanonicalUri(); if (StrictMode.vmFileUriExposureEnabled()) { notification.sound.checkFileUriExposed("Notification.sound"); } } fixLegacySmallIcon(notification, pkg); if (mContext.getApplicationInfo().targetSdkVersion > Build.VERSION_CODES.LOLLIPOP_MR1) { if (notification.getSmallIcon() == null) { throw new IllegalArgumentException("Invalid notification (no valid small icon): " + notification); } } if (localLOGV) Log.v(TAG, pkg + ": notify(" + id + ", " + notification + ")"); final Notification copy = Builder.maybeCloneStrippedForDelivery(notification); try { // !!! service.enqueueNotificationWithTag(pkg, mContext.getOpPackageName(), tag, id, copy, idOut, user.getIdentifier()); if (localLOGV && id != idOut[0]) { Log.v(TAG, "notify: id corrupted: sent " + id + ", got back " + idOut[0]); } } catch (RemoteException e) { throw e.rethrowFromSystemServer(); } } </pre></td></tr></table></figure>

我们可以看到，到最后会调用 service.enqueueNotificationWithTag() 方法，这里的是 service 是 INotificationManager 接口。如果熟悉 AIDL 等系统相关运行机制的话，就可以看出这里是代理类调用了代理接口的方法，实际方法实现是在 NotificationManagerService 当中。

<h4 id="NotificationManagerService-enqueueNotificationWithTag"><a href="#NotificationManagerService-enqueueNotificationWithTag" class="headerlink" title="NotificationManagerService#enqueueNotificationWithTag()"></a>NotificationManagerService#enqueueNotificationWithTag()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 </pre></td><td class="code"><pre>@Override public void enqueueNotificationWithTag(String pkg, String opPkg, String tag, int id, Notification notification, int[] idOut, int userId) throws RemoteException { enqueueNotificationInternal(pkg, opPkg, Binder.getCallingUid(), Binder.getCallingPid(), tag, id, notification, idOut, userId); } void enqueueNotificationInternal(final String pkg, final String opPkg, final int callingUid, final int callingPid, final String tag, final int id, final Notification notification, int[] idOut, int incomingUserId) { if (DBG) { Slog.v(TAG, "enqueueNotificationInternal: pkg=" + pkg + " id=" + id + " notification=" + notification); } checkCallerIsSystemOrSameApp(pkg); final boolean isSystemNotification = isUidSystem(callingUid) || ("android".equals(pkg)); final boolean isNotificationFromListener = mListeners.isListenerPackage(pkg); final int userId = ActivityManager.handleIncomingUser(callingPid, callingUid, incomingUserId, true, false, "enqueueNotification", pkg); final UserHandle user = new UserHandle(userId); // Fix the notification as best we can. try { final ApplicationInfo ai = getContext().getPackageManager().getApplicationInfoAsUser( pkg, PackageManager.MATCH_DEBUG_TRIAGED_MISSING, (userId == UserHandle.USER_ALL) ? UserHandle.USER_SYSTEM : userId); Notification.addFieldsFromContext(ai, userId, notification); } catch (NameNotFoundException e) { Slog.e(TAG, "Cannot create a context for sending app", e); return; } mUsageStats.registerEnqueuedByApp(pkg); if (pkg == null || notification == null) { throw new IllegalArgumentException("null not allowed: pkg=" + pkg + " id=" + id + " notification=" + notification); } final StatusBarNotification n = new StatusBarNotification( pkg, opPkg, id, tag, callingUid, callingPid, 0, notification, user); // Limit the number of notifications that any given package except the android // package or a registered listener can enqueue. Prevents DOS attacks and deals with leaks. if (!isSystemNotification && !isNotificationFromListener) { synchronized (mNotificationList) { if(mNotificationsByKey.get(n.getKey()) != null) { // this is an update, rate limit updates only final float appEnqueueRate = mUsageStats.getAppEnqueueRate(pkg); if (appEnqueueRate > mMaxPackageEnqueueRate) { mUsageStats.registerOverRateQuota(pkg); final long now = SystemClock.elapsedRealtime(); if ((now - mLastOverRateLogTime) > MIN_PACKAGE_OVERRATE_LOG_INTERVAL) { Slog.e(TAG, "Package enqueue rate is " + appEnqueueRate + ". Shedding events. package=" + pkg); mLastOverRateLogTime = now; } return; } } int count = 0; final int N = mNotificationList.size(); for (int i=0; i<N; i++) { final NotificationRecord r = mNotificationList.get(i); if (r.sbn.getPackageName().equals(pkg) && r.sbn.getUserId() == userId) { if (r.sbn.getId() == id && TextUtils.equals(r.sbn.getTag(), tag)) { break; // Allow updating existing notification } count++; if (count >= MAX_PACKAGE_NOTIFICATIONS) { mUsageStats.registerOverCountQuota(pkg); Slog.e(TAG, "Package has already posted " + count + " notifications. Not showing more. package=" + pkg); return; } } } } } // Whitelist pending intents. if (notification.allPendingIntents != null) { final int intentCount = notification.allPendingIntents.size(); if (intentCount > 0) { final ActivityManagerInternal am = LocalServices .getService(ActivityManagerInternal.class); final long duration = LocalServices.getService( DeviceIdleController.LocalService.class).getNotificationWhitelistDuration(); for (int i = 0; i < intentCount; i++) { PendingIntent pendingIntent = notification.allPendingIntents.valueAt(i); if (pendingIntent != null) { am.setPendingIntentWhitelistDuration(pendingIntent.getTarget(), duration); } } } } // Sanitize inputs notification.priority = clamp(notification.priority, Notification.PRIORITY_MIN, Notification.PRIORITY_MAX); // setup local book-keeping final NotificationRecord r = new NotificationRecord(getContext(), n); mHandler.post(new EnqueueNotificationRunnable(userId, r)); idOut[0] = id; } </pre></td></tr></table></figure>

这里代码比较多，但通过注释可以清晰地理清整个逻辑：

<ol>

<li>首先检查通知发起者是系统进程或者是查看发起者发送的是否是同个 app 的通知信息，否则抛出异常；</li>

<li>除了系统的通知和已注册的监听器允许入队列外，其他 app 的通知都会限制通知数上限和通知频率上限；</li>

<li>将 notification 的 PendingIntent 加入到白名单；</li>

<li>将之前的 notification 进一步封装为 StatusBarNotification 和 NotificationRecord，最后封装到一个异步线程 EnqueueNotificationRunnable 中</li>

</ol>

这里有一个点，就是 mHandler，涉及到切换线程，我们先跟踪一下 mHandler 是在哪个线程被创建。

mHandler 是 WorkerHandler 类的一个实例，在 NotificationManagerService#onStart() 方法中被创建，而 NotificationManagerService 是系统 Service，所以 EnqueueNotificationRunnable 的 run 方法会运行在 system_server 的主线程。

<h4 id="NotificationManagerService-EnqueueNotificationRunnable-run"><a href="#NotificationManagerService-EnqueueNotificationRunnable-run" class="headerlink" title="NotificationManagerService.EnqueueNotificationRunnable#run()"></a>NotificationManagerService.EnqueueNotificationRunnable#run()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 </pre></td><td class="code"><pre>@Override public void run() { synchronized(mNotificationList) { // 省略代码 if (notification.getSmallIcon() != null) { StatusBarNotification oldSbn = (old != null) ? old.sbn : null; mListeners.notifyPostedLocked(n, oldSbn); } else { Slog.e(TAG, "Not posting notification without small icon: " + notification); if (old != null && !old.isCanceled) { mListeners.notifyRemovedLocked(n); } // ATTENTION: in a future release we will bail out here // so that we do not play sounds, show lights, etc. for invalid // notifications Slog.e(TAG, "WARNING: In a future release this will crash the app: " + n.getPackageName()); } buzzBeepBlinkLocked(r); } } </pre></td></tr></table></figure>

<ol>

<li>省略的代码主要的工作是提取 notification 相关的属性，同时通知 notification ranking service，有新的 notification 进来，然后对所有 notification 进行重新排序；</li>

<li>然后到最后会调用 mListeners.notifyPostedLocked() 方法。这里 mListeners 是 NotificationListeners 类的一个实例。</li>

</ol>

<h4 id="NotificationManagerService-NotificationListeners-notifyPostedLocked-nbsp-gt-NotificationManagerService-NotificationListeners-notifyPosted"><a href="#NotificationManagerService-NotificationListeners-notifyPostedLocked-nbsp-gt-NotificationManagerService-NotificationListeners-notifyPosted" class="headerlink" title="NotificationManagerService.NotificationListeners#notifyPostedLocked()  -> NotificationManagerService.NotificationListeners#notifyPosted()"></a>NotificationManagerService.NotificationListeners#notifyPostedLocked()   -> NotificationManagerService.NotificationListeners#notifyPosted()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 </pre></td><td class="code"><pre>public void notifyPostedLocked(StatusBarNotification sbn, StatusBarNotification oldSbn) { // Lazily initialized snapshots of the notification. TrimCache trimCache = new TrimCache(sbn); for (final ManagedServiceInfo info: mServices) { boolean sbnVisible = isVisibleToListener(sbn, info); boolean oldSbnVisible = oldSbn != null ? isVisibleToListener(oldSbn, info) : false; // This notification hasn't been and still isn't visible -> ignore. if (!oldSbnVisible && !sbnVisible) { continue; } final NotificationRankingUpdate update = makeRankingUpdateLocked(info); // This notification became invisible -> remove the old one. if (oldSbnVisible && !sbnVisible) { final StatusBarNotification oldSbnLightClone = oldSbn.cloneLight(); mHandler.post(new Runnable() { @Override public void run() { notifyRemoved(info, oldSbnLightClone, update); } }); continue; } final StatusBarNotification sbnToPost = trimCache.ForListener(info); mHandler.post(new Runnable() { @Override public void run() { notifyPosted(info, sbnToPost, update); } }); } } private void notifyPosted(final ManagedServiceInfo info, final StatusBarNotification sbn, NotificationRankingUpdate rankingUpdate) { final INotificationListener listener = (INotificationListener) info.service; StatusBarNotificationHolder sbnHolder = new StatusBarNotificationHolder(sbn); try { listener.onNotificationPosted(sbnHolder, rankingUpdate); } catch (RemoteException ex) { Log.e(TAG, "unable to notify listener (posted): " + listener, ex); } } </pre></td></tr></table></figure>

调用到最后会执行 listener.onNotificationPosted() 方法。通过全局搜索得知，listener 类型是 NotificationListenerService.NotificationListenerWrapper 的代理对象。

<h4 id="NotificationListenerService-NotificationListenerWrapper-onNotificationPosted"><a href="#NotificationListenerService-NotificationListenerWrapper-onNotificationPosted" class="headerlink" title="NotificationListenerService.NotificationListenerWrapper#onNotificationPosted()"></a>NotificationListenerService.NotificationListenerWrapper#onNotificationPosted()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 </pre></td><td class="code"><pre>public void onNotificationPosted(IStatusBarNotificationHolder sbnHolder, NotificationRankingUpdate update) { StatusBarNotification sbn; try { sbn = sbnHolder.get(); } catch (RemoteException e) { Log.w(TAG, "onNotificationPosted: Error receiving StatusBarNotification", e); return; } try { // convert icon metadata to legacy format for older clients createLegacyIconExtras(sbn.getNotification()); maybePopulateRemoteViews(sbn.getNotification()); } catch (IllegalArgumentException e) { // warn and drop corrupt notification Log.w(TAG, "onNotificationPosted: can't rebuild notification from " + sbn.getPackageName()); sbn = null; } // protect subclass from concurrent modifications of (@link mNotificationKeys}. synchronized(mLock) { applyUpdateLocked(update); if (sbn != null) { SomeArgs args = SomeArgs.obtain(); args.arg1 = sbn; args.arg2 = mRankingMap; mHandler.obtainMessage(MyHandler.MSG_ON_NOTIFICATION_POSTED, args).sendToTarget(); } else { // still pass along the ranking map, it may contain other information mHandler.obtainMessage(MyHandler.MSG_ON_NOTIFICATION_RANKING_UPDATE, mRankingMap).sendToTarget(); } } } </pre></td></tr></table></figure>

这里在一开始会从 sbnHolder 中获取到 sbn 对象，sbn 隶属于 StatusBarNotificationHolder 类，继承于 IStatusBarNotificationHolder.Stub 对象。注意到这里捕获了一个 RemoteException，猜测涉及到跨进程调用，但我们不知道这段代码是在哪个进程中执行的，所以在这里暂停跟踪代码。

笔者之前是通过向系统发送通知的方式跟踪源码，发现走不通。故个人尝试从另一个角度入手，即系统接收我们发过来的通知并显示到通知栏这个方式入手跟踪代码。

<h3 id="系统如何显示-Notification，即对于系统端来说，Notification-的接收逻辑"><a href="#系统如何显示-Notification，即对于系统端来说，Notification-的接收逻辑" class="headerlink" title="系统如何显示 Notification，即对于系统端来说，Notification 的接收逻辑"></a>系统如何显示 Notification，即对于系统端来说，Notification 的接收逻辑</h3>系统显示 Notification 的过程，猜测是在 PhoneStatusBar.java 中，因为系统启动的过程中，会启动 SystemUI 进程，初始化整个 Android 显示的界面，包括系统通知栏。

<h4 id="PhoneStatusBar-start-nbsp-gt-BaseStatusBar-start"><a href="#PhoneStatusBar-start-nbsp-gt-BaseStatusBar-start" class="headerlink" title="PhoneStatusBar#start()  -> BaseStatusBar#start()"></a>PhoneStatusBar#start()   -> BaseStatusBar#start()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 </pre></td><td class="code"><pre>public void start() { // 省略代码 // Set up the initial notification state. try { mNotificationListener.registerAsSystemService(mContext, new ComponentName(mContext.getPackageName(), getClass().getCanonicalName()), UserHandle.USER_ALL); } catch (RemoteException e) { Log.e(TAG, "Unable to register notification listener", e); } // 省略代码 } </pre></td></tr></table></figure>

这段代码中，会调用 NotificationListenerService#registerAsSystemService() 方法，涉及到我们之前跟踪代码的类。我们继续跟进去看一下。

<h4 id="NotificationListenerService-registerAsSystemService"><a href="#NotificationListenerService-registerAsSystemService" class="headerlink" title="NotificationListenerService#registerAsSystemService()"></a>NotificationListenerService#registerAsSystemService()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 </pre></td><td class="code"><pre>public void registerAsSystemService(Context context, ComponentName componentName, int currentUser) throws RemoteException { if (mWrapper == null) { mWrapper = new NotificationListenerWrapper(); } mSystemContext = context; INotificationManager noMan = getNotificationInterface(); mHandler = new MyHandler(context.getMainLooper()); mCurrentUser = currentUser; noMan.registerListener(mWrapper, componentName, currentUser); } </pre></td></tr></table></figure>

这里会初始化一个 NotificationListenerWrapper 和 mHandler。由于这是在 SystemUI 进程中去调用此方法将 NotificationListenerService 注册为系统服务，所以在前面分析的那里：NotificationListenerService.NotificationListenerWrapper#onNotificationPosted()，这段代码是运行在 SystemUI 进程，而 mHandler 则是运行在 SystemUI 主线程上的 Handler。所以，onNotificationPosted() 是运行在 SystemUI 进程中，它通过 sbn 从 system_server 进程中获取到 sbn 对象。下一步是通过 mHandler 处理消息，查看 NotificationListenerService.MyHandler#handleMessage() 方法，得知当 message.what 为 MSG_ON_NOTIFICATION_POSTED 时，调用的是 onNotificationPosted() 方法。

但是，NotificationListenerService 是一个抽象类，onNotificationPosted() 为空方法，真正的实现是它的实例类。

观察到之前 BaseStatusBar#start() 中，是调用了 mNotificationListener.registerAsSystemService() 方法。那么，mNotificationListener 是在哪里进行初始化呢？

<h4 id="BaseStatusBar-mNotificationListener-onNotificationPosted"><a href="#BaseStatusBar-mNotificationListener-onNotificationPosted" class="headerlink" title="BaseStatusBar.mNotificationListener#onNotificationPosted"></a>BaseStatusBar.mNotificationListener#onNotificationPosted</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 </pre></td><td class="code"><pre>private final NotificationListenerService mNotificationListener = new NotificationListenerService() { // 省略代码 @Override public void onNotificationPosted(final StatusBarNotification sbn, final RankingMap rankingMap) { if (DEBUG) Log.d(TAG, "onNotificationPosted: " + sbn); if (sbn != null) { mHandler.post(new Runnable() { @Override public void run() { processForRemoteInput(sbn.getNotification()); String key = sbn.getKey(); mKeysKeptForRemoteInput.remove(key); boolean isUpdate = mNotificationData.get(key) != null; // In case we don't allow child notifications, we ignore children of // notifications that have a summary, since we're not going to show them // anyway. This is true also when the summary is canceled, // because children are automatically canceled by NoMan in that case. if (!ENABLE_CHILD_NOTIFICATIONS && mGroupManager.isChildInGroupWithSummary(sbn)) { if (DEBUG) { Log.d(TAG, "Ignoring group child due to existing summary: " + sbn); } // Remove existing notification to avoid stale data. if (isUpdate) { removeNotification(key, rankingMap); } else { mNotificationData.updateRanking(rankingMap); } return; } if (isUpdate) { updateNotification(sbn, rankingMap); } else { addNotification(sbn, rankingMap, null /* oldEntry */ ); } } }); } } // 省略代码 } </pre></td></tr></table></figure>

<ol>

<li>通过上述代码，我们知道了在 BaseStatusBar.java 中，创建了 NotificationListenerService 的实例对象，实现了 onNotificationPost() 这个抽象方法；</li>

<li>在 onNotificationPost() 中，通过 handler 进行消息处理，最终调用 addNotification() 方法</li>

</ol>

<h4 id="PhoneStatusBar-addNotification"><a href="#PhoneStatusBar-addNotification" class="headerlink" title="PhoneStatusBar#addNotification()"></a>PhoneStatusBar#addNotification()</h4><figure class="highlight java"><table><tr><td class="gutter"><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 </pre></td><td class="code"><pre>@Override public void addNotification(StatusBarNotification notification, RankingMap ranking, Entry oldEntry) { if (DEBUG) Log.d(TAG, "addNotification key=" + notification.getKey()); mNotificationData.updateRanking(ranking); Entry shadeEntry = createNotificationViews(notification); if (shadeEntry == null) { return; } boolean isHeadsUped = shouldPeek(shadeEntry); if (isHeadsUped) { mHeadsUpManager.showNotification(shadeEntry); // Mark as seen immediately setNotificationShown(notification); } if (!isHeadsUped && notification.getNotification().fullScreenIntent != null) { if (shouldSuppressFullScreenIntent(notification.getKey())) { if (DEBUG) { Log.d(TAG, "No Fullscreen intent: suppressed by DND: " + notification.getKey()); } } else if (mNotificationData.getImportance(notification.getKey()) < NotificationListenerService.Ranking.IMPORTANCE_MAX) { if (DEBUG) { Log.d(TAG, "No Fullscreen intent: not important enough: " + notification.getKey()); } } else { // Stop screensaver if the notification has a full-screen intent. // (like an incoming phone call) awakenDreams(); // not immersive & a full-screen alert should be shown if (DEBUG) Log.d(TAG, "Notification has fullScreenIntent; sending fullScreenIntent"); try { EventLog.writeEvent(EventLogTags.SYSUI_FULLSCREEN_NOTIFICATION, notification.getKey()); notification.getNotification().fullScreenIntent.send(); shadeEntry.notifyFullScreenIntentLaunched(); MetricsLogger.count(mContext, "note_fullscreen", 1); } catch (PendingIntent.CanceledException e) {} } } // !!! addNotificationViews(shadeEntry, ranking); // Recalculate the position of the sliding windows and the titles. setAreThereNotifications(); } </pre></td></tr></table></figure>

在这个方法中，最关键的方法是最后的 addNotificationViews() 方法。调用这个方法之后，你创建的 Notification 才会被添加到系统通知栏上。

<h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2>跟踪完整个过程中，之前提到的问题也可以一一解决了：

<ul>

<li>Q：我们创建的 Notification 实例最终以什么样的方式发送给系统？

A：首先，我们在 app 进程创建 Notification 实例，通过跨进程调用，传递到 system_server 进程的 NotificationManagerService 中进行处理，经过两次异步调用，最后传递给在 NotificationManagerService 中已经注册的 NotificationListenerWrapper。而 android 系统在初始化 systemui 进程的时候，会往 NotificationManagerService 中注册监听器（这里指的就是 NotificationListenerWrapper）。这种实现方法就是基于我们熟悉的一种设计模式：监听者模式。

</blockquote>

</li>

<li>Q：系统是如何获取到 Notification 实例并显示的？

A：上面提到，由于初始化的时候已经往 NotificationManagerService 注册监听器，所以系统 SystemUI 进程会接收到 Notification 实例之后经过进一步解析，然后构造出 Notification Views 并最终显示在系统通知栏上。

</blockquote>

</li>

<li>Q：我们是否能拦截 Notification 并获取其中的信息？

A：通过上面的流程，我个人认为可以通过 Xposed 等框架去 hook 其中几个重要的方法去捕获 Notification 实例，例如 hook NotificationManager#notify() 方法去获取 Notification 实例。

</blockquote>

</li>

</ul>

</div>

<a href="/tags/Android源码解析/" rel="tag"># Android源码解析</a>

</div>

使用Kotlin的一些心得体会以及部分语法解析

</a>

</div>

Android 单元测试和 UI 测试初步实践

</a>

</div>

</footer>

</div>

</article>

</div>

</div>

文章目录

</li>

站点概览

</li>

</ul>

Xu

Tencent / 一个自律的Developer

</div>

13

日志

</a>

</div>

1

分类

</a>

</div>

5

标签

</a>

</div>

</nav>

GitHub</a>

E-Mail</a>

掘金</a>

简书</a>

CSDN</a>

简历</a>

</div>

</section>

<div class="post-toc-content"><ol class="nav"><li class="nav-item nav-level-4"><a class="nav-link" href="#本文预计阅读时间为20分钟">本文预计阅读时间为20分钟</a></li></ol><li class="nav-item nav-level-2"><a class="nav-link" href="#本文需要解决的问题">本文需要解决的问题</a></li><li class="nav-item nav-level-2"><a class="nav-link" href="#什么是-Android-Notification-机制？">什么是 Android Notification 机制？</a></li><li class="nav-item nav-level-2"><a class="nav-link" href="#源码分析">源码分析</a><ol class="nav-child"><li class="nav-item nav-level-3"><a class="nav-link" href="#Notification-的发送逻辑">Notification 的发送逻辑</a><ol class="nav-child"><li class="nav-item nav-level-4"><a class="nav-link" href="#NotificationManager-notify">NotificationManager#notify()</a></li><li class="nav-item nav-level-4"><a class="nav-link" href="#NotificationManagerService-enqueueNotificationWithTag">NotificationManagerService#enqueueNotificationWithTag()</a></li><li class="nav-item nav-level-4"><a class="nav-link" href="#NotificationManagerService-EnqueueNotificationRunnable-run">NotificationManagerService.EnqueueNotificationRunnable#run()</a></li><li class="nav-item nav-level-4"><a class="nav-link" href="#NotificationManagerService-NotificationListeners-notifyPostedLocked-nbsp-gt-NotificationManagerService-NotificationListeners-notifyPosted">NotificationManagerService.NotificationListeners#notifyPostedLocked() -> NotificationManagerService.NotificationListeners#notifyPosted()</a></li><li class="nav-item nav-level-4"><a class="nav-link" href="#NotificationListenerService-NotificationListenerWrapper-onNotificationPosted">NotificationListenerService.NotificationListenerWrapper#onNotificationPosted()</a></li></ol></li><li class="nav-item nav-level-3"><a class="nav-link" href="#系统如何显示-Notification，即对于系统端来说，Notification-的接收逻辑">系统如何显示 Notification，即对于系统端来说，Notification 的接收逻辑</a><ol class="nav-child"><li class="nav-item nav-level-4"><a class="nav-link" href="#PhoneStatusBar-start-nbsp-gt-BaseStatusBar-start">PhoneStatusBar#start() -> BaseStatusBar#start()</a></li><li class="nav-item nav-level-4"><a class="nav-link" href="#NotificationListenerService-registerAsSystemService">NotificationListenerService#registerAsSystemService()</a></li><li class="nav-item nav-level-4"><a class="nav-link" href="#BaseStatusBar-mNotificationListener-onNotificationPosted">BaseStatusBar.mNotificationListener#onNotificationPosted</a></li><li class="nav-item nav-level-4"><a class="nav-link" href="#PhoneStatusBar-addNotification">PhoneStatusBar#addNotification()</a></li></ol></li></ol></li><li class="nav-item nav-level-2"><a class="nav-link" href="#总结">总结</a></li></div>

</div>

</section>

</div>

</aside>

</div>

</main>

Xu

</div>

</footer>

0%

</div>

if (Object.prototype.toString.call(window.Promise) !== '[object Function]') {

window.Promise = null;

}

</script>

function showTime(Counter) {

var query = new AV.Query(Counter);

var entries = [];

var $visitors = $(".leancloud_visitors");

$visitors.each(function () {

entries.push( $(this).attr("id").trim() );

});

query.containedIn('url', entries);

query.find()

.done(function (results) {

var COUNT_CONTAINER_REF = '.leancloud-visitors-count';

if (results.length === 0) {

$visitors.find(COUNT_CONTAINER_REF).text(0);

return;

}

for (var i = 0; i < results.length; i++) {

var item = results[i];

var url = item.get('url');

var time = item.get('time');

var element = document.getElementById(url);

$(element).find(COUNT_CONTAINER_REF).text(time);

}

for(var i = 0; i < entries.length; i++) {

var url = entries[i];

var element = document.getElementById(url);

var countSpan = $(element).find(COUNT_CONTAINER_REF);

if( countSpan.text() == '') {

countSpan.text(0);

}

})

.fail(function (object, error) {

console.log("Error: " + error.code + " " + error.message);

});

}

function addCount(Counter) {

var $visitors = $(".leancloud_visitors");

var url = $visitors.attr('id').trim();

var title = $visitors.attr('data-flag-title').trim();

var query = new AV.Query(Counter);

query.equalTo("url", url);

query.find({

success: function(results) {

if (results.length > 0) {

var counter = results[0];

counter.fetchWhenSave(true);

counter.increment("time");

counter.save(null, {

success: function(counter) {

var $element = $(document.getElementById(url));

$element.find('.leancloud-visitors-count').text(counter.get('time'));

error: function(counter, error) {

console.log('Failed to save Visitor num, with error message: ' + error.message);

}

});

} else {

var newcounter = new Counter();

/* Set ACL */

var acl = new AV.ACL();

acl.setPublicReadAccess(true);

acl.setPublicWriteAccess(true);

newcounter.setACL(acl);

/* End Set ACL */

newcounter.set("title", title);

newcounter.set("url", url);

newcounter.set("time", 1);

newcounter.save(null, {

success: function(newcounter) {

var $element = $(document.getElementById(url));

$element.find('.leancloud-visitors-count').text(newcounter.get('time'));

error: function(newcounter, error) {

console.log('Failed to create');

}

});

}

error: function(error) {

console.log('Error:' + error.code + " " + error.message);

}

});

}

$(function() {

var Counter = AV.Object.extend("Counter");

if ($('.leancloud_visitors').length == 1) {

addCount(Counter);

} else if ($('.post-title-link').length > 1) {

showTime(Counter);

}

});

</script>

(function(){

var bp = document.createElement('script');

var curProtocol = window.location.protocol.split(':')[0];

if (curProtocol === 'https') {

bp.src = 'https://zz.bdstatic.com/linksubmit/push.js';

}

else {

bp.src = 'http://push.zhanzhang.baidu.com/push.js';

}

var s = document.getElementsByTagName("script")[0];

View remainder of file in raw view

FilesExpand file tree

a01c957e.html

Latest commit

History

a01c957e.html

File metadata and controls