[ICS] [REQUEST] A Vanilla ICS messaging app - Galaxy S II Themes and Apps

[ICS] [REQUEST] A Vanilla ICS messaging app - Galaxy S II Themes and Apps

I'd like to ask for your help with finding a Vanilla ICS messaging app that:
Works on our SGS2 (or, ideally, cross-device)
Handles merged SNS profiles correctly
Allows me to disable automatic SMS -> MMS conversion
Here's what we've got at the moment:
Android 4 ICS Messaging SMS by Tim Hutt
The only thing this port does right is that it works. Other than that it doesn't allow you to disable MMS conversion and it appears to be unable to handle contacts correctly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ICS Messages by apptechbuzz
This one handles contacts correctly, but doesn't work. After having attempted to open a thread, the app crashes.
HTC Evo 3D 4.0+ Mms.apk dark themed by netwokz
This one is a true beauty. It does everything from looking slick through allowing me to disable MMS conversion and handling merged contacts correctly:
But it does seem to be missing the same dependancy as the aforementioned ICS Messages app, since it crashes once one tries to open a thread. Words can't do justice to how much I'd like to see a functional port of this app.
And that's about as far as vanilla messaging app ports I was able to find go. I hope some of you were luckier or savvier in this regard and will share their findings with us here.

No suggestions? I must say I'm pretty disappointed. Are all of you just happy using the stock app or do you all use Handcent / GoSMS? I won't lie, these apps do fit the bill, but I personally find them a tad too bloaty. I'm looking for a single-purpose simple app which would do what's needed. You can't deny the stock Samsung app the simplicity, true, but it doesn't really fullfil one's needs - see the original post as for why I believe that is. The stock google app, on the other hand, seems perfect.

I'm in the same boat as you...
Was using the Andorid 4 ICS one, but keep going back to the stock sammy one as it does the job without issues. Just wish I could change theme (like in early gb roms) or replace completely with stock ICS
I tried handcent/gosms, but they did too much

http://forum.xda-developers.com/showthread.php?t=1531422
this one seems for work on my galaxy sII. backup your mms.apk in system/app and then flash this zip.
it's missing a few things imo (changing vibration types) but all in all works well and it's good looking

ogk-slay said:
http://forum.xda-developers.com/showthread.php?t=1531422
this one seems for work on my galaxy sII. backup your mms.apk in system/app and then flash this zip.
it's missing a few things imo (changing vibration types) but all in all works well and it's good looking
Click to expand...
Click to collapse
Strange, I still get crashes as I try to open a thread. Running the XXLPW 4.0.3 stock FW with Siyah kernel. I installed the ICS Messages app by apptechbuzz, invoked the error and captured the log:
Code:
V/MmsProvider( 8956): Query uri=content://mms/drafts, match=6
V/MmsSmsProvider( 8956): called query()
I/SqliteDatabaseCpp( 8956): sqlite returned: error code = 1, msg = no such column: date_sent, db=xxx
E/DatabaseUtils( 8956): Writing exception to parcel
E/DatabaseUtils( 8956): android.database.sqlite.SQLiteException: no such column: date_sent: , while compiling: SELECT transport_type, _id, thread_id, address, body, date, date_sent, read, type, status, locked, error_code, sub, sub_cs, date, date_sent, read, m_type, msg_box, d_rpt, rr, err_type, locked FROM (SELECT DISTINCT date * 1 AS normalized_date, 'sms' AS transport_type, _id, thread_id, address, body, date, date_sent, read, type, status, locked, error_code, NULL AS sub, NULL AS sub_cs, date, date_sent, read, NULL AS m_type, NULL AS msg_box, NULL AS d_rpt, NULL AS rr, NULL AS err_type, locked FROM sms WHERE (thread_id = 75 AND (type != 3)) UNION SELECT DISTINCT date * 1000 AS normalized_date, 'mms' AS transport_type, pdu._id, thread_id, NULL AS address, NULL AS body, date, date_sent, read, NULL AS type, NULL AS status, locked, NULL AS error_code, sub, sub_cs, date, date_sent, read, m_type, msg_box, d_rpt, rr, err_type, locked FROM pdu LEFT JOIN pending_msgs ON pdu._id = pending_msgs.msg_id WHERE (thread_id = 75 AND msg_box != 3 AND (msg_box != 3 AND (m_type = 128 OR m_type = 132 OR m_type = 130))) UNION SELECT DISTINCT date * 1 AS normalized_date, 'wpm' AS transport_type, _id, thread_id, NULL AS address, body, date, date_sent, read, type, NULL AS status, locked, NULL AS error_code, NULL AS sub, NULL AS sub_cs, date, date_sent, read, NULL AS m_type, NULL AS msg_box, NULL AS d_rpt, NULL AS rr, NULL AS err_type, locked FROM wpm WHERE (thread_id = 75) ORDER BY normalized_date ASC)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteCompiledSql.native_compile(Native Method)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteCompiledSql.<init>(SQLiteCompiledSql.java:68)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteProgram.compileSql(SQLiteProgram.java:143)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteProgram.compileAndbindAllArgs(SQLiteProgram.java:361)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:127)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:94)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:53)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:47)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1690)
E/DatabaseUtils( 8956): at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1664)
E/DatabaseUtils( 8956): at com.android.providers.telephony.MmsSmsProvider.getConversationMessages(MmsSmsProvider.java:1509)
E/DatabaseUtils( 8956): at com.android.providers.telephony.MmsSmsProvider.query(MmsSmsProvider.java:423)
E/DatabaseUtils( 8956): at android.content.ContentProvider$Transport.query(ContentProvider.java:178)
E/DatabaseUtils( 8956): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
E/DatabaseUtils( 8956): at android.os.Binder.execTransact(Binder.java:338)
E/DatabaseUtils( 8956): at dalvik.system.NativeStart.run(Native Method)
W/AsyncQuery(12392): Exception thrown during handling EVENT_ARG_QUERY
W/AsyncQuery(12392): android.database.sqlite.SQLiteException: no such column: date_sent: , while compiling: SELECT transport_type, _id, thread_id, address, body, date, date_sent, read, type, status, locked, error_code, sub, sub_cs, date, date_sent, read, m_type, msg_box, d_rpt, rr, err_type, locked FROM (SELECT DISTINCT date * 1 AS normalized_date, 'sms' AS transport_type, _id, thread_id, address, body, date, date_sent, read, type, status, locked, error_code, NULL AS sub, NULL AS sub_cs, date, date_sent, read, NULL AS m_type, NULL AS msg_box, NULL AS d_rpt, NULL AS rr, NULL AS err_type, locked FROM sms WHERE (thread_id = 75 AND (type != 3)) UNION SELECT DISTINCT date * 1000 AS normalized_date, 'mms' AS transport_type, pdu._id, thread_id, NULL AS address, NULL AS body, date, date_sent, read, NULL AS type, NULL AS status, locked, NULL AS error_code, sub, sub_cs, date, date_sent, read, m_type, msg_box, d_rpt, rr, err_type, locked FROM pdu LEFT JOIN pending_msgs ON pdu._id = pending_msgs.msg_id WHERE (thread_id = 75 AND msg_box != 3 AND (msg_box != 3 AND (m_type = 128 OR m_type = 132 OR m_type = 130))) UNION SELECT DISTINCT date * 1 AS normalized_date, 'wpm' AS transport_type, _id, thread_id, NULL AS address, body, date, date_sent, read, type, NULL AS status, locked, NULL AS error_code, NULL AS sub, NULL AS sub_cs, date, date_sent, read, NULL AS m_type, NULL AS msg_box, NULL AS d_rpt, NULL AS rr, NULL AS err_type, locked FROM wpm WHERE (thread_id = 75) ORDER BY normalized_date ASC)
W/AsyncQuery(12392): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:179)
W/AsyncQuery(12392): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
W/AsyncQuery(12392): at android.content.ContentProviderProxy.query(ContentProviderNative.java:358)
W/AsyncQuery(12392): at android.content.ContentResolver.query(ContentResolver.java:311)
W/AsyncQuery(12392): at android.content.AsyncQueryHandler$WorkerHandler.handleMessage(AsyncQueryHandler.java:79)
W/AsyncQuery(12392): at android.os.Handler.dispatchMessage(Handler.java:99)
W/AsyncQuery(12392): at android.os.Looper.loop(Looper.java:137)
W/AsyncQuery(12392): at android.os.HandlerThread.run(HandlerThread.java:60)
V/MmsSmsProvider( 8956): called query()
D/AndroidRuntime(12392): Shutting down VM
W/dalvikvm(12392): threadid=1: thread exiting with uncaught exception (group=0x40c2e1f8)
E/AndroidRuntime(12392): FATAL EXCEPTION: main
E/AndroidRuntime(12392): java.lang.NullPointerException
E/AndroidRuntime(12392): at com.mms.ics.ext.ui.ComposeMessageActivity$BackgroundQueryHandler.onQueryComplete(ComposeMessageActivity.java:3844)
E/AndroidRuntime(12392): at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
E/AndroidRuntime(12392): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(12392): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(12392): at android.app.ActivityThread.main(ActivityThread.java:4507)
E/AndroidRuntime(12392): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(12392): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(12392): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/AndroidRuntime(12392): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
E/AndroidRuntime(12392): at dalvik.system.NativeStart.main(Native Method)
android.database.sqlite.SQLiteException: no such column: date_sent
Anyone has an idea what might be causing the problem? Is my sms db somehow broken?
That seems to be my problem only, though, so consider the aforementioned Dark themed Mms.apk to be working. Given the fact that it supports vibration patterns, emoji and other stuff, I suppose it might be worth giving a whirl.

Related

[Q] com.android.mms stopped unexpectedly - missing db table!

I am suddenly unable to send og view messages on my HTC Desire Z, I just get a popup saying com.android.mms has stopped unexpectedly.
Connected the device to my computer, and found this in the logcat:
Code:
01-06 11:11:01.812: INFO/Database(1433): sqlite returned: error code = 1, msg = no such table: contact_threads
01-06 11:11:01.832: ERROR/SqliteWrapper(12609): Catch a SQLiteException when query:
android.database.sqlite.SQLiteException: no such table: contact_threads: , while compiling: SELECT _id, message_count, recipient_ids, date, read, snippet, snippet_cs, error, unread_count, recipient_address, priority, type, transport_type, msg_box, locked, name, err_type FROM contact_threads WHERE htc_category=0 AND (_id IN (SELECT contact_id FROM contacts WHERE thread_id IN (SELECT DISTINCT thread_id FROM pdu WHERE htc_category=0 AND (msg_box != 3 AND (m_type = 128 OR m_type = 132 OR m_type = 130)) UNION SELECT DISTINCT thread_id FROM sms WHERE htc_category=0 AND (type != 3)))) ORDER BY date DESC
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:158)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
at android.content.ContentProviderProxy.bulkQueryInternal(ContentProviderNative.java:372)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:408)
at android.content.ContentResolver.query(ContentResolver.java:245)
at com.google.android.mms.util.SqliteWrapper.query(SqliteWrapper.java:112)
at com.android.mms.util.MmsAsyncQueryHandler$MmsWorkerHandler.handleMessage(MmsAsyncQueryHandler.java:93)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:143)
at android.os.HandlerThread.run(HandlerThread.java:60)
01-06 11:11:01.832: DEBUG/ConversationListAdapter(12609): onQueryComplete, the cursor is null or token changed.
I read somewhere that I can solve this by deleteing the messages database and the files with the content. Anybody who can verify this (I would like to keep my messages if possible, but itis not possible then ok).
Maybe I could just add the 'contact_threads' table again by sql?
Or if anybody has any other hints on how to solve this, please forward me in the right direction.
I'm new to android hacking, but looking at this as an opportunity to learn

Errors during booting in logcat - should I be worried?

Hi all, I'm new in this forum. When booting with the logcat on, I see several errors appearing:
(1) First error:
I/dalvikvm( 99): Zip is good, but no classes.dex inside, and no .odex file in the same directory
W/PackageManager( 99): Exception reading jar: /system/framework/com.htc.resources.apk
W/PackageManager( 99): java.io.IOException: /system/framework/com.htc.resources.apk
W/PackageManager( 99): at dalvik.system.DexFile.isDexOptNeeded(Native Method)
W/PackageManager( 99): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:908)
W/PackageManager( 99): at com.android.server.PackageManagerService.main(PackageManagerService.java:686)
W/PackageManager( 99): at com.android.server.ServerThread.run(SystemServer.java:144)
(2) Second error:
E/DatabaseUtils( 205): Writing exception to parcel
E/DatabaseUtils( 205): android.database.sqlite.SQLiteException: no such column: phonetic_name: , while compiling: SELECT _id, display_name, starred, photo_id, has_phone_number, lookup, ext_account_Type, status_update_id FROM contacts WHERE ( (in_visible_group=1) AND has_phone_number=1) ORDER BY phonetic_name COLLATE LOCALIZED ASC, display_name COLLATE LOCALIZED ASC
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteCompiledSql.native_compile(Native Method)
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteCompiledSql.compile(SQLiteCompiledSql.java:91)
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteCompiledSql.<init>(SQLiteCompiledSql.java:64)
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:80)
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:46)
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:53)
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1412)
E/DatabaseUtils( 205): at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:351)
E/DatabaseUtils( 205): at com.android.providers.contacts.HtcContactsProvider2.query(HtcContactsProvider2.java:4071)
E/DatabaseUtils( 205): at android.content.ContentProvider$Transport.bulkQuery(ContentProvider.java:156)
E/DatabaseUtils( 205): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:134)
E/DatabaseUtils( 205): at android.os.Binder.execTransact(Binder.java:288)
E/DatabaseUtils( 205): at dalvik.system.NativeStart.run(Native Method)
(3) Third error:
W/System.err( 505): java.lang.NullPointerException
W/System.err( 505): at com.paypal.android.a.h.a(Unknown Source)
W/System.err( 505): at com.paypal.android.a.a.j(Unknown Source)
W/System.err( 505): at com.paypal.android.a.f.run(Unknown Source)
Should I be worried about them?
First one seems to be an error in a standard HTC app.
Second one seems to be related to my contacts missing a field?
Third one seems related to paypal (why???) I don't have paypal.
thank u for any help

It is normal to get warnings, which 1 and 3 are. It is not so normal to get an error, but as long as your phone is working and not having any problems, it is something you can ignore

FF18 Leak (OTA) Bluetooth Panasonic Home phone

I have a panasonic th12 home phone base that normally my phone connects to when I am at home over bluetooth. This allows me to use regular handsets while in the house to make / receive phone calls. I just updated to the FF18 from sfhub's odin and now my device no longer will connect the home phone base. It pairs but it will not stay connected or allow me to check the box for phone calls as well. Any ideas? is this a bluetooth bug?

Every time I flash I have to pair my phone with car again. I typically delete device profile from phone, delete phone profile from device, change bluetooth name of phone, pair phone with device under new name. Finally after paired wait for message to pop up on phone asking if device has permission to access your stuff and check box for always allow.

Yes my phone does the same for Microsoft sync in my vehicle but it will not connect with my home phone.
EDIT: I have a couple of logcat during the time i tried to connect my device to the base if that helps anything?
Code:
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:conn_complete() status 0x00
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/src/adapter.c:adapter_get_device() 00:80:F0:8F:61:B6
V/BluetoothEventLoop.cpp( 1910): event_filter: Received signal org.bluez.Device:PropertyChanged from /org/bluez/2534/hci0/dev_00_80_F0_8F_61_B6
D/BluetoothEventLoop( 1910): Device property changed: 00:80:F0:8F:61:B6 property: Connected value: true
I/BluetoothService( 1910): ACL connected, mAclLinkCount = 1
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:remote_features_information() hci0 status 0
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:remote_name_information() hci0 status 0
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:link_key_request() hci0 dba 00:80:F0:8F:61:B6
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:get_auth_info() hci0 dba 00:80:F0:8F:61:B6
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:link_key_request() kernel auth requirements = 0x04
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:link_key_request() Matching key found
I//system/bin/bluetoothd( 2530): bluetoothd[2534]: external/bluetooth/bluez/plugins/hciops.c:link_key_request() link key type 0x00
W/ActivityManager( 1910): Permission Denial: receiving Intent { act=android.bluetooth.device.action.ACL_CONNECTED flg=0x10000010 (has extras) } to com.locationlabs.v3client requires android.permission.BLUETOOTH due to sender android (uid 1000)
V/BluetoothEventManager( 4127): Received android.bluetooth.device.action.UUID
D/Bluetooth HSHFP( 2156): SDP UUID: TYPE_HANDSFREE
E/CachedBluetoothDevice( 4127): updating profiles for Base TH12
V/CachedBluetoothDevice( 4127): Class: 620210
V/CachedBluetoothDevice( 4127): UUID:
V/CachedBluetoothDevice( 4127): 0000111e-0000-1000-8000-00805f9b34fb
E/CachedBluetoothDevice( 4127): onUuidChanged: Time since last connect2151
D/CachedBluetoothDevice( 4127): Command sent successfully:CONNECT Address:00:80:F0:8F:61:B6 Profile:HEADSET
D/CachedBluetoothDevice( 4127): Preferred profiles = 1
D/BluetoothUtils( 2156): isHeadsetAllowedBySecurityPolicy
V/BT HSHFP( 2156): waitForAsyncConnectNative
V/BT HSHFP( 2156): connectAsyncNative
I/BT HSHFP( 2156): Created RFCOMM socket fd 125.
I/BT HSHFP( 2156): async connect is in progress (Operation now in progress)
V/BT HSHFP( 2156): Remaining time 486ms
V/BT HSHFP( 2156): select() returned 2.
E/BT HSHFP( 2156): RFCOMM async connect() error: Connection refused (111), nr = -1
V/BT HSHFP( 2156): disconnectNative
D/BluetoothService( 1910): CONNECTION_STATE_CHANGE: : 1 -> 0
V/BluetoothEventManager( 4127): Received android.bluetooth.headset.profile.action.CONNECTION_STATE_CHANGED
I/BluetoothDeviceProfileState( 1910): Entering ACL Connected state with: 102
D/BluetoothPbap( 1910): disconnect()
Looks like someone on CM had issues with this as well, but it eventually worked... mine doesnt
http://forum.cyanogenmod.com/topic/41497-bluetooth-wont-auto-connect/

Maybe someone can even point me in the right direction as to how to debug this situation? I have a development environment up for apps, but havent ever explored the base source code. If anyone has any thoughts it would truly be appreciated.
Its really makes me made because I had a similar problem with my last phone, the HTC hero. It got to the point you wait for all of these updates and then I had to limit my phone to like andorid 1.5 otherwise my phone would not connect. Its should be a bigger issue only because users who are not on xda would be screwed and could not rollback to a previous Android release. At lease this community exists so that I can go back if needed. As of right now I'm liking the new ics on this phone and will be very disappointed if I have to to back to GB just for this.

How to format blank cards to NDEF properly?

I've bought some blank Mini S20 NFC cards after I mistakenly locked some cards I bought a few weeks ago. (That excel spreadsheet is a bit tricky to understand...) Anyway, I finally get these blank cards since it is my understanding that 4.0.3+ works fine for formatting blank cards to NDEF. However, I am on Jellybean, both 4.1.1 on my N7 and the latest Jellybro build on my toroplus. Is this the reason my cards will not format with NXP Tagwriter? Do I need to roll-back to 4.0.3+, or am I out of luck on another batch of cards?
http://code.google.com/p/android/issues/detail?id=22258

Straussberg said:
I've bought some blank Mini S20 NFC cards after I mistakenly locked some cards I bought a few weeks ago. (That excel spreadsheet is a bit tricky to understand...) Anyway, I finally get these blank cards since it is my understanding that 4.0.3+ works fine for formatting blank cards to NDEF. However, I am on Jellybean, both 4.1.1 on my N7 and the latest Jellybro build on my toroplus. Is this the reason my cards will not format with NXP Tagwriter? Do I need to roll-back to 4.0.3+, or am I out of luck on another batch of cards?
http://code.google.com/p/android/issues/detail?id=22258
Click to expand...
Click to collapse
No, The issue was fixed in 4.0.3. Jelly Bean formats blank tags just fine.
NXP's app was doing manual formatting for some time to get around the bug in ICS. They may not have set up formatting for this IC. Are these the tags? http://www.buynfctags.com/nfc-card-mini-s20-white.html
It's entirely possible they are not enumerating the proper techs in Android to be usable with the NDEF libraries. Grab NFC Tag Info and read the tag. Post the XML file (menu -> save) and I'll take a look at what's being enumerated (essentially you are looking for NdefFormatable).

Thanks for the quick reply! Here is a copy of the tag XML.
https://www.box.com/shared/ccda3faf686d3be55f1b
ETA: It does have NdefFormatable.
Code:
android.nfc.tech.MifareClassic,
android.nfc.tech.NdefFormatable,
android.nfc.tech.NfcA
It also won't format with NFC ReTag Free.
Sent from my Galaxy Nexus using xda app-developers app

Straussberg said:
Thanks for the quick reply! Here is a copy of the tag XML.
https://www.box.com/shared/ccda3faf686d3be55f1b
ETA: It does have NdefFormatable.
Code:
android.nfc.tech.MifareClassic,
android.nfc.tech.NdefFormatable,
android.nfc.tech.NfcA
It also won't format with NFC ReTag Free.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Try creating a shot URL or text tag to format it NDEF. Any chance you can grab the logcat output when it is trying to format?
Sent from my Galaxy Nexus using xda premium

krohnjw said:
Try creating a shot URL or text tag to format it NDEF. Any chance you can grab the logcat output when it is trying to format?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
With NXP TagWriter
Code:
I/ActivityManager( 307): START {cmp=com.nxp.nfc.tagwriter/.activities.WriteParametersActivity (has extras) u=0} from pid 5603
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): Displayed com.nxp.nfc.tagwriter/.activities.WriteParametersActivity: +287ms
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
I/ActivityManager( 307): START {act=com.nxp.nfc.tagwriter.WRITE cmp=com.nxp.nfc.tagwriter/.activities.WriterActivity (has extras) u=0} from pid 5603
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): Displayed com.nxp.nfc.tagwriter/.activities.WriterActivity: +217ms
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NfcDispatcher( 578): dispatch tag: TAG: Tech [android.nfc.tech.MifareClassic, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable] message: null
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): START {act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.nxp.nfc.tagwriter/.activities.WriterActivity (has extras) u=0} from pid -1
W/ActivityManager( 307): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.nxp.nfc.tagwriter/.activities.WriterActivity (has extras) }I/NfcDispatcher( 578): matched TAG override
D/NfcDispatcher( 578): Set Foreground Dispatch
V/AudioManager( 5603): shouldVibrate, group: a126d48a-aaef-47c4-baed-7f0e44aeffe5 mode: DEFAULT
W/WVMExtractor( 124): Failed to open libwvm.so
V/AudioManager( 5603): shouldVibrate, group: a126d48a-aaef-47c4-baed-7f0e44aeffe5 mode: DEFAULT
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NativeNfcTag( 578): Tag lost, restarting polling loop
With NFC ReTag FREE:
Code:
I/ActivityManager( 307): START {cmp=com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag u=0} from pid 5975
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): Displayed com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag: +174ms
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NfcDispatcher( 578): dispatch tag: TAG: Tech [android.nfc.tech.MifareClassic, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable] message: null
I/ActivityManager( 307): START {act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag (has extras) u=0} from pid -1
W/ActivityManager( 307): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag (has extras) }
I/NfcDispatcher( 578): matched TAG override
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
W/System.err( 5975): java.io.IOException
W/System.err( 5975): at android.nfc.tech.NdefFormatable.format(NdefFormatable.java:132)
W/System.err( 5975): at android.nfc.tech.NdefFormatable.format(NdefFormatable.java:95)
W/System.err( 5975): at com.widgapp.NFC_ReTAG_FREE.Ndef_format_tag.a(Unknown Source)
W/System.err( 5975): at com.widgapp.NFC_ReTAG_FREE.aa.onClick(Unknown Source)
W/System.err( 5975): at com.android.internal.app.AlertController$ButtonHandler.handleMessage(AlertController.java:166)
W/System.err( 5975): at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err( 5975): at android.os.Looper.loop(Looper.java:137)
W/System.err( 5975): at android.app.ActivityThread.main(ActivityThread.java:4928)
W/System.err( 5975): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err( 5975): at java.lang.reflect.Method.invoke(Method.java:511)
W/System.err( 5975): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
W/System.err( 5975): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
W/System.err( 5975): at dalvik.system.NativeStart.main(Native Method)
I/Choreographer( 5975): Skipped 42 frames! The application may be doing too much work on its main thread.
W/InputMethodManagerService( 307): Window already focused, ignoring focus gain of: [email protected] attribute=null
D/NativeNfcTag( 578): Tag lost, restarting polling loop

Straussberg said:
With NXP TagWriter
Code:
I/ActivityManager( 307): START {cmp=com.nxp.nfc.tagwriter/.activities.WriteParametersActivity (has extras) u=0} from pid 5603
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): Displayed com.nxp.nfc.tagwriter/.activities.WriteParametersActivity: +287ms
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
I/ActivityManager( 307): START {act=com.nxp.nfc.tagwriter.WRITE cmp=com.nxp.nfc.tagwriter/.activities.WriterActivity (has extras) u=0} from pid 5603
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): Displayed com.nxp.nfc.tagwriter/.activities.WriterActivity: +217ms
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NfcDispatcher( 578): dispatch tag: TAG: Tech [android.nfc.tech.MifareClassic, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable] message: null
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): START {act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.nxp.nfc.tagwriter/.activities.WriterActivity (has extras) u=0} from pid -1
W/ActivityManager( 307): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.nxp.nfc.tagwriter/.activities.WriterActivity (has extras) }I/NfcDispatcher( 578): matched TAG override
D/NfcDispatcher( 578): Set Foreground Dispatch
V/AudioManager( 5603): shouldVibrate, group: a126d48a-aaef-47c4-baed-7f0e44aeffe5 mode: DEFAULT
W/WVMExtractor( 124): Failed to open libwvm.so
V/AudioManager( 5603): shouldVibrate, group: a126d48a-aaef-47c4-baed-7f0e44aeffe5 mode: DEFAULT
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NativeNfcTag( 578): Tag lost, restarting polling loop
With NFC ReTag FREE:
Code:
I/ActivityManager( 307): START {cmp=com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag u=0} from pid 5975
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
I/ActivityManager( 307): Displayed com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag: +174ms
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NativeNfcTag( 578): Check NDEF Failed - status = 255
D/NfcDispatcher( 578): dispatch tag: TAG: Tech [android.nfc.tech.MifareClassic, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable] message: null
I/ActivityManager( 307): START {act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag (has extras) u=0} from pid -1
W/ActivityManager( 307): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { act=android.nfc.action.TAG_DISCOVERED flg=0x20000000 cmp=com.widgapp.NFC_ReTAG_FREE/.Ndef_format_tag (has extras) }
I/NfcDispatcher( 578): matched TAG override
D/NfcDispatcher( 578): Set Foreground Dispatch
D/NfcDispatcher( 578): Set Foreground Dispatch
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
E/Tuna PowerHAL( 307): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
W/System.err( 5975): java.io.IOException
W/System.err( 5975): at android.nfc.tech.NdefFormatable.format(NdefFormatable.java:132)
W/System.err( 5975): at android.nfc.tech.NdefFormatable.format(NdefFormatable.java:95)
W/System.err( 5975): at com.widgapp.NFC_ReTAG_FREE.Ndef_format_tag.a(Unknown Source)
W/System.err( 5975): at com.widgapp.NFC_ReTAG_FREE.aa.onClick(Unknown Source)
W/System.err( 5975): at com.android.internal.app.AlertController$ButtonHandler.handleMessage(AlertController.java:166)
W/System.err( 5975): at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err( 5975): at android.os.Looper.loop(Looper.java:137)
W/System.err( 5975): at android.app.ActivityThread.main(ActivityThread.java:4928)
W/System.err( 5975): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err( 5975): at java.lang.reflect.Method.invoke(Method.java:511)
W/System.err( 5975): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
W/System.err( 5975): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
W/System.err( 5975): at dalvik.system.NativeStart.main(Native Method)
I/Choreographer( 5975): Skipped 42 frames! The application may be doing too much work on its main thread.
W/InputMethodManagerService( 307): Window already focused, ignoring focus gain of: [email protected] attribute=null
D/NativeNfcTag( 578): Tag lost, restarting polling loop
Click to expand...
Click to collapse
Both are using Android's libraries and both are failing throwing an IO Exception from inside of the NdefFormatable class formatting to NDEF using the default key (FFFFFF). It sounds like the tags may not be supported on the Android side.

[ROM][UNOFFICIAL][GAPPS][13] ArrowOS for Fire HD10 9th gen (maverick)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS
This is an alpha build, not intended for use as a daily driver!
This ROM requires the temporary unlock to work, along with TWRP!
Your device must be on the 7.3.1.0 launch firmware!
Code:
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Everything except those mentioned on the not working list.
WHAT DOESN'T WORK?
Bluetooth audio
Hardware codecs
Brightness adjustment is buggy
SELinux permissive
Known performance issues
com.android.phone crashes from time to time
DRM
You tell me!
DOWNLOADS
Click here to Download
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
GPL compliance:
ROM Source- https://github.com/ArrowOS
Kernel Source- https://github.com/amazon-maverick-dev/android_kernel_amazon_mt8183 (branch: 13.0-new)
Device Source- https://github.com/amazon-maverick-dev/android_device_amazon_maverick

Reserved #2

Reserved #3

Installed it on my device. Looking good! Are the bluetooth issues isolated to Bluetooth audio? I was unable to pair a bluetooth game controller or a mouse.

moomph said:
Installed it on my device. Looking good! Are the bluetooth issues isolated to Bluetooth audio? I was unable to pair a bluetooth game controller or a mouse.
Click to expand...
Click to collapse
Hey, it's possible that there are more Bluetooth issues than meets the eye, I didn't really do much real world testing since this is in very early stages.
I'd be happy to have a look if you could attach a logcat while trying to pair the game controller.

Hey, thanks for getting back. To preface, when I attempt to pair the controller, the UI in the "Connected devices" screen behaves as if it is connected for a second, but the controller disconnects and moves down to the list of "Saved devices". I saw similar behavior with a bluetooth mouse - it seems to pair, but then it disconnects immediately.
Simply running logcat results in a deluge of log messages - lots of errors amongst them.
When I run logcat | grep bluetooth and attempt to pair the controller, this is what I see. Pardon how massive this is:
Code:
09-23 11:44:53.264 22003 22214 I bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:113 drop: Dropping event MAX_SLOTS_CHANGE
09-23 11:44:53.281 22003 22214 I bluetooth: packages/modules/Bluetooth/system/main/shim/acl.cc:525 OnReadClockOffsetComplete: UNIMPLEMENTED
09-23 11:44:53.287 21733 21759 I ActivityManager: Start proc 10056:com.google.android.projection.gearhead:shared/u0a54 for broadcast {com.google.android.projection.gearhead/com.google.android.apps.auto.wireless.bluetooth.WifiBluetoothReceiver}
09-23 11:44:53.403 21733 21904 I ActivityTaskManager: START u0 {act=android.bluetooth.device.action.PAIRING_REQUEST flg=0x10000000 cmp=com.android.settings/.bluetooth.BluetoothPairingDialog (has extras)} from uid 1000
09-23 11:44:53.514 21733 22058 D CoreBackPreview: Window{90ec256 u0 com.android.settings/com.android.settings.bluetooth.BluetoothPairingDialog}: Setting back callback OnBackInvokedCallbackInfo{[email protected]65, mPriority=0}
09-23 11:44:53.519 21733 22058 D CoreBackPreview: Window{97a6d06 u0 com.android.settings/com.android.settings.bluetooth.BluetoothPairingDialog}: Setting back callback OnBackInvokedCallbackInfo{[email protected]92, mPriority=0}
09-23 11:44:53.562 21733 21748 I ActivityTaskManager: Displayed com.android.settings/.bluetooth.BluetoothPairingDialog: +153ms
09-23 11:44:53.760 10056 10056 I GH.WifiBluetoothRcvr: Connection action: android.bluetooth.device.action.ACL_CONNECTED, device E4:17:D8:85:79:73
09-23 11:44:53.863 29843 30332 I BistoWorker: (REDACTED) bluetoothConnectionStateChanged. Action: %s
09-23 11:44:54.793 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 11:44:58.628 369 369 I HwBinder:369_3: type=1400 audit(0.0:16620973): avc: denied { call } for scontext=u:r:init:s0 tcontext=u:r:bluetooth:s0 tclass=binder permissive=1
09-23 11:44:58.632 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 11:44:59.775 21733 22688 D CoreBackPreview: Window{90ec256 u0 com.android.settings/com.android.settings.bluetooth.BluetoothPairingDialog}: Setting back callback null
09-23 11:44:59.787 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/vendor_specific_event_manager.cc:86 on_vendor_specific_event: Unhandled vendor specific event of type 0x52
09-23 11:44:59.787 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/vendor_specific_event_manager.cc:86 on_vendor_specific_event: Unhandled vendor specific event of type 0x52
09-23 11:44:59.788 21733 23979 W InputManager-JNI: Input channel object '90ec256 com.android.settings/com.android.settings.bluetooth.BluetoothPairingDialog (client)' was disposed without first being removed with the input manager!
09-23 11:44:59.860 21733 22058 D CoreBackPreview: Window{97a6d06 u0 com.android.settings/com.android.settings.bluetooth.BluetoothPairingDialog}: Setting back callback null
09-23 11:44:59.862 21733 22058 W InputManager-JNI: Input channel object '97a6d06 com.android.settings/com.android.settings.bluetooth.BluetoothPairingDialog (client)' was disposed without first being removed with the input manager!
09-23 11:45:00.152 21733 21758 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.bluetooth.device.action.UUID flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
09-23 11:45:00.152 21733 21758 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.bluetooth.device.action.UUID flg=0x10 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.broadcastreceiver.external.ExternalCommonBroadcastReceiver
09-23 11:45:00.152 21733 21758 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.bluetooth.device.action.UUID flg=0x10 (has extras) } to com.google.android.projection.gearhead/com.google.android.apps.auto.carservice.gmscorecompat.CarBluetoothReceiver
09-23 11:45:00.156 21733 21758 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.bluetooth.device.action.BOND_STATE_CHANGED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
09-23 11:45:00.156 21733 21758 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.bluetooth.device.action.BOND_STATE_CHANGED flg=0x10 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.broadcastreceiver.external.ExternalCommonBroadcastReceiver
09-23 11:45:00.157 10918 17585 I NearbyDiscovery: FastPairHandler: Received action android.bluetooth.device.action.UUID [CONTEXT service_id=49 ]
09-23 11:45:00.274 22003 22214 I bluetooth: packages/modules/Bluetooth/system/gd/hci/le_scanning_manager.cc:639 stop_scan: Scanning already stopped, return!
09-23 11:45:02.037 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 11:45:02.249 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 11:45:02.681 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 11:45:03.315 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 11:45:03.534 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 11:45:04.136 22003 22003 I bt_stack_manage: type=1400 audit(0.0:16623299): avc: denied { call } for scontext=u:r:bluetooth:s0 tcontext=u:r:init:s0 tclass=binder permissive=1
09-23 11:45:04.136 369 369 I HwBinder:369_3: type=1400 audit(0.0:16623300): avc: denied { call } for scontext=u:r:init:s0 tcontext=u:r:bluetooth:s0 tclass=binder permissive=1
09-23 11:45:04.219 22003 22230 E bluetooth: packages/modules/Bluetooth/system/stack/btm/btm_sco.cc:950 btm_sco_on_disconnected: Unable to find sco connection
09-23 11:45:04.245 29843 30332 I BistoWorker: (REDACTED) bluetoothConnectionStateChanged. Action: %s
09-23 11:45:06.296 22003 22003 I bt_stack_manage: type=1400 audit(0.0:16624639): avc: denied { call } for scontext=u:r:bluetooth:s0 tcontext=u:r:init:s0 tclass=binder permissive=1
09-23 11:45:06.299 22003 22214 I bluetooth: packages/modules/Bluetooth/system/gd/hci/le_scanning_manager.cc:639 stop_scan: Scanning already stopped, return!
09-23 11:45:06.300 369 369 I HwBinder:369_3: type=1400 audit(0.0:16624640): avc: denied { call } for scontext=u:r:init:s0 tcontext=u:r:bluetooth:s0 tclass=binder permissive=1

Did this again and saw some other logs relevant looking logs that perhaps I somehow missed in the first dump:
Code:
09-23 13:09:33.240 22003 22214 W bluetooth: packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:375 on_hci_event: Unhandled event of type 0xe5 (Unknown EventCode: 229)
09-23 13:09:33.467 22003 22230 W l2c_link: packages/modules/Bluetooth/system/stack/l2cap/l2c_link.cc:500 l2c_link_timeout: TODO: Remove this callback into bcm_sec_disconnect
09-23 13:09:33.467 22003 22230 I btm_acl : packages/modules/Bluetooth/system/stack/acl/btm_acl.cc:188 hci_btsnd_hcic_disconnect: Disconnecting peer:xx:xx:xx:xx:79:73 reason:Remote Terminated Connection comment:stack::l2cap::l2c_link::l2c_link_timeout All channels closed
09-23 13:09:33.562 22003 22230 E bluetooth: packages/modules/Bluetooth/system/stack/btm/btm_sco.cc:950 btm_sco_on_disconnected: Unable to find sco connection
09-23 13:09:33.562 22003 22230 I btm_acl : packages/modules/Bluetooth/system/stack/acl/btm_acl.cc:2569 btm_acl_iso_disconnected: ISO disconnection from GD, handle: 0x32, reason: 0x16
09-23 13:09:33.563 22003 22230 I btif_av : packages/modules/Bluetooth/system/btif/src/btif_av.cc:3409 btif_av_acl_disconnected: btif_av_acl_disconnected: Peer XX:XX:XX:XX:79:73 : ACL Disconnected
09-23 13:09:33.565 22003 22161 W BatteryService: getBatteryService(): service is NULL
09-23 13:09:33.604 26918 27235 I BistoWorker: (REDACTED) bluetoothConnectionStateChanged. Action: %s
09-23 13:09:33.611 26918 27027 I BistoWorker: (REDACTED) Failed to get bistoDeviceInfo %s
09-23 13:09:33.615 22003 22073 D BluetoothDatabase: getBondedDevicesOrdered: Invalid address for device LocalStorage
09-23 13:09:33.624 26982 26982 I NearbyDiscovery: onAclChange: state=DISCONNECTED, device=XX:XX:XX:XX:79:73 [CONTEXT service_id=49 ]
Also, I found that the telephony service was failing and infinitely restarting, causing the deluge of error logs. Running the following solved it:
am service-restart-backoff disable com.android.phone

After further testing with the Bluetooth mouse, looking at the logs and UI behavior, it appears that the pairing does succeed. The device remains listed within the section of currently paired devices, and when I turn off the mouse, the UI updates accordingly and new log messages appear indicating a disconnection. However, a mouse pointer never materializes on screen during connection.

Develop Bugs

welcome

[ICS] [REQUEST] A Vanilla ICS messaging app - Galaxy S II Themes and Apps

I'm in the same boat as you... Was using the Andorid 4 ICS one, but keep going back to the stock sammy one as it does the job without issues. Just wish I could change theme (like in early gb roms) or replace completely with stock ICS I tried handcent/gosms, but they did too much

http://forum.xda-developers.com/showthread.php?t=1531422 this one seems for work on my galaxy sII. backup your mms.apk in system/app and then flash this zip. it's missing a few things imo (changing vibration types) but all in all works well and it's good looking

Related

[Q] com.android.mms stopped unexpectedly - missing db table!

Errors during booting in logcat - should I be worried?

FF18 Leak (OTA) Bluetooth Panasonic Home phone

How to format blank cards to NDEF properly?

[ROM][UNOFFICIAL][GAPPS][13] ArrowOS for Fire HD10 9th gen (maverick)

Categories

Resources