00913268 FATAL EXCEPTION: BtOpp Transfer Handler

If you can't explain it simply, you don't understand it well enough.
- Albert Einstein
回覆文章
admin
系統管理員
文章: 82
註冊時間: 2013年 4月 5日, 21:16

00913268 FATAL EXCEPTION: BtOpp Transfer Handler

文章 admin » 2013年 4月 6日, 17:40

Subject

[David][BT] FATAL EXCEPTION: BtOpp Transfer Handler



Description

Dear QCT Team,
Our customer raise an issue about "Bluetooth Share" force close occurs when bluetooth share the playing video in messaging.
The repro procedures and attachments is adhere.
1. Launch ""Messaging
2. Open Message with attached Video File.
3. View the attached Video File by "Video Player"
4. Share the Video File with remote pnoe by "Bluetooth Share"
5. Send the file to remote phone by "Bluetooth Share"
6. Failed to send the video file.
7. Pop up "Unfortunately, Bluetooth Share has stopped."
After then whenever user try to use Bluetooth Share to send OPP file, DUT would pop up the step.7 message all the time.
Even we reboot the phone, user would always encounter with this problem all the time.

Please refer to the attached images and related ddms log for further information.
Thank you.
BR
David
圖檔

admin
系統管理員
文章: 82
註冊時間: 2013年 4月 5日, 21:16

Re: 00913268 FATAL EXCEPTION: BtOpp Transfer Handler

文章 admin » 2013年 4月 6日, 17:47

Comment

Created By: Wei-Ting Hsiao (7/15/2012 10:52 PM)
Hi David,

I have gone through the logcat you provided and agree with your analysis. This exception is only related to SQLlite database and nothing related to BT OPP. BT OPP is just trying to query MMS content provider to construct the file info. As you can also find other exception log right before the point you refer:

01-06 05:47:10.289: E/DatabaseUtils(529): at com.android.providers.telephony.MmsProvider.query(MmsProvider.java:202)
01-06 05:47:10.289: E/DatabaseUtils(529): at android.content.ContentProvider$Transport.query(ContentProvider.java:178)
01-06 05:47:10.289: E/DatabaseUtils(529): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
01-06 05:47:10.289: E/DatabaseUtils(529): at android.os.Binder.execTransact(Binder.java:338)
01-06 05:47:10.289: E/DatabaseUtils(529): at dalvik.system.NativeStart.run(Native Method)

Could you please check with your MMS team to ask them look into this exception? There is nothing we can do in BT side.

Thank you,

Richard




Created By: David Lan (7/13/2012 2:46 AM)
Dear Richard,

It seems the "force close Bluetooth Share" mainly came from *\packages\apps\Bluetooth\AndroidManifest.xml allowed MMS access to the Bluetooth Share Manager adhere.
#24
<uses-permission android:name="android.permission.READ_SMS"></uses-permission>
<uses-permission android:name="android.permission.WRITE_SMS"></uses-permission>

Refer to the error message of DatabaseUtils in log adhere
android.database.sqlite.SQLiteException: no such column: _display_name: , while compiling: SELECT _display_name, _size FROM part WHERE (_id=2) ORDER BY seq

The Activity try to get the data of _display_name column from the database of related (MMS?) Content Provider via ContentResolver, yet there is not any _display_name column in the database of "//mms/part/2" Content Provider, and result in this FATAL EXCEPTION: BtOpp Transfer Handler.

Do you think it is a problem by MMS itself?
BR
David




Created By: David Lan (7/13/2012 12:54 AM)
Dear Richard,
How nice to see you.
Please infomr me if you happen to need any further information.
Have a nice day.
BR
David




Created By: Wei-Ting Hsiao (7/13/2012 12:47 AM)
Hi David,

Will work with you on this issue.

Richard
圖檔

回覆文章