I want to use eclipse and the sdk to launch apps I am developing on my touch pro 2. I have installed the htc adb drivers, but my phone dosn't show up in adb even though android thinks it is connected. It is definitly some combo of phone/drivers as my friends hero works perfectly.
Any advice?
incase anybody cares, they answered this over on ppcgeeks
forum.ppcgeeks.com/showthread.php?t=116900
quick summary
millmanorama said:
incase anybody cares, they answered this over on ppcgeeks
forum.ppcgeeks.com/showthread.php?t=116900
Click to expand...
Click to collapse
For those just looking for the answer without registering for another forum:
Edit the andboot/conf/eclair.user.conf file to include
Code:
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
in the custom_shells section (at the bottom) so that it looks something like this:
Code:
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
}
Hello guys, I find this thread through Google and xda search. I am using XDAndroid port Froyo 2.2.1 update 1/23 and the method of edit user.conf doesn't work anymore.
This takes me many hours of searching to come to another solution in another thread.
Some may found that installing DroidExplorer may help, as suggested in this post and some posts after.
This takes me an amount of time, so I hope by leaving a note here may help some others when search for this problem.
there are two adb driver version
htc and google, you need to install htc driver
BTW,my adb shell have color control character ,so need to use shell soft to list files
Related
Hi Guys,
I've just followed a guide to rooting my phone as it seems to be the 'in' thing round these parts
Just 1 question is there an easy way to check it's now rooted successfully?
Cheers
Paul
this topic has been answered multiple times in these forums!
but the answer is "adb shell su"
i have searched but not found the info you mention.
Ok i have run that command from windows and it just seems to freeze with
#
If i run this from CommandBot i get
adb: permission denied
so i presume the root didnt work?
If i look in the applications window i now have an option in there now called 'Superuser permissions' - there were 2 entries in here which i pressed on and now they've dissapeared, shouldnt i have done this?
Download terminal editor.
Type "su"
do you have a # now? No? Well you are not root.
Can someone help me by telling me what this command actually does?
Code:
echo 1 > /sys/devices/system/cpu/cpu1/online
A thread has been started elsewhere claiming this enables the "second core" for the Atrix CPU. I know there is no need to "enable." I just want to make sure applying this is not harmful as it's been instructed for people to do this on their phone and then use this to check and make sure it worked:
Code:
cat /proc/cpuinfo
Help would be appreciated as I want to avoid problems caused by misinformation.
Thanks in advance.
Moved to Q&A as not android development
I don't know what these commands are supposed to be doing for you but...
"echo x > filename" is just going to create a file with x in it.
cat filename is just going to display what is in file.
Contact the original poster of that command and ask them for more info.
Thanks, I tried asking him. He essentially just found it somewhere on the net and decided to post it claiming that it 'cured' our 'inactive second core.' I don't think he knows, honestly. He's since stopped posting there. I just didn't want anyone to see it and try it and it do something harmful. Thanks again.
For some reason the upper left part of my touchscreen doesn't work.
I tried the "Touch Screen Recalibrate" apk from gojimi but it didn't help, well not with the corner at least.
I really noticed it while running CM7.1 (which unfortunately was my favorite ROM until this situation occurred) because I could not hit *anything* in that freaking corner , and I am very ocd so it irritated me way too much to be ignored. So i had to change back to Beasty's Froyo Ultimate (in the meantime) until this can be resolved. Correction, if this can be resolved.
If ANYONE has anything that may help please please PLEASE share it
Any help is appreciated
I have had good success with the procedure that starts by using a terminal emulator (like the one from Jack Palevich). From the terminal emulator, you do the following:
1. $ su
2. # touch /sdcard/calibration.ini
3. # /system/bin/TSCalibration
This is discussed in threads like: http://forum.xda-developers.com/showthread.php?t=1098010
Good luck.
Cannot open the file...?
I followed all the steps exactly as stated and this happened:
get devicetype!
get btmac!
can not open the file calibration.ini in emmc !
Except the last line repeated endlessly
poymeister said:
I have had good success with the procedure that starts by using a terminal emulator (like the one from Jack Palevich). From the terminal emulator, you do the following:
1. $ su
2. # touch /sdcard/calibration.ini
3. # /system/bin/TSCalibration
This is discussed in threads like: http://forum.xda-developers.com/showthread.php?t=1098010
Good luck.
Click to expand...
Click to collapse
So I looked at the thread you posted and tried the procedure given for Gingerbread ROMs (because I switched to cm7 again to do this) and it says that calibration.ini is a read only file system.
Heres what i followed:
rajeevvp said:
Ah! you're running one of the Gingerbread-based ROMs. The error message tells you what you need to do:
Code:
$ [B]su[/B]
# [B]touch /emmc/calibration.ini[/B]
# [B]/system/bin/TSCalibration; sleep 5[/B]
Don't type in the prompts ('$' and '#')--they're only there to show you how the screen should look--and don't touch the screen until you get the '#' prompt again. Make sure you have the Superuser app (also free) from Market first for the su command to work.
Remove the calibration.ini file if calibration succeeded:
Code:
$ [B]su[/B]
# [B]rm -f /emmc/calibration.ini[/B]
Click to expand...
Click to collapse
See post #20 of that same thread for a much simpler method.
rajeevvp said:
See post #20 of that same thread for a much simpler method.
Click to expand...
Click to collapse
Thank you SO much! this worked finally *phew*.
Still busted...
I took my gTab a part a few days ago to fix the power connector that had come loose. When I put it back together I did not have any sensitivity on the right side of the screen (when holding it in landscape position). I ran calibration.ini and later tried the TouchRecalibrate app. I finally got it all working again except for the last inch. When holding it in landcape position the last inch from top to bottom on the right has no sensitivity. Is there anything else that I can do to fix it?
Hi I am new to this forum and I hope I posted this in the right place. I am just looking for a place to tell about my findings and maybe helping a person or two with this info.
My g-sensor has been returning false values for ages. Auto rotation, camera, just about any application that used the device's calibration didn't work properly.
It didn't matter what ROM I had installed. It was always off by same amount.
None of those ROMS had calibration options and I couldn't find any calibration tools anywhere.
A couple of days ago I installed CM 10.2 because I found some terminal commands that could calibrate the g-sensor.
In terminal:
Code:
su
echo 1 > /sys/class/input/input4/calibration
Sadly enough that didn't work because there was no calibration file inside the input4 directory (anymore).
So I tried looking for any file with the same name and I found one that worked. I ran the same command for that file while my device was on a flat surface and finally my device worked properly again.
In terminal:
Code:
su
echo 1 > /sys/devices/virtual/sec/gsensorcal/calibration
I think I read somewhere virtual devices were added to android to remove the necessity of calibration because the built-in application messed up a lot of people's sensors. But I could be wrong.
My device: Samsung Galaxy s2 I9100
ROM: CM 10.2 (Android 4.3.1)
This might be old news for some people but I couldn't find any information about it so I made this thread.
Try it at your own risk. Rooted android and root access in terminal are required.
I don't know if it will work with other ROMs but I might as wel share it. sorry for any grammatical mistakes.
Fusixx said:
Hi I am new to this forum and I hope I posted this in the right place. I am just looking for a place to tell about my findings and maybe helping a person or two with this info.
My g-sensor has been returning false values for ages. Auto rotation, camera, just about any application that used the device's calibration didn't work properly.
It didn't matter what ROM I had installed. It was always off by same amount.
None of those ROMS had calibration options and I couldn't find any calibration tools anywhere.
A couple of days ago I installed CM 10.2 because I found some terminal commands that could calibrate the g-sensor.
In terminal:
Code:
su
echo 1 > /sys/class/input/input4/calibration
Sadly enough that didn't work because there was no calibration file inside the input4 directory (anymore).
So I tried looking for any file with the same name and I found one that worked. I ran the same command for that file while my device was on a flat surface and finally my device worked properly again.
In terminal:
Code:
su
echo 1 > /sys/devices/virtual/sec/gsensorcal/calibration
I think I read somewhere virtual devices were added to android to remove the necessity of calibration because the built-in application messed up a lot of people's sensors. But I could be wrong.
My device: Samsung Galaxy s2 I9100
ROM: CM 10.2 (Android 4.3.1)
This might be old news for some people but I couldn't find any information about it so I made this thread.
Try it at your own risk. Rooted android and root access in terminal are required.
I don't know if it will work with other ROMs but I might as wel share it. sorry for any grammatical mistakes.
Click to expand...
Click to collapse
Tried the both command and both of them says terminal emulator "no such as file or bla bla"
Fusixx said:
Code:
su
echo 1 > /sys/devices/virtual/sec/gsensorcal/calibration
Click to expand...
Click to collapse
Thanks for this great hint.
In my case there is not such device file... I have Android 4.4.4 with Cyanogenmod 11 on Sony Xperia Z1. I am now looking thru the complete file system for any file with "sensor" in its names. Maybe I still find a calibration device file to use....
I need to calibrate all my sensors, none is working currently after CM11 update.
(I'm running cuoco92 stable release, so I also posted in that thread. But maybe this section here is a better place for my problem)
Hi there!
Right after charging, the notification area and the "Home" and "Recent" buttons stopped working ("Back" still works). I also can't access the Settings>Users and Developer Options menus ("Developer options are not available for this user").
Most fixes I could find relate to other phones like Motorola and LG, but with the LeEco everything seems a little different. Those guides pretty much all tell the same thing:
1. Try a different user account (doesn't work, because I can't access it anymore) and
2. create an Activity Widget with Nova Launcher pointing to SetupWizard/.SetupWizardTestActivity (or com.google.android.setupwizard/.SetupWizardTestActivity). It also can have slightly different names like TestActivity, SetupExitActivity, or WizardFullActivity.
Problem is: I can't find any of those. There's LeEco Setup Wizard/.EnableSetupWizardActivity but it just says "App isn't installed" when I click on the widget.
Wiping the cache partition and re-installing the ROM also didn't work. I really hope someone can help me with this, because I don't have time for a complete wipe right now...
splicehere said:
(I'm running cuoco92 stable release, so I also posted in that thread. But maybe this section here is a better place for my problem)
Hi there!
Right after charging, the notification area and the "Home" and "Recent" buttons stopped working ("Back" still works). I also can't access the Settings>Users and Developer Options menus ("Developer options are not available for this user").
Most fixes I could find relate to other phones like Motorola and LG, but with the LeEco everything seems a little different. Those guides pretty much all tell the same thing:
1. Try a different user account (doesn't work, because I can't access it anymore) and
2. create an Activity Widget with Nova Launcher pointing to SetupWizard/.SetupWizardTestActivity (or com.google.android.setupwizard/.SetupWizardTestActivity). It also can have slightly different names like TestActivity, SetupExitActivity, or WizardFullActivity.
Problem is: I can't find any of those. There's LeEco Setup Wizard/.EnableSetupWizardActivity but it just says "App isn't installed" when I click on the widget.
Wiping the cache partition and re-installing the ROM also didn't work. I really hope someone can help me with this, because I don't have time for a complete wipe right now...
Click to expand...
Click to collapse
That's odd, the same thing happened to me 2 days ago on RevengeOS. I thought it must be a bug in ROS... Anyway, I was able to get the phone back along the lines you mention above. Through adb:
adb shell am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
Or just launch a terminal app on the phone, type su and then:
am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
mjoach said:
That's odd, the same thing happened to me 2 days ago on RevengeOS. I thought it must be a bug in ROS... Anyway, I was able to get the phone back along the lines you mention above. Through adb:
adb shell am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
Or just launch a terminal app on the phone, type su and then:
am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
Click to expand...
Click to collapse
Thanks for your suggestion!
Unfortunately, it went how I suspected it would. I'm getting:
Error Type 3
Error: Activity class {...} does not exist.So, this Setup Wizard is just not part of the ROM, it seems. There must be something equivalent in it somewhere, but where to find it?
I also tried:
am start -a android.intent.action.MAIN -n com.letv.android.setupwizard/.EnableSetupWizardActivityand got "Error: Activity not started, unknown error code -2".
But i only guessed the package name since I have no idea how to find those names. I only know the folder structure is "/system/priv-app/letvsetupwizard/letvsetupwizard.apk" and it shows up in activities as "LeEco Setup Wizard/.EnableSetupWizardActivity".
The only other thing I could think of is to create a new user via terminal. Is that possible?
But yeah, I'm running out of options. Should've looked into TWRP backups sooner. Was just about done perfectly configuring everything...
So, I got it working again, today!
First, I created a new user with
pm create-user User_Nameand switched to the new user with
am switch-user User_IDand back again to my old user.
(This first step might be unnecessary, can't tell after the fact.)
That action restored seemingly everything but the soft buttons. I then used this command I found after some googling:
settings --user 0 put secure user_setup_complete 1and it restored everything else!
So, maybe this can be of help for someone in the future if everything else fails...