Ever since I updated to coral-rp1a.201105.002, some time in the middle of the day I'll notice that my notifications no longer vibrate and I have no haptic feedback. Toggling the settings for feedback or asking Tasker to directly create a vibrate pattern do nothing. Restarting the phone fixes it... until maybe 12-24 hours later where it might happen again. It's hard to tell when it starts since I have to actively use the phone to know for sure. I feel like it happens about once a day, though it might have skipped a day somewhere.
Unfortunately, running rooted, with EdXposed gives a lot of additional vectors for where the issue could come from. I'm not sure I'm at the point where I want to disable things to figure it out. Doesn't seem to be A11 specific as it was fine before the November update. A11 just feels less polished than A10 in several ways and somehow it's getting worse with updates. I wonder if it's time for my phone's first full wipe since I got it.
Mostly I'm wondering if anyone else has seen this before... where it will happen almost daily. Next time it happens, I might look into logcat to see if something is mentioned somehow.
Well, logcat is definitely angry... I'm not sure what to make of it, though.
11-18 15:01:30.882 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:01:30.883 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:01:30.985 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:31.091 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:32.057 2008 2055 E JobScheduler.Background: App com.google.android.gms became active but still in NEVER bucket
11-18 15:01:39.057 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10216 (10)0x30000->*job*/com.handmark.expressweather/com.moengage.core.DataSyncJob
11-18 15:01:39.141 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10216 (10)0x30000->*job*/com.handmark.expressweather/com.moengage.core.DataSyncJob
11-18 15:01:48.921 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:01:48.921 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:01:49.023 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:49.126 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:49.131 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10202 (10)0x30000->*vibrator*
11-18 15:01:49.231 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:49.233 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:01:49.233 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:01:49.333 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:49.468 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:49.571 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:01:49.573 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/cp_dig_scale (107): Transport endpoint is not connected
11-18 15:01:49.573 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set effect amplitude (107): Transport endpoint is not connected
11-18 15:01:49.608 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10202 (10)0x30000->*vibrator*
11-18 15:02:00.199 27299 27299 E essService0:15: Not starting debugger since process cannot load the jdwp agent.
11-18 15:02:02.107 2008 2055 E JobScheduler.Background: App com.google.android.gms became active but still in NEVER bucket
11-18 15:02:13.709 27357 27357 E droid.apps.map: Not starting debugger since process cannot load the jdwp agent.
11-18 15:02:13.954 4202 4202 E putmethod.lati: Invalid ID 0x00000000.
11-18 15:02:13.954 4202 4202 E putmethod.lati: Invalid ID 0x00000000.
11-18 15:02:13.955 4202 4202 E putmethod.lati: Invalid ID 0x00000000.
11-18 15:02:13.955 4202 4202 E putmethod.lati: Invalid ID 0x00000000.
11-18 15:02:13.956 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:02:13.956 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:02:14.057 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:02:14.159 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:02:14.161 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10202 (10)0x30000->*vibrator*
11-18 15:02:14.261 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:02:14.262 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:02:14.262 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:02:14.363 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:02:14.497 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:02:14.600 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:02:14.602 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/cp_dig_scale (107): Transport endpoint is not connected
11-18 15:02:14.602 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set effect amplitude (107): Transport endpoint is not connected
11-18 15:02:14.655 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10202 (10)0x30000->*vibrator*
11-18 15:02:41.086 3958 24347 E SQLiteCastStore: Skip saving CastDeviceInfo: "Nearby device" (__cast_nearby___V_609dc0e2-240d-4379-a671-33115b7b31f6)
11-18 15:03:45.259 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:03:45.259 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:03:45.360 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:03:45.462 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:03:45.464 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10155 (10)0x30000->*vibrator*
11-18 15:03:45.565 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:03:45.566 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:03:45.566 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:03:45.666 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:03:45.799 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:03:45.900 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:03:45.901 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/cp_dig_scale (107): Transport endpoint is not connected
11-18 15:03:45.901 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set effect amplitude (107): Transport endpoint is not connected
11-18 15:03:45.934 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10155 (10)0x30000->*vibrator*
11-18 15:03:51.110 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10243 (10)0x30000->*launch*
11-18 15:03:51.187 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10243 (10)0x30000->*launch*
11-18 15:03:51.508 692 692 E Layer : [Surface(name=Task=24)/@0x11da827 - animation-leash#0] No local sync point found
11-18 15:03:51.508 692 692 E Layer : [Surface(name=Task=92)/@0x9dc089a - animation-leash#0] No local sync point found
11-18 15:04:00.198 27619 27619 E essService0:15: Not starting debugger since process cannot load the jdwp agent.
11-18 15:04:01.715 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:04:01.715 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:04:01.817 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:01.818 2008 2590 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:01.921 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:01.922 2008 2590 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:01.923 2008 2590 E VibratorService: Failed to perform haptic effect: effect=0, strength=2: Status(-5, EX_ILLEGAL_STATE): ''
11-18 15:04:01.925 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10202 (10)0x30000->*vibrator*
11-18 15:04:02.026 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:02.026 2008 27650 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:02.027 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:04:02.027 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:04:02.128 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:02.128 2008 27650 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:02.129 2008 27650 E VibratorService: vibratorOn command failed: Status(-5, EX_ILLEGAL_STATE): ''
11-18 15:04:02.132 1015 1021 E statsd : Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10202 (10)0x30000->*vibrator*
11-18 15:04:02.233 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:02.234 2008 6413 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:02.336 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:02.336 2008 6413 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:02.338 2008 6413 E VibratorService: Failed to perform haptic effect: effect=21, strength=2: Status(-5, EX_ILLEGAL_STATE): ''
11-18 15:04:02.340 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/cp_dig_scale (107): Transport endpoint is not connected
11-18 15:04:02.340 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set effect amplitude (107): Transport endpoint is not connected
11-18 15:04:02.440 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:02.441 2008 6413 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:02.544 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:02.545 2008 6413 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:02.546 2008 6413 E VibratorService: Failed to perform haptic effect: effect=2, strength=2: Status(-5, EX_ILLEGAL_STATE): ''
11-18 15:04:32.799 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:04:32.799 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:04:32.901 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:32.901 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:33.003 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:33.003 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:33.004 2008 6411 E VibratorService: Failed to perform haptic effect: effect=2, strength=2: Status(-5, EX_ILLEGAL_STATE): ''
11-18 15:04:33.333 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:04:33.333 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:04:33.439 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:33.440 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:33.542 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:33.543 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:33.545 2008 6411 E VibratorService: Failed to perform haptic effect: effect=0, strength=2: Status(-5, EX_ILLEGAL_STATE): ''
11-18 15:04:34.717 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:04:34.717 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:04:34.818 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:34.818 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:34.921 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:34.922 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:34.923 2008 6411 E VibratorService: Failed to perform haptic effect: effect=2, strength=2: Status(-5, EX_ILLEGAL_STATE): ''
11-18 15:04:35.542 1067 1067 E android.hardware.vibrator-cs40l25: Failed to write device/dig_scale (107): Transport endpoint is not connected
11-18 15:04:35.542 1067 1067 E android.hardware.vibrator-cs40l25: Failed to set global amplitude (107): Transport endpoint is not connected
11-18 15:04:35.644 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:35.644 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:35.750 1067 1067 E android.hardware.vibrator-cs40l25: Previous vibration pending.
11-18 15:04:35.750 2008 6411 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
11-18 15:04:35.752 2008 6411 E VibratorService: Failed to perform haptic effect: effect=0, strength=2: Status(-5, EX_ILLEGAL_STATE): ''
Sounds like a hardware issue that's easily fixed by restarting. Wish there was a way to reset whatever it was without restarting the entire phone.
jljtgr said:
Well, logcat is definitely angry... I'm not sure what to make of it, though. Sounds like a hardware issue that's easily fixed by restarting. Wish there was a way to reset whatever it was without restarting the entire phone.
Click to expand...
Click to collapse
There are several easy ways to rule out hardware. Why not start there? The update timing was just coincidence. If you used the OTA update method before, try flashing the full image.
I have never once used an OTA in any form.
You say coincidence, but it's still a strong one. Never happened before to happening every day just after updating...
To be clear, when I say hardware issue... I don't mean a hardware defect. My assumptions, based on the logcat, is that a sequence of commands gets sent to the vibrator IC that the IC doesn't like and sets it into an invalid state where the error register needs to be reset to resume functionality. But the HAL doesn't have a code path for detecting this or resetting when an error is encountered. Resetting the phone may interrupt power on the microcontroller or, as part of setup, send a sequence of initialization commands that clears the error.
What causes the invalid state could be the update itself having code paths that are more likely to corrupt the IC's state when acting normally, or something like Xposed is hooking one of these functions but is randomly crashing which aborts one/many commands. Updates always carry the risk of upsetting Xposed in some weird way. I don't trust downgrading Android versions without full wipes, so I'm going to resist that until the end.
Or lastly, sure... it could be a coincidence and the vibrator IC is failing somehow where it self-inflicts the invalid state and needs to be reset where Android doesn't account for this possibility and restarting the phone is the only way to fix it.
Bumping this thread because this is still happening and it's driving me crazy. @jljtgr have you had any revelations as to what's causing this problem on your end?
Resuming what was said in the kernel thread... I don't use any System UI mods or substratum themes. At the moment, I'm not running any Xposed Framework or its prerequisites such as Riru Core.
I cleared EXKM's data before installing Kirisakura... but only got about 36 hours running before losing vibration. I completely uninstalled EXKM and I'm currently 145 hours running without issue. I have not tried installing the Clean Slate configuration apps yet.
jljtgr said:
Resuming what was said in the kernel thread... I don't use any System UI mods or substratum themes. At the moment, I'm not running any Xposed Framework or its prerequisites such as Riru Core.
I cleared EXKM's data before installing Kirisakura... but only got about 36 hours running before losing vibration. I completely uninstalled EXKM and I'm currently 145 hours running without issue. I have not tried installing the Clean Slate configuration apps yet.
Click to expand...
Click to collapse
Appreciate the feedback sir. I tried reinstalling everything and ran into the issue, so it's back to uninstalling EXKM :/
After 360 hours, vibration failed... then 40 hours later it failed again. I was willing to overlook 15 days of no issues, but the 40 hours is more concerning.
January update with only Kirisakura installed, EXKM is not, Clean Slate etc was not.
Related
Since I'm hard bricked, I can help out others. We just need to work together.
Sadly though, our device ID is 05c6:f006 as proven by the HTC forum, it is not unbrickable just yet. But we can do this.
Useful Documents
http://www.cooking-hacks.com/skin/frontend/default/cooking/pdf/3G_modem_tutorial.pdf
Also, in our bootrom, I have seen 05c6:9008, but not 05c6:9006. (Maybe it's telling us that it was id changed, or another new version or completly different protocol).
here is what I get when I lsusb it as verbose:
Code:
Bus 003 Device 012: ID 05c6:f006 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0xf006
bcdDevice 0.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Device Status: 0x0000
(Bus Powered)
Also, for some odd reason, it is being registered as a Human Interface Device.
I will try to fix that.
All done on Ubuntu 12.10
Does this mean your any closer to unbricking, why don't you send it to at&t?
I also have a hard bricked Atrix HD laying around.
Sent from my Galaxy Nexus using Tapatalk 2
mattlgroff said:
I also have a hard bricked Atrix HD laying around.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What did you do to brick yours, Matt?
Sent from my phone.
Markyzz said:
What did you do to brick yours, Matt?
Sent from my phone.
Click to expand...
Click to collapse
It has a RAZR HD bootloader, nuff said lol
Wish Adam Outlater(missed spelled his name) was still working with us. He does such a fab job getting phones unbricked.
first thank you for comeing up with a way to unbrick the atrix HD i flash the 4.1.1 ATT i can get the full name but it seem to be a version where thay have patched the 4.1.1 root over samba trick by not blocking access to specdrive is there another root or can u falsh any version of the att
stock rom with RSD lite or what im kinda losein my mind i did use root for another things beside flashing roms an the first time i flash a rom it bricked my phone witch i wont be doing agin ya im sure i need to use spell check but im alitl unhappy right now been messing with this for 12 or so hurs now .... thank you for the unbrick tho lest i can use the phone for calls an what not
was useing http://forum.xda-developers.com/showthread.php?t=2143437 on my stock phone witch was a replacement of the 4.0.1 phone (ear pice issues)
also i think thay patched the samba expo from AT&T Moto Blur 98.2.2 / AT&T Moto Blur JB 4.1.1 is Blur 98.4.20
Now that bootloaders of MB886 are unlockable , I hope there would be a solution for this. I'm on a hard brick too. QPST/QHSUSB_DLOAD mode. Black screen, but Green Led shows sign of power.
mark_hatred said:
Now that bootloaders of MB886 are unlockable , I hope there would be a solution for this. I'm on a hard brick too. QPST/QHSUSB_DLOAD mode. Black screen, but Green Led shows sign of power.
Click to expand...
Click to collapse
Yeah, I would try unlocking the bootloader... That trick worked quite well on my OG Atrix with a hard brick.. Can't hurt to try if you can get into fastboot.
mark_hatred said:
Now that bootloaders of MB886 are unlockable , I hope there would be a solution for this. I'm on a hard brick too. QPST/QHSUSB_DLOAD mode. Black screen, but Green Led shows sign of power.
Click to expand...
Click to collapse
MobileTechVideos.com fixed mine us with JTAG repair.
Sent from my Galaxy Nexus using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=2227938 root is now up
and
http://forum.xda-developers.com/showthread.php?t=2226504 unlocked bootloader
Pretty old news man. Besides the fact that has nothing to do with the thread.
Sent from my U8655 using xda app-developers app
Yeah,
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sbl1
=
Hard brick!!!!!!!!
tcf38012 said:
Since I'm hard bricked, I can help out others. We just need to work together.
Sadly though, our device ID is 05c6:f006 as proven by the HTC forum, it is not unbrickable just yet. But we can do this.
Useful Documents
http://www.cooking-hacks.com/skin/frontend/default/cooking/pdf/3G_modem_tutorial.pdf
Also, in our bootrom, I have seen 05c6:9008, but not 05c6:9006. (Maybe it's telling us that it was id changed, or another new version or completly different protocol).
here is what I get when I lsusb it as verbose:
Code:
Bus 003 Device 012: ID 05c6:f006 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0xf006
bcdDevice 0.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Device Status: 0x0000
(Bus Powered)
Also, for some odd reason, it is being registered as a Human Interface Device.
I will try to fix that.
All done on Ubuntu 12.10
Click to expand...
Click to collapse
I'm havin' the same problem, too. An lsusb of "ID 05c6:f006 Qualcomm, Inc." with a dmesg of "ttyUSB0: Qualcomm USB modem converter". You figure anything out with yours?
Ive Hard Bricked the LG SU640 by flasing recovery to WRONG Partition no screen full BLACK no Charging nothing , Device Manager was showing QUALCOMM HS-USB QDLOADER , ive managed to unbrick it .. is that is your problem .. ?
Help me!
02busa said:
Yeah, I would try unlocking the bootloader... That trick worked quite well on my OG Atrix with a hard brick.. Can't hurt to try if you can get into fastboot.
Click to expand...
Click to collapse
Hey buddy, let me know if you managed to repair your Motorola and if so how?
Hi, i searched the whole forum and no luck =(
After oreo update, the sixaxis app stopped working.
Usually worked at method 2, but now it says "wrong number of ports were opened"
I tried somehow to connect the sixaxis with directly system Bluetooth, but It requires a pin.
I tried otg cable and none of those steps worked.
I'm so sad, any help please =))
fbrauns said:
Hi, i searched the whole forum and no luck =(
After oreo update, the sixaxis app stopped working.
Usually worked at method 2, but now it says "wrong number of ports were opened"
I tried somehow to connect the sixaxis with directly system Bluetooth, but It requires a pin.
I tried otg cable and none of those steps worked.
I'm so sad, any help please =))
Click to expand...
Click to collapse
I have the same issue. I believe its to do with Oreo update. Try emailing the dev, I have emailed them but no reply so far
This problem will be forever
It seems that the developer is dizzy and almost crazy. Because it won't be able to overcome this. Or because he has given up and resigned his life in the real world
Sixaxis works for me in almost every oreo custom ROM, not sure what you have experienced but mine works, I tried all oreo ROMs to get the best of PUGB smooth non-overheating like a lava and used sixaxis in every single one of them.
I just change my connection method to 2 and nothing else. *at first I changed my dualshock bluetooth address using the OTG* and then didn't need to do it all over again.
aboodyaiman said:
Sixaxis works for me in almost every oreo custom ROM, not sure what you have experienced but mine works, I tried all oreo ROMs to get the best of PUGB smooth non-overheating like a lava and used sixaxis in every single one of them.
I just change my connection method to 2 and nothing else. *at first I changed my dualshock bluetooth address using the OTG* and then didn't need to do it all over again.
Click to expand...
Click to collapse
So are you using Bluetooth or is it working with OTG?
---------- Post added at 06:45 PM ---------- Previous post was at 05:49 PM ----------
aboodyaiman said:
Sixaxis works for me in almost every oreo custom ROM, not sure what you have experienced but mine works, I tried all oreo ROMs to get the best of PUGB smooth non-overheating like a lava and used sixaxis in every single one of them.
I just change my connection method to 2 and nothing else. *at first I changed my dualshock bluetooth address using the OTG* and then didn't need to do it all over again.
Click to expand...
Click to collapse
Tried method 2 and it didn't work for me. I'm on stock OOS
Quick Start:
- Pair controllers via USB using supplied utility
- Use 'start' and 'stop' to toggle driver
- Press power button on controllers to activate
- Change input method to 'Sixaxis Controller'
- Check 'help' menu for detailed instructions
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Wrong number of ports were opened
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Wrong number of ports were opened
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not find stack manager interface in library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 6...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 7...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Attempting to close server...
Restoring previous bluetooth state...
Disconnected
ceanth said:
So are you using Bluetooth or is it working with OTG?
---------- Post added at 06:45 PM ---------- Previous post was at 05:49 PM ----------
Tried method 2 and it didn't work for me. I'm on stock OOS
Quick Start:
- Pair controllers via USB using supplied utility
- Use 'start' and 'stop' to toggle driver
- Press power button on controllers to activate
- Change input method to 'Sixaxis Controller'
- Check 'help' menu for detailed instructions
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Wrong number of ports were opened
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Wrong number of ports were opened
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not find stack manager interface in library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 6...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 7...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Attempting to close server...
Restoring previous bluetooth state...
Disconnected
Click to expand...
Click to collapse
I didn't try it on OOS actually, and input method was left untouched.
Sixaxis works with bluetooth I only used OTG in pairing at first, maybe your app is somehow corrupted?
Btw sixaxis still works on Pie too.
Still not working for me
anyone found any solution for it?
Hulk555 said:
anyone found any solution for it?
Click to expand...
Click to collapse
Nope, only solution I could find was to buy a Nintendo switch. On the plus side my phone battery now lasts for days as I don't play any games on it
aboodyaiman said:
I didn't try it on OOS actually, and input method was left untouched.
Sixaxis works with bluetooth I only used OTG in pairing at first, maybe your app is somehow corrupted?
Btw sixaxis still works on Pie too.
Click to expand...
Click to collapse
Are you sure about that: is sixaxis working on Pie?
Hi all!
I am kind of new to XDA so please bear with me. I have an issue with Sixaxis Controller application where It does not connect via bluetooth. I have taken all the steps and checked them 15 times now. I have pasted the exact error here.
If someone could please explain why this is happening and if it is possible to fix, I would DEEPLY appreciate this. Furthermore I had noticed that the SELinux was enforced and many reddit posts mentioned changing it to permissive so I had to install TGP Kernel, but even that had no effect!
Thanks again!
Error:
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Attempting to close server...
Restoring previous bluetooth state...
Disconnected
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 6...
Attempting to close server...
Restoring previous bluetooth state...
Driver Starting...
Disconnected
Can't connect to pipe for device
If I had to guess, the driver hasn't been updated to be compatible with later versions of android. Are you referring to the Sixaxis app by Dancing Pixel Studios?
Ah. Yes. It is the sixaxis app by dancingpixel!
Hello.
I want to connect my Dual Shock 4 controller with that app but when I give the START button I get all this text that I have put below;
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 6...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 7...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Attempting to close server...
Restoring previous bluetooth state...
Disconnected
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 6...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 7...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Attempting to close server...
Restoring previous bluetooth state...
Disconnected
With Android OREO if it works properly.
Someone can explain to me why this app doesn't work on Android 9? Other than running that app unupdated for quite some time.
D-Mak said:
Hello.
I want to connect my Dual Shock 4 controller with that app but when I give the START button I get all this text that I have put below;
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 6...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 7...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Attempting to close server...
Restoring previous bluetooth state...
Disconnected
Getting bluetooth address...
Attempting connection method 1...
Driver Starting...
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 2...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 3...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 4...
Driver Starting...
Could not load bluetooth library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 5...
Driver Starting...
Could not load HCI library
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 6...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Getting bluetooth address...
Attempting connection method 7...
Driver Starting...
Could not set HCI raw mode
Error: Failed to configure bluetooth
Attempting to close server...
Restoring previous bluetooth state...
Disconnected
With Android OREO if it works properly.
Someone can explain to me why this app doesn't work on Android 9? Other than running that app unupdated for quite some time.
Click to expand...
Click to collapse
Is the app you use last updated in 2014? That is probably the reason then, something must have changed with Pie which required the developer to update their app to be compatible.
Not much help but, my xbox one controller for Pc works great with Pie.
My gut feeling tells me this may not be the best place as it is really not a common problem, but I don't know where else to ask... so here goes:
My home network has two routers that are bridged together, have same SSID, and run 802.11r FT Fast Transition, so devices that support it should seamlessly retain wifi connection going from one router to the next.
The Mi9 I have however, will seemingly roam successfully, but only for a few seconds, before it apparently disconnects itself from the router, then makes a brand new connection attempt to the same router.
I use 'logcat' to dump the wpa_supplicant log during one of these incidents, as below:
Code:
09-04 20:14:06.113 2285 2285 I wpa_supplicant: wlan0: Associated with xx:xx:xx:xx:xx:xx
09-04 20:14:06.113 2285 2285 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed [id=0 id_str=%7B%22configKey%22%3A%22%5C%22[Redacted]%5C%22-WPA_PSK%22%2C%22creatorUid%22%3A%221000%22%7D]
09-04 20:14:06.115 2285 2285 I wpa_supplicant: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
09-04 20:14:06.123 2285 2285 I wpa_supplicant: getWifiGenerationStatusInternal: generation = 4, twtSupport = false, vhtMax8SpatialStreamsSupport = false
09-04 20:14:12.209 2285 2285 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
09-04 20:14:12.211 2285 2285 E wpa_supplicant: eap_proxy: eap_proxy_notify_config
09-04 20:14:12.212 2285 2285 I chatty : uid=1010(wifi) /vendor/bin/hw/wpa_supplicant identical 1 line
09-04 20:14:12.212 2285 2285 E wpa_supplicant: eap_proxy: eap_proxy_notify_config
09-04 20:14:12.256 2285 2285 I wpa_supplicant: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=HK
09-04 20:14:15.323 2285 2285 I wpa_supplicant: getCapabilitiesInternal capabilities: NONE IEEE8021X WPA-EAP WPA-PSK WPA-EAP-SUITE-B WPA-EAP-SUITE-B-192 OWE DPP FILS-SHA256 FILS-SHA384 FT-PSK
09-04 20:14:15.325 2285 2285 E wpa_supplicant: eap_proxy: eap_proxy_notify_config
09-04 20:14:15.326 2285 2285 I wpa_supplicant: wlan0: Trying to associate with SSID '[Redacted]'
09-04 20:14:15.335 2285 2285 E wpa_supplicant: eap_proxy: eap_proxy_notify_config
09-04 20:14:15.335 2285 2285 E wpa_supplicant: eap_proxy: eap_proxy_allowed_method
09-04 20:14:15.391 2285 2285 I wpa_supplicant: wlan0: Associated with xx:xx:xx:xx:xx:xx
09-04 20:14:15.391 2285 2285 I wpa_supplicant: wlan0: WPA: RX message 1 of 4-Way Handshake from xx:xx:xx:xx:xx:xx (ver=3)
09-04 20:14:15.401 2285 2285 I wpa_supplicant: wlan0: WPA: Sending EAPOL-Key 2/4
09-04 20:14:15.402 2285 2285 I wpa_supplicant: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
09-04 20:14:15.414 2285 2285 I wpa_supplicant: wlan0: WPA: RX message 3 of 4-Way Handshake from xx:xx:xx:xx:xx:xx (ver=3)
09-04 20:14:15.414 2285 2285 I wpa_supplicant: wlan0: WPA: Sending EAPOL-Key 4/4
09-04 20:14:15.419 2285 2285 I wpa_supplicant: wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
09-04 20:14:15.419 2285 2285 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed [id=0 id_str=%7B%22configKey%22%3A%22%5C%22[Redacted]%5C%22-WPA_PSK%22%2C%22creatorUid%22%3A%221000%22%7D]
09-04 20:14:15.438 2285 2285 I wpa_supplicant: getWifiGenerationStatusInternal: generation = 4, twtSupport = false, vhtMax8SpatialStreamsSupport = false
20:14:12.209 is where the the phone suddenly decides to disconnect.
Anything I can do to perhaps pinpoint the source of the problem and hopefully fix it?
Thanks!!