While connecting to my vehicle on the above date I noticed that the app was a bit buggy. After unplugging my phone and plugging it back in, the AA Mirror Plus app on the vehicle on screen display was missing. I checked my phone and it was still there.
After reading up I found that the software was blocked after an update to the vehicles infotainment software.
How can I get this work again. AAAD has asked me to contact developer directly for assistance but I do not know who they are to begin with.
Please can you help.
Related
i was wondering if anyone else might be having this problem.
when i connect the phone it shows up and is accessible in adb but after a few seconds, between 15 and 20, the device goes offline but still shows up as attached.
if anyone has any suggestions for diagnosing this problem or experience with it please share.
thank you
ok well the 10th reboot and 5th port change seems to made the phone happy. stable for 10 minutes so far.
it seems to like a shorter cable or to be plugged directly into the motherboard usb port instead of the front panel ports.
I have two t-mobile GS5s . Updated both to 5.1.1 . MHL is broken and I have to take some unconventional steps to get it working. Even then I get a floating message on the monitor saying that the device is not supported. Previously all that I had to do for mhl was to plug the phone into the mhl adaptor which is plugged into a monitor or a tv. now to get mhl working I have to un plug the monitor or tv before I attach the phone otherwise I get constant reboots. also if I attach a charger to the mhl adaptor it must be a 300 mah charger . any thing over that will also cause the boot loops.
I called tmobile and they told me to contact samsung. samsung told me to contact their service center. over the phone some guy told me that he had a t mobile s5 that was on 5.1.1 fof6 and that his mhl worked fine. now I am reluctant to go to their center as I am 99% sure that he just told me this to get me off the phone. My question is , does anyone who has updated to 5.1.1 NOT have issues with MHL?
Same issue, and tried contacting Samsung, TMobile, and Google.
I have the same issue you have (and have found at least 5 other cases, including people who have since the update bought an MHL cable on Amazon and sent the cable back thinking it doesn't work). In my case, I have validated that the 5.1.1 update does cause the issue, by testing this on two separate phones. Both had it working under 5.0, and immediately after the 5.1.1 update, the failure starts.
May I ask as to how you did get yours to work? Right now my only options are to send the phone back to T-Mobile as part of their customer satisfaction program, and get a new phone with the older 5.0 firmware, or to attempt to roll back on my own. This is a feature I used heavily for work presentations.
I contacted Android, and was shot down as it was a Samsung phone, and their developers don't want to consider my defect as "Samsung runs a lot of custom stuff".
Samsung gave me a boiler plate response with various troubleshooting techniques that did nothing of value. They want me to contact their support staff for a warranty repair. I already know where that is going to go from a prior experience.
T-Mobile is the best option. Their engineer at least acknowledged that they have gotten numerous defect reports associated with the 5.1.1 update, and took my notes into their system. They even checked for any patches, of which none were available as of yet. If enough people are returning phones for a "goodwill" replacement, I am certain that they will deliver a patch sometime in the next couple of months. However, I would still be skeptical of this.
Regardless, the best service has been from T-Mobile thus far.
I will gladly keep this forum posted if I find out anything more, including possible resolutions. Please do the same for me, including any workarounds you may already know of.
Thanks,
Oz
everyone has their own setup which is usually different from others . I am using an mhl adaptor that is connected to an hdmi to vga adaptor which connects to a vga monitor. also i can attach the mhl adaptor to hdmi input on my tv. to get either setup working I must shut off the monitor or tv and make sure it is unplugged. next i connect the adaptors or adaptor if using with the tv. then I attach the phone . next I attach the charger to the adaptor which must be charger that is 300mah , any higher will immediately cause the phone to reboot. next i make sure the screen is locked on the phone. after all this I plug in the monitor or tv and unlock the lockscreen on the phone. even though it works I get a floating toast message saying unsupported device. befor 5.1.1 all I had to do was plug in . this is alot of work to get mhl working and so far I have not found another way
i just tried my method again. it did not work. for some reason the charger that i used previously at 300 mah is now charging at 1100 mah. mhl now only can work for me if i don't use a charger. try not hooking up the charger to the mhl adaptor.
I have 3 T Mobile galaxy S5's and have updated two of them to 5.1.1 and they both reboot when I tried to connect with an MHL cable to my Brookstone projector. The s5 that still has kitkat works fine with mhl to same projector.
Hi everyone, I need your help.
A couple of days ago one of the ear peaces of the original Leeco headphones died because of wear and tear to the cable. I quickly opened amazon and found "Huawei 55030088 Headphones Type C, White" which seemed good enough for my needs. Sadly when I opened the box an hour ago and trying them nothing happened. It's like they are not even plugged in. The sound is coming from the speakers. I've tried several apps and rebooting as well and it didn't work. I am currently running DU v11.7.2 (7.1.2) with kernel Blackscreen 3.18.31. I was wondering if it's a compatibility issue.
Please help me unravel this mystery.
Best regards, Mysaka.
Heyyo, hmm it could need extra entries in audio files in order to work or it could require something else... By chance do you have a PC with a Type-C port? Please see if it works on there if yes otherwise maybe please try with a Type A to C adapter.
Otherwise? You could always attempt to revert to EUI ROM and see if it works there... If it does? Then we know there's definitely some kind of compatibility issue that will need to be resolved.
Unfortunately I don't have a USB c port on the PC or adaptor. Thanks for the idea, will try it this weekend and report the results.
Try this:
-plug the USB c adapter to the phone
-whait around 5-10 seconds
-unplug it than plug it upside down
This usually works for me and if it works for you than you need to do this every time.
After the Android 11 update my phone won't detect the fast charger and it crashes sometime I have pixel 2xl and it charges normally with a usb cable and detects it everytime
Ekansh09 said:
After the Android 11 update my phone won't detect the fast charger and it crashes sometime I have pixel 2xl and it charges normally with a usb cable and detects it everytime
Click to expand...
Click to collapse
Hi,
That problem needs to be solved by goog, you can contact them for support here :
https://support.google.com/pixelphone/answer/7109524?hl=en&ref_topic=7084203
You can send feedbacks from here :
https://support.google.com/pixelphone/answer/6398243?hl=en&ref_topic=7084203
In short, you have to wait for the next update to see that bug fixed. But who knows, maybe customer support will find a solution.
Good luck
Well I have tried contacting the support they are more clueless than I am and pretending as if the issue doesn't exist . Upon my research I have found that this issue is like 2 years old and had been in many pixel phones and arrived in mine just after the update ... That's what I'm counting waiting for the next update to see if it fixes it. .. the Google support is hell bent on claiming this to be my hardware issue saying they have to inspect my device and bla bla
:crying:
On Google Pixel 2 XL Fast Charging is capped at 10.5W although the phone will work with 27W charger. Any charger used must have an USB Type-C port because phone sports the USB Power Delivery specification
IIRC to force Fast Charging on any phone you in Android Settings make 2 changes as listed next
Developer option -> Background processs limit and set it to Standard limit
Apps -> Running and there close all applications
and then let charge the phone
Hi All,
I'm trying to resolve an issue with a Mate 20 pro which I hope doesn't end up hardware related on the main pcb.
The phone will no longer charge or communicate via the USB port. Luckily it will still charge using the wireless pad.
Ill start by listing the things I have tried to resolve the issue and then ask if anyone has any other suggestions -
Performed full factory reset/cache data clear
Checked and cleaned charging port
Tried other genuine cables, chargers and PC's
operated in safe mode
tried different usb settings in developer mode and project mode (*#2846579#*#*)
Ran the diagnostics in the Hcare app - which just tells me to contact for service and repair on the charging/usb test
replaced the USB-C ribbon assembly with a genuine replacement
Measured 5v via test points on the main PCB when the cable is connected
Soft boot mode connects to the PC and opens up hsuite, but shows as not connected
Soft boot mode will also show a device id in the Huawei service/download tool
Checked for any obvious damage to internal components
The phone warranty sadly ran out on Sunday.
I did contact Huawei last week, but without an original proof of purchase, they would not repair the phone foc.
This is why I made the decision to remove the back.
I have spent a long time looking for answers on this site and various repair methods on the internet, but nothing has come up.
My remaining thoughts were to consider downgrading the firmware from 10.1 to either 9 or 10 using either the SD card or purchase a USB otg to try?
I may try to check the continuity on the ribbon cable I removed just to double check I haven't ended up with two dodgy USB-C ribbons.
Can anyone tell me why the phone will still connect in soft boot mode, but not when booted up normal?
Current firmware is 10.1.0.328(C432E8R1P5)
A few final things to mention as its my first post -
I did purchase the phone with this fault and don't know the full history of the phone, which is why I wondered if the fault occurred following an OTA update.
If I cant get the port to work, Im happy to continue using it in its current state till I get bored and buy another phone with slight imperfections.
I am an electrical engineer (Drive technology) with previous experience of basic repair techniques on mobile phones and precision repair of other electronics, but I don't claim to have any in depth knowledge in repairing mobile phones, just a general hobby interest.
I just didn't want to portray an image of someone blinding jamming tools into a piece of electronics.
I'm happy to take any positive criticism, if it helps to resolve my query.
Thanks,
Phil