Android 4.4 incoming call interface InCallUI, androidincallui
There is a customer who wants to adapt the incoming call interface to the leather case they provide. In this case, the incoming call interface should be adjusted according to the window opened by the leather case. The caller interface is not in the Dialer code, but in pacakage/apps/InCallUI, the corresponding layout file is adjusted.
During com
In Android, InCallUI is too slow to display. androidincalluiI. symptom
When a phone call is sent, the system first hears the ringtone. After a relatively long period of time (3-4 s), the screen will light up and display the call interface.
Platform: MT6581
Android: 4.4KK
BuildType: userdebug
System software version: SWC1E + UP
RAM: 512 M
2. Android4.4 call and IncallUI display process 3. Problem Anal
well as the Telephony framework. In Android 4.4, the phone module was replaced by Incallui and Teleservice, where Incallui was packaged in dialer.apk. Incallui is primarily responsible for UI display, while Teleservice is responsible for logical processing.In Android 5.0, the Telephony service is the original Teleservice, and some features are extracted into the
Evolution
In Android 4.2 and earlier versions, the Telephony Phone module mainly involves Phone, Contacts, and Telephony Framework. In Android 4.4, phoneiis replaced by incalluiand teleservice, and incallui is packed into dialer.apk. InCallUI is mainly responsible for UI display, while TeleService is responsible for logic processing.
In Android 5.0, Telephony Service is the original TeleService. Some funct
Call status from the bottom to the upper layer. The DIALING status also comes from the bottom layer, therefore, the entire process is similar to MT and divided into three parts: Telephony framework, TeleService, and InCallUI, for example:
Through the preceding analysis, we know that all status changes are initiated by the underlying Modem and the related status information is fed back to the RILJ at the Framework layer. The upper layer interacts wi
How to correctly enable isLoggable in Android 5.0 (1) _ Usage Details, androidisloggableWhat is isLoggable?
In the Android source code, we often see the following code:
//packages/apps/InCallUI/src/com/android/incallui/Log.javapublic static final String TAG = "InCall";public static final boolean DEBUG = android.util.Log.isLoggable(TAG, android.util.Log.DEBUG);public static void d(String tag, String msg) {
Transferred from: http://blog.csdn.net/yihongyuelan/article/details/46409389What is isloggable?In the Android source code, we can often see the following codes:[Java]View PlainCopy
Packages/apps/incallui/src/com/android/incallui/log.java
Public static final String TAG = "Incall";
Public Static final Boolean DEBUG = Android.util.Log.isLoggable (TAG, Android.util.Log.DEBUG);
Public static void
1. Add the implementation file:Alps\packages\apps\incallui\src\com\android\incallui\sensorfunctionserviceincall.java/* Copyright (C) The Android Open Source Project * * Licensed under the Apache License, Version 2.0 (the "License") ; * You are not a use this file except in compliance with the License. * Obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * unless required by app
the MO process, then you should know that a complete MO process begins with dialer telecom and then to Incallui, and Incallactivity is in Incallui. So we infer that the state of this pri_dial_wait is set in Telecomm.The tracking process found that there is a key call type method in Callsmanager.java Startoutgoingcall (), which has a variable to control whether to display the SIM card inquiry box needsaccou
) getFragmentManager (). findFragmentById (R. id. callButtonFragment); mCallButtonFragment. getView (). setVisibility (View. INVISIBLE);} if (mCallCardFragment = null) {mCallCardFragment = (CallCardFragment) getFragmentManager (). findFragmentById (R. id. callCardFragment );}//...... omitted}Then, the status bar and the close-range sensor status are updated. In addition, MTK adds some customization to AOSP, such as SIMInfoWrapperr, which is used to display and save SIM card information. Compared
Under the big font, the call interface SIM card operator name is not fully displayedInsert a valid SIM card and set the font to large1. Test machine A and auxiliary testing machine B is in the call, auxiliary test machine C call A,a answer2. Observe the call interface[Actual results]Call interface SIM card operator name is not displayed (see attached)In the Incall interface, that is certainly in the Incallui module, this interface is the Incallactivit
,audiostate, all currently supported audiostate.Only the bottom setaudioroute () in the rightmost 6 ellipse is manually set, and our operation on the Incallui interface is passed from this entry. The rest can be thought of as automatic setup. audiostate
Let's talk about one of the key variables Maudiostate.Maudiostate This variable almost carries all the audio related information, the key two:
/**
* @return The current audio route being used.
The directory structure has not changedor the corresponding Package/app/incallui and Package/services/telephonyFile comparisonThe phone call process is basically the same as 4.4. The interface adds a lot of animation effects, and the layout structure is very different from 4.4.The layout of Incallactivity.java 5.0 is as followsUnlike the 4.4, which no longer contains the layout of the Callbuttonfragment answerfragment dialpadfragment, but allMove to t
applications such as want to access the Web page will open this browser homepage, because it must be at the bottom of the end of our visit to go back to our own application, imagine this home activity does not and mainlaunch together, Then he must have a browser. Other activity stacks, we have visited the point back to see the browser did not close the activity, many times back to return, very strange not. and the browser homepage is a cumbersome interface, if not set to Singletask we open from
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.