Database Users

Bridge work on the stock rom faulty machine!!

and after I rebooted again, then add 1 to the error as shown below :
{
"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"
}
I have tried reset and run 2 lines are not save me!

help me
help me

vdsno1 said:
help me
Click to expand...
Click to collapse
Hey, I'm not positive what your post is asking for, but I think its for the stock rom, is that correct? If so, pm me and I'll send you my stock backup. It may have some extra "stuff" you don't want, but it's all I've got.

thanks yu
S_transform said:
Hey, I'm not positive what your post is asking for, but I think its for the stock rom, is that correct? If so, pm me and I'll send you my stock backup. It may have some extra "stuff" you don't want, but it's all I've got.
Click to expand...
Click to collapse
thank you for your enthusiasm and now I can not get into TWRP hashcode of you can help me how to restore it or not!

vdsno1 said:
thank you for your enthusiasm and now I can not get into TWRP hashcode of you can help me how to restore it or not!
Click to expand...
Click to collapse
Do you have adb still? if you do it may be fixable, but if not it may be impossible. I had to get a replacement from Amazon after a build.prop bricked me and I lost adb. Do you know why it stopped booting correctly?

thanks
S_transform said:
Do you have adb still? if you do it may be fixable, but if not it may be impossible. I had to get a replacement from Amazon after a build.prop bricked me and I lost adb. Do you know why it stopped booting correctly?
Click to expand...
Click to collapse
I am not sure whether the current adb because when I connect my laptop hdx, I see it still looking for the driver jumps until hdx was standing at my screen was taken at # 1 is my laptop can not find that driver again so I was not sure adb

vdsno1 said:
I am not sure whether the current adb because when I connect my laptop hdx, I see it still looking for the driver jumps until hdx was standing at my screen was taken at # 1 is my laptop can not find that driver again so I was not sure adb
Click to expand...
Click to collapse
In order to get it working you may have to manually assign it to the device. Try going to devices, right click on the kindle device and go to properties. Switch to properties and go to the one that doesn't have an assigned driver, if there is one. Hit properties, then change settings on the window that pops up. Go to driver, update driver, browse my computer, and then pick from a list. If you have the adb drivers installed, go to kindle fire, or amazon, or something like that, and then click adb interface. If it lets you do that then you should be able to get adb working. Hopefully this is useful.

S_transform said:
In order to get it working you may have to manually assign it to the device. Try going to devices, right click on the kindle device and go to properties. Switch to properties and go to the one that doesn't have an assigned driver, if there is one. Hit properties, then change settings on the window that pops up. Go to driver, update driver, browse my computer, and then pick from a list. If you have the adb drivers installed, go to kindle fire, or amazon, or something like that, and then click adb interface. If it lets you do that then you should be able to get adb working. Hopefully this is useful.
Click to expand...
Click to collapse
I did as you said is absolutely not found 1 hdx devices and adb does not work I still do not know how to do it again!! can anyone help me not

help me help me

vdsno1 said:
help me help me
Click to expand...
Click to collapse
First of all, you need to stop posting this EVERYWHERE. There are many warning about messing with the HDX posted & you chose to ignore them.
Secondly, if you want help, be concise. All I see is "bridge doesn't work". Your picture does not show up, if that is what it is, so I have no idea what you are referencing. I have no idea what your setup is, or whether you have read any of the posts talking about loss of ADB. You need to slow down & take a breath.
Do you have the entire Android SDK installed? Have you tried getting ADB connection from the Android SDK home/main directory? Once I lost ADB access, the only way I could conenct after restoring was from my installed SDK directory, which for me is C:/Android. For you it depends on where you installed it, but you need to try from there or the platform tools folder.

thanks
GSLEON3 said:
First of all, you need to stop posting this EVERYWHERE. There are many warning about messing with the HDX posted & you chose to ignore them.
Secondly, if you want help, be concise. All I see is "bridge doesn't work". Your picture does not show up, if that is what it is, so I have no idea what you are referencing. I have no idea what your setup is, or whether you have read any of the posts talking about loss of ADB. You need to slow down & take a breath.
Do you have the entire Android SDK installed? Have you tried getting ADB connection from the Android SDK home/main directory? Once I lost ADB access, the only way I could conenct after restoring was from my installed SDK directory, which for me is C:/Android. For you it depends on where you installed it, but you need to try from there or the platform tools folder.
Click to expand...
Click to collapse
yes thank you for sharing .... I will not post any more awkward!
- Can you tell me in detail how do you save your machine is compatible or not?

vdsno1 said:
yes thank you for sharing .... I will not post any more awkward!
- Can you tell me in detail how do you save your machine is compatible or not?
Click to expand...
Click to collapse
FIrstly, do you have the Android SDK installed? You need to do that to have the latest version of the platform tools & you need to follow those instructions so that you can call those tools from any folder, by adding them to your environmental path. There are already a hundred tutorials on installing the SDK, so I am not going to list every step. Start here: http://developer.android.com/sdk/installing/index.html
Then, once you are done, follow up with the info here: http://forum.xda-developers.com/showthread.php?t=1842969
That will get you to a point of readiness & understanding to begin trying to recover. LMK when you are done.

ADB driver connection

Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?

rayjr13 said:
Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?
Click to expand...
Click to collapse
Yes but I know if you update to Windows 10 it can cause issues you need to reinstall moto drivers
Sent from my XT1585 using XDA Premium 4 mobile app

My Turbo 1 connect just fine not T2 I'll try it again when the wife brings it back

I had a small issue. I think mine cleared up when I installed Vysor, and installed the drivers through that.
http://koush.com/post/universal-adb-driver
Give this a shot and let me know how it goes. btw, Vysor is pretty fun.

Solution update (2017-2018 version) for recent Ubuntu-based Linux and Windows 10
(NOTE: I am unable to post complete URLs due to having an insufficient number of XDA Forum posts at this time. The bulk of this post and the information contained within is available by searching for my GitHub account (maxieds) and selecting the most obvious pinned repo description. My GitHub page is also linked off of my XDA Forum profile just to be clear. )
Preface: I realize that this thread is somewhat dated, but so is this antique 2015-era phone, so I figured it's worth pointing out a recent solution to those patient Google searchers who like me are still using the device. This solution (works for me on a recent 2017 Debian-derivative Linux box, and/or a loaner Windows 10 laptop) is to avoid the proprietary Motorola software and drivers you will stumble onto from the official ADB links from Android Studio. All you need is the standard Google USB drivers and a more recent list of phone USB device ID properties. I haven't tested, and so cannot confirm, but I suspect that this method should get ADB up and functioning on other hard-to-configure deviant phones using the list of Linux udev supported configurations from this recent (and often updated): <GITHUB>/M0Rf30/android-udev-rules. My modification for the DROID TURBO 2 phone is forked <GITHUB>/maxieds/android-udev-rules. If you find this information helpful, I'd appreciate it if you would STAR my repo on GitHub (<GITHUB>/maxieds/android-udev-rules/stargazers). As a variant of the the old Unix joke goes in obscure 20-year-old Slashdot references: How do we fix Windows? ... Well, I propose we port WINE to Windows ... With this in mind and in this spirit, let's port the oh-so-wonderful Linux UDEV config to Windows.
NOTE: the DROID TURBO 2 didn't work out-of-the-box on Ubuntu either however, even after installing other variants of the udev rule sets, so my mod is necessary to fix at least this stubborn class of Motorola devices. One possible explanation for why this device doesn't work like nearly every other Android phone is a USB3 bug where file explorer, etc. works on the same USB port, but ADB fails. The purported non-software work around is to chain the phone's USB connection in serial to a cheap self-powered USB hub that effectively masks this bug, but I had no such luck with this experimental fix and of course your mileage may vary. More likely, the cause is that the phone preempts the typical detection sequence by changing the id of it's ATTR{idProduct}=="2ea4" to ATTR{idProduct}=="2ea5" (or some other related ID) when it is connected through USB debugging for use with ADB. See the following image detailing the respective dmesg and lsusb changes pre/post enabling USB debugging on a device connected via USB in Linux:
{
"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"
}
===== Ok, so here, goes with the updated device details: =====
Recent (2017,2018) Solution for Using the DROID TURBO 2 Phone with ADB:
Recently, I finally got into Android development using my Motorola DROID TURBO 2 phone ... only to find that the phone isn't recognized out-of-the-box on either Linux or Windows. After searching around for a while, I finally have found a solution on Linux, which I then "ported" to Windows 10 using the stock Google USB drivers which are easy to find and install with Android studio. The solution is essentially this:
on Linux (after installing Android Studio / ADB / Android Tools in Ubuntu):
Use this updated udev file to get the TURBO 2 recognized: <GITHUB>/maxieds/android-udev-rules. The working forked file basically required setting a few non-standard udev options and inputting the complete device spec found with
Code:
lsusb
LSUSB Outputs: Bus 001 Device 0XX: ID 22b8:2ea5 Motorola PCS, where the XX is a decimal integer local to the running linux box
Click to expand...
Click to collapse
. After following the instructions at the referenced link, running
Code:
adb devices
from your favorite terminal should display the device. Now happy ADB and Android debugging to you and your ancient phone! (AND please be sure to STAR my repos!)​
in Windows 10 (Enterprise): First, install the Google USB Driver using the SDK manager in Android Studio (under Extras). This puts the driver files in (on my local text box) "Program Files (x86)\Android\android-sdk\extras\google\usb_driver\*". I had to right-click, install and enter the administrator password for the local box to install this. At this point, you can open up "Computer Management > Device Manager" (as ROOT) and see if your phone is automatically recognized by the stock Google USB driver. Mine is not, so we have more work to do. From the GitHub repo (<GITHUB>/maxieds/AndroidADBExtraUSBConfig) I have created, copy the two files under android_google_usb_driver_mod into the default folder for the Google USB Driver files (linked on Windows 10 as above). Repeat the process to install the driver.
Hopefully, now you can get the Motorola DROID TURBO 2 device up and developing with ADB and Android Studio! :good:
---------- Post added at 09:40 AM ---------- Previous post was at 09:32 AM ----------
Since I was unable to post the links to the GitHub repos relevant to the recent solution to this problem, maybe this will get past the XDA Forum filters. Here's a QR-Code to the Wiki page on my repo where you can find complete information and files for implementing the custom USB setup needed to get the DROID TURBO 2 phone working out-of-the-box with ADB under Android Studio: <img src='https://chart.googleapis.com/chart?cht=qr&chl=https%3A%2F%2Fgithub.com%2Fmaxieds%2FAndroidADBExtraUSBConfig%2Fwiki%2FFirstBootConfigurations&chs=180x180&choe=UTF-8&chld=L|2' alt=''>. A link to the original image file (which should have been displayed in the above post) using the repo site is also provided as follows: <img src="https://github.com/maxieds/AndroidADBExtraUSBConfig/blob/master/images/idproduct-discrepancy-illustrated.png" alt="" />.

Windows 10 & ADB/Fastboot

Anyone here having issues on Windows 10 with ADB/Fastboot recognition?
I'm using the Android SDK Toolkit from the Google website, and I have both ADB and Fastboot installed. ADB recognizes the device, and started a shell on the device, everything is ok.
I reboot the device into fastboot mode, plug it into the same USB port where ADB was working, and nothing happens. It says "connect the usb cable". Frustrating as I'm looking to unlock the bootloader.
Tried rebooting from both MHP/PHP/Stock usb modes, which all opened an adb shell successfully, but fastboot mode is not recognized at all on the same usb port.
SOLVED see lower posts.

when you run the "adb devices" what does it show? If I had to guess it will show your device but say something about it being locked. I had to go into device manager, and manually switch my ADB device driver over to the correct one. I cant remember off of the top of my head which driver it was, but it took me nearly an hour to figure it out.

rodcpierce said:
when you run the "adb devices" what does it show? If I had to guess it will show your device but say something about it being locked. I had to go into device manager, and manually switch my ADB device driver over to the correct one. I cant remember off of the top of my head which driver it was, but it took me nearly an hour to figure it out.
Click to expand...
Click to collapse
List of devices attached
84BXXXXXXXXXX66 device
Looks like what I'm used to, as I said, adb shell works fine, I can change directory to system or whatever. Just doesn't recognize the device at all in fastboot mode.

hmmm, odd. Does it say "waiting for device" in adb when you are in the bootloader? Or is it telling you to plug in the USB on the bootloader screen (phone).
If the latter is the case, try and run your commands.

rodcpierce said:
hmmm, odd. Does it say "waiting for device" in adb when you are in the bootloader? Or is it telling you to plug in the USB on the bootloader screen (phone).
If the latter is the case, try and run your commands.
Click to expand...
Click to collapse
It's telling me to plug in the cord on the bootloader screen. "connect usb cable", I connect it. It still says "connect usb cable". However, in my device manager, I have an Android device that does not have a driver (Code 28).

go ahead and try and run your commands in ADB while on the bootloader screen.

rodcpierce said:
go ahead and try and run your commands in ADB while on the bootloader screen.
Click to expand...
Click to collapse
neither adb or fastboot commands work in bootloader mode on the same USB that ADB worked when phone was on.
The device is recognized in device manager (when in fastboot mode) but has no driver. Is it not the same usb driver responsible for ADB when device is on???

one second, let me plug mine in here quick and see which device driver is assigned.
---------- Post added at 02:06 AM ---------- Previous post was at 01:59 AM ----------
here is what mine shows up as. I was hoping it would show me the driver file. If you have a device with no driver, I would point it to the google universal USB driver. (i believe that is what I used)
{
"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"
}

rodcpierce said:
one second, let me plug mine in here quick and see which device driver is assigned.
---------- Post added at 02:06 AM ---------- Previous post was at 01:59 AM ----------
here is what mine shows up as. I was hoping it would show me the driver file. If you have a device with no driver, I would point it to the google universal USB driver. (i believe that is what I used)
Click to expand...
Click to collapse
Solution to the problem was right click on "Android Phone" that was beside other "Unknown Devices" -> Update Driver Software -> Browse My Computer For Driver Software -> Let Me Pick From A List Of Devices -> (Since the Google SDK platform tools were installed, but not even full SDK, containined generic choices such as adb interface, bootloader interface, hawaii hdb interface etc.) -> Chose Android Bootloader Interface.
Phone now registers as Android Bootloader Interface under "Android Phone" in device manager. Strange since when phone is on it registers in a different category. Also strange, as phone still says "Connect USB Data Cable" as if it isn't connected to the laptop. But just performed "fastboot devices" and it is recognized by the computer for fastboot activities! So good enough for all intents and purposes.
When the phone is on, it appears as a ADB Interface under Universal Serial Bus devices. When the phone is in bootloader mode it appears as Android Bootloader under Android Phone (the new driver). ADB works when the phone is on, but ADB does not work in bootloader mode. Only fastboot works in bootloader mode.

Magnetox said:
Solution to the problem was right click on "Android Phone" that was beside other "Unknown Devices" -> Update Driver Software -> Browse My Computer For Driver Software -> Let Me Pick From A List Of Devices -> (Since the Google SDK platform tools were installed, but not even full SDK, containined generic choices such as adb interface, bootloader interface, hawaii hdb interface etc.) -> Chose Android Bootloader Interface.
Phone now registers as Android Bootloader Interface under "Android Phone" in device manager. Strange since when phone is on it registers in a different category. Also strange, as phone still says "Connect USB Data Cable" as if it isn't connected to the laptop. But just performed "fastboot devices" and it is recognized by the computer for fastboot activities! So good enough for all intents and purposes.
Click to expand...
Click to collapse
yeah, I had to do something similar. I couldnt remember the exact steps. But took me forever to figure it out!
Sorry I wasnt more help my friend.

rodcpierce said:
yeah, I had to do something similar. I couldnt remember the exact steps. But took me forever to figure it out!
Sorry I wasnt more help my friend.
Click to expand...
Click to collapse
No, thank you! Glad the post is here for others now.

Ok. I runned into all of this issues. I finally discovered that after you went into recovery, the device was being installed as a kedacom USB device. So I researched a little and found the solution in the link below.
Short solution:
Right click on "Start Button" and select Device Manager
Find Kedacom, drilldown and right click to update driver
Browser Computer
Let me Pick...
Then Select ADB Driver.
That should fix it.
I hope it helps.
https://www.reddit.com/r/oneplus/comments/59ux5d/cant_root_because_windows_10_keeps_installing/

[GUIDE] Fully Remote Control Your Amazon FireTV / FireTV Stick (No Root Needed!)

So you want to fully remote control your device, You will be able to see the screen of your Amazon device on your computer and you can use your keyboard & Mouse to interact with your device.
I tested this process on the 4K firestick , T95Q Android box and also the Xiaomi Mi Box S.
Steps
Download scrcpy from here You can get the 32bit version from here
Ensure you have ADB debugging enabled on your device
Verify what your current IP address is
Extract the contents of the zip to a folder on your C drive (e.g c:\scrcpy)
Open up a command prompt and navigate to c:\scrcpy
issue the command "adb connect x.x.x.x:5555" (where x.x.x.x is the IP address of your device)
On your Amazon device you will get the ADB prompt. Click Accept to authorize the connection
You can now issue the command "scrcpy" This will start the remote session and you will be able to see the screen of your device on your computer
You can see the step by step video instruction here
IF YOU WANT TO DO THIS FROM THE INTERNET - TRY THIS

Works great! Not sure what I will use it for but it does work great.

brick00444 said:
Works great! Not sure what I will use it for but it does work great.
Click to expand...
Click to collapse
What device did you test it on ?

Intenti0n said:
What device did you test it on ?
Click to expand...
Click to collapse
Fire tv gen 2 box

Works with Fire TV Stick 4K
Nice! I have been trying with Airdroid (needs root) and Teamviewer (needs Google services) and now it is that easy! Works perfectly on a new Fire TV Stick 4K

Nice! Will have to give it a try. Thanks!
Sent from my SM-N950U using Tapatalk

Seem to work but too slow.

I got it. Thanks

Thanks, it is works!! @Intenti0n
Does it exist any client or something like this to use it from an android device instead of a windows computer??
Thanks you very much un advance!

Scrcpy was written by XDA developer @Rom1v hosted on GitHub and available on multiple platforms so why are you linking files from https://www.techdoctoruk.com

adb server version (31) doesn't match this client (41); killing...
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...
getting this error

Works on 1st gen Fire Cube, but video goes in and out and sort of blurry with 32 bit version. Video is stable with x64 version. Great for making remote setting changes.
I do get the following
adb.exe: error: more than one device/emulator
ERROR: "adb reverse" returned with value 1
WARN: 'adb reverse' failed, fallback to 'adb forward'
Is this normal?

Here's the direct link to the Github releases
https://github.com/Genymobile/scrcpy/releases
Get your bits from here.
brentonv said:
Scrcpy was written by XDA developer @Rom1v hosted on GitHub and available on multiple platforms so why are you linking files from https://www.techdoctoruk.com
Click to expand...
Click to collapse

igeekyayush said:
adb server version (31) doesn't match this client (41); killing...
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...
getting this error
Click to expand...
Click to collapse
same

video working or just for remote control it?

Dear my fire tv stick 4k starts n after fire tv logo it goes to blank screen. At fire tv logo the screen resolution in bottom shows to be at 1920x1080 and after it passes logo it goes to 720x480 with blank screen as i told u earlier. Device is at reset position as last time i did a factory reset. Now i am stucked. Plz help. Model is E9L29Y.
Is there any way i can flash stock image? Or any other solution.
{
"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"
}
Sent from my ONEPLUS A6013 using Tapatalk

usmanqadeer said:
Dear my fire tv stick 4k starts n after fire tv logo it goes to blank screen. At fire tv logo the screen resolution in bottom shows to be at 1920x1080 and after it passes logo it goes to 720x480 with blank screen as i told u earlier. Device is at reset position as last time i did a factory reset.
Click to expand...
Click to collapse
You are in the wrong forum. I would suggest resetting it again using the remote control.
"You can use your Stick’s remote to reset it to factory settings. To reset it, press and hold the right and back buttons of your remote at the same time for at least 10 seconds or more. This will initiate the reset process. Follow the on-screen instructions to complete the process"
Click to expand...
Click to collapse

brentonv said:
You are in the wrong forum. I would suggest resetting it again using the remote control.
Click to expand...
Click to collapse
Done this multiple times. And comes to same blank screen after logo.
Sent from my ONEPLUS A6013 using Tapatalk

usmanqadeer said:
Done this multiple times. And comes to same blank screen after logo.
Click to expand...
Click to collapse
You can probably still adb connect via wifi or usb and sort it out. Try some different forums on here. This one maybe of help to you https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459

igeekyayush said:
adb server version (31) doesn't match this client (41); killing...
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...
getting this error
Click to expand...
Click to collapse
Try the latest adb version from https://developer.android.com/studio/releases/platform-tools
Make sure you remove your current adb package.

Disable AC control screen

Hi, I’ve Junson V1 head unit and I was wondering if there is an option to disable the AC control screen that show when I change the temperature?
{
"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"
}

There should be a setting under canbus setup in factory settings.
Use code 8888 or 8878 to enter factory settings.
Should look more or less like on the picture.

I couldn’t find such settings in CAN type options

Maybe you can find it under other. But please enter with code 8878. If you use 8888 you don't get all options.

TorstenH said:
Maybe you can find it under other. But please enter with code 8878. If you use 8888 you don't get all options.
Click to expand...
Click to collapse
Nice, I did not know that 8878 gives more options. However still can’t find the right one for the ac. I’ve disabled AC option one, but it still shows.

This are all the available menus

nstefano said:
This are all the available menusView attachment 5369617
Click to expand...
Click to collapse
You could try to identify the activity which shows the AC interface and the disable it via ADB:
- Install Remote ADB Shell on your Phone from Google PlayStore
- Open WiFi Hotspot on your Phone and connect the HU
- Start Remote ADB Shell and Execute the following command to get SU access:
Code:
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
- Open the AC interface on the head unit and Execute the command to identify the activity:
Code:
dumpsys activity | grep "mCurrentFocus"
Now you should get the Application name (MainUI) and the activity name which should contain something with "AC".
There are a lot of commands available to get the current activity. Another option could be to use
Code:
dumpsys activity recents

Command to disable the activity looks like this whereby the parameter after the slash is the name of the activity:
Code:
pm disable com.ts.MainUI/com.ts.main...

Can’t connect the adb shell
View attachment 5369641

nstefano said:
Can’t connect the adb shellView attachment 5369639View attachment 5369641
Click to expand...
Click to collapse
Tried 128.0.0.1 also

Do I need to do something else on the HU except to be connected on the phone hotspot?

nstefano said:
Tried 128.0.0.1 also
Click to expand...
Click to collapse
Check in the WiFi settings of the head unit which IP it has. There are also Apps in PlayStore to show current IP.
E.g. my phone gives the head unit the IP 192.168.43.155

nstefano said:
Can’t connect the adb shellView attachment 5369639View attachment 5369641
Click to expand...
Click to collapse
127.0.0.1 ist always localhost that means the device itself (and in your case your phone). This is also valid for Windows, Mac and Linux. Just in case you ever need that for another project ;-)

I’ve found it…it was CanACActivity, but since I’ve disabled it, the HU started to responses really bad when I change the temp.

And now if I try to enable it again it says

And here was the log that I used to locate the activity

nstefano said:
And now if I try to enable it again it saysView attachment 5369739
Click to expand...
Click to collapse
You are not root user and overseen the su command with the cryptic signs behind it. If su command was successful the prompt will change from dollar sign to #.

Oh ok, so I’ve to use the first code again in order to get the needed root level

However it is strange why everything freezes when I’ve disabled it and use the ac control. It’s like there are additional settings that I need to change.

nstefano said:
However it is strange why everything freezes when I’ve disabled it and use the ac control. It’s like there are additional settings that I need to change.
Click to expand...
Click to collapse
Disable and then reboot? My hope was mainui just tries to execute but skips because it's not allowed to execute