I am using miuimix 12.5.4
I can't find miui optimization
I tried reset to default value but it didn't work
Connect device to computer with adb and USB debug enabled
adb shell
setprop persist.sys.miui_optimization false
Related
At my university, the lab computers are locked down and won't allow the installation of Android's USB drivers. This prevents adb from connecting to the ADP1 via USB, but I can use another computer which does have USB permissions and use
Code:
adb tcpip 2222
to restart adbd in TCP listen mode on port 2222. Then, on a lab computer I can connect to the ADP1 using
Code:
adb connect <IP>:2222
and install packages, open a shell, etc.
My question is, how can adbd be preconfigured on the ADP1 to listen on a specified port on boot, instead of waiting for a USB connection and the above two commands?
This is "insecure" but it doesn't matter because the lab computers and wireless network are private, and the ADP1 has no SIM card and connects to the internet only via WiFi.
It seems that one way to do this involves editing the boot image to modify init.rc --- I'm prepared to do that, but I'm hesitant to spend the time trying it because I can't find any documentation saying what port adbd will listen on by default, or if it will listen on TCP at all.
tl;dr: Instructions on how to start adbd on boot in TCP listen mode? Thanks.
Did you find any answer to this? anybody knows how to enable it directly on phone without usb cable?
http://nookdevs.com/ADB_Over_USB
"By default, you won't be able to use adb over wifi, using this module/adbd. But if you set the persist.adb.tcp.port system property setprop persist.adb.tcp.port 5555 it will cause adbd to listen on the specified port so you can use adb over both usb and wifi. Note that adb over wifi is insecure and not recommended. Anyone on the same local network could potentially connect to your nook."
Maybe this will help you?
Not working
Gerdal said:
http://nookdevs.com/ADB_Over_USB
"By default, you won't be able to use adb over wifi, using this module/adbd. But if you set the persist.adb.tcp.port system property setprop persist.adb.tcp.port 5555 it will cause adbd to listen on the specified port so you can use adb over both usb and wifi. Note that adb over wifi is insecure and not recommended. Anyone on the same local network could potentially connect to your nook."
Maybe this will help you?
Click to expand...
Click to collapse
Thanks, but it didnt work. I tried the command in su mode, even restarted the adb service with stop/start command, no error but still can't connect to device over wifi. I can ping the device, so the connection is there. Any idea?
Solved
I finally solved the problem. these are the commands to enable adb over wifi:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
and to disable it:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
I assume you need su access to run it. I tested it and its working.
bohlool said:
I finally solved the problem. these are the commands to enable adb over wifi:
setprop service.adb.tcp.port 5555
[/CODE]
setprop has sucefully executed - no problem
how to restart this service ?
stop/start shows bad command or filename - which means command not found what is true since there is no shell command named start or stop
Click to expand...
Click to collapse
Worked for me
m32 said:
bohlool said:
I finally solved the problem. these are the commands to enable adb over wifi:
setprop service.adb.tcp.port 5555
[/CODE]
setprop has sucefully executed - no problem
how to restart this service ?
stop/start shows bad command or filename - which means command not found what is true since there is no shell command named start or stop
Click to expand...
Click to collapse
It worked for me. you can use my Widget to do it and see if it work or not, search market for "ADB over Wifi"
Click to expand...
Click to collapse
Hy!
I found my way of doing the same thing...
You have to enable dropbear ssh server on your device, and then you can forward the port 5037 (where adb listens by default on localhost only) to your computer trough ssh from your computer.
From your linux box, you can do this with this command:
ssh [email protected] -L 5555:localhost:5037
and then (but keep the ssh session open):
adb connect localhost
that's it
(note that you have to enable usb debugging for this to work!)
u-foka said:
Hy!
I found my way of doing the same thing...
You have to enable dropbear ssh server on your device, and then you can forward the port 5037 (where adb listens by default on localhost only) to your computer trough ssh from your computer.
From your linux box, you can do this with this command:
ssh [email protected] -L 5555:localhost:5037
and then (but keep the ssh session open):
adb connect localhost
that's it
(note that you have to enable usb debugging for this to work!)
Click to expand...
Click to collapse
that's pretty convenient. thanks.
Thanks and this works for me!!!
bohlool said:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Click to expand...
Click to collapse
hi
i am trying to use cdma in lag nexus 5. i am rooted & flashed dev mode. now device is connected. device manager show it android android devices next to android adb interface.
now when i type adb shell it changes to $
then when type su it chages to #.
but whhen type setprop sys.usb.config diag,adb the command again shows the same command setprop sys.usb.config diag,adb reposted but nexus 5 doesnt show in device manager. i also dont see in com/port any new .
so how do i correct it. i need to connect come to change to spc & misc....
I am wondering around the internet to learn any method to disable MTP/PTP/all usb stuff except charging.
So, why i want this?
Because i want my device to be secure.
I don't anyone to sneak around and try to go into bootloader or recovery/connection to a pc etc to set my device to make a fresh start/copying data and end my privacy up.
So is there a way to disable those functions?
And if it is possible then what? Will it be secured?
And the big question is that can i enable it through recovery (from adb or moving mobile files) as you know if one has a messed up rom then he/she should have those functions workable.
I have Galaxy S3 Neo GT-I9301I
With stock rom (rooted)
I found this on a web:
.
The most device-compatible way to disable everything is to run this command at startup or set this in your build.prop:
Code:
setprop persist.sys.usb.config none
which is equivalent to charge-only on all Android devices.
That also disables adb. If you use adb regularly, then:
Code:
setprop persist.sys.usb.config adb
will allow adb when developer options are turned on/checked. If you don't use ADB often, I would not recommend it, because setting adb causes my S5 to still recognize in device manager, even when it is locked.
To restore original functionality,
Code:
setprop persist.sys.usb.config mtp,ptp,adb
allows all USB protocols.
Hi,
I need to use Pixel 3 with QXDM to debug some LAA issues. But I cannot connect Pixel 3 with QXDM. Probably it requires to enter to diagnostic mode on Pixel but I have no idea how to do it. Probably userdebug ROM is required, but I cannot find any info about it on Pixel 3.
Has anyone tried to use Pixel 3 with QXDM?
Cibor said:
Hi,
I need to use Pixel 3 with QXDM to debug some LAA issues. But I cannot connect Pixel 3 with QXDM. Probably it requires to enter to diagnostic mode on Pixel but I have no idea how to do it. Probably userdebug ROM is required, but I cannot find any info about it on Pixel 3.
Has anyone tried to use Pixel 3 with QXDM?
Click to expand...
Click to collapse
This will only work if the ramdisk has the appropriate configs:
su
setprop sys.usb.config diag,adb
to revert:
setprop sys.usb.config mtp
The 3xl and 3 can also enter edl (emergency download mode) by issuing:
adb reboot edl (exit by hardware buttons)
AnierinB said:
This will only work if the ramdisk has the appropriate configs:
su
setprop sys.usb.config diag,adb
to revert:
setprop sys.usb.config mtp
The 3xl and 3 can also enter edl (emergency download mode) by issuing:
adb reboot edl (exit by hardware buttons)
Click to expand...
Click to collapse
Are the ramdisk configs done at kernel level?
Cibor said:
Hi,
I need to use Pixel 3 with QXDM to debug some LAA issues. But I cannot connect Pixel 3 with QXDM. Probably it requires to enter to diagnostic mode on Pixel but I have no idea how to do it. Probably userdebug ROM is required, but I cannot find any info about it on Pixel 3.
Has anyone tried to use Pixel 3 with QXDM?
Click to expand...
Click to collapse
Usually on pixel 2 I had to flash a debug vendor image , which are available from Google site. Make sure adb is setup properly and issue commands given by Friday response.
I was looking to enable WiFi calling but this phones files are really.locked down:-/
i enabled developer option then i changed the dpi from 392 to 900 just to see what happen but after that phone screen turned black
nothring is showing up then i long pressed the power key to reboot my device then that screen appear but the icons are very small .i cant access my smatrphone to adjust the dpi back to normal
please help
thanks
If phone's Android is rooted & can get accessed by means of ADB then you can reset display's DPI :
Example code:
Code:
adb devices
adb shell "su -c 'wm density reset'"
adb reboot
jwoegerbauer said:
If phone's Android is rooted & can get accessed by means of ADB then you can reset display's DPI :
Example code:
Code:
adb devices
adb shell "su -c 'wm density reset'"
adb reboot
Click to expand...
Click to collapse
thank you but my device is not rooted or usb debugging is not enable so cant do that. do you know any other solution to enable usb debugging or rooting
prathmesh23 said:
thank you but my device is not rooted or usb debugging is not enable so cant do that. do you know any other solution to enable usb debugging or rooting
Click to expand...
Click to collapse
NO
what did you do? I have the same problem except my phone isn't rebooting
you need twrp