Can't post this in the developer section so I'm asking here. I followed the OP's instructions regarding the nightly installation but when I tried to set the incorporated touch screen driver to use a stylus the command 'ts_srv_set' isn't found when I tried it in the terminal emulator. Has anyone else had this experience ?
you ever get this solved or does the latest CM7/CM9 work for you now?
Related
I have two G1's both running CyanogenMod 4.2.2 I recently configured adb use on my Windows computer but I'm having a strange problem.
On my primary G1 adb works fine and I can access it no problem
however on the second one I can never access it. When I try to do any adb commands the rest is a device not found error
Does anyone have any idea what could be causing this problem on just the one device?
(I apologize if there is an old thread related to this, I couldn't find anything)
Any help would be greatly appreciated
AimanF said:
I have two G1's both running CyanogenMod 4.2.2 I recently configured adb use on my Windows computer but I'm having a strange problem.
On my primary G1 adb works fine and I can access it no problem
however on the second one I can never access it. When I try to do any adb commands the rest is a device not found error
Does anyone have any idea what could be causing this problem on just the one device?
(I apologize if there is an old thread related to this, I couldn't find anything)
Any help would be greatly appreciated
Click to expand...
Click to collapse
Go into Settings->Applications->Development and see if you have USB debugging enabled. Toggle it off and back on.
Good luck
I tried that already but it didn't make any difference :\
You probably have different SPL's on them. If you have SPL 1.33.2005 on the one that's not working, then you need the updated driver.
http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
Or vice-versa
how would I change the driver for that specific device?
Right click on it in the device manager and choose update driver...
It says that the driver is already up to date
So I recently rerooted once I realized that all no root reuired tethering apps block https sites unless you buy the full version. I installed the latest version of cyanogen following the tutorial on the wiki to the T. My phone is fully functional except I can not get the tethering to work. I have uninstalled the remote ndis driver and went through the install wiazrd, directing it to the folder that has the driver and it says something like it hasn't been securely verified or something and I have the option to continue installation or stop and I continue. Then, it says it didn't work and I get a code 10. Troubleshooting did nothing to help me either. Anyone have any idea what I should do? Also, I know there are threads on this but I couldn't find an answer to this issue if there is I'm sorry.
afiellerddr said:
So I recently rerooted once I realized that all no root reuired tethering apps block https sites unless you buy the full version. I installed the latest version of cyanogen following the tutorial on the wiki to the T. My phone is fully functional except I can not get the tethering to work. I have uninstalled the remote ndis driver and went through the install wiazrd, directing it to the folder that has the driver and it says something like it hasn't been securely verified or something and I have the option to continue installation or stop and I continue. Then, it says it didn't work and I get a code 10. Troubleshooting did nothing to help me either. Anyone have any idea what I should do? Also, I know there are threads on this but I couldn't find an answer to this issue if there is I'm sorry.
Click to expand...
Click to collapse
Couldn't find the Cyanogen rom thread to ask this question?
afiellerddr said:
So I recently rerooted once I realized that all no root reuired tethering apps block https sites unless you buy the full version. I installed the latest version of cyanogen following the tutorial on the wiki to the T. My phone is fully functional except I can not get the tethering to work. I have uninstalled the remote ndis driver and went through the install wiazrd, directing it to the folder that has the driver and it says something like it hasn't been securely verified or something and I have the option to continue installation or stop and I continue. Then, it says it didn't work and I get a code 10. Troubleshooting did nothing to help me either. Anyone have any idea what I should do? Also, I know there are threads on this but I couldn't find an answer to this issue if there is I'm sorry.
Click to expand...
Click to collapse
You might have to enable it in the app drawer or in settings somewhere. I ran into a rom once that had the enabler in the app drawer.
bkmo said:
Couldn't find the Cyanogen rom thread to ask this question?
Click to expand...
Click to collapse
I found other threads, but none of the solutions such as unistalling and reinstalling the driver were working. I'm searching for other solutions
couldnt you atleast ask a QUESTION in the QUESTIONs and answers section?
did u try ticking the wired tether box in setting? (not to insult your intelligence, but i got asked about this via the cmupdater support address a while ago... and it turned out that the person hadnt even enabled it)
Moved as not Android Development.
Yes I made sure the little box was checked for usb tethering but I understand the necessity of the question lol.
And sorry stylez (moderator) I assumed since it was about cyanogen roms it would go under development. Looking back, Q & A makes more sense.
This thought just occured. Considering that unistalling and reinstalling the driver didn't work, could it be that I just have an outdated driver for this rom? I unrooted about 2 months ago so the driver might have changed from then. If so, does someone have a link to download the latest version?
Thank you all for your help.
xp, vista or 7?
7 is likely broken somehow
as are xp and vista coz MS made them....but anyway....
are u restarting between uninstalling and reinstalling?
I have xp. And it worked when I first had a cyanogen rom
And I tried restartingbetween uninstall and reinstall with no success
hello everyone,
I just installed CM9 Kang 3, but I can't use my phone as a developing device any more... debug USB is of course activated and drivers are ok... but I can't see my phone in the list of attached device while I used it with CM7 Nighlty 225...
any guess about how to solve the problem?
Can't make the ADB WiFi work either
Thanks for help!
Tiwiz
so you cant see your device on your pc?
had this problem once as well, try to reflash cm9 (+wipe)
dont know if theres another possible way to fix it but that worked for me
3 wipes?
I just installed all my apps LOL Well, I found adbWireless on the market and it's working, so I'll just wait for it to fix itself!
Tiwiz
Hi all, I flashed a stock rom, namely Flix123's V1.1 of V20S Gingerbread Update. However, the despite following the instructions in the thread, and looking through the posts, I could not find an answer to my problem.
The problem I encountered was:
1. Home button not functioning
2. No lockscreen
I've looked through other threads pertaining to this problem, but none of their solutions worked. Although I can just use another stock rom, I'd like to know the cause of the problem.
Please do advise or redirect me if there is a problem with this thread (I originally wanted to post a reply in his thread but I do not have permissions to do so at the moment).
You need to complete the configuration wizard that shows up at the first boot, don't press "exit".
TrymHansen said:
You need to complete the configuration wizard that shows up at the first boot, don't press "exit".
Click to expand...
Click to collapse
EDIT: Turns out that play button does not open a video...I must have mixed that up with another phone. Thanks for your advice, TrymHansen!
I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing.
I downloaded the latest google drivers here:
https://developer.android.com/studio/run/win-usb.html
I changed the USB mode from charging to file transfer (not sure if that matters but one of the threads said this helped discover the ADB device needs, which was the case for me)
When I look at the device manager, I see this:
http://pasteboard.co/5UkUolhM2.png
I actually thought I was going to see this (based on a few user posts I read) but no luck . . .
http://pasteboard.co/5Uo9QvP8z.png
I hate asking such a basic question (I'm trying to root my phone but I'm already stuck at the backup stage . . . heh) but I've honestly tried to look through the threads and resolve it but I haven't found a solution yet. It doesn't mean one doesn't exist (I apologize if one does, I honestly have tried to solve this myself).
I apologize for the links rather than pics but it doesn't seem to want to let me use the IMG tags (do they not work with *.png?).
Any help you can give me would be greatly appreciated. Thanks!
I have a somewhat similar problem. Which I can attribute to some sort of driver/inf screw up
Any device i connect to my Win 10 PC in MTP mode gets recognized in device manager as MTP device and I can't do anything about it.
Unless I go back to driver setting, have it automatically find updated drivers, which it doesn't.
But then right after, if i go to manually select driver and switch it from MTP to MTP USB - it fixes everything
Any idea how to fix that. I'm sure it's a similar issue to this.
I couldn't use the Google drivers, I had to use the OnePlus Driver package.
Beside, did you guys enable USB debugging?
Cheers
Tom
if device manager is showing any unknown devices then start with that when you can plug in the phone without problems have a look at this.
https://forum.xda-developers.com/showthread.php?t=2317790
Which adb version do you use?
Sent from my ONEPLUS A3003 using Tapatalk
I've actually tried installing those drivers (on the partition), the google drivers, a fastboot and ADB program, and even an all in one tool for drivers and none of them worked.
That said, I might have found my problem. I've tried several approaches and found out the the virus protection on this computer (Cylance) is blocking everything. Also explains some issues I had getting things to work with some home automation projects . . . I'll have to find another computer for development.
I'll give you guys an update once I have one. Thanks for the quick replies.
I wanted to follow up on this since I got it up and working just fine.
First off, thanks to everyone that helped, either those that provided answers, or those that confirmed they were seeing the same issues.
It does appear that cylance (my antivirus) was blocking a number of things. I have a different laptop with a fresh version of windows 10 (not a requirement, just making note of this) and protected by bit defender and set it up with that. This is what I did:
1) Plug phone into computer
2) Went to pulldown menu, clicked on "charging mode" and changed it to "transfer files"
3) A partition was found on my computer called "Oneplus Drivers" (on the my computer page, next to the C drive). I double clicked on the directory and it installed the drivers to my computer
4) I downloaded and installed Minimal ADB with fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790. (You'll need to click a few links to get to the actual download but I wanted everyone to know that it's a legitimate link and not just my own personal/questionable source)
5) I ran minimal adb and typed "adb devices". It will show your device as "unauthorized" initially because it hasn't been accepted on your device. Open your device and click allow or ok or something to that effect (didn't think to take a screenshot). Your call if you want it to always remember that device.
6) Type "adb devices" again and it should show your device labeled "device"
So yeah, that's how I got the basic ADB up and working. Hopefully you guys resolve this as well. Good luck!
I was too having the same issue but solved using this easy method https://youtu.be/LbAq6d2Du0U
jbrookley said:
I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing. ...
Click to expand...
Click to collapse
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/
hello2010 said:
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/
Click to expand...
Click to collapse
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?
jbrookley said:
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?
Click to expand...
Click to collapse
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.
hello2010 said:
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.
Click to expand...
Click to collapse
Oh, ok! All caught up!
Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.
j03x2 said:
Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.
Click to expand...
Click to collapse
Have you tried any of the solutions that were posted?
Didgeridoohan said:
Have you tried any of the solutions that were posted?
Click to expand...
Click to collapse
Problem solved now. For some reason the USB Debugging flag changed without me doing it.