I've some problem with usb debugging using roms based on 2.3.6.
I've using till days ago a rom based on cm7.2 and I've no problems connecting the phone to the pc, then I've installed S'perience rom based on 2.3.6 and after a little while the phone starts to not connecting the mass storage. After plug the usb cable to the phone the screen to select the option of usb storage is there but when when I select the option the status bar display the message that the sd-card is ready but 2 seconds after, the phone disables the option and starts to prepairing the sd-card and the pc don't recognize the mass storage. Even if I go to the development option and thick the "usb debugging" it selects and deselects at same time.
This issue only occur with roms based on 2.3.6 not on rms based on cm7.2. I've tried two roms 2.3.6 and in the middle one cm7.2.
Anyone have an idea why is it happen and how to resolve that?
FrizzerACE said:
I've some problem with usb debugging using roms based on 2.3.6.
I've using till days ago a rom based on cm7.2 and I've no problems connecting the phone to the pc, then I've installed S'perience rom based on 2.3.6 and after a little while the phone starts to not connecting the mass storage. After plug the usb cable to the phone the screen to select the option of usb storage is there but when when I select the option the status bar display the message that the sd-card is ready but 2 seconds after, the phone disables the option and starts to prepairing the sd-card and the pc don't recognize the mass storage. Even if I go to the development option and thick the "usb debugging" it selects and deselects at same time.
This issue only occur with roms based on 2.3.6 not on rms based on cm7.2. I've tried two roms 2.3.6 and in the middle one cm7.2.
Anyone have an idea why is it happen and how to resolve that?
Click to expand...
Click to collapse
Of which phone are you talking about man?
FrizzerACE said:
I've some problem with usb debugging using roms based on 2.3.6.
I've using till days ago a rom based on cm7.2 and I've no problems connecting the phone to the pc, then I've installed S'perience rom based on 2.3.6 and after a little while the phone starts to not connecting the mass storage. After plug the usb cable to the phone the screen to select the option of usb storage is there but when when I select the option the status bar display the message that the sd-card is ready but 2 seconds after, the phone disables the option and starts to prepairing the sd-card and the pc don't recognize the mass storage. Even if I go to the development option and thick the "usb debugging" it selects and deselects at same time.
This issue only occur with roms based on 2.3.6 not on rms based on cm7.2. I've tried two roms 2.3.6 and in the middle one cm7.2.
Anyone have an idea why is it happen and how to resolve that?
Click to expand...
Click to collapse
There is no such rom as S'perience rom or cm7.2 in Ace-i...
Problem with USB debugging with 2.3.6
Hey there,
I cant use my phone as usb debugger when developing any android app.
it says the followings:
Code:
E/dalvikvm(5082): /system/framework/pm.jar odex has stale dependencies
E/dalvikvm(5082): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
D/LibQmg_native(5082): register_android_app_LibQmg
W/dalvikvm(5082): threadid=1: thread exiting with uncaught exception (group=0x40018578)
E/(5082): Dumpstate > /data/log/dumpstate_sys_error
E/AndroidRuntime(5082): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime(5082): java.lang.ClassNotFoundException: com.android.commands.pm.Pm in loader dalvik.system.PathClassLoader[/system/framework/pm.jar]
E/AndroidRuntime(5082): at dalvik.system.PathClassLoader.findClass(PathClassLoader.java:240)
E/AndroidRuntime(5082): at java.lang.ClassLoader.loadClass(ClassLoader.java:551)
E/AndroidRuntime(5082): at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
E/AndroidRuntime(5082): at com.android.internal.os.RuntimeInit.finishInit(Native Method)
E/AndroidRuntime(5082): at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:241)
E/AndroidRuntime(5082): at dalvik.system.NativeStart.main(Native Method)
ROM: MindCR 2.3
limaakum said:
There is no such rom as S'perience rom or cm7.2 in Ace-i...
Click to expand...
Click to collapse
Hi. I've posted here by mistake. But if someone knows anything about this issue it would be great.
Related
Have a small problem created out of thin air. When I connect the phone to the computer with USB debugging mode it says "There might be problems with some files on this device or disc. It can happen if you remove the device or disc before all files have been transferred to the device or disc. Scan and fix(recommended) This will prevent future problems when copying files to this device or disc" and "Continue without scanning". Choosing either seems to make no difference."
Then when I do a search/scan for problems it says "there is nothing wrong to the device. its now ready for use". And then i can enter the sd card. I get this error message everytime i plug in the phone from the bugging mode. But if i connect it with "kies" mode is says nothing and the disc shows on the C drive. I am afraid that this will create problems if i want to transer something important by USB debugging in the future such new ROM or flash something else from the download mode....someone recognizes this problem? (computer Windows 7 64 bit)
As I know, the Kies connection does only work, if usb debugging is off.
Which kernel and rom are you using?
galaxysandstillnofroyo said:
As I know, the Kies connection does only work, if usb debugging is off.
Which kernel and rom are you using?
Click to expand...
Click to collapse
yes but i need usb debugging on if i want to flash , and when i turn the usb debugging on my computer gives me that message..Darkys 9.2 Extreme voodoo 5.4.1
You need to be using touchwiz.. Launcherpro isn't compatible with kies
Hi all,
Please bear with me as I'm a newbie here. I have an O2X with stock rooted V10A rom with modded status bar courtesy of UOT Kitchen (framework-res.apk taken from my stock rom). A month ago I installed an app called rescan media that requires usb debugging mode turned on. Then right after installing the app (with usb debugging mode on), I flashed the modded files from UOT Kitchen.
And now I'm beginning to notice a problem that wasn't there before I installed the app and flashed the customized files. Everytime I connect my phone to my laptop in usb storage mode, my phone reboots. Then after rebooting once, I can connect in usb storage mode without any problem. But later on the rebooting problem will show up again, and I don't know why.
What I've tried so far to get rid of the problem without luck :
1. Uninstalled rescan media and turned off the usb debugging mode;
2. Turned on usb debugging mode;
3. Wiped cache and delvik-cache then re-flashed the modded files from UOT;
4. Moved some apps that I noticed running in the background from SD card to internal memory.
Any suggestion how to fix this? For me stock ROM is good enough for daily use so I'd like to stick with it if possible.
i think you should update your firmware.. dont use v10a.. CMIIW
I'd like to upgrade my f/w but since I don't have unlimited internet access I'll wait til official GB is released. And before I installed rescan media, turned on the usb debugging mode & flashing modded status bar I had no such problem.
hi, when Rocket Rom 7 (ics) came out, i installed it. after doing this, when i connected my phone to the pc, the system detects the phone as Samsung_android and shows 2 removable drives in the system. however, if you click on them they dont work
it no longer detects my phone as GT-N7000
what i have noticed: when i connect the usb cable, the phone doesnt show "MTP connection" anymore... instead, it shows USB connected.
what has been done:
flashed rocket rom 10, nogo
reinstalled kies: nogo
reinstalled win7 (yes i actually did that even tho testing on other pcs showed the same issue)
the phone still charges and the only way i can connect my phone to d pc to view files is by clicking "usb storage"
any advice on this?
Uninstall kies, and just install driver (find latest from toolbox on my signature)
use different USB port, and dont use any extensor cable to connect device.
dr.ketan said:
Uninstall kies, and just install driver (find latest from toolbox on my signature)
use different USB port, and dont use any extensor cable to connect device.
Click to expand...
Click to collapse
hi bro... didnt work... i dont think its the driver... its the phone... coz i tested another note, its working fine
My Galaxy Tab has similar issues. I believe it would be due to the architechture of the ROM forcing you to have to mount your device to your computer before being able to load the Device Internal SD, and the External SD.
Click USB Storage when it shows, this should pop up a window which has a Lil android dude, and USB Storage Message with a button stating 'Turn on USB Storage'. After clicking it, you can click 'Turn Off USB Storage' to unmount the device.
thanx for that.. hehe.. i stumbled across it the other day.. at least i can transfer files... but just dont like the fact its not showing...
Hi,
I haven't been able to identify the problem.
When I try to connect my phone as USB mass storage (Settings -> Other -> USB Tools - "Connect to computer"),
it works fine for 1 minute. Then the phone hangs and restarts itself.
Also when I open camera from the lockscreen, it gets stucked often. I can see the picture but controls do not
show up, I can't do anything and phone restarts itself soon too.
I have tried to wipe the phone, now changed the kernel. Last option would be to go back to GB 2.3.x and test that.
Thanks for any suggestion
GT-I9070P, Android 4.1.2 (I9070PXXLPE), original kernel + now CoCore-EP-8.8
This is getting frustrating now, no matter what I do I get this message: "USB Device Not Recognised"
Here is what I have tried:
Connect on android
Connect as MTP
Different USB cable (5 to be precise)
DIfferent USB port
WebOS recovery
Reinstall Novacom Drivers
Restart PC
Restart Touchpad
I have no idea what else I can try, no matter what I do, this annoying message persists!
Platform? ROM?
What's the ROM you are using? Also, which platform is your PC on? Linux/Windows/Mac?
In case you are on some 5.1.x ROM, I would recommend a nandroid backup and flashing a known 4.4.4 ROM which might tell you if it's your hardware or just Android. If you were on a stable ROM earlier where USB was working, then I would recommend trying that. :fingers-crossed:
Similar Issue.
My TP actually works (sort of) via MTP but it frequently disconnects when transferring files and freezes my explorer window. I tried to use Mass Storage on PAC KitKat FINAL and windows reports that it can't find a driver for it and when I try to reboot into recovery it only mounts a tiny SD Card partition of some 800mb. This probably won't be answered but whatever. I've been trying to solve this issue the past 8 hours. I have nothing to lose.
Blaze Viper said:
My TP actually works (sort of) via MTP but it frequently disconnects when transferring files and freezes my explorer window. I tried to use Mass Storage on PAC KitKat FINAL and windows reports that it can't find a driver for it and when I try to reboot into recovery it only mounts a tiny SD Card partition of some 800mb. This probably won't be answered but whatever. I've been trying to solve this issue the past 8 hours. I have nothing to lose.
Click to expand...
Click to collapse
hi, had some trouble with my win7 PC detecting touchpad (using JC's 4.4 Cm11), although ADB was installed - I couldn't see it as a storage drive despite the driver installing. touchpad was connected via MTP.
what worked for me was on windows - go to Device Installation Settings (drivers) and choose never install from windows update. Then under device manager -> android device -> uninstall. reconnect and it should work properly. hope that helps