Database Develop

Dev Help Needed: Building a custom ROM off Tattoo dump

Rom Developers help needed!
using JAC/Cyrowski boot.img and the system.img from tattoo, I managed to put together a ROM, however I get the following error message after installation
D/AndroidRuntime( 161): CheckJNI is OFF
I/dalvikvm( 161): DexOpt: Some deps went away
E/dalvikvm( 161): /system/framework/com.htc.framework.jar odex has stale dependencies
I/dalvikvm( 161): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
D/libc-abort( 161): abort() called in pid 161
I/DEBUG ( 52): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 52): Build fingerprint: 'htc_wwe/htc_tattoo/bahamas/bahamas:1.6/DRC79/70570:user/release-keys'
I have a feeling it has something to do with the boot.img as I am not using the one from Tattoo dump.

just looking at the logcat, try odexing htc.framework.jar and placing the odex file in the same folder as htc.framework.jar
you can odex the file by putting it on your sdcard and running:
su
dexopt-wrapper /sdcard/com.htc.framework.jar
Click to expand...
Click to collapse
this is just a guess of what you have to do. not 100% sure

Thanks alritewhadeva,
Will try your suggestion, however the framework folder already contains odex files.

Yes but I don't think theres an odex file for com.htc.framework.jar

All the files in the framework folder are odexed.

ViperOne + ElementalX dofstrim wakelock issue - solved

I am using unlocked and activated HTC One M7 sprint edition in GSM network, rooted. ViperOne appeared to be the best ROM for my device, along with brilliant ElementalX kernel. but as some other people I've suffered from dotfstrim kernel wakelock that usually came at nights when phone was charged and sleeping on the table.
I've found that trim file system service could be made manually using fstrim tool and starting from 4.3 trim events processed at the volume daemon (vold) triggered by idle maintenance event. that event is interesting thing, triggered only when battery charge is > 80% and phone was not active for more than 73 minutes, but not more than once per day. now I was almost sure that dofstrim orphaned wakelock was left by that event processing.
instead of waiting for next event, I did more research and found that event can be fired anytime by shell command:
am idle-maintenance
voila! wakelock was there. knowing that idle maintenance running vold internal procedure for trim, I've checked daemon sources and found the following:
fstrim.c //
......
#define FSTRIM_WAKELOCK "dofstrim"
......
SLOGI("Finished fstrim work.\n");
release_wake_lock(FSTRIM_WAKELOCK);
......
acquire_wake_lock(PARTIAL_WAKE_LOCK, FSTRIM_WAKELOCK);
......
//
so wakelock was set before trim process but never released. logfile shown me following:
E/Vold (32356): failed to open /fstab.m7
E/Vold (32356): Error reading configuration (No such file or directory)... continuing anyways
......
I/fstrim (32356): Starting fstrim work...
...and then.. boom!
F/libc (31832): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 32353 (vold)
I/DEBUG ( 248): Build fingerprint: 'htc/sprint_wwe/m7wls:4.4.2/KOT49H/325784.5:user/release-keys'
I/DEBUG ( 248): AM write failure (32 / Broken pipe)
I/DEBUG ( 248): Write to AM fail, close AM fd
I/DEBUG ( 248): Revision: '4'
I/DEBUG ( 248): pid: 31832, tid: 32353, name: vold >>> /system/bin/vold <<<
I/DEBUG ( 248): debuggerd: checkTellHTCSettings
I/DEBUG ( 248): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
I/DEBUG ( 248): r0 2a01abd5 r1 fffffff0 r2 00000003 r3 00000000
I/DEBUG ( 248): r4 2a02017c r5 2a025290 r6 00000000 r7 b6b28d08
I/DEBUG ( 248): r8 00000000 r9 2a018bf6 sl b6c282d4 fp b6fac2f4
I/DEBUG ( 248): ip 00000003 sp b6b28ce8 lr b6fd1de1 pc 2a00f6ca cpsr 200b0030
so vold crashed but orphaned wakelock remained and prevents phone from sleeping ((
in theory problem caused by additional protected partition that exists on sprint model only but I had no time for vold recompiling so I've created a quite straightforward hex patch that simply removes trim process. so wakelock released and everyone's happy. just a note. vold will not run trim anymore so it must be done manually from shell by fstrim tool or from UI by LagFix app like once per week.
attached archive contains new (patched) and old (original) vold files that you have to upload to device using adb or any other method:
adb push vold /system/bin/vold
make sure you have fixed vold permissions from terminal like
chmod 755 /system/bin/vold
or you risk to stop on boot screen.
ps. this night my phone spent only 2% of battery for 7 hours. radio + wifi was on. so it was sleeping well ))

Verizon M7 solution?
I have the same issue with the dofstrim kernel wakelock preventing my phone from going into deep sleep after a charging cycle. Will your solution also work for the Verizon M7? I am rooted with the NuSenseSIX rom and ElementalX kernel.

aewald73 said:
I have the same issue with the dofstrim kernel wakelock preventing my phone from going into deep sleep after a charging cycle. Will your solution also work for the Verizon M7? I am rooted with the NuSenseSIX rom and ElementalX kernel.
Click to expand...
Click to collapse
I'd say probably not.. it's best not to flash zip files which are for different variants (they have different partition maps). Try posting here.

Any chance you can post sort of a noob guide on this fix? I'm a little confused with the steps you already posted, and then the additional steps needed for the weekly fix. Thanks.

fachadick said:
Any chance you can post sort of a noob guide on this fix? I'm a little confused with the steps you already posted, and then the additional steps needed for the weekly fix. Thanks.
Click to expand...
Click to collapse
While I cannot guarantee it will work for you, heres what I did:
1.) Extract the vold file from the .zip to the adb directory
2.) Have adb installed
3.) Do this:
Code:
adb devices
adb root
adb remount
adb push vold /system/bin/vold
adb shell
su
chmod 755 /system/bin/vold
CTRL-C
adb remount
Reboot and it should work.

Viewing Magisk Manager apk file in a file explorer causes Fatal Signal

Simply viewing the Magisk Manager apk file (downloaded from APKmirror) causes the file explorer app to crash. The crash occurs when you are scrolling down the list of files and Magisk Manager apk is next to be shown.
Tested with Solid Explorer and CM13 Stock File Manager.
The offending apk files are:
Magisk Manager 5.1.1
Magisk Manager 5.1.0
The rest of the 5.0 release is untested. Currently have 4.3.3 installed and the apk does not cause any crashes.
Installing one of the offending apk's will severely mess up my phone. The phone will boot up and stay at a black screen (right when the lock screen is supposed to appear). Magisk uninstaller does NOT fix this boot up problem and I had to resort to re-flashing my ROM.
My setup:
Nexus 4
CM13.0 2016-12-21 Snapshot
Magisk Manger v4.3.3
MagiskSu v12.0
Here is the ADB log:
Code:
07-25 01:28:16.106 8548-8610/? I/SolidExplorer: pl.solidexplorer.thumbs.ThumbnailManager$FileThumbTask#run(ThumbnailManager.java:511)
07-25 01:28:16.106 8548-8610/? I/SolidExplorer: Cache size: 1006.27 KB
07-25 01:28:16.230 8548-8610/? I/SolidExplorer: pl.solidexplorer.thumbs.ThumbnailManager$FileThumbTask#run(ThumbnailManager.java:511)
07-25 01:28:16.230 8548-8610/? I/SolidExplorer: Cache size: 1.02 MB
07-25 01:28:16.316 8548-8610/? I/SolidExplorer: pl.solidexplorer.thumbs.ThumbnailManager$FileThumbTask#run(ThumbnailManager.java:511)
07-25 01:28:16.316 8548-8610/? I/SolidExplorer: Cache size: 1.05 MB
07-25 01:28:16.358 8548-8610/? A/libc: invalid address or address of corrupt block 0x430d87fe passed to dlfree
07-25 01:28:16.370 8548-8610/? A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xdeadbaad in tid 8610 (pool-3-thread-1)
07-25 01:28:16.371 736-736/? I/DEBUG: property debug.db.uid not set; NOT waiting for gdb.
07-25 01:28:16.371 736-736/? I/DEBUG: HINT: adb shell setprop debug.db.uid 100000
07-25 01:28:16.371 736-736/? I/DEBUG: HINT: adb forward tcp:5039 tcp:5039
07-25 01:28:16.473 736-736/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-25 01:28:16.473 736-736/? A/DEBUG: CM Version: '13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-mako'
07-25 01:28:16.473 736-736/? A/DEBUG: Build fingerprint: 'google/occam/mako:5.1.1/LMY48M/2167285:user/release-keys'
07-25 01:28:16.473 736-736/? A/DEBUG: Revision: '0'
07-25 01:28:16.473 736-736/? A/DEBUG: ABI: 'arm'
07-25 01:28:16.473 736-736/? A/DEBUG: pid: 8548, tid: 8610, name: pool-3-thread-1 >>> pl.solidexplorer2 <<<
07-25 01:28:16.473 736-736/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
07-25 01:28:16.515 736-736/? A/DEBUG: Abort message: 'invalid address or address of corrupt block 0x430d87fe passed to dlfree'
07-25 01:28:16.515 736-736/? A/DEBUG: r0 00000000 r1 00000000 r2 00000000 r3 00000002
07-25 01:28:16.515 736-736/? A/DEBUG: r4 430d87fe r5 deadbaad r6 b6d72f38 r7 98fcc000
07-25 01:28:16.515 736-736/? A/DEBUG: r8 430d8806 r9 9bc730cc sl b6cd38db fp b6cd38e4
07-25 01:28:16.516 736-736/? A/DEBUG: ip b6d6d5d8 sp 9bc72fb8 lr b6d3ecdf pc b6d3ecde cpsr 600f0030
07-25 01:28:16.524 736-736/? A/DEBUG: backtrace:
07-25 01:28:16.524 736-736/? A/DEBUG: #00 pc 00030cde /system/lib/libc.so (dlfree+1285)
07-25 01:28:16.524 736-736/? A/DEBUG: #01 pc 000157a9 /system/lib/libandroidfw.so (_ZN7android13ResStringPool6uninitEv+38)
07-25 01:28:16.524 736-736/? A/DEBUG: #02 pc 000164f9 /system/lib/libandroidfw.so (_ZN7android10ResXMLTree6uninitEv+14)
07-25 01:28:16.524 736-736/? A/DEBUG: #03 pc 00016517 /system/lib/libandroidfw.so (_ZN7android10ResXMLTreeD1Ev+4)
07-25 01:28:16.525 736-736/? A/DEBUG: #04 pc 00013263 /system/lib/libandroidfw.so (_ZN7android12AssetManager10getPkgNameEPKc+258)
07-25 01:28:16.525 736-736/? A/DEBUG: #05 pc 000132bf /system/lib/libandroidfw.so (_ZN7android12AssetManager18getBasePackageNameEj+62)
07-25 01:28:16.525 736-736/? A/DEBUG: #06 pc 0008967f /system/lib/libandroid_runtime.so
07-25 01:28:16.525 736-736/? A/DEBUG: #07 pc 737486e1 /data/dalvik-cache/arm/[email protected]@boot.oat (offset 0x1f93000)
07-25 01:28:16.554 736-736/? W/debuggerd: type=1400 audit(0.0:1525): avc: denied { search } for name="default" dev="tmpfs" ino=8252 scontext=u:r:debuggerd:s0 tcontext=u:object_r:storage_file:s0 tclass=dir permissive=0
07-25 01:28:17.416 1230-8698/? W/ActivityManager: Force finishing activity pl.solidexplorer2/pl.solidexplorer.SolidExplorer
07-25 01:28:17.417 736-736/? A/DEBUG: Tombstone written to: /data/tombstones/tombstone_02
07-25 01:28:17.417 736-736/? E/DEBUG: AM write failed: Broken pipe
07-25 01:28:17.418 1230-1250/? I/BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
07-25 01:28:17.502 1230-1403/? W/InputDispatcher: channel '5ab4980 pl.solidexplorer2/pl.solidexplorer.SolidExplorer (server)' ~ Consumer closed input channel or an error occurred. events=0x9
07-25 01:28:17.502 1230-1403/? E/InputDispatcher: channel '5ab4980 pl.solidexplorer2/pl.solidexplorer.SolidExplorer (server)' ~ Channel is unrecoverably broken and will be disposed!
07-25 01:28:17.511 1230-1241/? I/WindowState: WIN DEATH: Window{5ab4980 u0 pl.solidexplorer2/pl.solidexplorer.SolidExplorer}
07-25 01:28:17.511 1230-1241/? W/InputDispatcher: Attempted to unregister already unregistered input channel '5ab4980 pl.solidexplorer2/pl.solidexplorer.SolidExplorer (server)'
07-25 01:28:17.518 1230-8698/? W/ActivityManager: Exception thrown during pause
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:727)
at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:879)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:2992)
at com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:2848)
at com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:2828)
at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:12449)
at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:12320)
at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:13036)
at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:12541)
at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)
07-25 01:28:17.523 724-724/? E/lowmemorykiller: Error writing /proc/8548/oom_score_adj; errno=22
07-25 01:28:17.538 748-748/? I/Zygote: Process 8548 exited due to signal (11)
07-25 01:28:17.617 1230-4016/? I/ActivityManager: Process pl.solidexplorer2 (pid 8548) has died
07-25 01:28:17.674 1230-1412/? I/OpenGLRenderer: Initialized EGL, version 1.4

Corrupt downloads?
Delete the files and download again.
Edit: Since your file explorer crashes when viewing the thumbnails of the files, use terminal to delete them... The command is:
Code:
rm [I]<path-to-file>[/I]

Didgeridoohan said:
Corrupt downloads?
Delete the files and download again.
Edit: Since your file explorer crashes when viewing the thumbnails of the files, use terminal to delete them... The command is:
Code:
rm [I]<path-to-file>[/I]
Click to expand...
Click to collapse
SHA-256 and SHA-1 File hashes match the ones on APKmirror so no, the downloads are not corrupt.
Yes I can either delete using the terminal, or on a PC via USB connection, or in Downloads and long-press --> delete.

AndrewDam said:
SHA-256 and SHA-1 File hashes match the ones on APKmirror so no, the downloads are not corrupt.
Yes I can either delete using the terminal, or on a PC via USB connection, or in Downloads and long-press --> delete.
Click to expand...
Click to collapse
Still... Worth a shot deleting them and starting over.

Apk view crash
Same problem here on Moto G (titan) running on Mokee OS (based on cm13).
It is not the corrupt apk. And I also encountered same problem while trying to install Pixlr 3.0.2.apk.
The file explorer crashes, when about to browse that particular .apk file.
I once somehow installed Magisk Manager whilst crashing, after that the whole system went crazy! All the running apps started crashing continuously, even the Nova Launcher, the inbuilt Nox Launcher. EVERY SINGLE APP!
Then I powered down the phone, went to recovery and deleted the app manually.
But if try to install again, the problem kicks in!
And I also observed one more thing, no matter what, the app's icon is not displayed by the file manager. I tried the same thing with in-built file manager, which doesn't display the app icon, the file manager didnot crash this time. But if I install, BOOM! LITERALLY EVERYTHING STARTS TO CRASH!!

Same problem on my G2 Mini - fatal signal, file explorer crashing. When I installed the app, opening it caused soft reboot.

same here, using dual boot patcher when i tap the roms section, it crashed.. i found fatal signal in the logs
device: redmi note 3 sd (kenzo)
rom: nitrogen os
magisk 13.3

8.1 bluetooth issue

Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...

xduser1 said:
Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...
Click to expand...
Click to collapse
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.

xduser1 said:
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.
Click to expand...
Click to collapse
I have the same issue with every 8.1 build I have tried. I think LOS is less problematic and I have fewer disconnects reconnects. Glad I'm not the only one with the issue. I was going to flash back to stock to see if the issue persists, but I'm pretty sure Bluetooth is incomplete for the N6 and 8.1. Every ROM i have tried also misreports Bluetooth battery drain.

I can say, I use a Bluetooth headset and external gps and connect to my ODBII port all simultaneously without any disconnects. I'm using ABC for shamu and it's been rock solid. I also do not get misreported numbers.
If that's one of the rooms you've tried, and you've clean flashed, then think about trying inn safe mode. Maybe some app is interfering. Safe mode will reset your settings and desktop. You probably want to take a nandroid first.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Several data points:
On 8.1, I only experience this issue with this one car, all other bluetooth devices and cars that I've tried worked perfect.
I do not experience this issue with this car on 7.1.2..
All ROMs were clean flashed.
Also tried friend's Pixel 2 with stock 8.1, and it worked with this car without any issues.

signal 5 (SIGTRAP, code 1 (TRAP_BRKPT) error in Mi 9

Hi Experts,
I have an unlocked Chinese version Mi 9 with 8gb RAM/128gb storage. I have unlocked the device now and installed official global ROM on my Mi 9.
I am facing this error (details below) with many of the apps (even with stock MIUI). :crying::crying::crying:
The backtrace of this error for all the apps causing this error point to Chrome.apk
Error Details:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/cepheus/cepheus:9/PKQ1.181121.001/V10.2.3.0.PFAMIXM:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 24929, tid: 25124, name: Chrome_InProcGp >>> com.amazon.mShop.android.shopping <<<
signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0xd3f49450
r0 00000000 r1 c1c5393f r2 0000008d r3 40000000
r4 d4007b8c r5 be47f118 r6 d4007ba0 r7 e811ad8c
r8 bfa8ace0 r9 0000007e r10 00000006 r11 d13885f1
ip e8113d00 sp be47f070 lr e80e74b9 pc d321a96c
backtrace:
#00 pc 05f3d96c /system/app/Chrome/Chrome.apk (offset 0x452b000)
#01 pc 0008e4b5 /system/lib/libc.so (je_free+76)
#02 pc 0537d255 /system/app/Chrome/Chrome.apk (offset 0x452b000)
Can someone please please help me on how to resolve it?
Thanks.

Can someone please help?