For those complained battery drain after update to A12 all version I propose a small tool to solve this issue . So , " Developer options " enabled , " USB debugging " also . Open a adb shell command window and run "optimizer" and let it finish the job . " Optimizer " should be in " C : " Windows folder something like "minimal_adb_fastboot " or " platform-tools_rxxx-windows ' or " tiny adb " . Restart the phone .
I used this tool on OnePlus Nord 2 and Samsung A52s every time after any updates and results are semnificative .
Hello, Thank for this tips, but what are there the command please, how to ?
" For those complained battery drain after update to A12 all version I propose a small tool to solve this issue . So , " Developer options " enabled , " USB debugging " also . Open a adb shell command window and run "optimizer" and let it finish the job . Extract archive " Optimizer " in " C : " Windows folder something like "minimal_adb_fastboot " or " platform-tools_rxxx-windows ' or " tiny adb " ....
Do all that and then click on Optimizer
How do i run this through ADB? Going to give this a try on my 11 Lite 5G NE running PixelOS Android 13 Beta. Same CPU as the Samsung A52 so might possibly work on this phone too.
EDIT: NVM lol didnt see the .bat file within the .rar. Thought i had to execute the rar somehow.
Not important the processor , it works on all android phones . Open a shell windows , enable phone developper option and debugging , then adb devices with connected phone to PC . After your phone is shown on PC , then run Optimizer
Related
Why Adb commands won't start in CMD with my - Vista x64
I just get an notification that Adb.exe (or other like the command > adb shell) is not compatible with Vista x64Bit
I want to install Busybox on my HTC Hero - which is already rooted.
My primary problem is - I want to install Apps on SD - for which one u need AppsToSD. AppsToSD need a rooted HTC with busybox - right ? OR another ROM (JFR)
I don't want to flash another ROM so - I decide to install Busybox on my own - which doesn't work for me - because of the incompatibility of adb with my vista ult x64 ! What now ? How to get Busybox on my Hero in order to dissolve my primary Problem - which is described on the top. Sry for my bad english hope u understand what i'm askin for.
adb is running on my vista x64 ultimate without problems. i have installed the sdk and added the tools folder to the path variable
Hm ... OK !? What I'm doing wrong ? I have downloaded the latest SDK extract to C:/ (in root) - add the PATH in same way ... to the Systemvariable.
Still the same notification
Do I have to download the SDK again - or something else ? What could I do - to get it work
Maybe its a problem with rights??? Vista protects his systemdrive (mostly "c:") drive more then other additional drive for security reasons. I have the SDK installed on my "d:" drive where everyone has full access.
Ok I will try to change to D:/
I will report tomorrow thx
Hi - doh' changed to D:/ ! Effect ... same notification as on C:/
Don't know what to do !? Thought to download the latest SDK again and try same ... BUT do I have to chage the system variables to "default" ?
If so ... HOW ? What is default on Vista Ult. x64 ?
I would never have thought that it would become so difficult. And all that for installing Apps on an SD Card. In my opinion it should have been implemented already like that. Instead, one tries to solve these problems even anyhow.
What would you do ? Pls Help
-------------------------------------------------------------------------------------
I have download the new SDK 1.6 r1 --- and ? DONE ! YAY ! Adb.exe start without any issue.Why ? I don't know --- Can be closed.
Thread can be closed ... tired searching a solution
try
running command prompt in admin priv.
right click the adb.exe and set compatibility to be xp.
Hello: I have this problem with the Kyocera echo M9300 i found this post
**alternate hard reset**
!!!MAKE SURE YOUR ADB IS SET-UP FIRST !!!!
PS - make sure all drivers of the kyocera echo are installed first!!!!
here you go: w w w. echo by kyocera . com / support / downloads /
after all that is done...phone off, hold volume up and power..the kyocera screen will come up, after it does let go of the buttons and PLUG YOUR USB IN COMPUTER AND PHONE, windows will automatically install the drivers and ready to go. open command prompt and search for your adb>tools folder and run <fastboot devices> to make sure the phone is connected...after run <fastboot -w> and this will erase all user data and cache...the <fastboot reboot> and their you go... HARD RESET!!!.
But there is someting i cant get it. <fastboot -w> i do everything i download and install all the drivers from the kyocera web site but when i go to the command promt and type <fastboot -w> it says <Fastboot> not recognized as an internal or external command, program or batch. can some one please tell me how to do a factory reset. for some reason the down and power doesnt work... the other question is where is located the adb>tools folder cuz the only folder i see is in C:\Program Files\Kyocera\KYOCERA USB Modem SY11 there is no more folder i make a file search and nothing cames out. Thanks in advance
ADB is included in the Android SDK, so you need install it first. You'll need to modify some environment variables for convenience, and there are many websites where explain how to install Android SDK (after install it, you'll need to download the platform-tools package, any other isn't needed for your purposes), search them
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
craterib said:
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
Click to expand...
Click to collapse
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
sz_gergo said:
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
Click to expand...
Click to collapse
Code:
[email protected]:/etc/udev/rules.d$ more 51-android.rules
# Sony Ericsson Mobile Communications AB
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="6168", MODE="0600", OWNER="kuisma"
Using this, you don't have to run the adb server as root. Use the "lsusb" to get Vendor and Product id for your device.
Also, change "kuisma" to your user, of course, unless toy happen to be me.
Restart udev (/etc/init.d/udev restart) once you've edited this.
sz_gergo said:
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Click to expand...
Click to collapse
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
bronzext said:
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
Click to expand...
Click to collapse
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
I did not see anybody here mention Knives-And-Forks Tools which is easiest way to Install adb and Fastboot on multiplatform computer. I did it and works like a charm
sz_gergo said:
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
Click to expand...
Click to collapse
hello i have question how to insert vid in hex notation...
digitized007 said:
hello i have question how to insert vid in hex notation...
Click to expand...
Click to collapse
Well therefor you will need an editor. I have used vi , but it is possible to use any editor.
2. step open the file in the editor
3. in a terminal window type " lsusb -v " that will give you the information of all the usb devices
look for the line beginning with idVendor of your device
for me it looks like: " idVendor 0x12d1 Huawei Technologies Co., Ltd."
4. copy the hexcode: 0x12d1 (yours may be another number) into the file
5. save the file
6. restart the server
only that number is needed nothing else
for every device you will get such a code , and each device code should came into a separate line
Hope that helps
br
sz_gergo
Hello,
I've a problem since I changed my Rom : I take the CyanogenMod 10.3 for my Alcatel OT995, it works fine on my device, but I can't use adb command line neither other features using adb.exe ! I can only access to storage mass device, so I think I have a problem with the USB drivers which connect ADB command to my phone.
I can add that before I've installed this Rom on the device, I've installed many drivers on the PC : Firstely I installed the owner's driver provided by Alcatel in the AlcatelAndroidManager.exe package, secondly I installed the Google USB drivers provided because I'm using Android Virtual Devices (AVD Manager) to do some developping works.
I used to launch adb with "adb start-server" so it's still working, I don't obtain any device in the list with "adb devices", why don't I get it ?
I've realized some cleaning actions : I uninstalled the USB drivers of Alcatel's software, I uninstall the Google USB driver , to finish I reboot the PC but it don't changed anything !
Moreover, I tryed to apply this (well explained) post without any success :http://forum.xda-developers.com/google-nexus-5/help/diagnosing-usb-driver-adb-issues-windows-t2514396 ; I see finely in the list, I can't find "Android devices" category, neither "Usb Adb" entry... so my device is not recognized in the "Settings Panel". However the storage mass device appears as a volume named "F:".
Help me please.
The post #4 published by Incubus 26jc saved me at http://forum.xda-developers.com/showthread.php?t=735937
Hi guys..
I ve rooted my quattro by Kingo root methed.
and i installed chainfire 3D, while installing driver it says " IT MAY STOP REBOOTING YOUR DEVICE" but i tried..... :silly:
But now my mobile stopped rebooting... whenever i try to start the logo "samsung galaxy grand quattro" comes and still stands...:crying:
is it died?:silly:
hii
Yabee said:
Hi guys..
I ve rooted my quattro by Kingo root methed.
and i installed chainfire 3D, while installing driver it says " IT MAY STOP REBOOTING YOUR DEVICE" but i tried..... :silly:
But now my mobile stopped rebooting... whenever i try to start the logo "samsung galaxy grand quattro" comes and still stands...:crying:
is it died?:silly:
Click to expand...
Click to collapse
Try flashing it using odin
CHAINFIRE 3D IS NOT TO BE USED ON JELLYBEAN WHY DON'T PEOPLE UNDERSTAND IT IS NOT FOR 4.0+?
Sent from my GT-I8552 using Tapatalk
GOT SOLUTION ( Chainfire 3D softbrick on samsung)
Please follow this instruction carefully
After you follow this:
... Download ADB here: url
...1. extract the file you just download
...2. put it in C: (so you can access it easily)
...3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
...4. open SDK Manager.exe
...5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
Then you follow this:
>reboot your phone in recovery mode (remember, ONLY IN RECOVERY MODE, DONT CONTINUE TO "APPLY UPDATE ADB", JUST STAY IN RECOVERY MODE)
>plug in your devices in USB,
>go to CMD (command prompt)
>type this: "cd c:\Android-adb\sdk\platform-tools" without quotes / quotemarks
>type "adb" without quotes / quotemarks
>type "adb shell" without quotes / quotemarks
>it will automatically type "[email protected]:/ $" so continue it with typing "su" after that, so it will be seen like: "[email protected]:/ $ su"
>it will automatically type for you again, "[email protected]: #" so continue it with typing "system/lib/cf3d_uninstal.sh" after that, so it will be seen like "[email protected]:/ # /system/lib/cf3d_uninstall.sh"
>ignoring all the fail and your device will rebooted and just fine
If you followed the instruction carefully, the CMD will seen like this
htt*p://s29.*postimg.*org/*tgq844hzb/*dev.*png
(delete all the "*"):victory::laugh:
Yabee said:
Please follow this instruction carefully
After you follow this:
... Download ADB here: url
...1. extract the file you just download
...2. put it in C: (so you can access it easily)
...3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
...4. open SDK Manager.exe
...5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
Then you follow this:
>reboot your phone in recovery mode (remember, ONLY IN RECOVERY MODE, DONT CONTINUE TO "APPLY UPDATE ADB", JUST STAY IN RECOVERY MODE)
>plug in your devices in USB,
>go to CMD (command prompt)
>type this: "cd c:\Android-adb\sdk\platform-tools" without quotes / quotemarks
>type "adb" without quotes / quotemarks
>type "adb shell" without quotes / quotemarks
>it will automatically type "[email protected]:/ $" so continue it with typing "su" after that, so it will be seen like: "[email protected]:/ $ su"
>it will automatically type for you again, "[email protected]: #" so continue it with typing "system/lib/cf3d_uninstal.sh" after that, so it will be seen like "[email protected]:/ # /system/lib/cf3d_uninstall.sh"
>ignoring all the fail and your device will rebooted and just fine
If you followed the instruction carefully, the CMD will seen like this
htt*p://s29.*postimg.*org/*tgq844hzb/*dev.*png
(delete all the "*"):victory::laugh:
Click to expand...
Click to collapse
Before you run the uninstall.sh script you may need to remount the /system partition in read/write mode with the following command. On my OneTouch 5020T the /system partition is in read-only mode.
This command will place it in read/write mode:
mount -oremount,rw /system
--Mouse2600